IPv6 Address Assignment to End Sites

Document Type Replaced Internet-Draft (individual in gen area)
Last updated 2008-09-12 (latest revision 2010-07-12)
Replaced by draft-ietf-v6ops-3177bis-end-sites
Stream IETF
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-v6ops-3177bis-end-sites
Telechat date
Responsible AD Jari Arkko
Send notices to narten@us.ibm.com

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 revisits and updates 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 a policy issue under the purview of the RIRs, subject to 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 3177 recommendations. Moreover, the 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 updates and replaces RFC 3177.


Thomas Narten (narten@us.ibm.com)
Geoff Huston (gih@apnic.net)
Rosalea Roberts (lea.roberts@stanford.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)