IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- Pseudo-flavors for Remote Procedure Calls with Transport Layer Security (draft-cel-nfsv4-rpc-tls-pseudoflavors)
By Chuck Lever, 2021-12-05 TXT HTML PDF
Abstract: Recent innovations in Remote Procedure Call (RPC) transport layer security enable broad deployment of encryption and mutual peer authentication when exchanging RPC messages. These security mechanisms can protect peers who continue to use the AUTH_SYS RPC auth flavor, which is not cryptographically secure, on open networks. This document introduces several RPC auth pseudo-flavors and other mechanisms that an RPC service can use to indicate transport layer security requirements for accessing that service.
- Scheduling Online Meetings (draft-nottingham-scheduling-online-meetings)
By Mark Nottingham, 2021-12-02 TXT HTML PDF
Abstract: This document recommends best practices when scheduling online meetings.
Updated Drafts
- IDNA2008 and Unicode 12.0.0 (draft-faltstrom-unicode12)
By Patrik Faltstrom, 2021-12-03 TXT HTML PDF
Abstract: This document describes the changes between Unicode 6.0.0 and Unicode 12.0.0 in the context of IDNA2008. Some additions and changes have been made in the Unicode Standard that affect the values produced by the algorithm IDNA2008 specifies. IDNA2008 allows adding exceptions to the algorithm for backward compatibility; however, this document does not add any such exceptions. This document provides the necessary tables to IANA to make its database consistent with Unicode 12.0.0.
- EAP-based Authentication Service for CoAP (draft-ietf-ace-wg-coap-eap)
By Rafael Marin-Lopez, Dan Garcia-Carrillo, 2021-12-05 TXT HTML PDF
Abstract: This document specifies an authentication service that uses the Extensible Authentication Protocol (EAP) transported employing Constrained Application Protocol (CoAP) messages. As such, it defines an EAP lower layer based on CoAP called CoAP-EAP. One of the main goals is to authenticate a CoAP-enabled IoT device (EAP peer) that intends to join a security domain managed by a Controller (EAP authenticator). Secondly, it allows deriving key material to protect CoAP messages exchanged between them based on Object Security for Constrained RESTful Environments (OSCORE), enabling the establishment of a security association between them.
- Constrained Join Proxy for Bootstrapping Protocols (draft-ietf-anima-constrained-join-proxy)
By Michael Richardson, Peter van der Stok, Panos Kampanakis, 2021-12-03 TXT HTML PDF
Abstract: This document defines a protocol to securely assign a Pledge to a domain, represented by a Registrar, using an intermediary node between Pledge and Registrar. This intermediary node is known as a "constrained Join Proxy". An enrolled Pledge can act as a Join Proxy.
- Unsolicited BFD for Sessionless Applications (draft-ietf-bfd-unsolicited)
By Enke Chen, Naiming Shen, Robert Raszuk, Reshad Rahman, 2021-12-03 TXT HTML PDF
Abstract: For operational simplification of "sessionless" applications using BFD, in this document we present procedures for "unsolicited BFD" that allow a BFD session to be initiated by only one side, and be established without explicit per-session configuration or registration by the other side (subject to certain per-interface or per-router policies).
- ECMAScript Media Types Updates (draft-ietf-dispatch-javascript-mjs)
By Matthew Miller, Myles Borins, Mathias Bynens, Bradley Farias, 2021-12-03 TXT HTML PDF
Abstract: This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This document obsoletes RFC4329, "Scripting Media Types", replacing the previous registrations for "text/javascript" and "application/javascript" with information and requirements aligned with implementation experiences.
- Simple Mail Transfer Protocol (draft-ietf-emailcore-rfc5321bis)
By John Klensin, 2021-12-03 TXT HTML PDF
Abstract: This document is a specification of the basic protocol for Internet electronic mail transport. It consolidates, updates, and clarifies several previous documents, making all or parts of most of them obsolete. It covers the SMTP extension mechanisms and best practices for the contemporary Internet, but does not provide details about particular extensions. The document also provides information about use of SMTP for other than strict mail transport and delivery. This document replaces RFC 5321, the earlier version with the same title.
- Route Leak Prevention and Detection using Roles in UPDATE and OPEN Messages (draft-ietf-idr-bgp-open-policy)
By Alexander Azimov, Eugene Bogomazov, Randy Bush, Keyur Patel, Kotikalapudi Sriram, 2021-12-04 TXT HTML PDF
Abstract: Route leaks are the propagation of BGP prefixes that violate assumptions of BGP topology relationships, e.g., announcing a route learned from one transit provider to another transit provider or a lateral (i.e., non-transit) peer or announcing a route learned from one lateral peer to another lateral peer or a transit provider. These are usually the result of misconfigured or absent BGP route filtering or lack of coordination between autonomous systems (ASes). Existing approaches to leak prevention rely on marking routes by operator configuration, with no check that the configuration corresponds to that of the eBGP neighbor, or enforcement that the two eBGP speakers agree on the relationship. This document enhances the BGP OPEN message to establish an agreement of the relationship on each eBGP session between autonomous systems in order to enforce appropriate configuration on both sides. Propagated routes are then marked according to the agreed relationship, allowing both prevention and detection of route leaks.
- Negotiating Media Multiplexing Using the Session Description Protocol (SDP) (draft-ietf-mmusic-rfc8843bis)
By Christer Holmberg, Harald Alvestrand, Cullen Jennings, 2021-12-05 TXT HTML PDF
Abstract: This specification defines a new Session Description Protocol (SDP) Grouping Framework extension called 'BUNDLE'. The extension can be used with the SDP offer/answer mechanism to negotiate the usage of a single transport (5-tuple) for sending and receiving media described by multiple SDP media descriptions ("m=" sections). Such transport is referred to as a BUNDLE transport, and the media is referred to as bundled media. The "m=" sections that use the BUNDLE transport form a BUNDLE group.
- Egress TLV for Nil FEC in Label Switched Path Ping and Traceroute Mechanisms (draft-ietf-mpls-egress-tlv-for-nil-fec)
By Deepti Rathi, Kapil Arora, Shraddha Hegde, Zafar Ali, Nagendra Nainar, 2021-12-03 TXT HTML PDF
Abstract: MPLS ping and traceroute mechanism as described in RFC 8029 and related extensions for SR as defined in RFC 8287 is very useful to precisely validate the control plane and data plane synchronization. There is a possibility that all intermediate or transit nodes may not have been upgraded to support these validation procedures. A simple mpls ping and traceroute mechanism comprises of ability to traverse any path without having to validate the control plane state. RFC 8029 supports this mechanism with Nil FEC. The procedures described in RFC 8029 are mostly applicable when the Nil FEC is used as intermediate FEC in the label stack. When all labels in label stack are represented using single Nil FEC, it poses some challenges.
- Conveying a Certificate Signing Request (CSR) in a Secure Zero Touch Provisioning (SZTP) Bootstrapping Request (draft-ietf-netconf-sztp-csr)
By Kent Watsen, Russ Housley, Sean Turner, 2021-12-03 TXT HTML PDF
Abstract: This draft extends the "get-bootstrapping-data" RPC defined in RFC 8572 to include an optional certificate signing request (CSR), enabling a bootstrapping device to additionally obtain an identity certificate (e.g., an LDevID from IEEE 802.1AR) as part of the "onboarding information" response provided in the RPC-reply.
- Network Telemetry Framework (draft-ietf-opsawg-ntf)
By Haoyu Song, Fengwei Qin, Pedro Martinez-Julia, Laurent Ciavaglia, Aijun Wang, 2021-12-03 TXT HTML PDF
Abstract: Network telemetry is a technology for gaining network insight and facilitating efficient and automated network management. It encompasses various techniques for remote data generation, collection, correlation, and consumption. This document describes an architectural framework for network telemetry, motivated by challenges that are encountered as part of the operation of networks and by the requirements that ensue. This document clarifies the terminologies and classifies the modules and components of a network telemetry system from different perspectives. The framework and taxonomy help to set a common ground for the collection of related work and provide guidance for related technique and standard developments.
- Date and Time on the Internet: Timestamps with additional information (draft-ietf-sedate-datetime-extended)
By Ujjwal Sharma, Carsten Bormann, 2021-12-03 TXT HTML PDF
Abstract: This document defines an extension to the timestamp format defined in RFC3339 for representing additional information including a time zone.
- Network Service Header Metadata Type 2 Variable-Length Context Headers (draft-ietf-sfc-nsh-tlv)
By Yuehua Wei, Uri Elzur, Sumandra Majee, Carlos Pignataro, Donald Eastlake, 2021-12-03 TXT HTML PDF
Abstract: Service Function Chaining (SFC) uses the Network Service Header (NSH) (RFC 8300) to steer and provide context Metadata (MD) with each packet. Such Metadata can be of various Types including MD Type 2 variable length context headers. This document specifies several such context headers that can be used within a service function path.
- Oblivious DNS Over HTTPS (draft-pauly-dprive-oblivious-doh)
By Eric Kinnear, Patrick McManus, Tommy Pauly, Tanya Verma, Christopher Wood, 2021-12-03 TXT HTML PDF
Abstract: This document describes an extension to DNS Over HTTPS (DoH) that allows hiding client IP addresses via proxying encrypted DNS transactions. This improves privacy of DNS operations by not allowing any one server entity to be aware of both the client IP address and the content of DNS queries and answers.
- IANA Registry Updates for TLS and DTLS (draft-salowey-tls-rfc8447bis)
By Joseph Salowey, Sean Turner, 2021-12-02 TXT HTML PDF
Abstract: This document describes a number of changes to TLS and DTLS IANA registries that range from adding notes to the registry all the way to changing the registration policy. These changes were mostly motivated by WG review of the TLS- and DTLS-related registries undertaken as part of the TLS 1.3 development process.
- Using GOST ciphers in ESP and IKEv2 (draft-smyslov-esp-gost)
By Valery Smyslov, 2021-12-03 TXT HTML PDF
Abstract: This document defines a set of encryption transforms for use in the Encapsulating Security Payload (ESP) and in the Internet Key Exchange version 2 (IKEv2) protocols which are parts of the IP Security (IPsec) protocols suite. The transforms are based on Russian cryptographic standard algorithms (GOST) in a Multilinear Galois Mode (MGM).
- Secure EVPN MAC Signaling (draft-thubert-bess-secure-evpn-mac-signaling)
By Pascal Thubert, Tony Przygienda, Jeff Tantsura, 2021-12-03 TXT HTML PDF
Abstract: This specification adds attributes to EVPN to carry IPv6 address metadata learned from RFC 8505 and RFC 8928 so as to maintain a synchronized copy of the 6LoWPAN ND registrar at each EVPN router and perform locally a unicast IPv6 ND service for address lookup and duplicate address detection.
Expired Drafts
- SDP Superimposition Grouping framework (draft-abhishek-mmusic-superimposition-grouping)
By Rohit Abhishek, Stephan Wenger, 2021-06-01 TXT HTML PDF
Abstract: This document defines semantics that allow for signaling a new SDP group "supim" for superimposed media in an SDP session. The "supim" attribute can be used by the application to relate all the fully or partly superimposed visual media streams enabling them to be added as an overlay on top of any one or more background visual media streams. The superimposition grouping semantics is helpful if the media stream data is separate and transported via different sessions.
- Map-like data in CBOR and CDDL (draft-bormann-cbor-cddl-map-like-data)
By Carsten Bormann, Brendan Moran, Henk Birkholz, Emile Cormier, 2021-06-01 TXT HTML PDF
Abstract: The Concise Binary Object Representation (CBOR, RFC 8949) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.
- DTN Bundle Protocol Security COSE Security Context (draft-bsipos-dtn-bpsec-cose)
By Brian Sipos, 2021-06-03 TXT HTML PDF
Abstract: This document defines a security context suitable for using CBOR Object Signing and Encryption (COSE) algorithms within Bundle Protocol Security (BPSec) integrity and confidentiality blocks. A profile of COSE and for PKIX certificates are also defined for BPSec interoperation.
- BGP Over QUIC (draft-chen-idr-bgp-over-quic)
By Shuanglong Chen, Yongkang Zhang, Haibo Wang, Zhenbin Li, 2021-06-03 TXT HTML PDF
Abstract: Border Gateway Protocol (BGP) is an autonomous system routing protocol. The main function of BGP is to exchange routing and reachability information between autonomous systems(AS) on the Internet. BGP uses TCP to implement reliable and orderly transmission of information. Similar to TCP, QUIC is a UDP-based, byte-stream-based reliable data transmission service. In addition, by integrating with TLS 1.3, QUIC also supports functions such as establishing connections with minimum latency and providing confidentiality and integrity protection for the transmitted data, and multi-stream multiplexing. Taking use of QUIC for BGP can achieve the possible advantages. This document defines the mechanism of BGP over QUIC to and corresponding procedures.
- Client Hint Reliability (draft-davidben-http-client-hint-reliability)
By David Benjamin, 2021-06-01 TXT HTML PDF
Abstract: This document defines the Critical-CH HTTP response header, and the ACCEPT_CH HTTP/2 and HTTP/3 frames to allow HTTP servers to reliably specify their Client Hint preferences, with minimal performance overhead.
- Path Selection for Multiple Paths In QUIC (draft-dawkins-quic-multipath-selection)
By Spencer Dawkins, 2021-06-02 TXT HTML PDF
Abstract: In QUIC working group discussions about proposals to use multiple paths, an obvious question came up - given multiple paths, how does QUIC select paths to send packets over?
- Pairing Friendly Curves Representations in JOSE and COSE (draft-denhartog-pairing-curves-jose-cose)
By Kyle Hartog, 2021-06-01 TXT HTML PDF
Abstract: This specification defines representations enabling the Standards for Pairing Frinedly Curves to be used for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) messages.
- YANG Model for Scalable VTN (draft-geng-teas-enhanced-vpn-scalable-vtn-yang)
By Xuesong Geng, Zhibo Hu, 2021-06-03 TXT HTML PDF
Abstract: This document defines the Yang data model for scalable Virtual Transport Network(VTN).
- IPv6 Hop-by-Hop Options Processing Procedures (draft-hinden-6man-hbh-processing)
By Robert Hinden, Gorry Fairhurst, 2021-06-02 TXT HTML PDF
Abstract: This document specifies procedures for how IPv6 Hop-by-Hop options are processed. It modifies the procedures specified in the IPv6 Protocol Specification (RFC8200) to make processing of IPv6 Hop-by- Hop options practical with the goal of making IPv6 Hop-by-Hop options useful to deploy and use in the Internet. When published, this document updates RFC8200.
- Operations, Administration and Maintenance (OAM) features for RAW (draft-ietf-raw-oam-support)
By Fabrice Theoleyre, Georgios Papadopoulos, Greg Mirsky, Carlos Bernardos, 2021-06-03 TXT HTML PDF
Abstract: Some critical applications may use a wireless infrastructure. However, wireless networks exhibit a bandwidth of several orders of magnitude lower than wired networks. Besides, wireless transmissions are lossy by nature; the probability that a packet cannot be decoded correctly by the receiver may be quite high. In these conditions, providing high reliability and a low delay is challenging. This document lists the requirements of the Operation, Administration, and Maintenance (OAM) features recommended to construct a predictable communication infrastructure on top of a collection of wireless segments. This document describes the benefits, problems, and trade- offs for using OAM in wireless networks to achieve Service Level Objectives (SLO).
- ICANN TMCH functional specifications (draft-ietf-regext-tmch-func-spec)
By Gustavo Ibarra, 2021-06-02 TXT HTML PDF
Abstract: This document describes the requirements, the architecture and the interfaces between the ICANN Trademark Clearinghouse (TMCH) and Domain Name Registries as well as between the ICANN TMCH and Domain Name Registrars for the provisioning and management of domain names during Sunrise and Trademark Claims Periods.
- Use cases of Application-aware Networking (APN) in Edge Computing (draft-liu-apn-edge-usecase)
By Peng Liu, Zongpeng Du, Shuping Peng, Zhenbin Li, 2021-06-01 TXT HTML PDF
Abstract: The ever-emerging new services are imposing more and more highly demanding requirements on the network. However, the current deployments could not fully accommodate those requirements due to limited capabilities. For example, it is difficult to utilize the traditional centralized deployment mode to meet the low-latency demand of some latency-sensitive applications. Moreover, the total amount of centralized service data is growing exponentially, which brings great pressure on the network bandwidth. There has been a clear trend that decentralized sites comprising of computing and storage resources are deployed at various locations to provide services. In particular, when the sites are deployed at the network edge, i.e. the Edge Computing, it can better handle the business needs of the users nearby, which provides the possibilities to provide differentiated network and computing services. In order to achieve the full benefits of the edge computing, it actually implies a precondition that the network should be aware of the applications' requirements in order to steer their traffic to the network paths that can satisfy their requirements. Application-aware networking (APN) aims to accommodate the edge services' needs, fully releasing the benefits of the edge computing.
- Data Fields Encapsulation Model of In-situ OAM in SRv6 Network (draft-qiu-spring-srv6-ioam-encap-model)
By Yuanxiang Qiu, Jinrong Ye, Hao Li, 2021-06-03 TXT HTML PDF
Abstract: OAM and PM information from the SR endpoints can be piggybacked in the data packet. The OAM and PM information piggybacking in the data packets is also known as In-situ OAM (IOAM). IOAM records OAM information within the packet while the packet traverses a particular network domain. The term "in-situ" refers to the fact that the IOAM data fields are added to the data packets rather than being sent within probe packets specifically dedicated to OAM. This document defines the data fields encapsulation model of IOAM TLV in SRv6 network.
- Effective DNS Service (draft-rintaro-eds)
By Rintaro Kobayashi, 2021-06-01 TXT HTML PDF
Abstract: In DNS Queries over HTTPS [RFC8484], the port that communicates with DNS would change from UDP to TCP 443. This change causes a new problem that makes it difficult to identify which is the name resolution request, so it is difficult to use web filtering, parental controls and so on. Furthermore, a user-agent in a HTTP header that is necessary for HTTPS communications could be a data used to track users. In summary, DNS Queries over HTTPS has some problems that affect users' security and privacy. This draft proposes a system that is set mediation servers between client side and DNS servers. With this proposal, it is expected that those two problems will be solved.
- Account based authentication for DHCP (draft-xu-dhc-authen)
By Yibin Xu, Hao Weiguo, Jianping Xie, 2021-06-03 TXT HTML PDF
Abstract: This document describes the mutual authentication between DHCP server and DHCP client based on account information to mitigate the security risk caused by rogue DHCP server, and the problem of illegal DHCP client exhausting DHCP server address.
|
Drafts Sent to IESG
IESG Progress
- Completely Encrypting RTP Header Extensions and Contributing Sources (draft-ietf-avtcore-cryptex): AD Evaluation::Revised I-D Needed » AD Evaluation
By Justin Uberti, Cullen Jennings, Sergio Murillo, 2021-10-25 TXT HTML PDF
Abstract: While the Secure Real-time Transport Protocol (SRTP) provides confidentiality for the contents of a media packet, a significant amount of metadata is left unprotected, including RTP header extensions and contributing sources (CSRCs). However, this data can be moderately sensitive in many applications. While there have been previous attempts to protect this data, they have had limited deployment, due to complexity as well as technical limitations.
- ECMAScript Media Types Updates (draft-ietf-dispatch-javascript-mjs): Waiting for AD Go-Ahead::Revised I-D Needed » ::AD Followup
By Matthew Miller, Myles Borins, Mathias Bynens, Bradley Farias, 2021-12-03 TXT HTML PDF
Abstract: This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This document obsoletes RFC4329, "Scripting Media Types", replacing the previous registrations for "text/javascript" and "application/javascript" with information and requirements aligned with implementation experiences.
- IMAP QUOTA Extension (draft-ietf-extra-quota): IESG Evaluation::AD Followup » Approved-announcement to be sent
By Alexey Melnikov, 2021-11-18 TXT HTML PDF
Abstract: This document defines a QUOTA extension of the Internet Message Access Protocol (RFC 3501/RFC 9051) that permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol.
- Route Leak Prevention and Detection using Roles in UPDATE and OPEN Messages (draft-ietf-idr-bgp-open-policy): Expert Review::External Party » In Last Call
By Alexander Azimov, Eugene Bogomazov, Randy Bush, Keyur Patel, Kotikalapudi Sriram, 2021-12-04 TXT HTML PDF
Abstract: Route leaks are the propagation of BGP prefixes that violate assumptions of BGP topology relationships, e.g., announcing a route learned from one transit provider to another transit provider or a lateral (i.e., non-transit) peer or announcing a route learned from one lateral peer to another lateral peer or a transit provider. These are usually the result of misconfigured or absent BGP route filtering or lack of coordination between autonomous systems (ASes). Existing approaches to leak prevention rely on marking routes by operator configuration, with no check that the configuration corresponds to that of the eBGP neighbor, or enforcement that the two eBGP speakers agree on the relationship. This document enhances the BGP OPEN message to establish an agreement of the relationship on each eBGP session between autonomous systems in order to enforce appropriate configuration on both sides. Propagated routes are then marked according to the agreed relationship, allowing both prevention and detection of route leaks.
- Network Service Header Metadata Type 2 Variable-Length Context Headers (draft-ietf-sfc-nsh-tlv): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Yuehua Wei, Uri Elzur, Sumandra Majee, Carlos Pignataro, Donald Eastlake, 2021-12-03 TXT HTML PDF
Abstract: Service Function Chaining (SFC) uses the Network Service Header (NSH) (RFC 8300) to steer and provide context Metadata (MD) with each packet. Such Metadata can be of various Types including MD Type 2 variable length context headers. This document specifies several such context headers that can be used within a service function path.
Drafts Sent to RFC Editor
Other Status Changes
RFC Editor Status Changes
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
