RFC 4852: IPv6 Enterprise Network Analysis - IP Layer 3 Focus
In plain English — editorial summary, not part of the RFC
This document analyzes the transition to IPv6 in enterprise networks focusing on IP Layer 3. These networks are characterized as having multiple internal links and one or more router connections to one or more Providers, and as being managed by a network operations entity. The analysis focuses on a base set of transition notational networks and requirements expanded from a previous document on enterprise scenarios. Discussion is provided on a focused set of transition analysis required for the enterprise to transition to IPv6, assuming a Dual-IP layer (IPv4 and IPv6) network and node environment within the enterprise. Then, a set of transition mechanisms are recommended for each notational network. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4852
- Published
- April 2007
- Authors
- J. Bound; Y. Pouffary; S. Klynsma; T. Chown; D. Green
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 4943IPv6 Neighbor Discovery On-Link Assumption Considered HarmfulCurrent
September 2007
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 5375IPv6 Unicast Address Assignment ConsiderationsCurrent
December 2008
- 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
- RFC 9818DHCPv6 Prefix Delegation on IPv6 Customer Edge (CE) Routers in LANsCurrent
July 2025
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?