Wireline Incremental IPv6

Document Type Replaced Internet-Draft (individual)
Author Victor Kuarsingh 
Last updated 2011-11-28 (latest revision 2011-10-09)
Replaced by RFC 6782, RFC 6782
Stream (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-v6ops-wireline-incremental-ipv6, draft-ietf-v6ops-wireline-incremental-ipv6
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Operators worldwide are in various stages of preparing for, or deploying IPv6 into their networks. The operators often face challenges related to both IPv6 introduction along with a growing risk of IPv4 run out within their organizations. The overall problem for many of there operators will be to meet the simultaneous needs of IPv6 connectivity and continue support for IPv4 connectivity for legacy devices and systems with a depleting supply of IPv4 addresses. The overall transition will take most networks form an IPv4-Only environment to a dual stack network environment and potentially an IPv6-Only operating mode. This document helps provide a framework for Wireline providers who may be faced with many of these challenges as they consider what IPv6 transition technologies to use, how to use the selected technologies and when to use them.


Victor Kuarsingh (victor.kuarsingh@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)