IETF Internet-Drafts & RFCs — Daily Digest

A working-group draft in the CATS (Computing-Aware Traffic Steering) group. By its name it defines a data model for CATS, the framework that steers traffic not only by network path but by the availability and load of compute resources at candidate service sites. The model would provide the structured representation (probably a YANG-based schema) used to advertise, configure, or exchange the computing and network metrics that steering decisions rely on. As a -00 it is the freshly adopted working-group baseline, likely carried over from an earlier individual submission. Specific objects and encodings are not restated here because the official abstract was not retrieved this run.

A working-group draft in NMOP (Network Management Operations). By its name it specifies a YANG data model for representing network incidents, giving operators a common structure to describe, correlate, and track incidents across management systems. This is revision -16, a mature and heavily iterated document, suggesting it is close to completing working-group process. The model would typically cover incident identity, lifecycle/state, affected resources, root-cause and event linkage, and notification. Exact leaves and identities are not summarized here since the official abstract was not fetched this run.

An individual submission related to the WIMSE space (Workload Identity in Multi-System Environments). By its name it concerns evaluation, probably an assessment or comparison of approaches, requirements, or mechanisms for workload identity across systems. As an individual -01 it is early-stage input intended to inform the WIMSE working group rather than a chartered deliverable. Precise scope is uncertain without the official abstract, which was not available this run.

An individual submission whose name points to the concept of verification state, likely a way to capture, represent, or convey the state of a verification process between parties. As a -02 individual draft it is still under early development. Without the official abstract (not retrieved this run) the exact protocol context and data structures cannot be stated precisely.

An individual submission in the WIMSE problem space (workload identity across systems). Its name suggests a 'connected flight' use case or scenario, plausibly workload identity and credential handling spanning connected, possibly aviation-related or multi-hop connected environments. As an individual -02 it is early input to the WIMSE discussion. The concrete use case and mechanisms are not confirmed here because the official abstract was not fetched.

An individual submission whose name references an 'at repository'. This is likely tied to the AT Protocol / decentralized social-networking ecosystem, describing a repository structure or its interaction over the network. As an individual -03 it has seen some iteration. The precise data model and operations are not summarized here since the official abstract was not available this run.

A working-group draft in DTN (Delay/Disruption Tolerant Networking). By its name it defines endpoint identifier (EID) patterns, a way to express sets or ranges of bundle-protocol EIDs, useful for matching, filtering, routing rules, or policy. Revision -11 indicates a well-developed document. Exact pattern syntax and matching semantics are not restated here because the official abstract was not retrieved this run.

An individual submission whose name concerns web bots and data collection. It probably addresses how automated agents/bots collect data on the web and how that activity is signaled, controlled, or made transparent. As an individual -01 it is early-stage. Without the official abstract (not fetched this run) the exact mechanism and its relation to existing bot-control conventions cannot be confirmed.

An individual submission using the short handle 'aadp'. The acronym is not expanded by the name alone, so its subject cannot be stated with confidence. As a -03 it has had some revision. The official abstract, which would clarify the protocol's purpose, was not available this run.

A working-group draft in BIER (Bit Index Explicit Replication). By its name it defines link-state routing (LSR) extensions for BIER in non-MPLS environments, i.e. advertising BIER information via IGP link-state protocols where MPLS encapsulation is not used. Revision -05 shows steady progress. The specific IGP TLVs/sub-TLVs and encapsulation details are not restated here because the official abstract was not fetched this run.

An individual submission targeting the CFRG (Crypto Forum Research Group). Its title is 'X-Wing: general-purpose hybrid post-quantum KEM'. It specifies X-Wing, a hybrid key-encapsulation mechanism that combines a post-quantum KEM (ML-KEM) with a classical elliptic-curve component so security holds if either building block remains strong. Revision -11 is a mature, widely-referenced specification. Exact combiner construction and parameter choices are not reproduced here because the official abstract was not retrieved this run.

A working-group draft in SCITT (Supply Chain Integrity, Transparency, and Trust). By its name it defines a profile for SCITT receipts based on CCF (the Confidential Consortium Framework), specifying how transparency-service receipts are produced and verified when the append-only log is backed by CCF. Revision -05 indicates active development. The precise receipt structure and verification steps are not summarized here since the official abstract was not fetched.

An individual submission whose name addresses AI evaluation and 'claim preservation'. It likely concerns how claims made about AI systems (for example evaluation results or assertions) are preserved, carried, or verified over time. As a -00 it is a first-cut individual proposal. The concrete data model and threat model are uncertain because the official abstract was not available this run.

An individual submission in the SCHC area (Static Context Header Compression). By its name it works toward a revision ('bis') of RFC 9363, the SCHC YANG data model, gathering the changes and lessons that a future updated model would incorporate. As a -00 it is an initial contribution. The specific proposed changes are not listed here because the official abstract was not retrieved this run.

An individual submission targeting the CFRG. Its name references 'libzk', suggesting a specification tied to a zero-knowledge (ZK) proof library or interface. It probably documents constructions or interfaces for zero-knowledge proofs for review by the crypto research community. Revision -03 shows some iteration. Exact schemes and APIs are not stated here since the official abstract was not fetched this run.

An individual submission whose name is 'ipv7'. By its name it proposes or discusses ideas around a notional 'IPv7' next-generation IP addressing/architecture. As a -00 individual draft it is an early, exploratory contribution rather than any chartered work. Its actual content and seriousness cannot be judged here because the official abstract was not available this run.

An individual submission connected to the IETF 'green'/sustainability networking discussion. By its name it defines capability discovery for green/energy-related features, letting devices advertise which power- or sustainability-related capabilities and metrics they support. Revision -02 indicates continued work. The exact discovery mechanism and data model are not restated here because the official abstract was not fetched this run.

An individual submission in the SATP problem space (Secure Asset Transfer Protocol). By its name it defines a registry of artefacts used by SATP, i.e. the named objects/parameters that asset-transfer flows reference. As an individual -01 it is early input to the SATP working group. Precise registry contents and allocation policy are uncertain without the official abstract, not retrieved this run.

An individual submission related to SATP (Secure Asset Transfer Protocol). By its name it specifies the setup stage of a SATP session, the initial phase where endpoints establish parameters and context before an asset transfer proceeds. Revision -05 shows sustained iteration. The concrete message exchange and state machine are not summarized here since the official abstract was not fetched this run.

A working-group draft in EMU (EAP Method Update). By its name it addresses post-quantum cryptography (PQC) in EAP-TLS, i.e. using PQC or hybrid key exchange and authentication within EAP-TLS network access authentication. Revision -02 indicates active development. Exact cipher/handshake profiling and fragmentation guidance are not restated here because the official abstract was not retrieved this run.

An individual submission whose name concerns 'accountable autonomous effectuation', pointing to mechanisms that let autonomous agents take actions ('effectuate') while remaining accountable. Part of a cluster of related agent/accountability drafts from the same author. As -01 it is early-stage. The concrete architecture and data structures are uncertain without the official abstract, not available this run.

A working-group draft in NFSv4. By its name it is a revision ('bis') of RFC 8881, the NFS version 4.1 protocol specification, folding errata and clarifications into an updated base document. Revision -11 is a mature, large specification. The specific corrections and changes relative to RFC 8881 are not enumerated here because the official abstract was not fetched this run.

A working-group draft in CCAMP (Common Control and Measurement Plane). By its name it defines a YANG data model for FlexE (Flexible Ethernet) configuration management ('cm'), used to configure and manage FlexE groups, clients, and calendars. Revision -11 indicates a well-developed model. Exact YANG containers and leaves are not summarized here since the official abstract was not retrieved this run.

An individual submission in the DTN area (Delay/Disruption Tolerant Networking). By its name it describes a traceroute-like diagnostic for DTN, likely using an 'extension block' ('eb') in Bundle Protocol to trace the path a bundle takes. As a -00 individual draft it is an initial proposal. The concrete block format and procedures are not stated here because the official abstract was not available this run.

An individual submission whose name concerns 'agentic adaptive authorization', i.e. authorization mechanisms that adapt to autonomous ('agentic') actors and changing context. Part of the same author's cluster of agent-related drafts. As a -00 it is an early proposal. The precise authorization model is uncertain without the official abstract, which was not fetched this run.

A draft with the unusually high revision number -41 whose name references handshake failure. By its name it likely deals with detecting, signaling, or handling handshake failures within a protocol exchange. The very high version suggests an automated or frequently-republished document; its true scope cannot be confirmed here because the official abstract was not retrieved this run and the name is terse.

An individual submission whose name references 'claim boundaries', probably delimiting the scope or extent of claims (assertions/attestations) so that consumers know exactly what a claim does and does not cover. As a -01 it is early-stage. The concrete data model and usage are uncertain without the official abstract, not available this run.

An individual submission whose name references 'succession receipts', likely receipts that record a succession or handover of authority, keys, or control from one holder to another in a verifiable way. Revision -05 shows some iteration. The specific receipt structure and verification are not summarized here because the official abstract was not fetched this run.

An individual submission whose name describes an 'agent registry protocol', a mechanism to register, discover, or manage software agents. This fits the broader wave of agent-oriented drafts currently appearing at the IETF. As a -02 it has had some revision. The concrete registration operations and data model are uncertain without the official abstract, not retrieved this run.

An individual submission in the IDR (Inter-Domain Routing) problem space. By its name it defines neighbor auto-discovery, most plausibly automatic discovery of BGP neighbors to reduce manual peering configuration. Revision -14 indicates a long-lived, iterated document. Exact discovery messages and procedures are not restated here since the official abstract was not fetched this run.

A working-group draft in PIM (multicast routing). By its name it specifies zero-configuration assignment of IPv6 multicast addresses, letting hosts obtain usable IPv6 multicast group addresses without manual configuration (an associated Last Call for this document appeared on ietf-announce, using mDNS). Revision -12 indicates a mature document near completion. Exact assignment procedures are not summarized here because the official abstract was not retrieved this run.

An individual submission using the name 'cedulon-core'. The term is not self-explanatory, so the subject cannot be stated with confidence from the name alone; 'core' suggests it defines the base/core of a system named Cedulon. As a -01 it is early-stage. The official abstract, which would clarify its purpose, was not available this run.

A working-group draft in the OpenPGP group. By its name it addresses 'external secrets', likely a way for OpenPGP to reference or use secret key material held outside the OpenPGP data itself (for example in hardware tokens or external key stores). As a freshly adopted -00 it is the working-group baseline. Concrete packet/format details are not stated here because the official abstract was not fetched this run.

An individual submission in the NETMOD problem space (YANG data modeling). By its name it defines YANG configuration templates, a mechanism to define reusable parameterized configuration snippets that can be instantiated across devices. Revision -04 shows continued work. Exact template structure and instantiation semantics are not summarized here since the official abstract was not retrieved this run.

An individual submission whose name concerns a 'workload authorization grant', likely an OAuth-style grant type or mechanism by which a workload obtains authorization/credentials. This aligns with current workload-identity work (e.g. WIMSE). As a -01 it is early-stage. The precise grant flow is uncertain without the official abstract, not available this run.

An individual submission using the short handle 'bcnp'. The acronym is not expanded by the name, so the subject cannot be stated with confidence. As a -00 it is a first individual proposal. The official abstract, which would explain the protocol, was not fetched this run.

An individual submission whose name concerns reform of the (IETF/RFC) publication process. It probably proposes changes to how documents are published or advanced, a process/procedural contribution rather than a protocol. Revision -08 shows substantial iteration. The specific reforms proposed are not enumerated here because the official abstract was not retrieved this run.