RFC 3627: Use of /127 Prefix Length Between Routers Considered Harmful
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6547.
Current version: RFC 6547 — RFC 3627 to Historic Status
In plain English — editorial summary, not part of the RFC
In some cases, the operational decision may be to use IPv6 /127 prefix lengths, especially on point-to-point links between routers. Under certain situations, this may lead to one router claiming both addresses due to subnet-router anycast being implemented. This document discusses the issue and offers a couple of solutions to the problem; nevertheless, /127 should be avoided between two routers.
Document record
- Document ID
- RFC3627
- Published
- September 2003
- Authors
- P. Savola
- Status
- HISTORIC
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 6
- Also known as
- —
- Obsoleted by:
- RFC 6547
Topics
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 9199Considerations for Large Authoritative DNS Server OperatorsCurrent
March 2022
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 4291IP Version 6 Addressing ArchitectureUpdated
February 2006
- RFC 2901Guide to Administrative Procedures of the Internet InfrastructureCurrent
August 2000
- RFC 2373IP Version 6 Addressing ArchitectureObsoleted
July 1998
- RFC 7094Architectural Considerations of IP AnycastCurrent
January 2014
- RFC 7534AS112 Nameserver OperationsCurrent
May 2015
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
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?