IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Passive DNS - Common Output Format (draft-dulaunoy-dnsop-passive-dns-cof)
By Alexandre Dulaunoy, Aaron Kaplan, Paul Vixie, Henry Stern, 2018-06-21 TXT HTML PDF
Abstract: This document describes a common output format of Passive DNS Servers which clients can query. The output format description includes also in addition a common semantic for each Passive DNS system. By having multiple Passive DNS Systems adhere to the same output format for queries, users of multiple Passive DNS servers will be able to combine result sets easily.
- Proposed Structure of the IETF Administrative Support Activity (IASA), Version 2.0 (for Discussion) (draft-ietf-iasa2-struct)
By Brian Haberman, Joseph Hall, Jason Livingood, 2018-06-21 TXT HTML PDF
Abstract: The IETF Administrative Support Activity (IASA) was originally established in 2005. In the 13 years from 2005 to 2018, the needs of the IETF have evolved in ways that require changes to its administrative structure. The purpose of this document is to outline a proposed new "IASA 2.0" structure. The proposal is for the work of the IETF's administrative and fundraising tasks to be conducted by a new administrative organization, the IETF Administration Limited Liability Corporation ("LLC"). Under the proposal, the Internet Administrative Oversight Committee (IAOC) will be eliminated, and its oversight and advising functions transferred to the new LLC Board.
- Test Cases for Evaluating RMCAT Proposals (draft-ietf-rmcat-eval-test)
By Zaheduzzaman Sarker, Varun Singh, Xiaoqing Zhu, Michael Ramalho, 2018-06-21 TXT HTML PDF
Abstract: The Real-time Transport Protocol (RTP) is used to transmit media in multimedia telephony applications, these applications are typically required to implement congestion control. This document describes the test cases to be used in the performance evaluation of such congestion control algorithms.
- Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) extension for recording TE Metric of a Label Switched Path (draft-ietf-teas-te-metric-recording)
By George Swallow, Clarence Filsfils, Kenji Kumaki, Ruediger Kunze, 2018-06-21 TXT HTML PDF
Abstract: There are many scenarios in which Traffic Engineering (TE) metrics such as cost, delay and delay variation associated with the TE link formed by Label Switched Path (LSP) are not available to the ingress and egress nodes. This draft provides extensions for the Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) to support automatic collection of cost, delay and delay variation information for the TE link formed by a LSP.
- Disabling PAWS When Other Protections Are Available (draft-nishida-tcpm-disabling-paws)
By Yoshifumi Nishida, 2018-06-20 TXT HTML PDF
Abstract: PAWS provides protection against old duplicated segments caused by wrapped sequence or earlier incarnated connections. One drawback of PAWS is that it requires to place timestamp option in all segments, which consumes 10-12 bytes in the option space of TCP. In addition, since PAWS just checks if timestamps is older or not, the protection logic is not very strong against malicious attacks or cannot work properly in some situations. On the other hand, some other technologies which can provide stronger protections than PAWS are becoming available these days. In this document, we propose to utilize other protection mechanisms as replacements of PAWS when they are available.
Updated Drafts
- IANA Registration of Trustword Lists: Guide, Template and IANA Considerations (draft-birk-pep-trustwords)
By Volker Birk, Hernani Marques, Bernie Hoeneisen, 2018-06-21 TXT HTML PDF
Abstract: This document specifies the IANA Registration Guidelines for Trustwords, describes corresponding registration procedures, and provides a guideline for creating Trustword list specifications.
- Extension for Stateful PCE to allow Optional Processing of PCEP Objects. (draft-dhody-pce-stateful-pce-optional)
By Dhruv Dhody, Stephane Litkowski, 2018-06-20 TXT HTML PDF
Abstract: This document introduces a mechanism to mark some Path Computation Element (PCE) Communication Protocol (PCEP) objects as optional during PCEP messages exchange for the Stateful PCE model to allow relaxing some constraints.
- PCEP Extension for Distribution of Link-State and TE Information. (draft-dhodylee-pce-pcep-ls)
By Dhruv Dhody, Young Lee, Daniele Ceccarelli, 2018-06-21 TXT HTML PDF
Abstract: In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally this TED has been obtained from a link state (LS) routing protocol supporting traffic engineering extensions.
- 6TiSCH Operation Sublayer Protocol (6P) (draft-ietf-6tisch-6top-protocol)
By Qin Wang, Xavier Vilajosana, Thomas Watteyne, 2018-06-20 TXT HTML PDF
Abstract: This document defines the IPv6 over the TSCH mode of IEEE 802.15.4e (6TiSCH) Operation Sublayer (6top) Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes to add/delete TSCH cells to one another. 6P is part of the 6TiSCH Operation Sublayer (6top), the next higher layer to the IEEE Std 802.15.4 TSCH medium access control layer. The 6top layer terminates the 6top Protocol defined in this document, and runs one or more 6top Scheduling Function(s). A 6top Scheduling Function (SF) decides when to add/delete cells, and triggers 6P Transactions. This document lists the requirements for an SF, but leaves the definition of SFs out of scope.
- EST over secure CoAP (EST-coaps) (draft-ietf-ace-coap-est)
By Peter Van der Stok, Panos Kampanakis, Sandeep Kumar, Michael Richardson, Martin Furuhed, Shahid Raza, 2018-06-21 TXT HTML PDF
Abstract: Enrollment over Secure Transport (EST) is used as a certificate provisioning protocol over HTTPS. Low-resource devices often use the lightweight Constrained Application Protocol (CoAP) for message exchanges. This document defines how to transport EST payloads over secure CoAP (EST-coaps), which allows low-resource constrained devices to use existing EST functionality for provisioning certificates.
- CAA Record Extensions for Account URI and ACME Method Binding (draft-ietf-acme-caa)
By Hugo Landau, 2018-06-21 TXT HTML PDF
Abstract: The CAA DNS record allows a domain to communicate issuance policy to CAs, but only allows a domain to define policy with CA-level granularity. However, the CAA specification also provides facilities for extension to admit more granular, CA-specific policy. This specification defines two such parameters, one allowing specific accounts of a CA to be identified by URI and one allowing specific methods of domain control validation as defined by the ACME protocol to be required.
- YANG Data Model for Bidirectional Forwarding Detection (BFD) (draft-ietf-bfd-yang)
By Reshad Rahman, Lianshu Zheng, Mahesh Jethanandani, Juniper Networks, Gregory Mirsky, 2018-06-21 TXT HTML PDF
Abstract: This document defines a YANG data model that can be used to configure and manage Bidirectional Forwarding Detection (BFD).
- PIM Signaling Through BIER Core (draft-ietf-bier-pim-signaling)
By Hooman Bidgoli, Andrew Dolganow, Jayant Kotalwar, Fengman Xu, mankamana mishra, Zhaohui Zhang, 2018-06-21 TXT HTML PDF
Abstract: Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. Neither does BIER require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. Such header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the according set of bits switched on in BIER packet header.
- A Yang Data Model for L1 Connectivity Service Model (L1CSM) (draft-ietf-ccamp-l1csm-yang)
By Giuseppe Fioccola, Kwang-koog Lee, Young Lee, Dhruv Dhody, Daniele Ceccarelli, 2018-06-21 TXT HTML PDF
Abstract: This document provides a YANG data model for Layer 1 Connectivity Service Model (L1CSM).
- A new cryptographic signature method for DKIM (draft-ietf-dcrup-dkim-crypto)
By John Levine, 2018-06-21 TXT HTML PDF
Abstract: This document adds a new signing algorithm,ed25519-sha256, to DKIM [RFC6376]. DKIM verifiers are required to implement this algorithm.
- Segment Routing Prefix SID extensions for BGP (draft-ietf-idr-bgp-prefix-sid)
By Stefano Previdi, Clarence Filsfils, Acee Lindem, Arjun Sreekantiah, Hannes Gredler, 2018-06-21 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. A segment can represent any instruction, topological or service-based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SID). Each SID represents a topological or a service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An SR domain is defined as a single administrative domain for global SID assignment.
- Dissemination of Flow Specification Rules (draft-ietf-idr-rfc5575bis)
By Susan Hares, Christoph Loibl, Robert Raszuk, Danny McPherson, Martin Bacher, 2018-06-21 TXT HTML PDF
Abstract: This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute traffic Flow Specifications. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix.
- Secure/Multipurpose Internet Mail Extensions (S/ MIME) Version 4.0 Certificate Handling (draft-ietf-lamps-rfc5750-bis)
By Jim Schaad, Blake Ramsdell, Sean Turner, 2018-06-21 TXT HTML PDF
Abstract: This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) v4.0 agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 5280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 5280. This document obsoletes RFC 5750.
- Information Model for Abstraction and Control of TE Networks (ACTN) (draft-ietf-teas-actn-info-model)
By Young Lee, Sergio Belotti, Dhruv Dhody, Daniele Ceccarelli, Bin-Yeong Yoon, 2018-06-21 TXT HTML PDF
Abstract: This draft provides an information model for Abstraction and Control of Traffic Engineered Networks (ACTN).
- A Yang Data Model for ACTN VN Operation (draft-ietf-teas-actn-vn-yang)
By Young Lee, Dhruv Dhody, Daniele Ceccarelli, Igor Bryskin, Bin-Yeong Yoon, Qin Wu, Peter Park, 2018-06-21 TXT HTML PDF
Abstract: This document provides a YANG data model for the Abstraction and Control of Traffic Engineered (TE) networks (ACTN) Virtual Network Service (VNS) operation.
- BGP FlowSpec Payload Matching (draft-khare-idr-bgp-flowspec-payload-match)
By Anurag Khare, John Scudder, Luay Jalil, 2018-06-21 TXT HTML PDF
Abstract: The rise in frequency, volume, and pernicious effects of DDoS attacks has elevated them from fare for the specialist to generalist press. Numerous reports detail the taxonomy of DDoS types, the varying motivations of their attackers, as well as the resulting business and reputation loss of their targets.
- Traffic Engineering and Service Mapping Yang Model (draft-lee-teas-te-service-mapping-yang)
By Young Lee, Dhruv Dhody, Daniele Ceccarelli, Jeff Tantsura, Giuseppe Fioccola, Qin Wu, 2018-06-21 TXT HTML PDF
Abstract: This document provides a YANG data model to map service model (e.g., L3SM) and Traffic Engineering model (e.g., TE Tunnel or ACTN VN model). This model is referred to as TE service Mapping Model. This model is applicable to the operation's need for a seamless control and management of their VPN services with TE tunnel support.
- PCEP Extensions for Establishing Relationships Between Sets of LSPs and Virtual Networks (draft-leedhody-pce-vn-association)
By Young Lee, Dhruv Dhody, Xian Zhang, Daniele Ceccarelli, 2018-06-20 TXT HTML PDF
Abstract: This document describes how to extend Path Computation Element (PCE) Communication Protocol (PCEP) association mechanism introduced by the PCEP Association Group specification, to further associate sets of LSPs with a higher-level structure such as a virtual network (VN) requested by clients or applications. This extended association mechanism can be used to facilitate virtual network control using PCE architecture.
- PCEP Extensions for Segment Routing leveraging the IPv6 data plane (draft-negi-pce-segment-routing-ipv6)
By Mahendra Negi, Prejeeth Kaladharan, Dhruv Dhody, Siva Sivabalan, 2018-06-20 TXT HTML PDF
Abstract: The Source Packet Routing in Networking (SPRING) architecture describes how Segment Routing (SR) can be used to steer packets through an IPv6 or MPLS network using the source routing paradigm. Segment Routing (SR) enables any head-end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE).
- Service Function Chaining: Subscriber and Service Identification Use Cases and Variable-Length NSH Context Headers (draft-sarikaya-sfc-hostid-serviceheader)
By Behcet Sarikaya, Mohamed Boucadair, Dirk Hugo, 2018-06-21 TXT HTML PDF
Abstract: This document discusses how to inform Service Functions about service- and subscriber-related information for the sake of policy enforcement and appropriate SFC-inferred forwarding. Once the information is consumed by SFC-aware elements of an SFC-enabled domain, it is stripped from packets when they leave the SFC-enabled domain. Thus privacy-sensitive information is not leaked outside the domain.
- Make-Before-Break MPLS-TE LSP restoration and reoptimization procedure using Stateful PCE (draft-tanaka-pce-stateful-pce-mbb)
By Yosuke Tanaka, Yuji Kamite, Dhruv Dhody, Ramanjaneya Palleti, 2018-06-20 TXT HTML PDF
Abstract: Stateful Path Computation Element (PCE) and its corresponding protocol extensions provide a mechanism that enables PCE to do stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP). Stateful PCE supports manipulating of the existing LSP's state and attributes (e.g., bandwidth and path) via delegation and also instantiation of new LSPs in the network via PCE Initiation procedures.
- Well-Known Community Policy Behavior (draft-ymbk-grow-wkc-behavior)
By Jay Borkenhagen, Randy Bush, Ron Bonica, Serpil Bayraktar, 2018-06-21 TXT HTML PDF
Abstract: Well-Known BGP Communities are manipulated inconsistently by current implementations. This results in difficulties for operators. It is recommended that removal policies be applied consistently to Well- Known Communities.
Expired Drafts
|
Drafts Sent to IESG
- IMAP Extension for object identifiers (draft-ietf-extra-imap-objectid): Active » Publication Requested
By Bron Gondwana, 2018-05-28 TXT HTML PDF
Abstract: This document updates RFC3501 (IMAP4rev1) with persistent identifiers on mailboxes and messages to allow clients to more efficiently re-use cached data when resources have changed location on the server.
IESG Progress
- 6TiSCH Operation Sublayer Protocol (6P) (draft-ietf-6tisch-6top-protocol): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Qin Wang, Xavier Vilajosana, Thomas Watteyne, 2018-06-20 TXT HTML PDF
Abstract: This document defines the IPv6 over the TSCH mode of IEEE 802.15.4e (6TiSCH) Operation Sublayer (6top) Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes to add/delete TSCH cells to one another. 6P is part of the 6TiSCH Operation Sublayer (6top), the next higher layer to the IEEE Std 802.15.4 TSCH medium access control layer. The 6top layer terminates the 6top Protocol defined in this document, and runs one or more 6top Scheduling Function(s). A 6top Scheduling Function (SF) decides when to add/delete cells, and triggers 6P Transactions. This document lists the requirements for an SF, but leaves the definition of SFs out of scope.
- A new cryptographic signature method for DKIM (draft-ietf-dcrup-dkim-crypto): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By John Levine, 2018-06-21 TXT HTML PDF
Abstract: This document adds a new signing algorithm,ed25519-sha256, to DKIM [RFC6376]. DKIM verifiers are required to implement this algorithm.
- Padding Policy for EDNS(0) (draft-ietf-dprive-padding-policy): IESG Evaluation » ::Revised I-D Needed
By Alexander Mayrhofer, 2018-04-13 TXT HTML PDF
Abstract: RFC 7830 specifies the EDNS(0) 'Padding' option, but does not specify the actual padding length for specific applications. This memo lists the possible options ("Padding Policies"), discusses implications of each of these options, and provides a recommended (experimental) option.
- Segment Routing Prefix SID extensions for BGP (draft-ietf-idr-bgp-prefix-sid): IESG Evaluation » ::AD Followup
By Stefano Previdi, Clarence Filsfils, Acee Lindem, Arjun Sreekantiah, Hannes Gredler, 2018-06-21 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. A segment can represent any instruction, topological or service-based. The ingress node prepends an SR header to a packet containing a set of segment identifiers (SID). Each SID represents a topological or a service-based instruction. Per-flow state is maintained only on the ingress node of the SR domain. An SR domain is defined as a single administrative domain for global SID assignment.
- IPv6, IPv4 and Coexistence Updates for IPPM's Active Metric Framework (draft-ietf-ippm-2330-ipv6): IESG Evaluation » ::Revised I-D Needed
By Al Morton, Joachim Fabini, Nalini Elkins, mackermann@bcbsm.com, Vinayak Hegde, 2018-05-24 TXT HTML PDF
Abstract: This memo updates the IP Performance Metrics (IPPM) Framework RFC 2330 with new considerations for measurement methodology and testing. It updates the definition of standard-formed packets in RFC 2330 to include IPv6 packets, deprecates the definition of minimum standard- formed packet, and augments distinguishing aspects of packets, referred to as Type-P for test packets in RFC 2330. This memo identifies that IPv4-IPv6 co-existence can challenge measurements within the scope of the IPPM Framework. Exemplary use cases include, but are not limited to IPv4-IPv6 translation, NAT, or protocol encapsulation. IPv6 header compression and use of IPv6 over Low- Power Wireless Area Networks (6LoWPAN) are considered and excluded from the standard-formed packet evaluation.
- Two-Way Active Measurement Protocol (TWAMP) Data Model (draft-ietf-ippm-twamp-yang): IESG Evaluation » ::Revised I-D Needed
By Ruth Civil, Al Morton, Reshad Rahman, Mahesh Jethanandani, Kostas Pentikousis, 2018-05-25 TXT HTML PDF
Abstract: This document specifies a data model for client and server implementations of the Two-Way Active Measurement Protocol (TWAMP). The document defines the TWAMP data model through Unified Modeling Language (UML) class diagrams and formally specifies it using YANG.
- Secure/Multipurpose Internet Mail Extensions (S/ MIME) Version 4.0 Certificate Handling (draft-ietf-lamps-rfc5750-bis): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By Jim Schaad, Blake Ramsdell, Sean Turner, 2018-06-21 TXT HTML PDF
Abstract: This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) v4.0 agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 5280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 5280. This document obsoletes RFC 5750.
- Using Simulcast in SDP and RTP Sessions (draft-ietf-mmusic-sdp-simulcast): IESG Evaluation » ::Revised I-D Needed
By Bo Burman, Magnus Westerlund, Suhas Nandakumar, Mo Zanaty, 2018-04-10 TXT HTML PDF
Abstract: In some application scenarios it may be desirable to send multiple differently encoded versions of the same media source in different RTP streams. This is called simulcast. This document describes how to accomplish simulcast in RTP and how to signal it in SDP. The described solution uses an RTP/RTCP identification method to identify RTP streams belonging to the same media source, and makes an extension to SDP to relate those RTP streams as being different simulcast formats of that media source. The SDP extension consists of a new media level SDP attribute that expresses capability to send and/or receive simulcast RTP streams.
- Entropy label for SPRING tunnels (draft-ietf-mpls-spring-entropy-label): Waiting for Writeup » IESG Evaluation
By Sriganesh Kini, Kireeti Kompella, Siva Sivabalan, Stephane Litkowski, Rob Shakir, Jeff Tantsura, 2018-05-23 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. Segment Routing can be applied to the Multi Protocol Label Switching (MPLS) data plane. Entropy label (EL) is a technique used in MPLS to improve load-balancing. This document examines and describes how ELs are to be applied to Segment Routing MPLS.
- Use of Ethernet Control Word RECOMMENDED (draft-ietf-pals-ethernet-cw): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By Stewart Bryant, Andrew Malis, Ignas Bagdonas, 2018-05-25 TXT HTML PDF
Abstract: The pseudowire (PW) encapsulation of Ethernet, as defined in RFC 4448, specifies that the use of the control word (CW) is optional. In the absence of the CW an Ethernet pseudowire packet can be misidentified as an IP packet by a label switching router (LSR). This in turn may lead to the selection of the wrong equal-cost-multi- path (ECMP) path for the packet, leading in turn to the misordering of packets. This problem has become more serious due to the deployment of equipment with Ethernet MAC addresses that start with 0x4 or 0x6. The use of the Ethernet PW CW addresses this problem. This document recommends the use of the Ethernet pseudowire control word in all but exceptional circumstances.
- RTP Payload Format for VC-2 HQ Profile Video (draft-ietf-payload-rtp-vc2hq): IESG Evaluation » Approved-announcement to be sent::Revised I-D Needed
By James Weaver, 2018-05-23 TXT HTML PDF
Abstract: This memo describes an RTP Payload format for the High Quality (HQ) profile of Society of Motion Picture and Television Engineers Standard ST 2042-1 known as VC-2. This document describes the transport of HQ Profile VC-2 in RTP packets and has applications for low-complexity, high-bandwidth streaming of both lossless and lossy compressed video.
- Dynamic Authorization Proxying in Remote Authorization Dial-In User Service Protocol (RADIUS) (draft-ietf-radext-coa-proxy): Publication Requested » AD Evaluation::Revised I-D Needed
By Alan DeKok, Jouni Korhonen, 2018-04-24 TXT HTML PDF
Abstract: RFC 5176 defines Change of Authorization (CoA) and Disconnect Message (DM) behavior for RADIUS. Section 3.1 of that document suggests that proxying these messages is possible, but gives no guidance as to how that is done. This specification corrects that omission for scenarios where networks use Realm-based proxying as defined in [RFC7542].
- Hierarchical Service Function Chaining (hSFC) (draft-ietf-sfc-hierarchical): IESG Evaluation » ::Revised I-D Needed
By David Dolson, Shunsuke Homma, Diego Lopez, Mohamed Boucadair, 2018-06-13 TXT HTML PDF
Abstract: Hierarchical Service Function Chaining (hSFC) is a network architecture allowing an organization to decompose a large-scale network into multiple domains of administration.
- Segment Routing interworking with LDP (draft-ietf-spring-segment-routing-ldp-interop): IESG Evaluation » ::Revised I-D Needed
By Ahmed Bashandy, Clarence Filsfils, Stefano Previdi, Bruno Decraene, Stephane Litkowski, 2018-06-13 TXT HTML PDF
Abstract: A Segment Routing (SR) node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any topological path while maintaining per-flow state only at the ingress node to the SR domain.
- Information Model for Abstraction and Control of TE Networks (ACTN) (draft-ietf-teas-actn-info-model): IESG Evaluation » Approved-announcement to be sent::Point Raised - writeup needed
By Young Lee, Sergio Belotti, Dhruv Dhody, Daniele Ceccarelli, Bin-Yeong Yoon, 2018-06-21 TXT HTML PDF
Abstract: This draft provides an information model for Abstraction and Control of Traffic Engineered Networks (ACTN).
- Example Handshake Traces for TLS 1.3 (draft-ietf-tls-tls13-vectors): Publication Requested » AD Evaluation
By Martin Thomson, 2018-05-29 TXT HTML PDF
Abstract: Examples of TLS 1.3 handshakes are shown. Private keys and inputs are provided so that these handshakes might be reproduced. Intermediate values, including secrets, traffic keys and ivs are shown so that implementations might be checked incrementally against these values.
Drafts Sent to RFC Editor
Other Status Changes
- Proposed Structure of the IETF Administrative Support Activity (IASA), Version 2.0 (for Discussion) (draft-hall-iasa2-struct): Active » Replaced by draft-ietf-iasa2-struct
By Brian Haberman, Joseph Hall, Jason Livingood, 2018-06-06 TXT HTML PDF
Abstract: The IETF Administrative Support Activity (IASA) was originally established in 2005. In the 13 years from 2005 to 2018, the needs of the IETF have evolved in ways that require changes to its administrative structure. The purpose of this document is to outline a proposed new "IASA 2.0" structure. The proposal is for the work of the IETF's administrative and fundraising tasks to be conducted by a new administrative organization, the IETF Administration Limited Liability Corporation ("LLC"). Under the proposal, the Internet Administrative Oversight Committee (IAOC) will be eliminated, and its oversight and advising functions transferred to the new LLC Board.
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
