RFC Publications

{
  "url": "https://www.rfc-editor.org/info/rfc9851/",
  "title": "TLS 1.2 is in Feature Freeze",
  "rfc_id": "RFC9851",
  "abstract": "Use of TLS 1.3, which fixes some known deficiencies in TLS 1.2, is growing. This document specifies that no changes will be approved for TLS 1.2 outside of urgent security fixes (as determined by TLS Working Group consensus), new TLS Exporter Labels, and new Application-Layer Protocol Negotiation (ALPN) Protocol IDs. This applies to TLS only; it does not apply to DTLS (in any DTLS version).",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9851,
  "published_at": "2026-07-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9954/",
  "title": "Hybrid Key Exchange in TLS 1.3",
  "rfc_id": "RFC9954",
  "abstract": "Hybrid key exchange refers to using multiple key exchange algorithms simultaneously and combining the result with the goal of providing security even if a way is found to defeat the encryption for all but one of the component algorithms. It is motivated by the transition to post-quantum cryptography. This document provides a construction for hybrid key exchange in the Transport Layer Security (TLS) protocol version 1.3.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9954,
  "published_at": "2026-07-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9973/",
  "title": "TLS 1.3 Extension for Using Certificates with an External Pre-Shared Key",
  "rfc_id": "RFC9973",
  "abstract": "This document specifies a TLS 1.3 extension that allows TLS clients and servers to authenticate with certificates and provide confidentiality based on encryption with a symmetric key from the usual key agreement algorithm and an external pre-shared key (PSK). This Standards Track RFC obsoletes RFC 8773, which was an Experimental RFC.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9973,
  "published_at": "2026-07-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9916/",
  "title": "Updates to the Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)",
  "rfc_id": "RFC9916",
  "abstract": "Section 3.4 of RFC 8253 specifies TLS connection establishment restrictions for PCEPS; PCEPS refers to usage of TLS to provide a secure transport for the Path Computation Element Communication Protocol (PCEP). This document adds restrictions to specify what PCEPS implementations do if they support more than one version of the TLS protocol and to restrict the use of TLS 1.3's early data.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9916,
  "published_at": "2026-07-14T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9918/",
  "title": "Updates to Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication",
  "rfc_id": "RFC9918",
  "abstract": "RFC 7589 defines how to protect Network Configuration Protocol (NETCONF) messages with TLS 1.2. This document updates RFC 7589 to update support requirements for TLS 1.2 and add TLS 1.3 support requirements, including restrictions on the use of TLS 1.3's early data.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9918,
  "published_at": "2026-07-14T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9919/",
  "title": "The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments",
  "rfc_id": "RFC9919",
  "abstract": "This specification defines a profile of the Online Certificate Status Protocol (OCSP) that addresses the scalability issues inherent when using OCSP in large scale (high volume) Public Key Infrastructure (PKI) environments and/or in PKI environments that require a lightweight solution to minimize communication bandwidth and client- side processing. This specification obsoletes RFC 5019. The profile specified in RFC 5019 has been updated to allow and recommend the use of SHA-256 over SHA-1.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9919,
  "published_at": "2026-07-14T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9933/",
  "title": "Carrying SR-Algorithm in Path Computation Element Communication Protocol (PCEP)",
  "rfc_id": "RFC9933",
  "abstract": "This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) to enhance support for Segment Routing (SR) with a focus on the use of Segment Identifiers (SIDs) and SR-Algorithms in Traffic Engineering (TE). The SR-Algorithm associated with a SID defines the path computation algorithm used by Interior Gateway Protocols (IGPs). It introduces mechanisms for PCEP peers to signal the SR-Algorithm associated with SIDs by encoding this information in Explicit Route Object (ERO) and Record Route Object (RRO) subobjects, enables SR-Algorithm constraints for path computation, and defines new metric types for the METRIC object. This document updates RFC 8664 and RFC 9603 to allow such extensions.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9933,
  "published_at": "2026-07-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9995/",
  "title": "CBOR Object Signing and Encryption (COSE) Hash Envelope",
  "rfc_id": "RFC9995",
  "abstract": "This document defines new CBOR Object Signing and Encryption (COSE) header parameters for signaling a payload as an output of a hash function. This mechanism enables faster validation, as access to the original payload is not required for signature validation. Additionally, hints of the hashed payload's content format and availability are defined, providing references to optional discovery mechanisms that can help to find the original payload content.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9995,
  "published_at": "2026-07-13T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9999/",
  "title": "Remote ATtestation procedureS (RATS) Conceptual Message Wrapper (CMW)",
  "rfc_id": "RFC9999",
  "abstract": "The conceptual messages introduced by the Remote ATtestation procedureS (RATS) architecture (RFC 9334) are protocol-agnostic data units that are conveyed between RATS roles during RATS interactions. Conceptual messages describe the meaning and function of such data units within RATS data flows without specifying a wire format, encoding, transport mechanism, or processing details. The initial set of conceptual messages is defined in Section 8 of RFC 9334 and includes Evidence, Attestation Results, Endorsements, Reference Values, and Appraisal Policies. This document introduces the Conceptual Message Wrapper (CMW) that provides a common structure to encapsulate these messages. It defines a dedicated Concise Binary Object Representation (CBOR) tag, corresponding JSON Web Token (JWT) and CBOR ",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9999,
  "published_at": "2026-07-14T00:00:00.000Z"
}

{
  "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"
}