RFC Publications

{
  "url": "https://www.rfc-editor.org/info/rfc9997/",
  "title": "YANG-CBOR: Allocating SID Ranges for Private Enterprise Number (PEN) Holders",
  "rfc_id": "RFC9997",
  "abstract": "YANG-CBOR (RFC 9254, \"Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)\") defines YANG Schema Item iDentifiers (YANG SIDs), globally unique 63-bit unsigned integers used to identify YANG items. RFC 9595 (\"YANG Schema Item iDentifier (YANG SID)\") defines ways to allocate these SIDs using IANA registries. The present specification employs these SID allocation mechanisms to allocate ranges of 100 000 SIDs (representation size 64 bits) to each holder of an IANA Private Enterprise Number (PEN) of a value below 1 000 000. Holders of PENs of values smaller than 100 000 are also allocated ranges of 10 000 SIDs (representation size 32 bits).",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9997,
  "published_at": "2026-07-23T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10026/",
  "title": "Operational Recommendations for DNSSEC Delegation Signer (DS) Automation",
  "rfc_id": "RFC10026",
  "abstract": "Enabling support for automatic acceptance of DNSSEC Delegation Signer (DS) parameters from the Child DNS operator (via RFCs 7344, 8078, and 9615) requires the Parental Agent, often a registry or registrar, to make a number of technical decisions around acceptance checks, error and success reporting, and multi-party issues such as concurrent updates. This document describes recommendations about how these points are best addressed in practice.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10026,
  "published_at": "2026-07-23T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10002/",
  "title": "Certificate Management over CMS (CMC)",
  "rfc_id": "RFC10002",
  "abstract": "This document defines the base syntax for CMC, a Certificate Management protocol using the Cryptographic Message Syntax (CMS). This protocol addresses two immediate needs within the Internet Public Key Infrastructure (PKI) community: CMC also requires the use of the transport document (RFC 10003) and the requirements usage document (RFC 10004) along with this document for a full definition. This document obsoletes RFCs 5272 and 6402.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10002,
  "published_at": "2026-07-17T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10003/",
  "title": "Certificate Management over CMS (CMC): Transport Protocols",
  "rfc_id": "RFC10003",
  "abstract": "This document defines a number of transport mechanisms that are used to move Certificate Management over CMS (CMC) messages. The transport mechanisms described in this document are HTTP, file, mail, and TCP. This document obsoletes RFCs 5273 and 6402.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10003,
  "published_at": "2026-07-17T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10004/",
  "title": "Certificate Management over CMS (CMC): Compliance Requirements",
  "rfc_id": "RFC10004",
  "abstract": "This document provides a set of compliance statements about the Certificate Management over CMS (CMC) enrollment protocol. The ASN.1 structures and the transport mechanisms for the CMC enrollment protocol are covered in other documents (RFCs 10002 and 10003). This document provides the information needed to make a compliant version of CMC. This document obsoletes RFCs 5274 and 6402.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10004,
  "published_at": "2026-07-17T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9852/",
  "title": "New Protocols Using TLS Must Require TLS 1.3",
  "rfc_id": "RFC9852",
  "abstract": "TLS 1.3 is widely used, has had comprehensive security proofs, and improves both security and privacy deficiencies in TLS 1.2. Therefore, new protocols that use TLS must require TLS 1.3. As DTLS 1.3 is not widely available or deployed, this prescription does not pertain to DTLS (in any DTLS version); it pertains to TLS only. This document updates RFC 9325. It discusses post-quantum cryptography and the security and privacy improvements in TLS 1.3 as the rationale for the update.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9852,
  "published_at": "2026-07-16T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9955/",
  "title": "Hybrid Signature Spectrums",
  "rfc_id": "RFC9955",
  "abstract": "This document describes classification of design goals and security considerations for hybrid digital signature schemes, including proof composability, non-separability of the component signatures given a hybrid signature, backwards and forwards compatibility, hybrid generality, and Simultaneous Verification (SV).",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9955,
  "published_at": "2026-07-16T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10015/",
  "title": "Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2",
  "rfc_id": "RFC10015",
  "abstract": "For (D)TLS 1.2, this document deprecates the use of two key exchanges, namely Diffie-Hellman (DH) over a finite field and RSA. It also discourages the use of static Elliptic Curve Diffie-Hellman (ECDH) cipher suites. These prescriptions apply only to (D)TLS 1.2, since (D)TLS 1.0 and TLS 1.1 are deprecated by RFC 8996 and (D)TLS 1.3 either does not use the affected algorithms or does not share the relevant configuration options. (There is no DTLS version 1.1.) This document updates RFCs 4162, 4279, 4346, 4785, 5246, 5288, 5289, 5469, 5487, 5932, 6209, 6347, 6367, 6655, 7905, 8422, and 9325 to either deprecate or discourage the use of cipher suites using the above key exchange methods in (D)TLS 1.2 connections.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10015,
  "published_at": "2026-07-16T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9850/",
  "title": "The SSLKEYLOGFILE Format for TLS",
  "rfc_id": "RFC9850",
  "abstract": "This document describes a format that supports logging information about the secrets used in a TLS connection. Recording secrets to a file in SSLKEYLOGFILE format allows diagnostic and logging tools that use this file to decrypt messages exchanged by TLS endpoints. This format is intended for use in systems where TLS only protects test data.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9850,
  "published_at": "2026-07-15T00:00:00.000Z"
}

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