RFC Publications

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

{
  "url": "https://www.rfc-editor.org/info/rfc10014/",
  "title": "Guidelines for Characterizing the Term \"OAM\"",
  "rfc_id": "RFC10014",
  "abstract": "As the IETF continues to produce and standardize different Operations, Administration, and Maintenance (OAM) protocols and technologies, various qualifiers and modifiers are prepended to the OAM abbreviation. While, at first glance, the most used qualifiers appear to be well understood, the same qualifier may be interpreted differently in different contexts. A case in point is the qualifiers \"in-band\" and \"out-of-band\", which have their origins in the radio lexicon, and which have been extrapolated into other communication networks. This document recommends not to use these two terms when referring to OAM. This document considers some common qualifiers and modifiers that are prepended, within the context of packet networks, to the OAM abbreviation and lays out guidelines for their use in I",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10014,
  "published_at": "2026-06-30T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10008/",
  "title": "The HTTP QUERY Method",
  "rfc_id": "RFC10008",
  "abstract": "This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe and idempotent manner and then respond with the result of that processing. This is similar to POST requests, but QUERY requests can be automatically repeated or restarted without concern for partial state changes.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10008,
  "published_at": "2026-06-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9888/",
  "title": "Out-of-Band Secure Telephone Identity Revisited (STIR) for Service Providers",
  "rfc_id": "RFC9888",
  "abstract": "The Secure Telephone Identity Revisited (STIR) framework defines means of carrying its Personal Assertion Tokens (PASSporTs) either in-band, within the headers of a Session Initiation Protocol (SIP) request, or out-of-band, through a service that stores PASSporTs for retrieval by relying parties. This specification defines a way that the out-of-band conveyance of PASSporTs can be used to support large service providers for cases in which in-band STIR conveyance is not universally available.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9888,
  "published_at": "2026-06-18T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9958/",
  "title": "Post-Quantum Cryptography for Engineers",
  "rfc_id": "RFC9958",
  "abstract": "The advent of a cryptographically relevant quantum computer (CRQC) would render state-of-the-art, traditional public key algorithms deployed today obsolete, as the mathematical assumptions underpinning their security would no longer hold. To address this, protocols and infrastructure must transition to post-quantum algorithms, which are designed to resist both traditional and quantum attacks. This document explains why engineers need to be aware of and understand post-quantum cryptography (PQC), and it details the impact of CRQCs on existing systems and the challenges involved in transitioning to post-quantum algorithms. Unlike previous cryptographic updates, this shift may require significant protocol redesign due to the unique properties of post-quantum algorithms.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9958,
  "published_at": "2026-06-18T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9985/",
  "title": "Optimizing Bidirectional Forwarding Detection (BFD) Authentication",
  "rfc_id": "RFC9985",
  "abstract": "This document describes an experimental optimization to Bidirectional Forwarding Detection (BFD) Authentication. This optimization enables BFD to scale better when there is a desire to use authentication where applying the same authentication mechanism to every BFD Control Packet may adversely impact performance. This optimization partitions BFD Authentication into a more computationally intensive (MCI) mechanism that is applied to BFD significant changes and a less computationally intensive (LCI) mechanism that is applied to the majority of BFD Control Packets.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9985,
  "published_at": "2026-06-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9986/",
  "title": "Meticulous Keyed ISAAC for Bidirectional Forwarding Detection (BFD) Optimized Authentication",
  "rfc_id": "RFC9986",
  "abstract": "This document describes a Bidirectional Forwarding Detection (BFD) Optimized Authentication Mode known as Meticulous Keyed ISAAC Authentication. This mode can be used to authenticate some BFD packets with less CPU time cost than using MD5 or SHA-1 with the trade-off of decreased security. This mechanism cannot be used to signal state changes, but it can be used to maintain a session in the Up state.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9986,
  "published_at": "2026-06-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc10008/",
  "title": "The HTTP QUERY Method",
  "rfc_id": "RFC10008",
  "abstract": "This specification defines the QUERY method for HTTP. A QUERY requests that the request target process the enclosed content in a safe and idempotent manner and then respond with the result of that processing. This is similar to POST requests, but QUERY requests can be automatically repeated or restarted without concern for partial state changes.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 10008,
  "published_at": "2026-06-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9984/",
  "title": "YANG Groupings for UDP Clients and UDP Servers",
  "rfc_id": "RFC9984",
  "abstract": "This document presents two YANG 1.1 modules with reusable groupings for managing UDP clients and UDP servers.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9984,
  "published_at": "2026-06-15T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9998/",
  "title": "Report from the IAB/W3C Workshop on Age-Based Restrictions on Content Access",
  "rfc_id": "RFC9998",
  "abstract": "The Workshop on Age-Based Restrictions on Content Access was convened by the Internet Architecture Board (IAB) and World Wide Web Consortium (W3C) in October 2025. This report summarizes the significant points of discussion and identifies topics that may warrant further consideration and work. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB or W3C views and positions.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9998,
  "published_at": "2026-06-15T00:00:00.000Z"
}