All groups · 48-hour window (2026-10-20 to 2026-10-22) · generated 2026-10-22 UTC
By its name this individual submission appears to define something named 'ACTS' together with a 'for' qualifier, likely in the emerging space of AI-agent identity and authorization that several draft-morrison documents address. Without the official Abstract the precise scope cannot be confirmed. It is a brand-new -00 draft, so it should be read as an initial proposal that may change substantially. A grounded description will be added on the next run once the Abstract is reachable.
By its name this draft probably proposes an IANA-style registry for the names of 'tool surfaces' exposed via MCP (the Model Context Protocol used by AI agents to call tools). The likely goal is to give tool and capability names a shared namespace so that agents and services can refer to them unambiguously. This is one of a family of draft-morrison documents dealing with agent/MCP infrastructure. Details such as registration policy and field definitions cannot be confirmed without the official Abstract and are approximate here.
By its name this individual draft appears to describe how an organization can provision and alter policy, seemingly tied to the 'alter' family of mechanisms proposed in other draft-morrison documents (see the alter URI scheme and DID alter method drafts). The likely subject is machine-readable policy that governs agent or identity actions on behalf of an organization. The exact data model and operations are not confirmed without the Abstract.
By its name this draft probably specifies how a standalone ('solo') software agent can earn or obtain a registration, likely an identity or authorization registration within the agent-identity framework shared by the draft-morrison series. The mechanism for 'earning' registration (for example proof-of-work, attestation, or endorsement) is not confirmed without the official Abstract.
By its name this draft likely standardizes a 'Reviewed-by' trailer, i.e. a structured metadata line (reminiscent of Git commit trailers) that records who reviewed an artifact such as a commit, document, or agent action. The intent is probably to make review provenance machine-verifiable. Precise syntax and semantics are approximate pending the official Abstract.
By its name this new -00 draft appears to define a Decentralized Identifier (DID) method called 'alter', part of the draft-morrison 'alter' family. A DID method specifies how identifiers are created, resolved, updated, and deactivated for a particular verifiable-data registry. The concrete resolution and update rules are not confirmed without the Abstract.
By its name this draft probably deals with recording and settling 'consent' between parties, plausibly in the context of agent or identity interactions where one party grants permission and the record must be durable and auditable. The exact settlement procedure and data structures are approximate pending the official Abstract.
By its name this draft likely defines a way to represent a person's or entity's pronouns as part of an identity record, so that systems can store and convey them consistently. It is part of the draft-morrison identity series. The precise schema and handling rules cannot be confirmed without the official Abstract.
By its name this draft probably specifies how source-code commits can be cryptographically attributed to an identity, linking commit authorship to a verifiable identity record. This complements other draft-morrison identity and trailer drafts. Exact mechanisms (signing, trailers, verification) are approximate pending the official Abstract.
By its name this draft appears to register an 'alter:' URI scheme used across the draft-morrison 'alter' family (see the DID alter method and org alter policy drafts). A URI-scheme draft typically defines syntax, semantics, and resolution behavior for the scheme. Specifics are approximate without the official Abstract.
By its name this draft probably defines how MCP (Model Context Protocol) endpoints or servers can be discovered using the DNS, for example via dedicated resource records or well-known names, so that agents can find tool services dynamically. The exact record types and discovery procedure are approximate pending the official Abstract.
By its name this individual draft likely defines 'delegation receipts' for software agents: verifiable records that one agent (or principal) delegated authority to another, useful for audit and for chaining trust across agent calls. At revision -15 it is a fairly mature individual document. Exact receipt format and validation rules are approximate without the official Abstract.
By its name this individual draft defines something abbreviated 'CMG'; the expansion is not evident from the name alone. Without the official Abstract the scope cannot be confirmed. A grounded description will be provided on a later run once the document's Abstract is reachable.
A STIR working-group document whose name indicates it applies Certificate Transparency concepts to STIR, the framework for Secure Telephone Identity that signs caller identity to combat caller-ID spoofing and robocalls. The likely aim is public, append-only logging of the certificates used to sign call credentials so that misissued or rogue certificates can be detected. Exact log formats and procedures are approximate pending the official Abstract.
By its name this draft updates/replaces RFC 2931 ('DNS Request and Transaction Signatures', SIG(0)) — the 'bis' and 'sigzero' tokens point to a revision of SIG(0) transaction signatures — in a DNS Service Discovery (dnssd) context. The likely goal is to modernize the cryptography and procedures for signing DNS requests/transactions with SIG(0). Specifics are approximate without the official Abstract.
By its name this individual draft (SIDROPS area) probably concerns exporting BGP 'point of view' (POV) data via IPFIX, i.e. carrying information about how routes look from a particular vantage point for routing-security operations and measurement. Exact IPFIX information elements and semantics are approximate pending the official Abstract.
By its name this new -00 draft targets IPsec/IKEv2 and post-quantum signatures: 'fn-dsa' refers to FN-DSA (FALCON, the NIST lattice-based signature), and 'pkr' likely denotes a public-key/authentication payload. The probable aim is to define how FN-DSA signatures are used for authentication in IKEv2. Specifics are approximate without the official Abstract.
By its name this new -00 draft describes interconnecting LISP (Locator/ID Separation Protocol) and EVPN (Ethernet VPN) networks, likely specifying how the two control planes exchange reachability so that overlay segments can be stitched together. Exact procedures and encodings are approximate pending the official Abstract.
By its name this OAuth-related individual draft introduces a concept it calls 'mission', plausibly a scoped, task-oriented authorization grant for agents or applications acting toward a defined goal. The exact token model and flows are approximate pending the official Abstract.
By its name this draft concerns OpenID Connect (OIDC) and certificate-based authentication context, likely defining how information about certificate authentication is conveyed within an OIDC authentication context. Exact claims and semantics are approximate pending the official Abstract.
By its name this new DNSOP-area individual draft probably defines a way to express or verify 'domain affiliation' — a relationship between domains — likely using DNS records so that one domain can assert or prove association with another. Exact record format and verification are approximate pending the official Abstract.
By its name this new OAuth individual draft defines a mechanism to look up OAuth client metadata, plausibly letting a party retrieve a client's registered metadata (such as redirect URIs and capabilities) on demand. Exact lookup endpoints and formats are approximate pending the official Abstract.
An IPPM working-group document extending STAMP (the Simple Two-way Active Measurement Protocol, RFC 8762) with extension headers / TLVs that carry additional measurement information in STAMP test packets. Given the many revisions announced in this window it is under active iteration. Exact header formats and new TLVs are approximate pending the official Abstract.
By its name this new LAMPS-area draft concerns encoding ML-DSA and ML-KEM (the NIST post-quantum signature and key-encapsulation standards) using a 'seed-only' representation of the private key, i.e. storing just the seed from which keys are regenerated rather than the expanded key material. Exact ASN.1/encoding details are approximate pending the official Abstract.
By its name this new HTTPBIS individual draft deals with signatures for HTTP tunnels (such as CONNECT-based or MASQUE-style tunnels), likely a way to authenticate or authorize tunnel establishment with signatures. Exact signature inputs and header formats are approximate pending the official Abstract.
By its name this new individual draft (PIM area) defines a sub-TLV for PFM (PIM Flooding Mechanism) carrying 'pre-join' information, plausibly letting routers advertise interest before a join so multicast state can be set up proactively. Exact sub-TLV layout is approximate pending the official Abstract.
An IPSECME working-group document whose name indicates a 'ping' mechanism carried inside encrypted ESP, likely a keepalive/liveness or path-verification probe that travels within the IPsec ESP tunnel itself rather than outside it. Exact packet format and procedures are approximate pending the official Abstract.
By its name this individual draft (LSR area) proposes deprecating the use of the IP Authentication Header (AH) for OSPFv3 authentication, presumably in favor of the newer OSPFv3 authentication trailer mechanisms. Exact normative changes are approximate pending the official Abstract.
A DKIM working-group document that appears to specify the DNS aspects of 'DKIM2', a next-generation evolution of DomainKeys Identified Mail for email authentication. The likely focus is how DKIM2 keys and policy are published and discovered in the DNS. Exact record types and selectors are approximate pending the official Abstract.
By its name this REGEXT-area individual draft proposes a reliability-scoring mechanism for RDAP (the Registration Data Access Protocol used for domain/IP registration data), plausibly a way to rate the reliability of RDAP servers or responses. Exact scoring model is approximate pending the official Abstract.
An AVTCORE working-group document about carrying SFrame (end-to-end media frame encryption) over RTP, i.e. how SFrame-protected media is packetized and signaled in RTP for secure real-time communications. Exact payload format and signaling are approximate pending the official Abstract.
A DMARC working-group document whose name indicates a proposal to move ARC (Authenticated Received Chain) to Historic status, i.e. to reclassify the ARC specifications. The likely rationale and process details are approximate pending the official Abstract.
By its name this new individual draft is part of a draft-watts series on evidence; it likely defines 'continuity evidence' for agents — verifiable records that an agent's operation or identity persisted without interruption or tampering. Exact evidence structures are approximate pending the official Abstract.
By its name this new individual draft addresses the admissibility of scientific evidence, plausibly defining criteria or metadata so that digital evidence meets scientific/legal admissibility standards. It is part of a draft-watts evidence series. Exact framework is approximate pending the official Abstract.
By its name this new individual draft is closely related to the scientific-admissibility draft above and likely elaborates the admissibility of scientific evidence in more detail. Both are part of the draft-watts evidence series. The precise distinction and content are approximate pending the official Abstract.
By its name this new individual draft defines an 'evidence envelope' for research data — a container format that wraps research evidence with metadata (and plausibly integrity/provenance information). Part of the draft-watts evidence series. Exact envelope structure is approximate pending the official Abstract.
By its name this new individual draft defines a profile for 'protocol test evidence', plausibly a standardized way to record and convey the results and provenance of protocol conformance/interop testing. Part of the draft-watts evidence series. Exact profile fields are approximate pending the official Abstract.
By its name this new individual draft touches RATS (Remote ATtestation) concepts — verification, promotion, and appraisal — likely describing how attestation evidence is appraised and how results are promoted through a trust pipeline. Exact procedures are approximate pending the official Abstract.
By its name this new individual draft defines a 'research evidence bundle', plausibly a packaged collection of research evidence items grouped for exchange or archival, complementing the research-evidence-envelope draft. Exact bundle format is approximate pending the official Abstract.
A DTN (Delay/Disruption-Tolerant Networking) working-group document defining an 'echo service' for the Bundle Protocol, i.e. a DTN analogue of ping/echo that reflects bundles back to the sender for reachability and round-trip testing across intermittently connected networks. Exact service endpoint and bundle handling are approximate pending the official Abstract.
By its name this individual draft defines something abbreviated 'XCIM'; the expansion is not evident from the name. Multiple early revisions were announced in this window, indicating active iteration. The scope cannot be confirmed without the official Abstract and will be grounded on a later run.
By its name this individual draft (routing area working group topic) describes 'KIRA', a routing approach; KIRA has been presented as a scalable, self-organizing routing architecture (e.g. for zero-touch / large autonomic networks). As an individual draft it is not yet WG-adopted. Exact mechanisms are approximate pending the official Abstract.
By its name this new individual draft defines something called 'HYPR'; the expansion and scope are not evident from the name alone. A grounded description will be provided once the official Abstract is reachable.
A SNAC working-group document ('Stub Network Auto Configuration for IPv6'). The 'simple' variant likely specifies a streamlined way for a stub network to auto-configure its connection to an adjacent infrastructure network without manual setup. At revision -13 it is a mature WG document. Exact procedures are approximate pending the official Abstract.
A SIDROPS working-group document defining a YANG data model for the RPKI-to-Router (RTR) protocol, used to feed validated route-origin and ASPA data to routers for routing security. The model likely covers configuration and operational state of RTR sessions. Exact YANG structure is approximate pending the official Abstract.
By its name this new individual draft (routing working group topic) discusses 'agentic systems' in a routing context, plausibly how AI agents interact with or operate network routing. As a -00 individual draft it is an early proposal. Exact scope is approximate pending the official Abstract.
By its name this individual draft sets out security requirements for agent-to-agent (A2A) AI interactions, likely enumerating threats and requirements for authenticating and securing communications between AI agents. Exact requirement set is approximate pending the official Abstract.
A PIM working-group document extending IGMP/MLD proxy behavior for multipath scenarios, plausibly allowing a proxy to use multiple upstream paths for multicast. Exact procedures and state handling are approximate pending the official Abstract.
By its name this individual draft concerns 'handshake fail' behavior (the 'intra' token and the unusually high revision number suggest an automated or experimental series); the exact protocol and scope are not evident from the name. The content will be grounded once the official Abstract is reachable.
By its name this individual draft defines agent identity in an OpenID context, likely extending OpenID Connect so that AI agents can carry and present verifiable identity. Exact claims and flows are approximate pending the official Abstract.
By its name this individual draft proposes a TCP mechanism abbreviated 'SRO'; the expansion is not evident from the name. It is part of a draft-cmcc cluster that also includes ASRP. Exact scope is approximate pending the official Abstract.
Defines the Available Session Recovery Protocol (ASRP), an experimental protocol aimed at high-availability network clusters that run stateful services such as load balancing and NAT. It specifies how session state is backed up and recovered and the message formats used for those exchanges. Unlike traditional designs that keep backup state inside the cluster, ASRP distributes state information out to clients or servers. The authors argue this improves elastic scaling, enables rapid recovery from single or multiple failures, and removes the need for centralized backup nodes, while simplifying cluster implementation. Overall it positions ASRP as an enabler for large-scale elastic network clusters.
An ANIMA working-group document about automatic deployment of network services, consistent with ANIMA's autonomic-networking charter (self-configuring, self-managing networks). It likely specifies how services are provisioned automatically across an autonomic domain. Exact signaling is approximate pending the official Abstract.
A JMAP working-group document defining a 'FileNode' data type / capability for JMAP (JSON Meta Application Protocol), plausibly a way to represent files and folders so JMAP clients can manage file storage. At revision -18 it is mature. Exact object model is approximate pending the official Abstract.
An LSR working-group document extending link-state routing (IS-IS/OSPF) to advertise the remote identifier of L2 bundle members, i.e. the far-end link identity for members of a Layer-2 link bundle. Exact TLV/sub-TLV encoding is approximate pending the official Abstract.
By its name this individual draft defines 'learnlog'; the expansion is not evident from the name, though it plausibly concerns logging for learning/telemetry purposes. Several early revisions were announced in this window. Exact scope is approximate pending the official Abstract.
A TEAS working-group document updating RSVP (or RSVP-TE) cryptographic authentication to use HMAC-SHA2 rather than older hashes, improving the integrity protection of RSVP signaling. Exact normative changes are approximate pending the official Abstract.
By its name this individual draft defines an agent discovery framework (the 'DAWN' token appears to name the framework), likely describing how AI agents advertise and discover one another. Exact architecture is approximate pending the official Abstract.
By its name this new individual draft defines cache-control semantics for 'sessions', plausibly how session data or tokens may be cached and for how long. Exact directives are approximate pending the official Abstract.
A PPM working-group document specifying DAP, the Distributed Aggregation Protocol for Privacy-Preserving Measurement. DAP lets clients submit measurements that are aggregated across non-colluding servers so that only aggregate results — not individual contributions — are revealed. At revision -20 it is a mature WG document. Exact message flows are approximate pending the official Abstract.
A BIER working-group document defining OSPFv3 extensions to advertise BIER (Bit Index Explicit Replication) information, so that OSPFv3 can distribute the data needed for stateless multicast forwarding. Exact LSA/TLV encoding is approximate pending the official Abstract.
By its name this individual draft (6lo area) concerns a padding-length mechanism for 6LoWPAN, the IPv6-over-low-power-wireless adaptation layer, plausibly to align or obscure frame lengths. Exact encoding is approximate pending the official Abstract.
By its name this individual draft defines a routing policy for agents, plausibly how requests are routed among AI agents according to policy. Exact policy model is approximate pending the official Abstract.
Proposes 'Epoch Markers' as a mechanism that lets actors in a distributed system agree on what counts as fresh. Epoch Markers work like regular time ticks that delimit intervals. A dedicated component, the 'Epoch Bell', produces and distributes the markers to participants. Receiving systems therefore do not need to judge freshness with their own timekeeping (for example a local real-time clock); instead, receipt of a particular marker starts a new epoch shared by all recipients. The work sits in the RATS (Remote ATtestation procedureS) context, where freshness of evidence and attestation results is a core concern.
A JOSE working-group document defining PQ/T hybrid composite signatures for JOSE and COSE, i.e. combining a post-quantum signature with a traditional one in a single composite signature so that JSON/CBOR object signing remains secure if either algorithm holds. Exact algorithm identifiers and encodings are approximate pending the official Abstract.
By its name this individual draft defines an 'agent disclosure bundle', plausibly a packaged set of disclosures an AI agent must present (identity, capabilities, policies). Exact bundle contents are approximate pending the official Abstract.
By its name this new individual draft defines something abbreviated 'RSDGGS'; the expansion is not evident from the name. A grounded description will be added once the official Abstract is reachable.
A CORE working-group document about YANG metadata in constrained environments, plausibly how YANG-defined metadata annotations are represented for CoAP/CORE (for example in CBOR/SenML). Exact encoding is approximate pending the official Abstract.
By its name this IPSECME-area individual draft specifies use of AES-GCM-SIV (a nonce-misuse-resistant authenticated encryption mode) within IPsec/IKEv2, improving robustness against nonce reuse. Exact transform definitions are approximate pending the official Abstract.
A REGEXT working-group document concerning RDAP extensions — the Registration Data Access Protocol's mechanism for defining and identifying protocol extensions. It likely clarifies how extensions are declared and discovered. At revision -16 it is mature. Exact rules are approximate pending the official Abstract.
By its name this new OAuth individual draft links agents to DNS, plausibly using DNS records to associate an OAuth agent with a domain or to discover agent authorization endpoints. Exact record format is approximate pending the official Abstract.
By its name this new individual draft (TSVWG transport area) concerns 'Homa', a low-latency datacenter transport protocol designed as an alternative to TCP for many short remote-procedure-call messages. As a -00 individual draft it is an early contribution. Exact mechanisms are approximate pending the official Abstract.
Part of the Computing-Aware Traffic Steering (CATS) work. CATS is a traffic-engineering approach that steers traffic toward a service instance while taking into account how computing and network resources vary over time. Making such resource-aware decisions requires exchanging metrics that report the current state of those resources. The Abstract notes that network-domain metrics have long been used in networking systems, and states that this document defines a set of computing-domain metrics for use with CATS, complementing the existing network metrics.
By its name this individual draft defines something named 'AER1'; the expansion is not evident from the name, and the high revision number suggests an automated or long-running individual series. Exact scope is approximate pending the official Abstract.
By its name this individual draft concerns gender representation in the IETF's NomCom (Nominating Committee) process, i.e. a process/administrative document about representation on the committee. Exact proposals are approximate pending the official Abstract.
A CDNI working-group document defining metadata for source access control in Content Delivery Network Interconnection, i.e. how an upstream CDN conveys access-control rules for origin/source content to a downstream CDN. Exact metadata objects are approximate pending the official Abstract.
An IDR working-group document extending BGP-LS to carry administrative flags for Segment Routing (SR) policies, so that SR policy state distributed via BGP-LS can include admin-level flag information. Exact TLV encoding is approximate pending the official Abstract.
By its name this individual draft proposes an update to BCP 35 (the IETF's best current practice on URI scheme registration / 'Guidelines and Registration Procedures for URI Schemes'). Exact normative changes are approximate pending the official Abstract.
By its name this individual draft specifies use of HQC (a code-based KEM selected by NIST for standardization) as a key-encapsulation mechanism in TLS, likely for post-quantum key exchange. Exact TLS integration is approximate pending the official Abstract.
A NETMOD working-group document defining 'YANG packages', a way to group and version collections of YANG modules so that a server's supported schema can be referenced as a named, versioned package. Exact package structure is approximate pending the official Abstract.
By its name this individual draft defines an 'agent://' URI scheme — a URI-based framework for identifying and reaching interoperable agents (consistent with earlier published revisions of the same document). It likely specifies scheme syntax and resolution so agents can be addressed uniformly. Exact details are approximate pending the current revision's official Abstract.
An AVTCORE working-group document about carrying HEVC (H.265) video in WebRTC, i.e. the RTP payload and negotiation specifics needed to use HEVC in browser-based real-time communication. Exact payload/signaling is approximate pending the official Abstract.
By its name this individual draft (Internet area) defines a 'challenge' ICMPv6 message, plausibly an ICMPv6 analogue of the TCP/ICMP challenge mechanism used to validate that a peer is on-path before acting on a message. Exact message format is approximate pending the official Abstract.
A PQUIP working-group document about post-quantum cryptography on constrained HSMs (Hardware Security Modules), likely discussing challenges and guidance for running PQC algorithms where HSM memory/compute is limited. Exact recommendations are approximate pending the official Abstract.
A WIMSE working-group document (Workload Identity in Multi-System Environments) about HTTP message signatures for workload-to-workload authentication, i.e. how workloads sign HTTP requests to prove identity to each other at the application layer. Exact signature components and profiles are approximate pending the official Abstract.
By its name this individual draft (LSVR area) extends BGP-SPF (BGP link-state with shortest-path-first) to support SRv6 (Segment Routing over IPv6), likely for massively scaled data-center routing. Exact encodings are approximate pending the official Abstract.
By its name this new individual draft (MASQUE area) defines qlog event definitions for CONNECT-IP, i.e. structured logging schema for MASQUE IP tunneling so implementations can record and analyze CONNECT-IP behavior. Exact qlog fields are approximate pending the official Abstract.
By its name this individual draft concerns Zstandard (zstd) dictionaries, plausibly registering or specifying how shared compression dictionaries are defined and used. Exact scope is approximate pending the official Abstract.
A PIM working-group document defining a YANG data model for EVPN multicast, i.e. configuration and operational state for multicast in Ethernet VPN deployments. Exact YANG structure is approximate pending the official Abstract.
By its name this individual draft defines 'evaluation state' for an agent protocol, plausibly how the state of an agent's evaluation or task execution is represented and exchanged. Exact state model is approximate pending the official Abstract.
By its name this individual draft (GROW area) extends BMP (BGP Monitoring Protocol) to support multiple instances, plausibly letting a BMP station distinguish and monitor several routing instances on a device. Exact encoding is approximate pending the official Abstract.
By its name this individual draft defines a well-known URI for 'software status', plausibly a standardized endpoint where software can publish its status/version/health. Exact schema is approximate pending the official Abstract.
By its name this individual draft (IPPM area) adds a bandwidth-related trace type to IOAM (In-situ Operations, Administration and Maintenance), so that per-hop bandwidth information can be collected in the IOAM trace option. Exact field definition is approximate pending the official Abstract.
By its name this individual draft defines a JSON format for 'audits', plausibly a structured way to record audit information. Exact schema is approximate pending the official Abstract.
By its name this new HTTPBIS individual draft defines an HTTP 'preview' capability, plausibly letting a server or client obtain a preview of a resource or response before full transfer. Exact header/semantics are approximate pending the official Abstract.