| |
| RFC 9800 | Compressed SRv6 Segment List Encoding |
| |
| Authors: | W. Cheng, Ed., C. Filsfils, Z. Li, B. Decraene, F. Clad, Ed.. |
| Date: | June 2025 |
| Formats: | txt xml pdf json html |
| Updates: | RFC 8754 |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9800 |
|
Segment Routing over IPv6 (SRv6) is the instantiation of SegmentRouting (SR) on the IPv6 data plane. This document specifies new flavors for the SRv6 endpoint behaviors defined in RFC 8986, which enable the compression of an SRv6 segment list. Such compression significantly reduces the size of the SRv6 encapsulation needed to steer packets over long segment lists.
This document updates RFC 8754 by allowing a Segment List entry in the Segment Routing Header (SRH) to be either an IPv6 address, as specified in RFC 8754, or a REPLACE-CSID container in packed format, as specified in this document. |
|
| |
| RFC 9801 | Private Line Emulation over Packet Switched Networks |
| |
| Authors: | S. Gringeri, J. Whittaker, N. Leymann, C. Schmutzer, Ed., C. Brown. |
| Date: | July 2025 |
| Formats: | txt json xml pdf html |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9801 |
|
This document expands the applicability of Virtual Private WireService (VPWS) bit-stream payloads beyond Time Division Multiplexing(TDM) signals and provides pseudowire transport with complete signal transparency over Packet Switched Networks (PSNs). |
|
| |
| RFC 9802 | Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key Infrastructure |
| |
| Authors: | D. Van Geest, K. Bashiri, S. Fluhrer, S. Gazdag, S. Kousidis. |
| Date: | June 2025 |
| Formats: | txt html pdf json xml |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9802 |
|
This document specifies algorithm identifiers and ASN.1 encoding formats for the following stateful Hash-Based Signature (HBS) schemes: Hierarchical Signature System (HSS), eXtended MerkleSignature Scheme (XMSS), and XMSS^MT (a multi-tree variant of XMSS).This specification applies to the Internet X.509 Public KeyInfrastructure (PKI) when digital signatures are used to sign certificates and certificate revocation lists (CRLs). |
|
| |
| RFC 9803 | Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values |
| |
|
|
This document describes an extension to the Extensible ProvisioningProtocol (EPP) that allows EPP clients to manage the Time-to-Live(TTL) value for domain name delegation records. |
|
| |
| RFC 9804 | Simple Public Key Infrastructure (SPKI) S-Expressions |
| |
|
|
This memo specifies the data structure representation that was devised to support Simple Public Key Infrastructure (SPKI) certificates, as detailed in RFC 2692, with the intent that it be more widely applicable. It has been and is being used elsewhere.There are multiple implementations in a variety of programming languages. Uses of this representation are referred to in this document as "S-expressions". This memo makes precise the encodings of these SPKI S-expressions: It gives a "canonical form" for them, describes two "transport" representations, and also describes an"advanced" format for display to people. |
|
| |
| RFC 9805 | Deprecation of the IPv6 Router Alert Option for New Protocols |
| |
|
|
This document deprecates the IPv6 Router Alert option. Protocols that use the IPv6 Router Alert option may continue to do so, even in future versions. However, new protocols that are standardized in the future must not use the IPv6 Router Alert option.
This document updates RFC 2711. |
|
| |
| RFC 9806 | Updates to SIP-Based Media Recording (SIPREC) to Correct Metadata Media Type |
| |
|
|
The SIP-based Media Recording (SIPREC) protocol is defined by both"Session Initiation Protocol (SIP) Recording Metadata" (RFC 7865) and"Session Recording Protocol" (RFC 7866). Unfortunately, both RFCs contradict each other regarding how recording metadata is to be labeled. In addition, neither RFC registered the new media type.This document updates RFC 7866 to align with RFC 7865 when labeling recording metadata and also registers the media type. |
|
| |
| RFC 9809 | X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical Communication |
| |
| Authors: | H. Brockhaus, D. Goltzsche. |
| Date: | July 2025 |
| Formats: | txt xml json pdf html |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9809 |
|
RFC 5280 defines the Extended Key Usage (EKU) extension and specifies several extended key purpose identifiers (KeyPurposeIds) for use with that extension in X.509 certificates. This document definesKeyPurposeIds for general-purpose and trust anchor configuration files, for software and firmware update packages, and for safety- critical communication to be included in the EKU extension of X.509 v3 public key certificates. |
|
| |
| RFC 9813 | Operational Considerations for Using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS |
| |
|
|
This document provides implementation and operational considerations for using TLS Pre-Shared Keys (TLS-PSKs) with RADIUS/TLS (RFC 6614) and RADIUS/DTLS (RFC 7360). The purpose of the document is to help smooth the operational transition from the use of RADIUS/UDP toRADIUS/TLS. |
|
