RFC 4057: IPv6 Enterprise Network Scenarios
In plain English — editorial summary, not part of the RFC
This document describes the scenarios for IPv6 deployment within enterprise networks. It defines a small set of basic enterprise scenarios and includes pertinent questions to allow enterprise administrators to further refine their deployment scenarios. Enterprise deployment requirements are discussed in terms of coexistence with IPv4 nodes, networks and applications, and in terms of basic network infrastructure requirements for IPv6 deployment. The scenarios and requirements described in this document will be the basis for further analysis to determine what coexistence techniques and mechanisms are needed for enterprise IPv6 deployment. The results of that analysis will be published in a separate document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4057
- Published
- June 2005
- Authors
- J. Bound
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4218Threats Relating to IPv6 Multihoming SolutionsCurrent
October 2005
- RFC 4219Things Multihoming in IPv6 (MULTI6) Developers Should Think AboutCurrent
October 2005
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4852IPv6 Enterprise Network Analysis - IP Layer 3 FocusCurrent
April 2007
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 4943IPv6 Neighbor Discovery On-Link Assumption Considered HarmfulCurrent
September 2007
- RFC 5375IPv6 Unicast Address Assignment ConsiderationsCurrent
December 2008
- 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?