Daily digest · window Aug 25-27, 2026 (last 48h) · generated 2026-08-27
RFC 10035 adds an 'augmented-by' list to the YANG Library, so that a module's entry can point to the modules that augment it. This makes it easier for clients to discover augmentation relationships directly from the YANG Library rather than inferring them, improving tooling and management of YANG-based data models.
Probably defines a data model for CATS (Computing-Aware Traffic Steering), which steers traffic toward the most suitable compute instance. By its name it structures the metrics and service information used to make steering decisions.
Probably specifies a hybrid TLS key-exchange combining classical ECDH with 'SCloud', a lattice-based post-quantum KEM, so that a session stays secure if either component holds. By its name it targets post-quantum resilience for the TLS handshake.
By its name, an individual draft documenting the Ogg 'Skeleton' bitstream — a metadata track inside the Ogg media container that describes the other logical streams (codecs, timing) to aid seeking and demultiplexing.
By its name, an individual draft concerning transport aspects of 'SEAT'/'expat'. The exact meaning is unclear from the name; it appears to define a transport mechanism. Approximate pending grounding.
By its name, an individual draft describing the architecture of 'SDLP'. Without the abstract the exact expansion is uncertain, but it appears to lay out the components and design of a data-link or delivery protocol.
By its name, an individual draft defining a grammar for expressing the provenance of a computational 'substrate' — probably a structured way to record where and how AI/agent computation originated. Approximate.
By its name, part of a cluster of individual drafts on autonomous ('agentic') AI systems, here covering how a solo agent registers to 'earn' — likely participate in a compensation or accounting scheme. Approximate without the abstract.
Probably standardises a 'Reviewed-by' trailer (similar to commit-message trailers) to record who reviewed a document or artifact. By its name it formalises attribution of review in a machine-parseable line.
By its name, an individual draft defining an 'identity accord' — an agreement or framework for establishing and reconciling identities, likely between AI agents or services. Approximate without the abstract.
By its name, an individual draft on 'consent settlement' — likely a mechanism for recording, reconciling, or settling consent decisions between parties or agents. Approximate.
By its name, an individual draft proposing a 'gate' that constrains where computation may run based on location — probably for compliance, data-residency, or trust in agentic/AI contexts. Approximate.
Probably defines an OAuth 'identity continuation assertion' — a token or claim that carries identity context across steps or sessions. By its name it supports maintaining verified identity through a multi-stage flow.
By its name, an individual submission proposing policy-based anonymous tokens for OAuth, letting a client obtain tokens that authorise access while hiding the user's identity, with issuance governed by policy. Probably aimed at privacy-preserving authorization flows.
Probably a CATS (Computing-Aware Traffic Steering) draft dealing with identifiers ('IDN') used to name compute services or instances for steering. Approximate without the abstract.
By its name, an individual draft extending SCIM (System for Cross-domain Identity Management) with a 'tenant' resource, supporting multi-tenant identity provisioning. Probably defines a schema for representing tenants.
Probably a v6ops working-group document offering guidance on testing applications for correct behaviour over IPv6 (and in IPv6-only or dual-stack environments). By its name it targets operational readiness of applications.
By its name, a SPRING working-group draft defining the concept of an 'SR Policy group' — a way to group Segment Routing policies for shared handling or selection. Probably extends SR Policy management.
Probably a YANG data model, produced in the IPPM working group, for configuring and managing on-path telemetry — collecting per-hop measurement data as packets traverse a network path. By its name it complements IPPM's performance-metric work with a machine-readable model for operators.
By its name, a YANG data model in the IPPM working group for the Alternate-Marking (AltMark) method, a technique that colours packet batches to measure loss and delay in operational networks. It likely defines configuration and state for enabling AltMark on network elements.
Probably an IDR working-group draft using BGP Flow Specification to steer matching traffic into an SRv6 policy. By its name it links Flowspec traffic-steering rules to Segment Routing over IPv6 paths.
By its name, an individual draft about 'memory DNS' pivoting — likely a security/analysis topic concerning how DNS resolution or caching can be used to pivot. Details are approximate without the abstract.
Probably relates to SCITT (Supply Chain Integrity, Transparency and Trust) and defines a 'time anchor' — a trusted timestamp binding transparency-log entries to a point in time. By its name it strengthens temporal assurances for signed supply-chain statements.
Probably a revision (2930bis) of the DNS TKEY resource record specification, updating how secret keying material is established for DNS transactions. By its name it modernises RFC 2930 within DNS operations work.
By its name, part of a new 'Cedulon' family of individual drafts (with companion streaming and reattestation documents). The base document likely defines the core protocol; scope is approximate without the abstract.
By its name, an individual draft referring to 'CCS'. The exact scope is unclear from the name alone; it appears to define a mechanism or protocol abbreviated CCS. Treated as approximate pending grounding.
By its name, an individual draft cataloguing use cases and requirements for agentic AI systems in a networking/IETF context. Probably motivates future protocol work by enumerating scenarios and needs.
Probably a CATS (Computing-Aware Traffic Steering) draft on operational handling of service metrics — how compute/service metrics are collected and represented for steering decisions. Approximate.
By its name, an individual draft binding 'AIC' to JSON Web Tokens (JWT). The exact expansion of AIC is unclear from the name; it appears to define a JWT-based representation. Approximate.
Probably an inter-domain routing draft defining an Outbound Route Filtering (ORF) capability keyed on a BGP path attribute, letting a receiver ask a peer to filter routes. Approximate without the abstract.
By its name, a Templin individual draft in the 6man space extending the AERO/OMNI framework (Automatic Extended Route Optimization over the Overlay Multilink Network Interface) with an 'AMEN' mechanism. Approximate.
By its name, an individual draft referencing 'SOOS'/'GAR'. The scope is unclear from the name alone; treated as approximate pending grounding from the official abstract.
By its name, an individual draft (part of a Reilly cluster of AI/resilience submissions) defining a framework abbreviated 'UAEMF'. Exact expansion uncertain; approximate.
By its name, an evaluation companion to the 'AIMED' draft, likely defining how AIMED is measured or assessed. Part of a cluster of AI-related individual submissions. Approximate.
By its name, an individual draft defining 'AIMED', apparently an AI-related method or framework. Exact expansion uncertain without the abstract; approximate.
By its name, an individual draft binding SCIM identity provisioning to Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). Probably lets SCIM resources reference or carry DID/VC data. Approximate.
By its name, the URI companion to the 'ARS' draft, probably defining a URI scheme or naming syntax for ARS resources. Approximate without the abstract.
By its name, an individual draft defining 'ARS' (with a companion URI draft). The exact expansion is unclear from the name; it appears to specify a system or scheme abbreviated ARS. Approximate.
By its name, an individual draft concerning handshake failure handling ('intra' handshake). The exact protocol is unclear from the name; it appears to specify behaviour when a handshake fails. Approximate.
Probably a v6ops revision (6146bis) of Stateful NAT64, updating RFC 6146's specification for translating IPv6 traffic to IPv4. By its name it modernises the stateful NAT64 mechanism.
Probably a UTA working-group profile specifying how to use TLS 1.3 in constrained IoT environments, recommending parameters and options suited to devices with limited resources. By its name it tightens TLS usage for IoT.
Probably an RTGWG working-group draft on using BGP within the Aeronautical Telecommunications Network (ATN), adapting inter-domain routing to aviation networking requirements. By its name it targets ATN/IPS routing.
Probably a PIM working-group draft enhancing the PIM Flooding Mechanism (PFM) forwarding behaviour, refining how multicast control information is flooded and forwarded. By its name it builds on existing PFM work.
By its name, a PIM working-group YANG data model for EVPN multicast, providing configuration and state for multicast forwarding in Ethernet VPNs. Probably complements EVPN multicast specifications.
By its name, an OPSAWG working-group YANG data model named 'Veloce'. The precise subject is unclear from the name; it defines a model for some operational function. Approximate.
Probably a revision (8881bis) of the NFS version 4 minor version 1 (NFSv4.1) protocol specification, updating and clarifying RFC 8881. By its name it is a maintenance/consolidation effort in the NFSv4 working group.
By its name, a NETCONF working-group draft defining how to run the NETCONF management protocol over QUIC transport, gaining QUIC's multiplexing and TLS-based security. Probably specifies the mapping and session handling.
By its name, a MANET working-group gap analysis comparing mobile ad hoc networking needs against existing Internet protocols, identifying where standards fall short. Probably guides future MANET work.
Probably the core DKIM working-group specification for 'DKIM2', a next-generation evolution of DomainKeys Identified Mail signatures for email authentication. By its name it defines the DKIM2 protocol and signature format.
By its name, an AVTCORE working-group draft defining an RTP payload format for 'avatar' data — probably carrying avatar/animation streams (e.g. for immersive or telepresence media) over RTP. Approximate.
By its name, an individual draft (author Dick Hardt) specifying an email verification mechanism — likely a standard way to prove control of an email address. Approximate without the abstract.
By its name, the streaming companion in the 'Cedulon' draft family, probably covering how the Cedulon protocol handles streamed data or continuous delivery. Approximate.
By its name, the reattestation companion in the 'Cedulon' family, likely covering how a previously attested entity refreshes or renews its attestation. Approximate.
By its name, an individual draft proposing a protocol layer for 'execution finality' — likely ensuring that an operation is irreversibly committed, a concept common in distributed/ledger systems. Approximate.
By its name, an individual draft on '6G' communication proposing query-scoped communication handles — identifiers whose validity is bounded to a query or interaction. Forward-looking mobile/6G topic; approximate.
Probably an individual draft (author Benoit Claise) on discovering 'green'/energy-efficiency capabilities of network devices, aligning with sustainability and power-management work. By its name it enables querying device green features.
By its name, an individual draft enumerating OAuth authorization use cases for AI 'agents' acting on a user's behalf. Probably motivates extensions for delegated, agent-driven access. Approximate.
By its name, an individual draft in the network-management operations (NMOP) space on evaluating anomaly-detection methods, likely proposing criteria or a methodology to compare detectors. Approximate.