RFC 5375: IPv6 Unicast Address Assignment Considerations
In plain English — editorial summary, not part of the RFC
One fundamental aspect of any IP communications infrastructure is its addressing plan. With its new address architecture and allocation policies, the introduction of IPv6 into a network means that network designers and operators need to reconsider their existing approaches to network addressing. Lack of guidelines on handling this aspect of network design could slow down the deployment and integration of IPv6. This document aims to provide the information and recommendations relevant to planning the addressing aspects of IPv6 deployments. The document also provides IPv6 addressing case studies for both an enterprise and an ISP network. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5375
- Published
- December 2008
- Authors
- G. Van de Velde; C. Popoviciu; T. Chown; O. Bonness; C. Hahn
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4147Proposed Changes to the Format of the IANA IPv6 RegistryCurrent
August 2005
- RFC 4943IPv6 Neighbor Discovery On-Link Assumption Considered HarmfulCurrent
September 2007
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 4852IPv6 Enterprise Network Analysis - IP Layer 3 FocusCurrent
April 2007
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4219Things Multihoming in IPv6 (MULTI6) Developers Should Think AboutCurrent
October 2005
- RFC 4218Threats Relating to IPv6 Multihoming SolutionsCurrent
October 2005
- RFC 4057IPv6 Enterprise Network ScenariosCurrent
June 2005
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?