RFC 6177: IPv6 Address Assignment to End Sites
In plain English — editorial summary, not part of the RFC
RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks in most cases. The Regional Internet Registries (RIRs) adopted that recommendation in 2002, but began reconsidering the policy in 2005. This document obsoletes the RFC 3177 recommendations on the assignment of IPv6 address space to end sites. The exact choice of how much address space to assign end sites is an issue for the operational community. The IETF's role in this case is limited to providing guidance on IPv6 architectural and operational considerations. This document reviews the architectural and operational considerations of end site assignments as well as the motivations behind the original recommendations in RFC 3177. Moreover, this document clarifies that a one-size-fits-all recommendation of /48 is not nuanced enough for the broad range of end sites and is no longer recommended as a single default. This document obsoletes RFC 3177. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6177
- Published
- March 2011
- Authors
- T. Narten; G. Huston; L. Roberts
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- BCP157
- Obsoletes:
- RFC 3177
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5633Nominating Committee Process: Earlier Announcement of Open Positions and Solicitation of VolunteersObsoleted
August 2009
- RFC 5078IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees TimelineObsoleted
October 2007
- RFC 7437IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
January 2015
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 5771IANA Guidelines for IPv4 Multicast Address AssignmentsCurrent
March 2010
- RFC 8907The Terminal Access Controller Access-Control System Plus (TACACS+) ProtocolUpdated
September 2020
- RFC 3410Introduction and Applicability Statements for Internet-Standard Management FrameworkCurrent
December 2002
- RFC 3222Terminology for Forwarding Information Base (FIB) based Router PerformanceCurrent
December 2001
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?