Skip to main content

IPv6 Address Assignment to End Sites
RFC 6177 also known as BCP 157

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc6177 in bcp157 via sync to the rfc-index
2023-12-12
(System) No history of BCP157 is currently available in the datatracker before this point
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks in most cases. …
Received changes through RFC Editor sync (changed abstract to '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]')
2017-05-16
(System) Changed document authors from "Geoff Huston, Thomas Narten" to "Geoff Huston, Thomas Narten, Rosalea Roberts"
2015-10-14
(System) Notify list changed from v6ops-chairs@ietf.org, draft-ietf-v6ops-3177bis-end-sites@ietf.org to (None)
2011-03-28
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-03-28
Cindy Morgan [Note]: changed to 'BCP 157, RFC 6177
'
2011-03-27
(System) RFC published