Recent RFCs

RFC 10030: Network Time Protocol (NTP) over the Precision Time Protocol (PTP)

Fri, 14 Aug 2026 00:00:00 GMT

This document specifies a transport for the client-server and symmetric modes of the Network Time Protocol (NTP) that encapsulates NTP messages in messages of the Precision Time Protocol (PTP). This transport enables hardware timestamping in network interface controllers (NICs) that can timestamp only PTP messages and delay corrections in PTP transparent clocks.

RFC 10031: Media Access Control (MAC) Addresses in X.509 Certificates

Thu, 13 Aug 2026 00:00:00 GMT

This document defines a new GeneralName.otherName for inclusion in the X.509 Subject Alternative Name (SAN) and Issuer Alternative Name (IAN) extensions to carry an IEEE Media Access Control (MAC) address. The new name form makes it possible to bind a Layer 2 interface identifier to a public key certificate. Additionally, this document defines how constraints on this name form can be encoded and processed in the X.509 Name Constraints extension (NCE).

RFC 10028: Updates to Dynamic IPv6 Multicast Address Group IDs

Thu, 13 Aug 2026 00:00:00 GMT

This document describes limitations of the existing range of dynamic IPv6 multicast addresses specified in "Allocation Guidelines for IPv6 Multicast Addresses" (RFC 3307). It updates RFC 3307 by replacing these allocations with a new IANA registry in the "IPv6 Multicast Address Space" registry group. The document also defines initial contents of the new registry: a reduced allocation for the Multicast Address Dynamic Client Allocation Protocol (MADCAP) (RFC 2730), a range for Source-Specific Multicast (SSM), a Private Use range, a range for Experimental Use, and Solicited-Node multicast addresses (which were not previously noted in RFC 3307).

RFC 10018: Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress Replication

Thu, 13 Aug 2026 00:00:00 GMT

A Point-to-Multipoint (P2MP) tree in a Segment Routing (SR) domain carries traffic from a Root to a set of Leaves. This document specifies extensions to BGP encodings and procedures for P2MP trees and Ingress Replication used in BGP/MPLS IP VPNs and Ethernet VPNs (EVPNs) in an SR domain. This document updates RFCs 6514 and 7988.

RFC 9971: Multiple Loss Ratio Search

Thu, 13 Aug 2026 00:00:00 GMT

This document describes an alternative to throughput in "Benchmarking Methodology for Network Interconnect Devices" (RFC 2544) by defining a new methodology called Multiple Loss Ratio Search (MLRsearch). MLRsearch aims to minimize Search Duration, support multiple loss ratio goals, and improve result repeatability and comparability.

MLRsearch is motivated by the pressing need to address the challenges of evaluating and testing the various data plane solutions, especially in software-based networking systems based on Commercial Off-the-Shelf (COTS) CPU hardware vs. purpose-built Application-Specific Integrated Circuit (ASIC) / Network Processing Unit (NPU) / Field-Programmable Gate Array (FPGA) hardware.

RFC 10027: Best Current Practice for Security of Cross-Device Flows

Tue, 11 Aug 2026 00:00:00 GMT

This document describes threats against cross-device flows along with practical mitigations, protocol selection guidance, and a summary of formal analysis results identified as relevant to the security of cross-device flows. It serves as a security guide to system designers, architects, product managers, security specialists, fraud analysts, and engineers implementing cross-device flows.

RFC 10006: Automatic SIP Trunking and Peering

Tue, 11 Aug 2026 00:00:00 GMT

This document specifies a framework that enables enterprise telephony

Session Initiation Protocol (SIP) networks to solicit and obtain a

capability set document from a SIP service provider. The capability

set document encodes a set of characteristics that enable easy

peering between enterprise and service provider SIP networks.

RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments

Tue, 11 Aug 2026 00:00:00 GMT

This document provides guidelines and documents best current practice for operating authoritative DNS servers, recursive resolvers, and stub resolvers in a mixed IPv4/IPv6 environment. This document recommends that both authoritative DNS servers and recursive resolvers support IPv4 and IPv6. It also provides guidance on how recursive DNS resolvers should select upstream DNS servers, including when IPv4-embedded IPv6 addresses are available.

This document obsoletes RFC 3901.

RFC 10024: Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3

Mon, 10 Aug 2026 00:00:00 GMT

This document defines three hybrid key agreement mechanisms for TLS 1.3 -- X25519MLKEM768, SecP256r1MLKEM768, and SecP384r1MLKEM1024 -- that combine the post-quantum ML-KEM (Module-Lattice-Based Key Encapsulation Mechanism) with an ECDHE (Ephemeral Elliptic Curve Diffie-Hellman) exchange.

RFC 10029: DNS Multiple QTYPEs

Fri, 31 Jul 2026 00:00:00 GMT

This document specifies a method for a DNS client to request additional DNS record types to be delivered alongside the primary record type specified in the Question section of a DNS QUERY (OpCode=0).

RFC 10022: IMAP UIDBATCHES Extension

Fri, 31 Jul 2026 00:00:00 GMT

The UIDBATCHES extension of the Internet Message Access Protocol (IMAP) allows clients to retrieve Unique Identifier (UID) ranges that partition a mailbox's messages into equally sized batches. This enables clients to perform operations such as FETCH, SEARCH, and STORE on specific message batches, providing better control over resource usage and response sizes. The extension is particularly useful with the UIDONLY mode where sequence numbers are unavailable.

RFC 10023: The "_for-sale" Underscored and Globally Scoped DNS Node Name

Thu, 30 Jul 2026 00:00:00 GMT

This document defines an operational convention that uses the

reserved underscored DNS leaf node name "_for-sale" to indicate the

parent domain name is available for purchase.

The convention can be deployed without disrupting existing

operations, and it may be applied even when the domain name is still

actively in use.

RFC 10019: Zeroconf Multicast Address Allocation Problem Statement and Requirements

Thu, 30 Jul 2026 00:00:00 GMT

This document surveys current problems with existing protocols for automatically assigning multicast IP addresses in zero-configuration (zeroconf) networking environments. It addresses key challenges, such as link-layer address collisions, hardware limitations, multicast snooping inefficiencies, and the need to avoid manual configuration. Based on these challenges, it derives requirements for a lightweight, decentralized solution for dynamically allocating unique multicast group addresses without central coordination.

The document presents explicit requirements covering discovery, allocation, conflict detection and resolution, and lease management. It also evaluates considerations specific to IPv6 and IPv4 multicast address ranges, and identifies approaches that are unsuited for zeroconf deployment. This foundation serves as a reference for developing future solutions for multicast address allocation that operate autonomously within local networks.

RFC 10013: Entity Attestation Token (EAT) Measured Component

Thu, 30 Jul 2026 00:00:00 GMT

The term "measured component" refers to an object within the attester's target environment whose state can be sampled and typically digested using a cryptographic hash function. Examples of measured components include firmware stored in flash memory, software loaded into memory at start time, data stored in a file system, or values in a CPU register. This document provides the information model for the measured component and two associated data models. This separation is intentional: The JSON and Concise Binary Object Representation (CBOR) serializations, coupled with the media types and associated Constrained Application Protocol (CoAP) Content-Formats, enable the immediate use of the semantics within the Entity Attestation Token (EAT) framework. Meanwhile, the information model can be reused in future specifications to provide additional serializations, for example, using ASN.1.

RFC 9996: Media Types for Protocol Buffers

Thu, 30 Jul 2026 00:00:00 GMT

This document registers media types for Protocol Buffers, a common

extensible mechanism for serializing structured data.