RFC 6589: Considerations for Transitioning Content to IPv6
In plain English — editorial summary, not part of the RFC
This document describes considerations for the transition of end-user content on the Internet to IPv6. While this is tailored to address end-user content, which is typically web-based, many aspects of this document may be more broadly applicable to the transition to IPv6 of other applications and services. This document explores the challenges involved in the transition to IPv6, potential migration tactics, possible migration phases, and other considerations. The audience for this document is the Internet community generally, particularly IPv6 implementers. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6589
- Published
- April 2012
- Authors
- J. Livingood
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 27
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6583Operational Neighbor Discovery ProblemsCurrent
March 2012
- RFC 6576IP Performance Metrics (IPPM) Standard Advancement TestingCurrent
March 2012
- RFC 6615Definitions of Managed Objects for IP Flow Information ExportCurrent
June 2012
- RFC 6555Happy Eyeballs: Success with Dual-Stack HostsObsoleted
April 2012
- RFC 6632An Overview of the IETF Network Management StandardsCurrent
June 2012
- RFC 6536Network Configuration Protocol (NETCONF) Access Control ModelObsoleted
March 2012
- RFC 6643Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG ModulesCurrent
July 2012
- RFC 6534Loss Episode Metrics for IP Performance Metrics (IPPM)Current
May 2012
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?