RFC 5156: Special-Use IPv6 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 is a compilation of special IPv6 addresses defined in other RFCs. It can be used as a checklist of invalid routing prefixes for developing filtering policies for routes and IP packets. It does not discuss addresses that are assigned to operators and users through the Regional Internet Registries. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5156
- Published
- April 2008
- Authors
- M. Blanchet
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6890
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 5157IPv6 Implications for Network ScanningObsoleted
March 2008
- RFC 5153IP Flow Information Export (IPFIX) Implementation GuidelinesCurrent
April 2008
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 5180IPv6 Benchmarking Methodology for Network Interconnect DevicesCurrent
May 2008
- RFC 5132IP Multicast MIBCurrent
December 2007
- RFC 5181IPv6 Deployment Scenarios in 802.16 NetworksCurrent
May 2008
- RFC 5110Overview of the Internet Multicast Routing ArchitectureCurrent
January 2008
- RFC 5103Bidirectional Flow Export Using IP Flow Information Export (IPFIX)Current
January 2008
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?