IETF-Announce List
![[Feed]](feedicon16.png) New RFCs
New and Revived Drafts
- P2MP Policy Ping (draft-hb-pim-p2mp-policy-ping)
By Hooman Bidgoli, Dan Voyer, Rishabh Parekh, Zhaohui Zhang, 2021-07-25 TXT HTML PDF
Abstract: SR P2MP policies are set of policies that enable architecture for P2MP service delivery. A P2MP Policy consists of candidate paths that connects the Root of the Tree to a set of Leaves. The P2MP policy is composed of replication segments. A replication segment is a forwarding instruction for a candidate path which is downloaded to the Root, transit nodes and the leaves.
- JWS signed Voucher Artifacts for Bootstrapping Protocols (draft-ietf-anima-jws-voucher)
By Michael Richardson, Thomas Werner, 2021-07-25 TXT HTML PDF
Abstract: RFC8366 defines a digital artifact called voucher as a YANG-defined JSON document that has been signed using a Cryptographic Message Syntax (CMS) structure. This memo introduces a variant of the voucher structure in which CMS is replaced by the JSON Object Signing and Encryption (JOSE) mechanism described in RFC7515 to better support use-cases in which JOSE is preferred over CMS.
- Echo Request/Reply for Enabled In-situ OAM Capabilities (draft-ietf-ippm-ioam-conf-state)
By Xiao Min, Greg Mirsky, Lei Bo, 2021-07-25 TXT HTML PDF
Abstract: This document describes an extension to the echo request/reply mechanisms used in IPv6, MPLS, SFC and BIER environments, which can be used within an IOAM domain, allowing the IOAM encapsulating node to acquire the enabled IOAM capabilities of each IOAM transit node and/or IOAM decapsulating node.
Updated Drafts
- Lightweight Directory Access Protocol (LDAP) Procedures and Schema Definitions for the Storage of X.660 Registration Information (draft-coretta-x660-ldap)
By Jesse Coretta, 2021-07-25 TXT HTML PDF
Abstract: This specification defines models, procedures and schema definitions meant to facilitate the storage of [X.660] registration data within a Lightweight Directory Access Protocol Directory Information Tree.
- (strong) AuCPace, an augmented PAKE (draft-haase-aucpace)
By Bjoern Haase, 2021-07-25 TXT HTML PDF
Abstract: This document describes AuCPace which is an augmented PAKE protocol for two parties. The protocol was tailored for constrained devices and smooth migration for compatibility with legacy user credential databases. It is designed to be compatible with any group of both prime- and non-prime order and comes with a security proof providing composability guarantees.
- Constrained Voucher Artifacts for Bootstrapping Protocols (draft-ietf-anima-constrained-voucher)
By Michael Richardson, Peter van der Stok, Panos Kampanakis, Esko Dijk, 2021-07-25 TXT HTML PDF
Abstract: This document defines a protocol to securely assign a Pledge to an owner and to enroll it into the owner's network. The protocol uses an artifact that is signed by the Pledge's manufacturer. This artifact is known as a "voucher".
- PIM Signaling Through BIER Core (draft-ietf-bier-pim-signaling)
By Hooman Bidgoli, Fengman Xu, Jayant Kotalwar, IJsbrand Wijnands, Mankamana Mishra, Zhaohui Zhang, 2021-07-25 TXT HTML PDF
Abstract: Consider large networks deploying traditional PIM multicast service. Typically, each portion of these large networks have their own mandates and requirements. It might be desirable to deploy BIER technology in some part of these networks to replace traditional PIM services. In such cases downstream PIM states need to be signaled over the BIER Domain toward the source.
- CBOR tags for IPv4 and IPv6 addresses and prefixes (draft-ietf-cbor-network-addresses)
By Michael Richardson, Carsten Bormann, 2021-07-25 TXT HTML PDF
Abstract: This specification describes two CBOR Tags to be used with IPv4 and IPv6 addresses and prefixes.
- Constrained Resource Identifiers (draft-ietf-core-href)
By Carsten Bormann, Henk Birkholz, 2021-07-25 TXT HTML PDF
Abstract: The Constrained Resource Identifier (CRI) is a complement to the Uniform Resource Identifier (URI) that serializes the URI components in Concise Binary Object Representation (CBOR) instead of a sequence of characters. This simplifies parsing, comparison and reference resolution in environments with severe limitations on processing power, code size, and memory size.
- Drone Remote Identification Protocol (DRIP) Architecture (draft-ietf-drip-arch)
By Stuart Card, Adam Wiethuechter, Robert Moskowitz, Shuai Zhao, Andrei Gurtov, 2021-07-25 TXT HTML PDF
Abstract: This document describes an architecture for protocols and services to support Unmanned Aircraft System Remote Identification and tracking (UAS RID), plus RID-related communications. This architecture adheres to the requirements listed in the DRIP Requirements document.
- Unmanned Aircraft System Remote Identification (UAS RID) (draft-ietf-drip-rid)
By Robert Moskowitz, Stuart Card, Adam Wiethuechter, Andrei Gurtov, 2021-07-25 TXT HTML PDF
Abstract: This document describes the use of Hierarchical Host Identity Tags (HHITs) as self-asserting IPv6 addresses and thereby a trustable identifier for use as the Unmanned Aircraft System Remote Identification and tracking (UAS RID). HHITs self-attest to the included explicit hierarchy that provides Registrar discovery for 3rd-party identifier attestation.
- BPSec Default Security Contexts (draft-ietf-dtn-bpsec-default-sc)
By Edward Birrane, Alex White, Sarah Heiner, 2021-07-25 TXT HTML PDF
Abstract: This document defines default integrity and confidentiality security contexts that can be used with the Bundle Protocol Security Protocol (BPSec) implementations. These security contexts are intended to be used for both testing the interoperability of BPSec implementations and for providing basic security operations when no other security contexts are defined or otherwise required for a network.
- HTTP Caching (draft-ietf-httpbis-cache)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.
- HTTP/1.1 (draft-ietf-httpbis-messaging)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns.
- HTTP Semantics (draft-ietf-httpbis-semantics)
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.
- In-situ OAM Flags (draft-ietf-ippm-ioam-flags)
By Tal Mizrahi, Frank Brockners, Shwetha Bhandari, Ramesh Sivakolundu, Carlos Pignataro, Aviv Kfir, Barak Gafni, Mickey Spiegel, Jennifer Lemon, 2021-07-25 TXT HTML PDF
Abstract: In-situ Operations, Administration, and Maintenance (IOAM) records operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document presents new flags in the IOAM Trace Option headers. Specifically, the document defines the Loopback and Active flags.
- Simple TWAMP (STAMP) Extensions for Segment Routing Networks (draft-ietf-ippm-stamp-srpm)
By Rakesh Gandhi, Clarence Filsfils, Dan Voyer, Mach Chen, Bart Janssens, Richard Foote, 2021-07-25 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. SR is applicable to both Multiprotocol Label Switching (SR-MPLS) and IPv6 (SRv6) forwarding planes. This document specifies RFC 8762 (Simple Two-Way Active Measurement Protocol (STAMP)) extensions for SR networks, for both SR-MPLS and SRv6 forwarding planes by augmenting the optional extensions defined in RFC 8972.
- SCHC over NB-IoT (draft-ietf-lpwan-schc-over-nbiot)
By Edgar Ramos, Ana Minaburo, 2021-07-25 TXT HTML PDF
Abstract: The Static Context Header Compression (SCHC) specification describes a header compression and fragmentation functionalities for LPWAN (Low Power Wide Area Networks) technologies. SCHC was designed to be adapted over any of the LPWAN technologies.
- Performance Measurement Using RFC 6374 for Segment Routing Networks with MPLS Data Plane (draft-ietf-mpls-rfc6374-sr)
By Rakesh Gandhi, Clarence Filsfils, Dan Voyer, Stefano Salsano, Mach Chen, 2021-07-25 TXT HTML PDF
Abstract: Segment Routing (SR) leverages the source routing paradigm. RFC 6374 specifies protocol mechanisms to enable the efficient and accurate measurement of packet loss, one-way and two-way delay, as well as related metrics such as delay variation in MPLS networks. This document utilizes these mechanisms for Performance Delay and Loss Measurements in SR networks with MPLS data plane (SR-MPLS), for both SR-MPLS links and end-to-end SR-MPLS paths including Policies. In addition, this document defines Return Path TLV and Block Number TLV extensions for RFC 6374.
- Use of Internationalized Email Addresses in EPP protocol (draft-ietf-regext-epp-eai)
By Dmitry Belyavsky, James Gould, 2021-07-25 TXT HTML PDF
Abstract: This document describes an EPP extension that permits usage of Internationalized Email Addresses in the EPP protocol and specifies the terms when it can be used by EPP clients and servers. The Extensible Provisioning Protocol (EPP), being developed before appearing the standards for Internationalized Email Addresses (EAI), does not support such email addresses.
- Registry Maintenance Notifications for the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-epp-registry-maintenance)
By Tobias Sattler, Roger Carney, Jody Kolker, 2021-07-25 TXT HTML PDF
Abstract: This document describes an Extensible Provision Protocol (EPP) extension called "Registry Maintenance Notification", used by EPP servers to notify EPP clients and allow EPP clients to query EPP servers on maintenance events.
- HyStart++: Modified Slow Start for TCP (draft-ietf-tcpm-hystartplusplus)
By Praveen Balasubramanian, Yi Huang, Matt Olson, 2021-07-25 TXT HTML PDF
Abstract: This doument describes HyStart++, a simple modification to the slow start phase of TCP congestion control algorithms. Traditional slow start can cause overshooting of the ideal send rate and cause large packet loss within a round-trip time which results in poor performance. HyStart++ uses a delay increase heuristic to exit slow start early while also mitigating poor performance which can result from false positives.
- CPace, a balanced composable PAKE (draft-irtf-cfrg-cpace)
By Michel Abdalla, Bjoern Haase, Julia Hesse, 2021-07-25 TXT HTML PDF
Abstract: This document describes CPace which is a protocol for two parties that share a low-entropy secret (password) to derive a strong shared key without disclosing the secret to offline dictionary attacks. This method was tailored for constrained devices, is compatible with any group of both prime- and non-prime order, and comes with a security proof providing composability guarantees.
- An in-band BGP mechanism for looking-glass address discovery (draft-jaufeerally-bgp-lg-cap)
By Rayhaan Jaufeerally, 2021-07-25 TXT HTML PDF
Abstract: Autonomous Systems (ASes) that peer with one another using the Border Gateway Protocol (BGP) RFC 4271 [RFC4271] do not have an automated way to tell if the prefixes announced over a particular peering link are acceped by the peer. One way in which an AS operator can verify acceptance of routes by a peer is using a looking glass which may be provided by the peer, however this introduces manual toil in the operation and turnup of peering links, and does not allow for continued validation to ensure there are no regressions. Looking glasses are often manually found by browsing the website of the peer or via a database of peering participants.
- IKEv2 Optional SA&TS Payloads in Child Exchange (draft-kampati-ipsecme-ikev2-sa-ts-payloads-opt)
By Sandeep Kampati, Wei Pan, Paul Wouters, Bharath Meduri, chenmeiling, 2021-07-25 TXT HTML PDF
Abstract: This document describes a method for reducing the size of the Internet Key Exchange version 2 (IKEv2) CREATE_CHILD_SA exchanges used for rekeying of the IKE or Child SA by replacing the SA and TS payloads with a Notify Message payload. Reducing size and complexity of IKEv2 exchanges is especially useful for low power consumption battery powered devices.
- One-way Delay Measurement Based on Reference Delay (draft-li-ippm-ref-delay-measurement)
By Yang Li, Tao Sun, Hongwei Yang, Danyang Chen, Yali Wang, 2021-07-25 TXT HTML PDF
Abstract: The end-to-end network one-way delay is an important performance metric in the 5G network. For realizing the accurate one-way delay measurement, existing methods requires the end-to-end deployment of accurate clock synchronization mechanism, such as PTP or GPS, which results in relatively high deployment cost. Another method can derive the one-way delay from the round-trip delay. In this case, since the delay of the downlink and uplink of the 5G network may be asymmetric, the measurement accuracy is relatively low. Hence, this document introduces a method to measure the end-to-end network one- way delay based on a reference delay guaranteed by deterministic networking without clock synchronization.
- JOSE signed Voucher Artifacts for Bootstrapping Protocols (draft-richardson-anima-jose-voucher)
By Michael Richardson, Thomas Werner, 2021-06-23 TXT HTML PDF
Abstract: This document describes a serialiation of the RFC8366 voucher format to a JSON format is then signed using the JSON Object Signing and Encryption mechanism described in RFC7515.
- Deadline-aware Transport Protocol (draft-shi-quic-dtp)
By Yong Cui, Zhiwen Liu, Hang Shi, Jie Zhang, Kai Zheng, Wei Wang, 2021-07-25 TXT HTML PDF
Abstract: This document defines Deadline-aware Transport Protocol (DTP) to provide block-based deliver-before-deadline transmission. The intention of this memo is to describe a mechanism to fulfill unreliable transmission based on QUIC as well as how to enhance timeliness of data delivery.
- IPv4+ The Extended Protocol Based On IPv4 (draft-tang-ipv4plus)
By ZiQiang Tang, 2021-07-25 TXT HTML PDF
Abstract: This document specifies version 4+ of the Internet Protocol (IPv4+). IPv4 is very successful,simple and elegant. continuation and expansion of the IPv4 is necessary. Existing systems, devices only need to upgrade the software to support IPv4+, without the need to update new hardwares,saving investment costs. Ipv4+ is also an interstellar Protocol, so the Internet will evolve into a star Internet.
- IETF Network Slice Service YANG Model (draft-wd-teas-ietf-network-slice-nbi-yang)
By Bo Wu, Dhruv Dhody, Reza Rokui, Tarek Saad, Liuyan Han, 2021-07-25 TXT HTML PDF
Abstract: This document provides a YANG data model for the IETF Network Slice service model. The model can be used by a IETF Network Slice customer to manage IETF Network Slice from an IETF Network Slice Controller (NSC).
Expired Drafts
|
Drafts Sent to IESG
IESG Progress
- OSCORE Profile of the Authentication and Authorization for Constrained Environments Framework (draft-ietf-ace-oscore-profile): IESG Evaluation::AD Followup » Approved-announcement sent
By Francesca Palombini, Ludwig Seitz, Goeran Selander, Martin Gunnarsson, 2021-05-06 TXT HTML PDF
Abstract: This document specifies a profile for the Authentication and Authorization for Constrained Environments (ACE) framework. It utilizes Object Security for Constrained RESTful Environments (OSCORE) to provide communication security and proof-of-possession for a key owned by the client and bound to an OAuth 2.0 access token.
- Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension (draft-ietf-acme-dtnnodeid): AD Evaluation » ::Revised I-D Needed
By Brian Sipos, 2021-06-06 TXT HTML PDF
Abstract: This document specifies an extension to the Automated Certificate Management Environment (ACME) protocol which allows an ACME server to validate the Delay-Tolerant Networking (DTN) Node ID for an ACME client. The DTN Node ID is encoded as a certificate Subject Alternative Name (SAN) of type Uniform Resource Identifier (URI) and ACME Identifier type "uri".
- PIM Signaling Through BIER Core (draft-ietf-bier-pim-signaling): AD Evaluation::Revised I-D Needed » ::AD Followup
By Hooman Bidgoli, Fengman Xu, Jayant Kotalwar, IJsbrand Wijnands, Mankamana Mishra, Zhaohui Zhang, 2021-07-25 TXT HTML PDF
Abstract: Consider large networks deploying traditional PIM multicast service. Typically, each portion of these large networks have their own mandates and requirements. It might be desirable to deploy BIER technology in some part of these networks to replace traditional PIM services. In such cases downstream PIM states need to be signaled over the BIER Domain toward the source.
- DNS Query Name Minimisation to Improve Privacy (draft-ietf-dnsop-rfc7816bis): Waiting for AD Go-Ahead::AD Followup » IESG Evaluation
By Stephane Bortzmeyer, Ralph Dolmans, Paul Hoffman, 2021-07-02 TXT HTML PDF
Abstract: This document describes a technique called "QNAME minimisation" to improve DNS privacy, where the DNS resolver no longer always sends the full original QNAME and original QTYPE to the upstream name server. This document obsoletes RFC 7816.
- Building Protocols with HTTP (draft-ietf-httpbis-bcp56bis): In Last Call » Waiting for AD Go-Ahead
By Mark Nottingham, 2021-04-27 TXT HTML PDF
Abstract: Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet, but might be applicable in other situations.
- HTTP Caching (draft-ietf-httpbis-cache): Approved-announcement to be sent::Revised I-D Needed » ::AD Followup
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.
- HTTP/1.1 (draft-ietf-httpbis-messaging): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns.
- HTTP Semantics (draft-ietf-httpbis-semantics): IESG Evaluation::Revised I-D Needed » ::AD Followup
By Roy Fielding, Mark Nottingham, Julian Reschke, 2021-07-25 TXT HTML PDF
Abstract: The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.
- Registry Maintenance Notifications for the Extensible Provisioning Protocol (EPP) (draft-ietf-regext-epp-registry-maintenance): AD Evaluation::Revised I-D Needed » ::AD Followup
By Tobias Sattler, Roger Carney, Jody Kolker, 2021-07-25 TXT HTML PDF
Abstract: This document describes an Extensible Provision Protocol (EPP) extension called "Registry Maintenance Notification", used by EPP servers to notify EPP clients and allow EPP clients to query EPP servers on maintenance events.
Drafts Sent to RFC Editor
- Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE) (draft-ietf-ace-dtls-authorize): Approved-announcement sent » RFC Ed Queue
By Stefanie Gerdes, Olaf Bergmann, Carsten Bormann, Goeran Selander, Ludwig Seitz, 2021-06-04 TXT HTML PDF
Abstract: This specification defines a profile of the ACE framework that allows constrained servers to delegate client authentication and authorization. The protocol relies on DTLS version 1.2 for communication security between entities in a constrained network using either raw public keys or pre-shared keys. A resource- constrained server can use this protocol to delegate management of authorization information to a trusted host with less severe limitations regarding processing power and memory.
Other Status Changes
- JOSE signed Voucher Artifacts for Bootstrapping Protocols (draft-richardson-anima-jose-voucher): Active » Replaced by draft-ietf-anima-jws-voucher
By Michael Richardson, Thomas Werner, 2021-06-23 TXT HTML PDF
Abstract: This document describes a serialiation of the RFC8366 voucher format to a JSON format is then signed using the JSON Object Signing and Encryption mechanism described in RFC7515.
- Echo Request/Reply for Enabled In-situ OAM Capabilities (draft-xiao-ippm-ioam-conf-state): Active » Replaced by draft-ietf-ippm-ioam-conf-state
By Xiao Min, Greg Mirsky, Lei Bo, 2021-06-07 TXT HTML PDF
Abstract: This document describes an extension to the echo request/reply mechanisms used in IPv6, MPLS, SFC and BIER environments, which can be used within an IOAM domain, allowing the IOAM encapsulating node to acquire the enabled IOAM capabilities of each IOAM transit node and/or IOAM decapsulating node.
RFC Editor Status Changes
- DNS Zone Transfer-over-TLS (draft-ietf-dprive-xfr-over-tls): » AUTH48
By Willem Toorop, Sara Dickinson, Shivan Sahib, Pallavi Aras, Allison Mankin, 2021-05-27 TXT HTML PDF
Abstract: DNS zone transfers are transmitted in clear text, which gives attackers the opportunity to collect the content of a zone by eavesdropping on network connections. The DNS Transaction Signature (TSIG) mechanism is specified to restrict direct zone transfer to authorized clients only, but it does not add confidentiality. This document specifies the use of TLS, rather than clear text, to prevent zone content collection via passive monitoring of zone transfers: XFR-over-TLS (XoT). Additionally, this specification updates RFC1995 and RFC5936 with respect to efficient use of TCP connections, and RFC7766 with respect to the recommended number of connections between a client and server for each transport.
- Distribution of Traffic Engineering Extended Administrative Groups using BGP-LS (draft-ietf-idr-eag-distribution): » AUTH48
By Jeff Tantsura, Zitao Wang, Qin WU, Ketan Talaulikar, 2021-06-04 TXT HTML PDF
Abstract: Administrative groups are link attributes used for traffic engineering. This document defines an extension to BGP-LS for advertisement of extended administrative groups (EAGs).
IPR Disclosures
IESG/IAB/IAOC/Trust Minutes
Liaison Statements
Classified Ads
|
WGs marked with an 
