| |
| RFC 9900 | Updates to NETCONF Transport Port Numbers |
| |
|
|
This document releases IANA-assigned port numbers for services related to the Network Configuration Protocol (NETCONF) that have not been in use in production networks. |
|
| |
| RFC 9901 | Selective Disclosure for JSON Web Tokens |
| |
| Authors: | D. Fett, K. Yasuda, B. Campbell. |
| Date: | November 2025 |
| Formats: | txt html pdf xml json |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9901 |
|
This specification defines a mechanism for the selective disclosure of individual elements of a JSON data structure used as the payload of a JSON Web Signature (JWS). The primary use case is the selective disclosure of JSON Web Token (JWT) claims. |
|
| |
| RFC 9902 | A YANG Data Model for IS-IS Segment Routing over the MPLS Data Plane |
| |
| Authors: | S. Litkowski, Y. Qu, A. Lindem, I. Chen, J. Tantsura. |
| Date: | December 2025 |
| Formats: | txt json html xml pdf |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9902 |
|
This document defines a YANG data model that can be used to manageIS-IS extensions for Segment Routing (SR) over the MPLS data plane. |
|
| |
| RFC 9903 | A YANG Data Model for OSPF Segment Routing over the MPLS Data Plane |
| |
| Authors: | Y. Qu, A. Lindem, J. Zhang, I. Chen. |
| Date: | December 2025 |
| Formats: | txt json xml pdf html |
| Status: | PROPOSED STANDARD |
| DOI: | 10.17487/RFC 9903 |
|
This document defines a YANG data model that can be used to manageOSPF extensions for Segment Routing over the MPLS data plane. |
|
| |
| RFC 9904 | DNSSEC Cryptographic Algorithm Recommendation Update Process |
| |
|
|
The DNSSEC protocol makes use of various cryptographic algorithms to provide authentication of DNS data and proof of nonexistence. To ensure interoperability between DNS resolvers and DNS authoritative servers, it is necessary to specify both a set of algorithm implementation requirements and usage guidelines to ensure that there is at least one algorithm that all implementations support. This document replaces and obsoletes RFC 8624 and moves the canonical source of algorithm implementation requirements and usage guidance for DNSSEC from RFC 8624 to the IANA DNSSEC algorithm registries.This is done to allow the list of requirements to be more easily updated and referenced. Extensions to these registries can be made in future RFCs. This document also updates RFC 9157 and incorporates the revised IANA DNSSEC considerations from that RFC.
This document does not change the recommendation status (MUST, MAY,RECOMMENDED, etc.) of the algorithms listed in RFC 8624; that is the work of future documents. |
|
| |
| RFC 9905 | Deprecating the Use of SHA-1 in DNSSEC Signature Algorithms |
| |
|
|
This document deprecates the use of the RSASHA1 andRSASHA1-NSEC3-SHA1 algorithms for the creation of DNS Public Key(DNSKEY) and Resource Record Signature (RRSIG) records.
It updates RFCs 4034 and 5155 as it deprecates the use of these algorithms. |
|
