RFC 5737: IPv4 Address Blocks Reserved for Documentation
In plain English — editorial summary, not part of the RFC
Three IPv4 unicast address blocks are reserved for use in examples in specifications and other documents. This document describes the use of these blocks. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5737
- Published
- January 2010
- Authors
- J. Arkko; M. Cotton; L. Vegoda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 1166
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 2009
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 6145IP/ICMP Translation AlgorithmObsoleted
April 2011
- RFC 6441Time to Remove Filters for Previously Unallocated IPv4 /8sCurrent
November 2011
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 6540IPv6 Support Required for All IP-Capable NodesCurrent
April 2012
- RFC 6556Testing Eyeball HappinessCurrent
April 2012
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?