ietf-announce archive shows no announcements after 2026-08-19; there are no newly published RFCs in the 48-hour window (2026-08-22 to 2026-08-24). The most recent RFC announcements were RFC 10030, RFC 10031, and RFC 9971 on 2026-08-14.By its name, this individual submission defines initial registry entries for the service metrics used in Computing-Aware Traffic Steering (CATS). CATS steers each flow toward the most appropriate computing service instance based on both network conditions and computing-resource state, which only works if all parties share a common vocabulary of well-defined metric identifiers. The draft most likely enumerates concrete metric entries — such as load, capacity, or latency indicators — and the IANA procedures for allocating new ones. This is a new -00 revision; the summary is derived from the document name because the official abstract could not be retrieved on this run.
By its name, this individual, TEAS-related draft describes RSVP-TE signaling extensions for Segment Routing over IPv6 (SRv6). It probably specifies how the classic RSVP-TE control plane can establish and control traffic-engineered paths whose data plane is built from SRv6 SIDs, bridging established traffic engineering with an SRv6 forwarding substrate. Typical content would be new RSVP objects or sub-objects that carry SRv6 segment information along a signaled path. New -00 revision; the description is inferred from the name because the official abstract was not retrieved.
By its name, this MPLS Working Group document defines extensions to MPLS Fast Reroute (FRR). Fast Reroute provides local protection so that traffic can be diverted around a failed link or node within tens of milliseconds while the rest of the network reconverges. These extensions likely refine how backup paths are signaled, selected, or scoped in current MPLS deployments. As a new -00 working group draft it marks the adoption of this work item; the summary is based on the name because the official abstract could not be fetched.
By its name, this individual draft proposes an “autonomy governor” — most plausibly a control mechanism that bounds or supervises the autonomous behavior of automated or AI-driven agents acting on a network. The document probably outlines the policies, limits, or enforcement point that keep autonomous actions within agreed constraints. This is revision -01. The description is inferred from the title because the official abstract was not available on this run and should be confirmed later.
By its name, this individual draft concerns establishing a “verified human root” — a trust anchor or attestation that a human, rather than an automated agent, sits at the origin of an identity or action chain. Given growing interest in separating human from machine actors online, it likely defines a verification model or root-of-trust construct for human presence. Revision -01; the summary is derived from the title because the abstract could not be retrieved on this run.
By its name, this OAuth Working Group document addresses metadata remediation for Rich Authorization Requests (RAR). RAR (RFC 9396) lets clients express fine-grained authorization details through the authorization_details parameter, and authorization servers advertise their support via metadata. This draft probably corrects or clarifies how that RAR-related metadata is published and interpreted, remediating gaps or inconsistencies surfaced in deployment. New -00 working group revision; the description is based on the name because the official abstract was not fetched.
By its name, this individual draft describes discovery of “x402” resources via DNS. x402 refers to payment-oriented interactions built around the HTTP 402 “Payment Required” status, and DNS-based discovery would let clients locate the relevant endpoints or metadata through DNS records such as TXT entries. A parallel draft by another author (draft-jeftovic-x402-dns-discovery) explores the same space. Revisions -02 and -03 both appear in this window; the summary is inferred from the name because the official abstract could not be retrieved.
By its name, this individual draft relates to SCITT (Supply Chain Integrity, Transparency and Trust) and concerns “disclosure evidence” — most likely a way to represent and convey verifiable evidence about what has been disclosed for a software or supply-chain artifact. It probably builds on SCITT’s transparency-service and signed-statement model to attach, register, or query such disclosure records. Revision -07; the description is derived from the name because the official abstract was not available on this run.
This CFRG (Crypto Forum Research Group) document specifies extensions to existing digital signature schemes that support key blinding. With key blinding, a blinded public key and every signature produced under the blinded key pair are independent of the underlying unblinded key pair, so an observer cannot link them back to it. Signatures made with blinded keys are also indistinguishable from ordinary signatures. The technique enables privacy-preserving applications such as Tor onion services and privacy-preserving airdrops for bootstrapping cryptocurrency systems. This is revision -11 of the research-group draft.
By its name, this draft deals with handshake-failure handling — most plausibly the signaling or diagnosis of failed cryptographic or protocol handshakes, for example in TLS or a comparable security handshake. It likely defines how endpoints report, classify, or respond to a handshake that does not complete successfully. Revisions -10 and -11 both appear within this window. The summary is inferred from the name because the official abstract could not be retrieved; the precise protocol scope should be confirmed on a later run.
By its name, this draft deals with handshake-failure handling — most plausibly the signaling or diagnosis of failed cryptographic or protocol handshakes, for example in TLS or a comparable security handshake. It likely defines how endpoints report, classify, or respond to a handshake that does not complete successfully. Revisions -10 and -11 both appear within this window. The summary is inferred from the name because the official abstract could not be retrieved; the precise protocol scope should be confirmed on a later run.
By its name, this individual draft describes discovery of “x402” resources via DNS. x402 refers to payment-oriented interactions built around the HTTP 402 “Payment Required” status, and DNS-based discovery would let clients locate the relevant endpoints or metadata through DNS records such as TXT entries. A parallel draft by another author (draft-jeftovic-x402-dns-discovery) explores the same space. Revisions -02 and -03 both appear in this window; the summary is inferred from the name because the official abstract could not be retrieved.
This document specifies a DKIM (RFC 6376) extension that allows cryptographic verification of SMTP (RFC 5321) envelope data, and of DKIM signatures prior to changes made to the RFC 5322 message content along the delivery path, thereby addressing security gaps and enabling email solutions that move complexity away from lower network layers where such problems cannot be solved. It also updates DKIM to obsolete aspects that experience has shown to be superfluous, incomplete, or outdated. The authors frame it as a forward-looking foundation — “the future of email for email of the future.” This is revision -13.
By its name, this individual draft defines “SCSWP,” an acronym that is not self-explanatory from the title alone, so its exact scope is uncertain. It is authored outside any working group and appears here as both a new -00 and a -01 revision on the same day. Without the official abstract the subject cannot be stated reliably; this entry will be grounded once the abstract can be fetched on a later run.
By its name, this individual draft defines “SCSWP,” an acronym that is not self-explanatory from the title alone, so its exact scope is uncertain. It is authored outside any working group and appears here as both a new -00 and a -01 revision on the same day. Without the official abstract the subject cannot be stated reliably; this entry will be grounded once the abstract can be fetched on a later run.
By its name, this individual SCITT-related draft addresses “derived subjects” — most likely how the subject identifiers of supply-chain artifacts are derived from, or related to, one another within a transparency service. It appears to complement SCITT’s model of signed statements made about subjects. New -00 revision; the description is inferred from the name because the official abstract was not fetched on this run.
By its name, this individual draft proposes a “structured value model” — a general way to represent structured data values, plausibly for reuse across other specifications by the same author. Its precise application domain is not clear from the title alone. New -00 revision; the summary is derived from the name and should be confirmed against the official abstract on a later run.
By its name, this individual draft describes methods for comparing “derived identifiers” — identifiers computed from some underlying data — to determine equivalence or linkage between them. It appears related to the same author’s work on derived subjects and a structured value model. New -00 revision; the description is inferred from the title because the official abstract could not be retrieved.
By its name, this individual draft sets out an architecture for “PRP.” The acronym is ambiguous — it could denote a Parallel Redundancy Protocol or something else entirely — so the exact subject is uncertain without the abstract. As an architecture document it most likely defines the relevant components, roles, and their relationships. New -00 revision; this tentative summary will be grounded once the official abstract becomes available.
By its name, this SSHM (SSH Maintenance) Working Group document specifies the use of composite signatures in the Secure Shell (SSH) protocol. Composite signatures combine a traditional algorithm with a post-quantum one so that the overall signature stays secure as long as at least one component remains unbroken, easing SSH’s migration toward quantum-resistant authentication. The draft probably defines the relevant public-key and signature formats and how they are negotiated within SSH. New -00 working group revision; the description is derived from the name because the official abstract was not fetched.
By its name, this individual draft defines a URI representation for a “LinkID,” associated with the “linkgenetic” author or organization token. It most likely specifies how such link identifiers are expressed as URIs and possibly how they are resolved. The precise purpose is not evident from the title alone. New -00 revision; the summary is inferred from the name and will be grounded on a later run.
By its name, this LSR (Link State Routing) Working Group document extends the link-state advertisement of Layer 2 (L2) bundle member links so they carry a “remote ID.” L2 bundles group parallel member links between two nodes, and advertising each member’s remote (far-end) identifier lets controllers and traffic-engineering applications correlate the two ends of every member link. The draft most likely defines the corresponding IS-IS or OSPF sub-TLV. This is revision -06; the summary is based on the name because the official abstract was not fetched.
By its name, this individual draft concerns “grid curtailment” — most plausibly the signaling or coordination of reductions (curtailment) in electrical-grid load or generation, perhaps to align network or datacenter demand with available energy. It may define data or protocol elements for exchanging curtailment requests and responses. New -00 revision; the description is inferred from the title because the official abstract could not be retrieved.
By its name, this individual draft is a “Welcome to the IETF” document — most likely an informational, onboarding-style text that introduces newcomers to how the IETF works. Documents of this kind typically orient new participants to the organization’s processes, culture, and terminology rather than defining any protocol behavior. New -00 revision; the description is inferred from the title because the official abstract could not be retrieved.
This NVO3 Working Group document is a resubmission of RFC 7348 (VXLAN) as an IETF-stream document so that proper IETF code points can be assigned via IANA for future work based on it. It obsoletes RFC 7348, which defined the Virtual eXtensible Local Area Network (VXLAN) to meet the need for overlay networks in virtualized, multi-tenant data centers. VXLAN overlays are used in cloud-provider and enterprise data-center networks, and this memo documents the deployed protocol for the benefit of the Internet community. This is revision -05.