Motivations for Stateless IPv4 over IPv6 Migration Solutions
draft-operators-softwire-stateless-4v6-motivation-02

Document Type Replaced Internet-Draft (individual)
Last updated 2011-12-05 (latest revision 2011-06-09)
Replaced by draft-ietf-softwire-stateless-4v6-motivation
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-softwire-stateless-4v6-motivation
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
https://www.ietf.org/archive/id/draft-operators-softwire-stateless-4v6-motivation-02.txt

Abstract

IPv4 service continuity is one of the most sensitive problems that must be resolved by Service Providers during the IPv6 transition period - especially after the exhaustion of the public IPv4 address space. Current standardization effort that addresses IPv4 service continuity focuses on stateful mechanisms. This document elaborates on the motivations for the need to undertake a companion effort to specify stateless IPv4 over IPv6 approaches.

Authors

Gang Chen (chengang@chinamobile.com)
Isabel Borges (Isabel@ptinovacao.pt)
Yiu Lee (yiu_lee@cable.comcast.com)
Olaf Bonness (olaf.bonness@telekom.de)
Mohamed Boucadair (mohamed.boucadair@orange-ftgroup.com)
Satoru Matsushima (satoru.matsushima@tm.softbank.co.jp)

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