<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Recent RFCs</title>
        <link>https://www.rfc-editor.org</link>
        <description>Recently published RFCs</description>
        <lastBuildDate>Fri, 28 Aug 2026 20:38:28 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://www.npmjs.com/package/feed</generator>
        <language>en-us</language>
        <item>
            <title><![CDATA[RFC 10038: Distributing the Segment Routing over IPv6 (SRv6) Locator Using DHCPv6]]></title>
            <link>https://www.rfc-editor.org/info/rfc10038/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10038/</guid>
            <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned an SRv6 Locator, and segment identifiers (SIDs) are generated within the address space of this SRv6 Locator. This document describes a method for assigning SRv6 Locators to SRv6 Segment Endpoint Nodes through the Dynamic Host Configuration Protocol for IPv6 (DHCPv6).]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10037: Registration Data Access Protocol (RDAP) Extension for DNS Time-to-Live (TTL) Values]]></title>
            <link>https://www.rfc-editor.org/info/rfc10037/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10037/</guid>
            <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This document specifies an extension to the Registration Data Access Protocol (RDAP), which allows the Time-to-Live (TTL) values for relevant DNS record types to be included in RDAP responses.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10034: RTP Payload Format for Visual Volumetric Video-Based Coding (V3C)]]></title>
            <link>https://www.rfc-editor.org/info/rfc10034/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10034/</guid>
            <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[A visual volumetric video-based coding (V3C) ISO/IEC 23090-5 bitstream is composed of V3C units that contain V3C atlas sub-bitstreams, V3C video sub-bitstreams, and a V3C parameter set. This document describes an RTP payload format for V3C atlas sub-bitstreams. The RTP payload format for V3C video sub-bitstreams is defined by relevant IETF RFCs for the applicable video codec. The V3C RTP payload format allows for the packetization of one or more V3C atlas Network Abstraction Layer (NAL) units in an RTP packet payload as well as the fragmentation of a V3C atlas NAL unit into multiple RTP packets. The document also describes the mechanisms for grouping RTP streams of V3C component sub-bitstreams, providing a complete solution for streaming V3C-encoded content.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10035: YANG Library: Addition of the augmented-by List]]></title>
            <link>https://www.rfc-editor.org/info/rfc10035/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10035/</guid>
            <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[<p>"YANG Library" (RFC 8525) specifies the "ietf-yang-library" YANG module that provides information about the YANG modules, datastores, and datastore schemas used by a network management server.</p><p>This document augments the "ietf-yang-library" module to provide the augmented-by list. It facilitates the process of obtaining all dependencies between YANG modules by querying the network management server's YANG library. This document updates RFC 8525 to also include the augmented-by list.</p>]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10036: Incremental Forwarding of HTTP Messages]]></title>
            <link>https://www.rfc-editor.org/info/rfc10036/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10036/</guid>
            <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[<p>This document specifies the "Incremental" HTTP header field, which</p><p>instructs HTTP intermediaries to forward the HTTP message</p><p>incrementally.</p>]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10017: OAuth 2.0 for Browser-Based Applications]]></title>
            <link>https://www.rfc-editor.org/info/rfc10017/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10017/</guid>
            <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[This specification details the threats, attack consequences, security considerations, and best practices that must be taken into account when developing browser-based applications that use OAuth 2.0.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10030: Network Time Protocol (NTP) over the Precision Time Protocol (PTP)]]></title>
            <link>https://www.rfc-editor.org/info/rfc10030/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10030/</guid>
            <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10031: Media Access Control (MAC) Addresses in X.509 Certificates]]></title>
            <link>https://www.rfc-editor.org/info/rfc10031/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10031/</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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).]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10028: Updates to Dynamic IPv6 Multicast Address Group IDs]]></title>
            <link>https://www.rfc-editor.org/info/rfc10028/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10028/</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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).]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10018: Multicast and Ethernet VPN with Segment Routing Point-to-Multipoint (P2MP) and Ingress Replication]]></title>
            <link>https://www.rfc-editor.org/info/rfc10018/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10018/</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 9971: Multiple Loss Ratio Search]]></title>
            <link>https://www.rfc-editor.org/info/rfc9971/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc9971/</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[<p>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.</p><p>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.</p>]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10027: Best Current Practice for Security of Cross-Device Flows]]></title>
            <link>https://www.rfc-editor.org/info/rfc10027/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10027/</guid>
            <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10006: Automatic SIP Trunking and Peering]]></title>
            <link>https://www.rfc-editor.org/info/rfc10006/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10006/</guid>
            <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[<p>This document specifies a framework that enables enterprise telephony</p><p>Session Initiation Protocol (SIP) networks to solicit and obtain a</p><p>capability set document from a SIP service provider.  The capability</p><p>set document encodes a set of characteristics that enable easy</p><p>peering between enterprise and service provider SIP networks.</p>]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10001: Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments]]></title>
            <link>https://www.rfc-editor.org/info/rfc10001/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10001/</guid>
            <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[<p>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.</p><p>This document obsoletes RFC 3901.</p>]]></description>
        </item>
        <item>
            <title><![CDATA[RFC 10024: Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3]]></title>
            <link>https://www.rfc-editor.org/info/rfc10024/</link>
            <guid isPermaLink="true">https://www.rfc-editor.org/info/rfc10024/</guid>
            <pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
        </item>
    </channel>
</rss>