Window: Aug 25 - Aug 27, 2026 (last 48h) | Generated 2026-08-27 UTC | All groups, 100% coverage
By its title, this RFC updates the YANG Library, the mechanism that lets a client discover which YANG modules, submodules, features and deviations a server implements. It adds an "augmented-by" list so that a module entry can explicitly enumerate the other modules that augment it. That makes augmentation relationships directly discoverable from the library rather than something a client must infer by parsing every module. It most likely extends the YANG Library defined in RFC 8525. Written from the announcement title; the official Abstract will be grounded on the next run.
By its name, this IPPM working-group draft defines a YANG data model for on-path telemetry, i.e. configuring and/or reporting measurement data collected by nodes along a packet's forwarding path. It probably gives operators standardized structures to enable, collect and export in-situ / on-path performance information through NETCONF/RESTCONF. This is revision 06, an actively maintained document. Description inferred from the name.
An individual submission that, by its name, proposes policy-based anonymous tokens within the OAuth framework. It likely describes issuing access tokens that preserve user anonymity while still letting a resource server enforce authorization policy. This is an initial -00 version. Details are inferred from the title only and are approximate.
By its name, an IPPM working-group YANG data model for the Alternate-Marking (AltMark) performance-measurement method. It would let operators configure and manage alternate-marking-based packet-loss and delay measurement through standard network-management interfaces. Revision 06. Inferred from the name.
By its name, this individual draft specifies a hybrid TLS key exchange that combines classical ECDH with a post-quantum scheme referred to as "SCloud" (probably a lattice-based KEM). Hybrid key exchange aims to stay secure as long as either component is unbroken, a common transition strategy toward post-quantum TLS. Revision 02. Inferred from the title.
By its name, this individual draft likely documents the Ogg "Skeleton" metadata bitstream, the logical track that carries timing and structural metadata for multiplexed Ogg media streams, possibly to register a media type or formalize the format for IETF reference. Revision 02. Inferred from the title.
By its name, this draft relates to CATS (Computing-Aware Traffic Steering). It probably defines a data model for CATS, describing information such as compute and network metrics used to steer traffic toward suitable service instances. Revision 08. Inferred from the name and approximate.
By its name, an architecture document for something abbreviated "SDLP." Without the official abstract the exact expansion is uncertain; the draft presents an architectural framework and is at revision 04. Written cautiously from the name and will be grounded on the next run.
By its name, this draft relates to SCITT (Supply Chain Integrity, Transparency and Trust) and defines a "time anchor", probably a mechanism to bind trustworthy timestamps to SCITT transparency statements or receipts. Revision 05. Inferred from the title.
By its name, this initial draft concerns DNS and something called "memdns", with "pivoting" suggesting a resolution- or security-related technique. The precise scope is uncertain from the name alone. Initial -00 version; approximate and to be grounded next run.
By its name, an individual draft abbreviated "CCS"; the expansion cannot be determined from the name alone. It is at revision 07, so an actively revised document. Description is approximate pending the official abstract.
By its name, a V6OPS working-group document about testing applications for IPv6 behavior (and likely IPv6-only / IPv4-independence). It probably offers guidance or a methodology for validating that applications work correctly over IPv6. Revision 02. Inferred from the name.
One of a cluster of "morrison-" individual drafts in this digest that appear to concern AI-agent identity, provenance and consent. By its name this one addresses registration for a "solo agent earn" scenario. Scope is inferred from the title; revision 01 and approximate.
Another "morrison-" individual draft; by its name it concerns gating based on compute location, possibly controlling where computation may run. Inferred from the title; revision 01 and approximate.
By its name, this draft defines or discusses a "Reviewed-by" trailer, likely a metadata line (similar to Git commit trailers) that captures review provenance. Inferred from the title; revision 02 and approximate.
A "morrison-" individual draft on an "identity accord", probably a framework or agreement governing identity assertions among agents or parties. Inferred from the title; revision 02 and approximate.
By its name, this draft defines a grammar for expressing "substrate provenance", likely a structured way to describe the origin or lineage of computational substrate or content. Inferred from the title; revision 02 and approximate.
By its name, this draft relates to CATS (Computing-Aware Traffic Steering); the "idn" component's scope is uncertain from the name. Revision 01. Inferred from the name and approximate.
A "morrison-" individual draft on "consent settlement", probably a mechanism to record and settle consent between parties or agents. Inferred from the title; revision 05 and approximate.
By its name, a "bis" revision of RFC 2930 (TKEY, Secret Key Establishment for DNS). It most likely updates and replaces RFC 2930, refining the TKEY resource record used to establish shared secret keys for DNS transaction security such as TSIG. It sits in the DNSOP space though it is named as an individual submission. Revision 06. Inferred from the title.
By its name, this draft extends SCIM (System for Cross-domain Identity Management) with a "tenant" resource, probably to model multi-tenancy in identity provisioning. Initial -00 version. Inferred from the title.
By its name, this individual draft concerns a "SEAT" / "expat" transport; the exact expansions are not determinable from the name alone. Revision 02. Description is approximate pending the official abstract.
By its name, this draft collects use cases and requirements for agentic AI. It probably surveys scenarios and derives requirements to guide any protocol work related to AI agents. It carries no ietf/irtf working-group prefix, so it is treated as an individual / non-WG submission. Revision 02. Inferred from the title.
By its name, an OAuth-related individual draft defining an "ID continuation assertion", probably a token or assertion that carries identity continuity across sessions or steps of a flow. Revision 01. Inferred from the title.
By its name, an IDR working-group draft on BGP Flow Specification for traffic steering into SRv6 policies. It likely defines how Flowspec rules direct matching traffic into Segment Routing over IPv6 (SRv6) policy paths. Revision 17, a mature document. Inferred from the name.
By its name, a SPRING working-group draft introducing a Segment Routing "policy group", grouping SR policies for common handling. Revision 01. Inferred from the name and approximate.
By its name, an individual draft named "cedulon"; the term is not a standard acronym and its scope cannot be determined from the name. It is the base of a small cluster (see the -streaming and -reattestation variants in this digest). Revision 01. Approximate pending the official abstract.
By its name, this draft concerns handling of handshake failure ("handshake-fail"), likely in a security or transport context; the "intra" scope is uncertain. Its high revision (13) suggests a long-lived document. Inferred from the name and approximate.
By its name, part of Templin's AERO / OMNI work (Automatic Extended Route Optimization and the Overlay Multilink Network Interface), with "amen" as a further extension. It relates to the 6MAN space though it is named as an individual submission. Revision 13. Inferred from the name.
By its name, a MANET working-group gap analysis for running MANET protocols over the Internet ("inet"). It probably identifies gaps between existing MANET mechanisms and Internet-deployment needs. Revision 09. Inferred from the name.
By its name, an RTGWG working-group draft on using BGP within the Aeronautical Telecommunications Network (ATN). Its very high revision (32) indicates extended development. Inferred from the name.
By its name, an individual draft with the acronym "UAEMF", which is not determinable from the name alone. Revision 02. Description is approximate pending the official abstract.
By its name, part of Reilly's "AIMED" set of drafts; this one concerns evaluation ("eval"). The exact scope is uncertain from the name. Revision 01 and approximate.
By its name, the base "AIMED" individual draft; the acronym's expansion is not determinable from the name alone. Revision 01. Approximate pending the official abstract.
By its name, an OPSAWG working-group YANG data model for something named "Veloce". Initial -00 version. Beyond "a YANG model in the operations and management area" the scope is uncertain. Inferred from the name.
By its name, an individual draft on "query-scoped communication handles" in a 6G context, probably identifiers scoped to a particular query for communication. Revision 01. Inferred from the title and approximate.
By its name, a PIM working-group draft enhancing PFM (the PIM Flooding Mechanism) forwarding. It probably refines how PFM-distributed information is forwarded. Revision 08. Inferred from the name.
By its name, an individual draft describing an email-verification mechanism, likely a protocol or flow to verify control of an email address. Revision 02. Inferred from the title.
By its name, the "streaming" variant of the "cedulon" cluster (see also the -reattestation and base drafts). The term is not a standard acronym, so scope cannot be determined from the name. Initial -00. Approximate pending the official abstract.
By its name, the "reattestation" variant of the "cedulon" cluster, which suggests some attestation-related mechanism. Initial -00. Approximate pending the official abstract.
By its name, a DKIM working-group specification for "DKIM2", an evolution of DomainKeys Identified Mail. It probably defines a next-generation email-signing mechanism building on DKIM. Revision 05. Inferred from the name.
By its name, an AVTCORE working-group draft on carrying avatar-related data over RTP, likely an RTP payload format or signaling for avatar / immersive media. Revision 02. Inferred from the name.