RFC Publications

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

{
  "url": "https://www.rfc-editor.org/info/rfc9992/",
  "title": "Routing in Fat Trees (RIFT) Key/Value Topology Information Elements Structure and Processing",
  "rfc_id": "RFC9992",
  "abstract": "The Routing in Fat Trees (RIFT) protocol allows for key/value pairs to be advertised within Key-Value Topology Information Elements (KV TIEs). The data contained within these KV TIEs can be used for any imaginable purpose. This document specifies behavior for the various Key Types (i.e., Well-Known, Organizationally Unique Identifier (OUI), and Experimental) and a method to structure corresponding values. It also defines a Well-Known Key Sub-Type used for testing tie-breaking behavior.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9992,
  "published_at": "2026-06-10T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9965/",
  "title": "The eap.arpa. Domain and Extensible Authentication Protocol (EAP) Provisioning",
  "rfc_id": "RFC9965",
  "abstract": "This document defines the eap.arpa. domain for use only in Network Access Identifiers (NAIs) as a way for Extensible Authentication Protocol (EAP) peers to signal to EAP servers that they wish to obtain limited, and unauthenticated, network access. EAP peers signal which kind of access is required via certain predefined identifiers that use the NAI format of RFC 7542. A table of identifiers and meanings is defined, which includes entries for RFC 9140. This document updates RFCs 5216 and 9190 to define an unauthenticated provisioning method. Those specifications suggest that such a method is possible, but they do not define how it would be done. This document also updates RFC 9140 to deprecate \"eap-noob.arpa\" and replace it with \"@noob.eap.arpa\".",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9965,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9969/",
  "title": "Report from the IAB Workshop on AI-CONTROL",
  "rfc_id": "RFC9969",
  "abstract": "The AI-CONTROL Workshop was convened by the Internet Architecture Board (IAB) in September 2024. This report summarizes its 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 views and positions.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9969,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9972/",
  "title": "Advanced BGP Monitoring Protocol (BMP) Statistics Types",
  "rfc_id": "RFC9972",
  "abstract": "The BGP Monitoring Protocol (BMP) described in RFC 7854 defines statistics message types to observe events that occur on a monitored router. This document defines new statistics types to monitor BMP Adj-RIB-In and Adj-RIB-Out Routing Information Bases (RIBs).",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9972,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9983/",
  "title": "OSPFv2 Anycast Property Advertisement",
  "rfc_id": "RFC9983",
  "abstract": "An IP prefix may be configured as anycast and, as such, the same value can be advertised by multiple routers. It is useful for other routers to know that the advertisement is for an anycast prefix. This document defines a new flag in the OSPFv2 Extended Prefix TLV Flags to advertise the anycast property. The document also specifies a companion YANG module for managing this function.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9983,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9989/",
  "title": "Domain-Based Message Authentication, Reporting, and Conformance (DMARC)",
  "rfc_id": "RFC9989",
  "abstract": "This document describes the Domain-based Message Authentication, Reporting, and Conformance (DMARC) protocol. DMARC permits the owner of an email's Author Domain to enable validation of the domain's use to indicate the Domain Owner's or Public Suffix Operator's message handling preference regarding failed validation and to request reports about the use of the domain name. Mail-receiving organizations can use this information when evaluating handling choices for incoming mail. This document obsoletes RFCs 7489 and 9091.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9989,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9990/",
  "title": "Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting",
  "rfc_id": "RFC9990",
  "abstract": "Domain-based Message Authentication, Reporting, and Conformance (DMARC) allows for Domain Owners to request aggregate reports from receivers. This report is an XML document and contains extensible elements that allow for other types of data to be specified later. The aggregate reports can be submitted by the receiver to the Domain Owner's specified destination as declared in the associated DNS record. This document obsoletes RFC 7489.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9990,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9991/",
  "title": "Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting",
  "rfc_id": "RFC9991",
  "abstract": "Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism by which a Domain Owner can request feedback about email messages using their domain in the From: address field. This document describes \"failure reports\", or \"failed message reports\", which provide details about individual messages that failed to authenticate according to the DMARC mechanism. This document updates RFC 6591 and obsoletes RFC 7489.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9991,
  "published_at": "2026-05-19T00:00:00.000Z"
}

{
  "url": "https://www.rfc-editor.org/info/rfc9966/",
  "title": "Bootstrapped TLS Authentication with Proof of Knowledge",
  "rfc_id": "RFC9966",
  "abstract": "This document defines a mechanism that enables a bootstrapping device to establish trust and mutually authenticate against a TLS server. Bootstrapping devices have a public/private key pair; this mechanism enables a TLS server to prove to the device that it knows the public key and enables the device to prove to the TLS server that it knows the private key. The mechanism leverages existing Device Provisioning Profile (DPP) and TLS standards and can be used in an Extensible Authentication Protocol (EAP) exchange with an EAP server.",
  "standard": "ietf_rfc",
  "categories": [],
  "rfc_number": 9966,
  "published_at": "2026-05-26T00:00:00.000Z"
}