Motivations for Carrier-side Stateless IPv4 over IPv6 Migration Solutions

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc: RFC Editor <>,
    softwire mailing list <>,
    softwire chair <>
Subject: Document Action: 'Motivations for Carrier-side Stateless IPv4 over IPv6 Migration Solutions' to Informational RFC (draft-ietf-softwire-stateless-4v6-motivation-04.txt)

The IESG has approved the following document:
- 'Motivations for Carrier-side Stateless IPv4 over IPv6 Migration
  (draft-ietf-softwire-stateless-4v6-motivation-04.txt) as Informational

This document is the product of the Softwires Working Group.

The IESG contact persons are Ralph Droms and Brian Haberman.

A URL of this Internet Draft is:

Technical Summary 

  IPv4 service continuity is a desired function even for IPv6 access
  networks. 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.

Working Group Summary  

  The softwire interim meeting in Beijing intensively discussed the
  stateless motivations and potential solutions. The stateless
  motivation got strong concencus during the following ietf
  face-to-face meetings and on the mailing list, from both major
  operators and vendors. Most of the operators in Softwire are quite
  active in stateless motivations and they joined the detailed work of
  composing the motivations into the document.  The document was
  reviewed thoroughly in the working group. There are not any existing
  issues in the document and the document is ready for advancement.

Document Quality 

  This is motivation document rather than a protocol definition, so
  there are no implementations to report on.  The document was not
  given any special external review beyond thorough review in the
  working group.


  Softwire co-chair, Yong Cui, is the Document Shepherd.  Ralph Droms
  is the Responsible AD.

RFC Editor Note

  (Insert RFC Editor Note here or remove section)


  (Insert IRTF Note here or remove section)


  (Insert IESG Note here or remove section)


  (Insert IANA Note here or remove section)