RFC 3177: IAB/IESG Recommendations on IPv6 Address Allocations to Sites
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6177.
Current version: RFC 6177 — IPv6 Address Assignment to End Sites
In plain English — editorial summary, not part of the RFC
This document provides recommendations to the addressing registries (APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites. In particular, it recommends the assignment of /48 in the general case, /64 when it is known that one and only one subnet is needed and /128 when it is absolutely known that one and only one device is connecting.
Document record
- Document ID
- RFC3177
- Published
- September 2001
- Authors
- IAB; IESG
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 6177
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 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 2000
- RFC 2282IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 1998
- RFC 2027IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
October 1996
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
- RFC 4305Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
December 2005
- RFC 4835Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)Obsoleted
April 2007
- RFC 3238IAB Architectural and Policy Considerations for Open Pluggable Edge ServicesCurrent
January 2002
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?