RFCs
Request for Comments series with full text and status metadata.
Latest records
Tiebreaking Resource Public Key Infrastructure (RPKI) Trust Anchors
Internet Engineering Task Force (IETF) J. Snijders Request for Comments: 10097 BSD Updates: 8630 T. Buehler Category: Standards Track OpenBSD ISSN: 2070-1721 T. de Kock RIPE NCC November 2026 Tiebreaking Resource Public Key Infrastructure (RPKI) Trust Anchors Abstract A Trust Anchor (TA) in the Resource Public Key Infrastructure (RPKI) is represented by a self-signed X.509 Certification Authority (CA) certificate. Over time, Relying Parties (RPs) may have acquired multiple different issuances of valid TA certificates from the same TA operator. This document specifies a tiebreaking scheme to be used by RPs to select one TA certificate for certification path validation. This document updates RFC 8630. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtaine
Clarifying Segment Routing over IPv6 (SRv6) Segment Identifier (SID) List Processing
Internet Engineering Task Force (IETF) A. Farrel Request for Comments: 10094 Old Dog Consulting Updates: 8754 S. Krishnan Category: Standards Track Cisco Systems, Inc. ISSN: 2070-1721 November 2026 Clarifying Segment Routing over IPv6 (SRv6) Segment Identifier (SID) List Processing Abstract Segment Routing over IPv6 (SRv6) is the instantiation of Segment Routing (SR) on the IPv6 data plane. Segments are indicated by Segment Identifiers (SIDs). SRv6 utilizes the Segment Routing Header (SRH), an IPv6 extension header that includes a SID list indicating the sequence of segments and any additional processing to be performed. This document updates RFC 8754 by clarifying the processing of SID list entries. It does not change any elements of the SRv6 architecture. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10094. Copyrig
Extension Registry for the Extensible Provisioning Protocol
Internet Engineering Task Force (IETF) S. Hollenbeck Request for Comments: 10091 Verisign Labs BCP: 248 November 2026 Obsoletes: 7451 Category: Best Current Practice ISSN: 2070-1721 Extension Registry for the Extensible Provisioning Protocol Abstract The Extensible Provisioning Protocol (EPP) includes features to add functionality by extending the protocol. It does not, however, describe how those extensions are maintained. This document describes a procedure for the registration and management of extensions to EPP, and it specifies a format for an IANA registry to record those extensions. This document obsoletes RFC 7451. Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10091. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is su
Extensible Provisioning Protocol (EPP) Transport over QUIC
Internet Engineering Task Force (IETF) J. Yao Request for Comments: 10087 H. Li Category: Standards Track M. Zhang ISSN: 2070-1721 CNNIC D. Keathley J. Gould VeriSign, Inc. November 2026 Extensible Provisioning Protocol (EPP) Transport over QUIC Abstract This document specifies how an Extensible Provisioning Protocol (EPP) session is mapped onto a QUIC connection. EPP over QUIC (EoQ) leverages features of the QUIC protocol. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10087. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to B
Composite Module-Lattice-Based Digital Signature Algorithm (ML-DSA) for Use in the Cryptographic Message Syntax (CMS)
Internet Engineering Task Force (IETF) M. Ounsworth Request for Comments: 10082 J. Gray Category: Standards Track Entrust ISSN: 2070-1721 J. Klaußner Bundesdruckerei GmbH D. Van Geest CryptoNext Security November 2026 Composite Module-Lattice-Based Digital Signature Algorithm (ML-DSA) for Use in the Cryptographic Message Syntax (CMS) Abstract The Composite Module-Lattice-Based Digital Signature Algorithm (ML- DSA) defines combinations of ML-DSA with RSA, ECDSA, and EdDSA. This document specifies the conventions for using Composite ML-DSA algorithms within the Cryptographic Message Syntax (CMS). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10082. Copyright
Updated Use of the Expires Message Header Field
Internet Engineering Task Force (IETF) B. Billon Request for Comments: 10080 Splio Updates: 4021 J. Levine Category: Standards Track Standcore LLC ISSN: 2070-1721 October 2026 Updated Use of the Expires Message Header Field Abstract This document allows broader use of the "Expires" message header field for mail messages. Message creators can then indicate when a message expires, while recipients can use this information to handle an expired message differently. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10080. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of th
Updates to the SFrame Cipher Suites Registry
Internet Engineering Task Force (IETF) R. Barnes Request for Comments: 10079 Cisco Updates: 9605 E. Omara Category: Standards Track A. Rosenberg ISSN: 2070-1721 Apple November 2026 Updates to the SFrame Cipher Suites Registry Abstract This document addresses two omissions in the Secure Frame (SFrame) protocol specification. First, the definition of the IANA "SFrame Cipher Suites" registry in RFC 9605 omits several important fields. This document updates the IANA registry by adding those fields and defining the contents of those fields for current entries. Second, the Authenticated Encryption with Associated Data (AEAD) construction based on AES-CTR and HMAC is defined only for the 128-bit security level. This document registers parallel constructions at the 256-bit security level. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how t
Problem Statement, Gap Analysis, and Requirements for Intra-Domain Source Address Validation
Internet Engineering Task Force (IETF) L. Qin Request for Comments: 10078 Zhongguancun Laboratory Category: Informational D. Li ISSN: 2070-1721 J. Wu Tsinghua University M. Huang Zhongguancun Laboratory N. Geng Huawei October 2026 Problem Statement, Gap Analysis, and Requirements for Intra-Domain Source Address Validation Abstract Source Address Validation (SAV) is an important means to mitigate IP source address spoofing (RFC 2827). This document analyzes the gaps in current operational mechanisms for intra-domain SAV. It also identifies the properties that new intra-domain SAV mechanisms are expected to provide. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved b
The SNAC Router Flag in ICMPv6 Router Advertisement Messages
Internet Engineering Task Force (IETF) J. Hui Request for Comments: 10075 Google LLC Category: Standards Track October 2026 ISSN: 2070-1721 The SNAC Router Flag in ICMPv6 Router Advertisement Messages Abstract This document defines a new flag, the SNAC Router flag, in the Router Advertisement message that can be used to distinguish configuration information sent by Stub Network Auto-Configuring (SNAC) routers from information sent by transit routers. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc10075. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with res
Composite Module-Lattice-Based Digital Signature Algorithm (ML-DSA) for Use in X.509 Public Key Infrastructure
Internet Engineering Task Force (IETF) M. Ounsworth Request for Comments: 10073 J. Gray Category: Standards Track Entrust ISSN: 2070-1721 M. Pala OpenCA Labs J. Klaußner Bundesdruckerei GmbH S. Fluhrer Cisco Systems November 2026 Composite Module-Lattice-Based Digital Signature Algorithm (ML-DSA) for Use in X.509 Public Key Infrastructure Abstract This document defines a PQ/T hybrid scheme with concrete instantiations that combine the US NIST Module-Lattice-Based Digital Signature Algorithm (ML-DSA) with traditional algorithms RSASSA- PKCS1-v1_5, RSASSA-PSS, ECDSA, Ed25519, and Ed448. These combinations are tailored to meet regulatory guidelines in certain regions. Composite ML-DSA is applicable in applications that use X.509 or PKIX data structures that accept ML-DSA, but where the operator wants extra protection against breaks or catastrophic bugs in ML-DSA and where the level of security provided by Existential Unforgeability under Chosen Message Attack (EUF-CMA) is acceptable. Status of This Memo This is an Internet S
Updates to OAuth 2.0 JSON Web Token (JWT) Client Authentication and Assertion-Based Authorization Grants
Internet Engineering Task Force (IETF) M.B. Jones Request for Comments: 10070 Self-Issued Consulting Updates: 7521, 7522, 7523, 9126 B. Campbell Category: Standards Track Ping Identity ISSN: 2070-1721 C. Mortimore Ticketmaster F. Skokan Okta November 2026 Updates to OAuth 2.0 JSON Web Token (JWT) Client Authentication and Assertion-Based Authorization Grants Abstract This document updates RFCs 7521, 7522, 7523, and 9126 with respect to the treatment of audience values in OAuth 2.0 Client Assertion Authentication and Assertion-based Authorization Grants to address a security vulnerability identified in the previous requirements for those audience values in multiple OAuth 2.0 specifications. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status
Managing Multiple Paths for a QUIC Connection
Internet Engineering Task Force (IETF) 刘彦梅 (Y. Liu), Ed. Request for Comments: 10069 Alibaba Inc. Category: Standards Track 马云飞 (Y. Ma) ISSN: 2070-1721 Harvey AI Q. De Coninck, Ed. University of Mons (UMONS) O. Bonaventure UCLouvain and WELRI C. Huitema Private Octopus Inc. M. Kühlewind, Ed. Ericsson November 2026 Managing Multiple Paths for a QUIC Connection Abstract This document specifies a multipath extension for the QUIC protocol to enable the simultaneous usage of multiple paths for a single connection. It introduces explicit path identifiers to create, delete, and manage multiple paths. This document does not specify address discovery or management, nor how applications using QUIC schedule traffic over multiple paths. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF com