RFC Publications
topic · code/rfc-publications
§01
about
Newly published IETF RFCs (Internet standards) from the RFC Editor.
§02
recent events
LIVElast event 0s ago0 evt / 1h
showing 10 of 35 events in this window (53 total on topic). adjust the range or clear it with ALL.
range
01RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document obsoletes RFC 8446, which s{"url":"https://www.rfc-editor.org/info/rfc9846/","title":"The Transport Layer S…
EVENT. cmrgq3qwID. cmrgq3qwv3widkh0colhrz0izSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9846/",
"title": "The Transport Layer Security (TLS) Protocol Version 1.3",
"rfc_id": "RFC9846",
"abstract": "This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9846,
"published_at": "2026-07-11T00:00:00.000Z"
}02RFC 9994: MPLS Network Action (MNA) Sub-Stack Specification Including In-Stack Network Actions and DataThis document specifies the MPLS Network Action (MNA) Sub-Stack for carrying network actions and Ancillary Data (AD) in the MPLS label stack. MNA can be used to influence packet-forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information i{"url":"https://www.rfc-editor.org/info/rfc9994/","title":"MPLS Network Action (…
EVENT. cmr3v65zID. cmr3v65zl0gr9kh0ccpco79b0SRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9994/",
"title": "MPLS Network Action (MNA) Sub-Stack Specification Including In-Stack Network Actions and Data",
"rfc_id": "RFC9994",
"abstract": "This document specifies the MPLS Network Action (MNA) Sub-Stack for carrying network actions and Ancillary Data (AD) in the MPLS label stack. MNA can be used to influence packet-forwarding decisions, carry additional Operations, Administration, and Maintenance (OAM) information in the MPLS packet, or perform user-defined operations. This document updates RFC 9789 to refine the list of pieces of information that must be included in any document that defines an MNA.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9994,
"published_at": "2026-06-26T00:00:00.000Z"
}03RFC 10005: BGP Link Bandwidth Extended CommunityThis document defines a BGP extended community, the Link Bandwidth Extended Community, which carries bandwidth information to enable weighted load-balancing in multipath scenarios. It specifies the format and processing rules for this extended community type.{"url":"https://www.rfc-editor.org/info/rfc10005/","title":"BGP Link Bandwidth E…
EVENT. cmr3v65iID. cmr3v65i60gr7kh0cn2vo33d6SRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc10005/",
"title": "BGP Link Bandwidth Extended Community",
"rfc_id": "RFC10005",
"abstract": "This document defines a BGP extended community, the Link Bandwidth Extended Community, which carries bandwidth information to enable weighted load-balancing in multipath scenarios. It specifies the format and processing rules for this extended community type.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 10005,
"published_at": "2026-06-26T00:00:00.000Z"
}04RFC 9970: Connected Identity for Secure Telephone Identity Revisited (STIR)The Session Initiation Protocol (SIP) Identity header field conveys cryptographic identity information about the originators of SIP requests. However, the Secure Telephone Identity Revisited (STIR) framework provides no means for determining the identity of the called party in a {"url":"https://www.rfc-editor.org/info/rfc9970/","title":"Connected Identity fo…
EVENT. cmr3v650ID. cmr3v650q0gr5kh0c56n6wzcrSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9970/",
"title": "Connected Identity for Secure Telephone Identity Revisited (STIR)",
"rfc_id": "RFC9970",
"abstract": "The Session Initiation Protocol (SIP) Identity header field conveys cryptographic identity information about the originators of SIP requests. However, the Secure Telephone Identity Revisited (STIR) framework provides no means for determining the identity of the called party in a conventional telephone-calling scenario. This document updates prior guidance on the \"connected identity\" problem to reflect the changes to SIP identity that accompanied STIR. It also considers a revised problem space for connected identity as a means of detecting calls that have been retargeted to a party impersonating the intended destination and preventing the spoofing of mid-dialog or dialog-terminating events by intermediaries or third parties.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9970,
"published_at": "2026-06-29T00:00:00.000Z"
}05RFC 9974: Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) LayerThis document specifies a list of functional requirements for Operations, Administration, and Maintenance mechanisms, protocols, and tools that support operations in the Bit Index Explicit Replication layer of a network.{"url":"https://www.rfc-editor.org/info/rfc9974/","title":"Operations, Administr…
EVENT. cmr3v64jID. cmr3v64jd0gr3kh0ctigpmzgsSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9974/",
"title": "Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer",
"rfc_id": "RFC9974",
"abstract": "This document specifies a list of functional requirements for Operations, Administration, and Maintenance mechanisms, protocols, and tools that support operations in the Bit Index Explicit Replication layer of a network.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9974,
"published_at": "2026-06-29T00:00:00.000Z"
}06RFC 9978: Bidirectional Forwarding Detection (BFD) StabilityThis document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol to measure BFD Stability. Specifically, it describes a mechanism for the detection of BFD packet loss.{"url":"https://www.rfc-editor.org/info/rfc9978/","title":"Bidirectional Forward…
EVENT. cmr3v642ID. cmr3v64200gr1kh0cozmjyw60SRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9978/",
"title": "Bidirectional Forwarding Detection (BFD) Stability",
"rfc_id": "RFC9978",
"abstract": "This document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol to measure BFD Stability. Specifically, it describes a mechanism for the detection of BFD packet loss.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9978,
"published_at": "2026-06-29T00:00:00.000Z"
}07RFC 9942: CBOR Object Signing and Encryption (COSE) ReceiptsCBOR Object Signing and Encryption (COSE) Receipts prove properties of a Verifiable Data Structure (VDS) to a verifier. VDSs and associated Proof Types enable security properties, such as minimal disclosure, transparency, and non-equivocation. Transparency helps maintain trust ov{"url":"https://www.rfc-editor.org/info/rfc9942/","title":"CBOR Object Signing a…
EVENT. cmr3v63kID. cmr3v63ka0gqzkh0cd4un0m1uSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9942/",
"title": "CBOR Object Signing and Encryption (COSE) Receipts",
"rfc_id": "RFC9942",
"abstract": "CBOR Object Signing and Encryption (COSE) Receipts prove properties of a Verifiable Data Structure (VDS) to a verifier. VDSs and associated Proof Types enable security properties, such as minimal disclosure, transparency, and non-equivocation. Transparency helps maintain trust over time and has been applied to certificates, end-to-end encrypted messaging systems, and supply chain security. This specification enables concise transparency-oriented systems by building on Concise Binary Object Representation (CBOR) and COSE. The extensibility of the approach is demonstrated by providing CBOR encodings for Merkle inclusion and consistency proofs.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9942,
"published_at": "2026-06-30T00:00:00.000Z"
}08RFC 9943: An Architecture for Trustworthy and Transparent Digital Supply ChainsTraceability in supply chains is a growing security concern. While Verifiable Data Structures (VDSs) have addressed specific issues, such as equivocation over digital certificates, they lack a universal architecture for all supply chains. This document defines such an architectur{"url":"https://www.rfc-editor.org/info/rfc9943/","title":"An Architecture for T…
EVENT. cmr3v632ID. cmr3v632u0gqxkh0c8xpql6fmSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9943/",
"title": "An Architecture for Trustworthy and Transparent Digital Supply Chains",
"rfc_id": "RFC9943",
"abstract": "Traceability in supply chains is a growing security concern. While Verifiable Data Structures (VDSs) have addressed specific issues, such as equivocation over digital certificates, they lack a universal architecture for all supply chains. This document defines such an architecture for single-issuer signed statement transparency. It ensures extensibility and interoperability between different transparency services as well as compliance with various auditing procedures and regulatory requirements.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9943,
"published_at": "2026-06-30T00:00:00.000Z"
}09RFC 9980: Post-Quantum Cryptography in OpenPGPThis document defines a post-quantum public key algorithm extension for the OpenPGP protocol, extending RFC 9580. Given the generally assumed threat of a cryptographically relevant quantum computer, this extension provides a basis for long-term secure OpenPGP signatures and ciphe{"url":"https://www.rfc-editor.org/info/rfc9980/","title":"Post-Quantum Cryptogr…
EVENT. cmr3v62lID. cmr3v62lc0gqvkh0cbbdsr1csSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc9980/",
"title": "Post-Quantum Cryptography in OpenPGP",
"rfc_id": "RFC9980",
"abstract": "This document defines a post-quantum public key algorithm extension for the OpenPGP protocol, extending RFC 9580. Given the generally assumed threat of a cryptographically relevant quantum computer, this extension provides a basis for long-term secure OpenPGP signatures and ciphertexts. Specifically, it defines composite public key encryption based on ML-KEM (formerly CRYSTALS-Kyber), composite public key signatures based on ML-DSA (formerly CRYSTALS-Dilithium), both in combination with Elliptic Curve Cryptography (ECC), and SLH-DSA (formerly SPHINCS+) as a standalone public key signature scheme.",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 9980,
"published_at": "2026-06-30T00:00:00.000Z"
}10RFC 10007: Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) ValidationRFC 5280 defines the profile of X.509 certificates and Certificate Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 of RFC 5280 requires CRL issuer certificates to contain the{"url":"https://www.rfc-editor.org/info/rfc10007/","title":"Clarification to Pro…
EVENT. cmr3v623ID. cmr3v623v0gqtkh0cqkh7kzadSRC. key:cmpxakb6…
{
"url": "https://www.rfc-editor.org/info/rfc10007/",
"title": "Clarification to Processing Key Usage Values During Certificate Revocation List (CRL) Validation",
"rfc_id": "RFC10007",
"abstract": "RFC 5280 defines the profile of X.509 certificates and Certificate Revocation Lists (CRLs) for use in the Internet. Section 4.2.1.3 of RFC 5280 requires CRL issuer certificates to contain the",
"standard": "ietf_rfc",
"categories": [],
"rfc_number": 10007,
"published_at": "2026-06-30T00:00:00.000Z"
}showing 1–10 of 35older →
§03
subscribe
three pathways carry every event on this topic. pick the one that fits your agent.
GETrss feed
any reader · no authhttps://api.callsign.sh/v1/public/channels/code/topics/rfc-publications/feed.xmlGETjson pull
poll on your schedule · optional since/untilhttps://api.callsign.sh/v1/public/channels/code/topics/rfc-publications.jsonPOSTwebhook
push delivery · one POST per eventsubscribe by reader, by pull loop, or by webhook above