RFC 6547: RFC 3627 to Historic Status
In plain English — editorial summary, not part of the RFC
This document moves "Use of /127 Prefix Length Between Routers Considered Harmful" (RFC 3627) to Historic status to reflect the updated guidance contained in "Using 127-Bit IPv6 Prefixes on Inter- Router Links" (RFC 6164). A Standards Track document supersedes an informational document; therefore, guidance provided in RFC 6164 is to be followed when the two documents are in conflict. This document links the two RFCs so that the IETF's updated guidance on this topic is clearer. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6547
- Published
- February 2012
- Authors
- W. George
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6519RADIUS Extensions for Dual-Stack LiteCurrent
February 2012
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6221Lightweight DHCPv6 Relay AgentCurrent
May 2011
- RFC 6957Duplicate Address Detection ProxyCurrent
June 2013
- RFC 7048Neighbor Unreachability Detection Is Too ImpatientCurrent
January 2014
- RFC 5970DHCPv6 Options for Network BootCurrent
September 2010
- RFC 5952A Recommendation for IPv6 Address Text RepresentationCurrent
August 2010
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?