Skip to main content

IPv4 Run-Out and IPv4-IPv6 Co-Existence Scenarios
RFC 6127

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'When IPv6 was designed, it was expected that the transition from IPv4 to IPv6 would occur …
Received changes through RFC Editor sync (changed abstract to 'When IPv6 was designed, it was expected that the transition from IPv4 to IPv6 would occur more smoothly and expeditiously than experience has revealed. The growth of the IPv4 Internet and predicted depletion of the free pool of IPv4 address blocks on a foreseeable horizon has highlighted an urgent need to revisit IPv6 deployment models. This document provides an overview of deployment scenarios with the goal of helping to understand what types of additional tools the industry needs to assist in IPv4 and IPv6 co-existence and transition.

This document was originally created as input to the Montreal co- existence interim meeting in October 2008, which led to the rechartering of the Behave and Softwire working groups to take on new IPv4 and IPv6 co-existence work. This document is published as a historical record of the thinking at the time, but hopefully will also help readers understand the rationale behind current IETF tools for co-existence and transition. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2015-10-14
(System) Notify list changed from jari.arkko@piuha.net, townsley@cisco.com, draft-arkko-townsley-coexistence@ietf.org to (None)
2011-05-26
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-05-25
(System) RFC published