RFC 9637: Expanding the IPv6 Documentation Space
In plain English — editorial summary, not part of the RFC
The document describes the reservation of an additional IPv6 address prefix for use in documentation. This update to RFC 3849 expands on the existing 2001:db8::/32 address block with the reservation of an additional, larger prefix. The addition of a /20 prefix allows documented examples to more closely reflect a broader range of realistic, current deployment scenarios and more closely aligns with contemporary allocation models for large networks.
Document record
- Document ID
- RFC9637
- Published
- August 2024
- Authors
- G. Huston; N. Buraglio
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 3849
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9640YANG Data Types and Groupings for CryptographyCurrent
October 2024
- RFC 9641A YANG Data Model for a TruststoreCurrent
October 2024
- RFC 9642A YANG Data Model for a KeystoreCurrent
October 2024
- RFC 9632Finding and Using Geofeed DataCurrent
August 2024
- RFC 9643YANG Groupings for TCP Clients and TCP ServersCurrent
October 2024
- RFC 9644YANG Groupings for SSH Clients and SSH ServersCurrent
October 2024
- RFC 9630Multicast On-Path Telemetry Using In Situ Operations, Administration, and Maintenance (IOAM)Current
August 2024
- RFC 9645YANG Groupings for TLS Clients and TLS ServersCurrent
October 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?