Window: last 48 hours (2026-09-23 to 2026-09-25) · Generated 2026-09-25 05:19 UTC
Defines a DNS-based mechanism for discovering Model Context Protocol (MCP) servers through TXT resource records published under the _mcp.<domain> underscore-prefixed label. A server can advertise its endpoint URL, transport protocol, cryptographic identity, and capability profile via DNS, complementing the existing HTTPS-based discovery approach (the .well-known/mcp/server-card.json document). The DNS approach gives a lightweight, resolver-cached bootstrap that needs no HTTPS round-trip, following the precedent of domain-scoped metadata protocols such as DKIM, SPF, DMARC, and MTA-STS.
By its name, this individual submission appears to define an "action evidence boundary" — the point at which evidence about an action is captured and attested. It probably fits the current work on accountability and verifiable records for autonomous or agentic systems, delimiting what evidence crosses the boundary of a performed action. This summary is approximate and drawn from the title, since the official abstract could not be retrieved on this run.
On-path network elements can sometimes be configured to apply rate limits to the flows passing through them. This document specifies the Standard Communication with Network Elements (SCONE) protocol, a method for signaling to endpoints that rate-limiting policies are in force on the path and what the applicable rate limit is. Endpoints can use that signal to adapt their sending behaviour rather than probing blindly for available capacity.
Part of the Media over QUIC (MoQ) family from the moq-lite author. By its name it probably defines a "solicit" mechanism used to request or subscribe to media tracks or content over MoQ transport. This description is approximate and based on the draft name; it will be grounded against the official abstract on the next run.
A Media over QUIC (MoQ) companion document that, by its name, likely specifies end-to-end encryption for MoQ content so that payloads remain confidential from relays and CDNs that forward them. Approximate, from the name; the official abstract was not available this run.
By its name, this MoQ draft probably defines how to carry MPEG-2 Transport Stream (MPEG-TS) content over Media over QUIC. Approximate, drawn from the draft name; to be grounded against the abstract next run.
Hang is a real-time conferencing protocol built on top of moq-lite. A room consists of multiple participants who publish media tracks, and all updates — such as a change in participants or in the set of media tracks — are delivered live. It provides the conferencing layer above the generic MoQ transport.
moq-lite is designed to fan out live content 1->N across the internet. It leverages QUIC to prioritize important content, avoiding head-of-line blocking while still respecting encoding dependencies. While primarily designed for media, the transport is payload-agnostic and can be proxied by relays and CDNs without any knowledge of codecs, containers, or encryption keys.
By its name, this MoQ draft likely defines a compression scheme (a "flate"/DEFLATE-style codec) for content or metadata carried over Media over QUIC. Approximate, from the draft name; the abstract was not retrievable on this run.
By its title, this individual draft provides deployment and operational considerations for running IPv6 inside data-center networks, likely covering addressing, routing, and transition concerns specific to the data-center environment. Approximate, based on the title.
Describes a technique for signaling the presence of a zone cut in the DNS without specifying any nameservers for the delegated child zone. The mechanism is useful when it is important to make clear to clients that a zone cut exists, but the child zone is only provisioned in a private namespace. Adopted by the DNSOP working group (it began as an individual submission).
By its name, this new DNSOP working-group item likely defines an Extended DNS Error (EDE) code associated with Negative Trust Anchors (NTAs) used in DNSSEC validation, so resolvers can signal that a name is under an NTA. Approximate, from the name; the official abstract was not available this run.
A Media over QUIC (MoQ) related individual submission. Its precise scope could not be confirmed from the name alone, but it appears to define a media format, timing, or segmentation construct used with MoQ. Approximate and tentative, pending the official abstract.
A revision ("bis") of RFC 4130, which defines AS2 — MIME-based EDIINT for exchanging structured business data (EDI) securely over HTTP/HTTPS with signing, encryption, and message disposition notifications. This update refreshes and clarifies the AS2 specification. Approximate framing based on the scope of RFC 4130; the current abstract was not retrieved this run.
By its name, this individual draft (already at a very high revision number) appears to document handshake-failure scenarios and their handling, most plausibly within a connection/transport or TLS-style handshake. Approximate, from the name; the abstract could not be retrieved on this run.
BGP was originally designed to carry IPv4 routing information, with the NEXT_HOP attribute representing the next router for forwarding. Modern tunneling technologies (GRE, MPLS, SR-MPLS, SRv6) decouple the control-plane view of the next hop from the actual data-plane forwarding endpoint. This document describes the problems that arise from that decoupling — sub-optimal path selection, incorrect resolvability tracking leading to traffic drop or misrouting, and others — and proposes modifications to BGP best-path selection to accommodate these cases.
Deep-space communications involve long delays (Earth-to-Mars one-way delay is roughly 4-24 minutes) and intermittent connectivity, largely because of orbital dynamics. The IP protocol stack used on the Internet assumes shorter delays and mostly uninterrupted communication. This document describes the key characteristics, use cases, and requirements for deep-space networking, intended to help when profiling IP protocols for such environments.
Defines RTP payload formats for Video-based Dynamic Mesh Coding (V-DMC), which comprises several component types such as a base mesh, a set of displacements, 2D representations of attributes, and an atlas. New RTP payload formats are described for the base mesh and displacement components. The payload header formats support packetizing a video-stream packet within an RTP packet payload and fragmenting a video-stream packet across multiple RTP packets.
An individual submission aimed at the Routing Area Working Group. Its evocative title suggests an architectural or considerations document arguing about how the network should (and should not) be treated as a general-purpose carrier. The specific content could not be confirmed from the name; this summary is approximate.
A SCITT-related individual submission that, by its name, defines a "time anchor" — a mechanism for binding trustworthy timing (trusted timestamps) to transparency or supply-chain receipts. Approximate, from the name; the official abstract was not retrieved this run.
A revision ("bis") of RFC 5706, "Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions." It updates the guidance authors and working groups use to ensure new protocols are manageable and operationally sound. Approximate framing based on RFC 5706's scope; the current abstract was not retrieved this run.
By its name, a REGEXT working-group extension to the Extensible Provisioning Protocol (EPP) for querying and reporting a registrar's account balance at a registry. Approximate, from the name; to be grounded against the abstract on the next run.
By its name, this GROW working-group item defines a BGP community used to signal a route "downgrade" in inter-domain operations (for example, to make a path less preferred). Approximate, from the name; the official abstract was not available this run.
By its name, a PCE working-group extension to PCEP for signaling the position of MPLS entropy labels (Entropy Label Position) along a computed path, helping load-balance MPLS traffic. Approximate, from the name; the abstract was not retrieved this run.
Describes the core security features of the NFSv4 family of protocols, applicable to all minor versions, including the security features provided by RPC on a per-connection basis. The current version is intended to drive working-group discussion of existing NFSv4 security issues and to provide a framework for addressing them and reaching consensus on necessary changes. When published, it would supersede the security descriptions in existing minor-version specifications such as RFC 7530 and RFC 8881.
By its name, this individual submission analyzes the applicability of Computing-Aware Traffic Steering (CATS) to Optical Transport Networks (OTN). Approximate, from the name; the official abstract was not available this run.
An individual submission whose name ("rttp"/"iqa" addressing) is too opaque to interpret confidently. It appears to propose an addressing scheme for a specific transport or application context. Tentative and approximate, pending the official abstract.
By its name, a new RADEXT working-group item defining a RADIUS attribute (or attributes) that convey connection information about a user's session. Approximate, from the name; the abstract was not retrieved this run.
Titled "Source Prefix Advertisement for Intra-domain SAVNET," this draft addresses Source Address Validation (SAV) within a domain by advertising the legitimate source prefixes so routers can build accurate SAV rules and reject spoofed traffic. Approximate summary grounded in the document title; the full abstract was not retrievable this run.
Specifies a CBOR encoding for X.509 certificates, producing "C509 Certificates." The encoding covers a large portion of RFC 5280 plus certificates conforming to RFC 7925, IEEE 802.1AR (DevID), CNSA, RPKI, GSMA eUICC, and CA/Browser Forum Baseline Requirements profiles. Re-encoding DER X.509 certificates often yields size reductions above 50% for RFC 7925 profiles. C509 supports being natively signed (no re-encoding for verification), and the document also defines C509 COSE headers, a C509 TLS certificate type, and a C509 file format.
Defines post-quantum/traditional (PQ/T) composite schemes for OpenPGP based on ML-KEM and ML-DSA combined with ECDH and ECDSA, using the NIST and Brainpool elliptic-curve domain parameters. The composites let OpenPGP implementations gain post-quantum protection while retaining a classical algorithm in the same construction.
Titled a YANG data model for network incidents, this NMOP working-group item defines a structured model for representing, reporting, and managing network incidents so operators and tools can exchange incident information consistently. Approximate summary grounded in the document title; the full abstract was not retrieved this run.
A new RADEXT working-group item whose name abbreviation could not be expanded with confidence; it defines a RADIUS extension for a specific credential or provisioning use case. Tentative and approximate, pending the official abstract.
An individual submission defining the "ZTDS" protocol; the acronym could not be confirmed from the name, but it appears to specify a zero-trust or data-security oriented protocol. Approximate and tentative, pending the official abstract.
An individual submission whose short name ("aer1") is too opaque to interpret reliably. The scope could not be inferred from the name; this placeholder will be replaced once the official abstract is available.
An individual submission that, by its name, defines a discovery mechanism for "AINS." The exact expansion could not be confirmed from the name. Approximate and tentative, pending the official abstract.
An individual submission that, by its name, concerns process integrity for something abbreviated "UPIP." The exact scope could not be confirmed from the name. Approximate and tentative, pending the official abstract.
A new CATS working-group item that, by its name, defines a data model for Computing-Aware Traffic Steering — the structured information used to steer traffic based on both network and computing metrics. Approximate, from the name; the abstract was not retrieved this run.
A WIMSE-related individual submission that, by its name, evaluates approaches for workload identity in multi-system environments. Approximate, from the name; the official abstract was not available this run.
An individual submission that, by its name, concerns representing or conveying a "verification state." The precise context could not be confirmed from the name. Approximate and tentative, pending the official abstract.
A WIMSE-related individual submission that, by its name, applies workload identity concepts to a "connected flight" (aviation) scenario. Approximate, from the name; the abstract was not retrieved this run.
Specifies the repository and synchronization semantics for Authenticated Transfer (AT), a protocol for cryptographically verifiable storage and distribution of structured, user-controlled data. It defines the AT repository that serves as the fundamental data-storage model and specifies synchronization mechanisms that efficiently distribute repository changes to interested parties. This document covers the repository and sync protocol specifically; the overall network architecture is described in a companion AT-ARCH document.
By its name, this DTN working-group item defines patterns for matching Bundle Protocol endpoint identifiers (EIDs), useful for expressing sets of endpoints compactly (for example in security or routing policy). Approximate, from the name; the official abstract was not available this run.
An individual submission that, by its name, addresses web-bot data collection — likely signaling or governing how automated agents collect data from websites. Approximate, from the name; the abstract was not retrieved this run.
An individual submission whose acronym ("AADP") could not be expanded from the name with confidence. The scope is unclear from the title alone; this placeholder will be replaced once the official abstract is available.
Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding across a BIER domain without requiring intermediate routers to maintain multicast per-flow state. This document updates RFC 8296 and defines extensions to IS-IS, OSPFv2, and OSPFv3 that enable BIER support in networks that do not use MPLS, specifically via BIER non-MPLS encapsulation methods.
Defines X-Wing, a general-purpose post-quantum/traditional hybrid key encapsulation mechanism (PQ/T KEM) built on X25519 and ML-KEM-768. It combines a classical and a post-quantum KEM so that the result remains secure as long as either component holds.
Defines a new verifiable data structure (VDS) type for COSE Receipts, together with an inclusion proof, specifically designed for the append-only logs produced by the Confidential Consortium Framework (CCF). The goal is to provide stronger tamper-evidence guarantees for SCITT transparency receipts backed by CCF ledgers.
An individual submission that, by its name, concerns preserving AI-evaluation claims — capturing and retaining verifiable records of AI evaluation results. Approximate, from the name; the official abstract was not available this run.
An individual SCHC (Static Context Header Compression) submission working toward a revision ("bis") of RFC 9363, the SCHC YANG data model. It likely gathers proposed changes ahead of a formal 9363bis effort. Approximate framing based on the name and RFC 9363's scope; the abstract was not retrieved this run.
An individual submission aimed at the CFRG that, by its name, specifies a zero-knowledge proof library or scheme ("libzk"). Approximate, from the name; the official abstract was not available this run.
An individual submission referencing "IPv7." Such proposals are typically speculative or exploratory extensions/successors to the IP addressing model; the specific content could not be confirmed from the name. Approximate and tentative, pending the official abstract.
An individual submission (from a well-known network-management author) that, by its name, defines capability discovery for "green" (energy-efficiency/sustainability) network management, letting devices advertise their power/energy-related capabilities. Approximate, from the name; the abstract was not retrieved this run.
A SATP-related individual submission that, by its name, defines a registry of "artefacts" used in the Secure Asset Transfer Protocol. Approximate, from the name; the official abstract was not available this run.
SATP Core defines a unidirectional transfer of assets in three stages: Transfer Initiation (Stage-1), Lock-Assertion (Stage-2), and Commitment Establishment (Stage-3). This document defines the Setup Phase, often called "Stage-0," that precedes SATP Core. During Setup, the two gateways that will participate in the transfer are bound together via a "transfer context" that conveys information about the assets to be exchanged, allowing any negotiation to happen before SATP Core begins.
Proposes enhancements to EAP-TLS and EAP-TTLS to incorporate post-quantum cryptographic mechanisms. It also addresses the challenges of large certificate sizes and long certificate chains identified in RFC 9191, and gives recommendations for integrating PQC algorithms into EAP-TLS and EAP-TTLS deployments.
An individual submission that, by its name, addresses accountability for autonomous "effectuation" — i.e., holding autonomous agents accountable for actions they carry out. Approximate, from the name; the official abstract was not available this run.
A revision ("bis") of RFC 8881, the NFS Version 4 Minor Version 2 (NFSv4.2) protocol specification. It updates and consolidates the NFSv4.2 protocol definition. Approximate framing based on RFC 8881's scope; the current abstract was not retrieved this run.
Defines a service-provider-targeted YANG data model for the configuration and management of a Flex Ethernet (FlexE) network, including the FlexE group and FlexE client. The YANG module conforms to the Network Management Datastore Architecture (NMDA).
A DTN-related individual submission that, by its name, defines a traceroute-style diagnostic for Bundle Protocol networks using an extension block ("EB"). Approximate, from the name; the official abstract was not available this run.
An individual submission that, by its name, defines adaptive authorization for agentic (AI-agent) systems, adjusting access decisions dynamically to agent behaviour and context. Approximate, from the name; the abstract was not retrieved this run.
By its name, this individual draft (already at a very high revision number) appears to document handshake-failure scenarios and their handling, most plausibly within a connection/transport or TLS-style handshake. Approximate, from the name; the abstract could not be retrieved on this run.
An individual submission that, by its name, defines "claim boundaries" — the scope or delimitation of claims (for example in tokens or attestation evidence). Approximate, from the name; the official abstract was not available this run.
An individual submission that, by its name, defines "succession receipts" — verifiable receipts documenting the succession or handover of a key or identity, in a transparency-log style. Approximate, from the name; the abstract was not retrieved this run.
An individual submission that, by its name, defines a protocol for an AI-agent registry (registering and discovering agents), part of the current wave of agent-identity and discovery work. Approximate, from the name; the official abstract was not available this run.
An IDR-related individual submission that, by its name, defines a BGP neighbor auto-discovery mechanism, letting routers discover and establish BGP peering with less manual configuration. Approximate, from the name; the abstract was not retrieved this run.