A YANG Data Model and RADIUS Extension for Policy-Based Network Access Control
RFC 10065, titled 'A YANG Data Model and RADIUS Extension for Policy-Based Network Access Control'. By its title it defines a YANG data model together with a RADIUS extension to support policy-based network access control, i.e. representing and provisioning access-control policy and carrying related attributes over RADIUS. Description derived from the announcement title; the official abstract is grounded on the next run.
By its name, a 6MAN (IPv6 Maintenance) working-group document concerning the IPv6 loopback address or loopback behaviour. It probably clarifies or specifies handling of loopback addressing in IPv6, likely addressing scope, forwarding, or address-architecture considerations. Being a -00 it is a new working-group item, so the exact scope should be read from the draft itself.
An individual submission in the CATS (Computing-Aware Traffic Steering) space, apparently describing a CSMA-related implementation. By its name it likely reports on implementation aspects of a CATS mechanism. Treat specifics as approximate until the abstract is read.
An individual -00 submission whose short name 'learnlog' suggests a logging or learning-log mechanism. The precise subject is not derivable from the name alone; read the draft for scope.
An individual submission in the IDR/BGP-LS area, by its name about performance measurement (PM) for traffic-engineering (TE) policies advertised via BGP-LS. It probably defines BGP-LS extensions or encodings to carry performance-measurement information for TE policies.
An individual submission; the short name 'sovp' is not self-explanatory. Scope cannot be inferred reliably from the name; read the draft for details.
An IPPM working-group document, by its name about extension headers for STAMP (Simple Two-Way Active Measurement Protocol). It likely specifies how STAMP carries additional extension/TLV header fields for performance measurement. A late revision (-16), so it is a mature WG item.
An individual submission relating to the IETF NomCom process and representation. By its name it discusses representation considerations within NomCom. Specifics are approximate.
An NMOP working-group document defining a YANG data model for network incidents. It probably standardizes how network-incident information is represented and exchanged for network operations and management. Two consecutive revisions (-18 and -19) appeared in the window.
An individual submission referencing 'CAIN' and a header. By its name it likely defines a header or header fields for a CAIN-related mechanism. Scope should be confirmed from the draft.
An individual submission in the COSE space, by its name about using SQIsign (a post-quantum signature scheme) with CBOR Object Signing and Encryption. It probably specifies COSE algorithm identifiers and encodings for SQIsign signatures.
A KEYTRANS working-group document describing the architecture for Key Transparency. It likely defines the overall architecture, components, and trust model for a key-transparency system. A mature revision (-10).
An individual -00 submission, by its name about permission receipts for agents. It probably describes a mechanism for recording or conveying permissions granted to software agents. New item; scope approximate.
An individual submission related to IPv6 (6man topic area); 'mla' is a long-running effort (revision -34). By its name it concerns a Multilink or multi-address/link mechanism in IPv6. Read the draft for precise scope.
An individual submission; 'cedulon-core' is not a widely known term, suggesting the core specification of a mechanism or system named Cedulon. Scope cannot be reliably inferred from the name.
An individual -00 submission, by its name about cryptographic keys that are bound to conditions (condition-bound keys). It probably describes a scheme where key use is gated on specified conditions.
An IDR working-group document; by its name a revision ('bis') of RFC 4271, the base BGP-4 specification. It likely updates and consolidates the BGP-4 protocol specification. An early WG revision (-02) of a foundational effort.
A PLANTS working-group document, by its name about Merkle Tree Certificates. It probably specifies a certificate format or issuance mechanism based on Merkle trees, likely aimed at efficient/compact certificate distribution.
An RTGWG (Routing Area Working Group) document, by its name about BGP for the Aeronautical Telecommunications Network (ATN). A long-running effort (revision -34), likely profiling or extending BGP for ATN/IPS use.
An individual -00 submission in the Media Over QUIC (MOQ) space, by its name defining a URI scheme or URI format for MOQ. It probably specifies how MOQ resources are identified by URI.
An individual -00 submission, by its name about handling of AI in email. It probably describes conventions or signalling for how AI-generated or AI-processed email should be handled. New item.
An individual -00 submission, by its name about signalling AI involvement in email (a companion to the AI-handling draft). It probably defines a signal/header indicating AI generation or processing of a message.
An individual -00 submission; 'numina pair binding' suggests a mechanism for binding a pair (of devices, keys, or endpoints) in a system named Numina. Scope is approximate pending the abstract.
An individual submission about reforming the IETF/RFC publication process. By its name it proposes changes to how documents are published. A mature revision (-10).
An individual -00 submission in the NMOP topic area, by its name about the semantics of KPIs (key performance indicators) for network operations. It probably defines a model or vocabulary for KPI semantics.
A DCONN working-group document, by its name about Domain Connect, a protocol for configuring DNS for services at a domain. It likely standardizes or profiles the Domain Connect mechanism.
An individual submission, by its name defining a framework for agent discovery (in a context abbreviated 'DAWN'). It probably describes how software agents advertise and discover one another.
An individual submission; 'ccs' is ambiguous from the name alone. Scope cannot be reliably inferred; read the draft for details. A mature revision (-10).
An individual -00 submission in the WIMSE (Workload Identity) space, by its name about proofs for local tool calls. It probably defines a mechanism to prove or attest a local tool invocation by a workload.
An individual -00 submission, by its name specifying a TLS hybrid key-exchange group combining ML-KEM-1024 with X448. It probably registers and defines this post-quantum/classical hybrid group for TLS.
An HTTPBIS working-group document, by its name specifying the 'No-Vary-Search' HTTP caching extension. It likely defines a response header letting servers declare which URL query parameters do not affect the response for caching/prefetch purposes.
An individual -00 submission in the Media Over QUIC (MOQ) space, by its name about flow control for subscriptions. It probably defines mechanisms to flow-control MOQ subscription data.
An NMOP working-group document defining a YANG data model for network incidents. It probably standardizes how network-incident information is represented and exchanged for network operations and management. Two consecutive revisions (-18 and -19) appeared in the window.
An individual -00 submission referencing the NMRG research-group topic area, by its name about ad-hoc semantic reconciliation. It probably discusses reconciling differing data semantics in network management.
An individual submission in the DTN (Delay-Tolerant Networking) space, by its name about a traceroute mechanism using an extension block ('eb'). It probably defines a Bundle Protocol extension block to support traceroute in DTN.