No RFCs were announced in the 48-hour window. See the freshness note above.
Monday, 14 September 2026 35 drafts
A mature PIM working-group document (revision 24) concerning IP multicast (Protocol Independent Multicast). The token "gaap" is not fully determinable from the title alone, so the precise scope is uncertain. Abstract not retrieved this run; approximate and to be grounded next run.
Proposes the Personal Data Portability Archive (PDPA) format, suitable for import/export, backup/restore, and data-transfer scenarios for personal data. (Grounded in the document's official Abstract, captured from its personal-submission predecessor draft-happel-mailmaint-pdparchive.)
No description available for this document.
Describes using EVPN Ethernet Segment Link Aggregation Group (ES-LAG) technology to provide multi-homing redundancy for Layer 3 services. It synchronizes ARP/ND, multicast state, and IGP routes between redundant PEs without requiring Layer 2 constructs or proprietary Inter-Chassis Communication protocols.
By its name, an individual 6MAN-related draft continuing the author's AERO / OMNI work (Automatic Extended Route Optimization and the Overlay Multilink Network Interface) with an additional "amen" component. Abstract not retrieved this run; approximate.
By its name, an individual draft relating to SCITT (Supply Chain Integrity, Transparency and Trust) receipts covering physical-site engagement. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft defining receipts that record authority transitions for (AI) agents. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft defining enforcement profiles for enterprise AI. Abstract not retrieved this run; approximate. (One of several related -00 submissions by the same author on AI/enforcement/finality themes appearing in this window.)
An IDR working-group document (revision 13) that, by its name, concerns the criteria used in BGP best-path selection. Abstract not retrieved this run; approximate.
Defines version 2.0 of JSCalendar, a data model and JSON representation of calendar data for storage and data exchange in calendaring and scheduling environments. It obsoletes RFC 8984 (version 1.0), improving interoperability with existing iCalendar-based systems and aligning its definitions (IANA registry policy, validation requirements, versioning scheme) with JSContact.
Specifies an RTP payload format for video encoded with JPEG XS (ISO/IEC 21122), a low-latency, low-complexity coding system enabling sub-frame latencies. It is a revision of RFC 9134 adding support for third-edition JPEG XS features, notably the TDC coding mode, and obsoletes RFC 9134 while keeping existing RFC 9134 implementations valid. It also consolidates RFC 9134 errata and adds clarifications for implementers and users.
By its name, an individual IDR-related draft on error handling for BGP NLRI (Network Layer Reachability Information). Abstract not retrieved this run; approximate.
Describes the structure of NFSv4 ACLs and their role in the NFSv4 security architecture, focusing on ACLs as a more flexible file-access authorization approach than the POSIX-derived attributes. It reframes the relationship among supported ACL models, presenting a core feature set derived from the withdrawn POSIX draft ACLs, with additional NFSv4 ACL features as OPTIONAL extensions. Intended to drive working-group discussion; when published it would update RFC 7530 and RFC 8881. (Grounded in the abstract of predecessor draft-dnoveck-nfsv4-acls.)
Defines methodologies for benchmarking the performance of Source Address Validation (SAV) mechanisms, which generate rules to prevent source-address spoofing. Treating a SAV device as a black box, the methodology is agnostic to the underlying mechanism and provides a way to measure the performance of existing and new SAV implementations. (Grounded in the abstract of predecessor draft-chen-bmwg-savnet-sav-benchmarking.)
Describes Semantic Definition Format (SDF) modeling for digital twins and their components. SDF is a format for creating and maintaining data interactions representing exchanged data; here it models the characteristics, behavior, and interactions of Things (physical objects) within digital-twin systems that contain those Things as components. (Grounded in the abstract of predecessor draft-lee-asdf-digital-twin.)
Specifies the FideX Protocol (Application Statement 5, AS5), an application-layer protocol for secure business-to-business message exchange. FideX provides non-repudiation, data integrity, and confidentiality using JOSE over HTTPS, offering a REST-oriented replacement for legacy AS2/AS4. It defines the message format, cryptographic operations, partner discovery, state management, acknowledgment receipts (J-MDN), and error handling.
By its name, an individual TLS draft specifying a hybrid ECDHE + ML-KEM-512 post-quantum key agreement for TLS 1.3. Abstract not retrieved this run; approximate.
Notes that the Cryptographic Message Syntax (CMS) verifies signatures differently depending on whether signed attributes are present, creating a potential existential-forgery (EUF-CMA) vulnerability in CMS and protocols that use it. The document describes the vulnerability and lists best practices and mitigations. (Grounded in the abstract of predecessor draft-vangeest-lamps-cms-euf-cma-signeddata.)
Proposes Flexicast QUIC, a simple extension to Multipath QUIC that lets a source send the same information to a set of receivers using a combination of unicast paths and multicast distribution trees.
By its name, a new -00 individual draft defining "orbital finality" profiles for satellite contexts. Abstract not retrieved this run; approximate.
By its name, an individual TCP-related draft concerning an "SRO" mechanism/option. The exact meaning of the acronym is uncertain from the title alone. Abstract not retrieved this run; approximate.
Describes an experimental Available Session Recovery Protocol (ASRP) that optimizes high-availability clusters for stateful services such as load balancing and NAT. Instead of backing up session state inside the cluster, ASRP distributes state to clients or servers, improving elastic scaling, enabling fast recovery from single- or multi-point failures, removing centralized backup nodes, and simplifying cluster implementation. It defines the backup/recovery procedures and message formats.
By its name, a new -00 individual draft on "silicon finality" in AI-factory / compute contexts. Abstract not retrieved this run; approximate.
Defines an mDNS and DNS-SD mechanism for discovering encrypted DNS services on local networks. It specifies new service types (_dot, _doh, _doq) and TXT-record parameters for zero-configuration discovery of DoT, DoH, and DoQ resolvers, addressing local-network privacy gaps while remaining backward compatible with RFC 6763.
Provides operational guidelines for RPKI delegated Certification Authorities (CAs) and the registry operators managing such delegations. It addresses common operational issues — CA availability, publication quality, and lifecycle management — aiming to improve the health and efficiency of the RPKI ecosystem through best practices for CA operations and delegation management.
A CoRE working-group document (revision 14) that, by its name, defines conditional attributes (likely governing conditions for CoAP resource notification/observation). Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft defining enforcement profiles for execution finality. Abstract not retrieved this run; approximate.
An OPSAWG working-group document (revision 09) that, by its name, addresses the scheduling of OAM (Operations, Administration and Maintenance) tests. Abstract not retrieved this run; approximate.
A DetNet working-group document (revision 11) that, by its name, sets out requirements for scaling deterministic networking. Abstract not retrieved this run; approximate.
By its name, an individual Media-over-QUIC (MoQ) draft on conditional filtering of media objects. Abstract not retrieved this run; approximate.
By its name, an individual draft on the problems and requirements of DNS for "IoA" (likely an Internet-of-Agents / Internet-of-Things context). Abstract not retrieved this run; approximate.
Defines a vocabulary for expressing preferences about how digital assets may be used by automated processing systems, allowing content owners to declare restrictions or permissions for the use of their assets by such systems (e.g., AI training and processing).
By its name, an individual draft on bilateral attestation between agents. Abstract not retrieved this run; approximate.
A very mature IDR working-group document (revision 44) that, by its name, defines BGP-LS extensions for inter-AS topology. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft defining enforcement profiles for "CVID". The acronym is uncertain from the title alone. Abstract not retrieved this run; approximate.
Sunday, 13 September 2026 18 drafts
By its name, an individual REGEXT draft on reliability scoring for RDAP (the Registration Data Access Protocol). Abstract not retrieved this run; approximate.
Defines two HTTP header fields and one Accept-Signature parameter for use with HTTP Message Signatures (RFC 9421). The Signature-Key request header distributes public keys for verifying signatures via five schemes (pseudonymous inline keys, self-issued key delegation via JWK-thumbprint JWTs, JWKS-URI discovery, JWT-based delegation, and X.509 certificate chains). The sigkey parameter extends Accept-Signature to indicate the required key type, and the Signature-Error response header carries structured verification-error information. Together they enable trust models ranging from privacy-preserving pseudonymous verification to scalable delegated authentication and PKI identity chains.
By its name, an individual draft on agent management within "SAMP". The acronym is uncertain from the title alone. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft describing the "core" of HACP agency (an agent-control / agency protocol). Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft describing the architecture of HACP agency (companion to the HACP agency-core draft). Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft on evidence boundaries for agents. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft on OAuth-based revocation closure for agents. Abstract not retrieved this run; approximate.
By its name, an individual RATS-related draft referencing an "extraction" procedure in OpenAI / Anthropic contexts. Abstract not retrieved this run; approximate.
By its name, an individual RATS (Remote ATtestation procedureS) draft on security considerations. Abstract not retrieved this run; approximate.
A PCE working-group document (revision 17) that, by its name, concerns PCEP extensions for flexible-grid (flexi-grid) optical networks. Abstract not retrieved this run; approximate.
A mature individual draft (revision 31) that, by its name, concerns handshake-failure handling. Its exact scope is uncertain from the title alone. Abstract not retrieved this run; approximate.
By its name, an individual LAMPS draft defining a key/certificate "rotation envelope". Abstract not retrieved this run; approximate. (One of several related PQC/PKI submissions by the same author in this window.)
By its name, an individual OAuth draft concerning "APM". The acronym is uncertain from the title alone. Abstract not retrieved this run; approximate.
By its name, an individual PQUIP draft setting out requirements for multi-tenant PKI. Abstract not retrieved this run; approximate.
By its name, an individual PQUIP draft on gaps in post-quantum cryptography readiness. Abstract not retrieved this run; approximate.
By its name, an individual ACME draft defining a post-quantum-cryptography agility profile. Abstract not retrieved this run; approximate.
By its name, a new -00 individual draft on execution finality at the "AI boundary". Abstract not retrieved this run; approximate.
By its name, an individual SCITT draft on payload binding. Abstract not retrieved this run; approximate.