RFC 3330: Special-Use IPv4 Addresses
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5735.
Current document in this lineage: RFC 6890 — Special-Purpose IP Address Registries
In plain English — editorial summary, not part of the RFC
This document describes the global and other specialized IPv4 address blocks that have been assigned by the IANA. It does not address IPv4 address space assigned to operators and users through the Regional Internet Registries. It also does not address allocations or assignments of IPv6 addresses or autonomous system numbers.
Document record
- Document ID
- RFC3330
- Published
- October 2002
- Authors
- IANA
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 5735
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
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6890Special-Purpose IP Address RegistriesUpdated
April 2013
- RFC 3378EtherIP: Tunneling Ethernet Frames in IP DatagramsCurrent
September 2002
- RFC 3387Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP NetworkCurrent
October 2002
- RFC 3021Using 31-Bit Prefixes on IPv4 Point-to-Point LinksCurrent
December 2000
- RFC 2917A Core MPLS IP VPN ArchitectureCurrent
September 2000
- RFC 2764A Framework for IP Based Virtual Private NetworksCurrent
February 2000
- RFC 2638A Two-bit Differentiated Services Architecture for the InternetCurrent
July 1999
- RFC 2523Photuris: Extended Schemes and AttributesCurrent
March 1999
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?