RFC 7381: Enterprise IPv6 Deployment Guidelines
In plain English — editorial summary, not part of the RFC
Enterprise network administrators worldwide are in various stages of preparing for or deploying IPv6 into their networks. The administrators face different challenges than operators of Internet access providers and have reasons for different priorities. The overall problem for many administrators will be to offer Internet- facing services over IPv6 while continuing to support IPv4, and while introducing IPv6 access within the enterprise IT network. The overall transition will take most networks from an IPv4-only environment to a dual-stack network environment and eventually an IPv6-only operating mode. This document helps provide a framework for enterprise network architects or administrators who may be faced with many of these challenges as they consider their IPv6 support strategies.
Document record
- Document ID
- RFC7381
- Published
- October 2014
- Authors
- K. Chittimaneni; T. Chown; L. Howard; V. Kuarsingh; Y. Pouffary; E. Vyncke
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7373Textual Representation of IP Flow Information Export (IPFIX) Abstract Data TypesCurrent
September 2014
- RFC 7398A Reference Path and Measurement Points for Large-Scale Measurement of Broadband PerformanceCurrent
February 2015
- RFC 7359Layer 3 Virtual Private Network (VPN) Tunnel Traffic Leakages in Dual-Stack Hosts/NetworksCurrent
August 2014
- RFC 7404Using Only Link-Local Addressing inside an IPv6 NetworkCurrent
November 2014
- RFC 7407A YANG Data Model for SNMP ConfigurationCurrent
December 2014
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
- RFC 7423Diameter Applications Design GuidelinesCurrent
November 2014
- RFC 7424Mechanisms for Optimizing Link Aggregation Group (LAG) and Equal-Cost Multipath (ECMP) Component Link Utilization in NetworksCurrent
January 2015
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?