RFC 5735: Special Use IPv4 Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6890.
Current document in this lineage: RFC 6890 — Special-Purpose IP Address Registries
In plain English — editorial summary, not part of the RFC
This document obsoletes RFC 3330. It describes the global and other specialized IPv4 address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA). It does not address IPv4 address space assigned to operators and users through the Regional Internet Registries, nor does it address IPv4 address space assigned directly by IANA prior to the creation of the Regional Internet Registries. It also does not address allocations or assignments of IPv6 addresses or autonomous system numbers. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC5735
- Published
- January 2010
- Authors
- M. Cotton; L. Vegoda
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Read the full history of Special-Purpose IP Address Registries →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5944IP Mobility Support for IPv4, RevisedCurrent
November 2010
- RFC 5445Basic Forward Error Correction (FEC) SchemesCurrent
March 2009
- RFC 6034Unicast-Prefix-Based IPv4 Multicast AddressesCurrent
October 2010
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6434IPv6 Node RequirementsObsoleted
December 2011
- RFC 4891Using IPsec to Secure IPv6-in-IPv4 TunnelsCurrent
May 2007
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?