Protocol Action: 'IPv4 Service Continuity Prefix' to Proposed Standard (draft-ietf-v6ops-clatip-04.txt)

The IESG <iesg-secretary@ietf.org> Tue, 05 August 2014 13:29 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'IPv4 Service Continuity Prefix' to Proposed Standard (draft-ietf-v6ops-clatip-04.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140805132932.9415.45052.idtracker@ietfa.amsl.com>
Date: Tue, 05 Aug 2014 06:29:32 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/NtyxR3yYqFLtHp-OflWC0uUjk3o
Cc: v6ops mailing list <v6ops@ietf.org>, v6ops chair <v6ops-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Reply-To: ietf@ietf.org

The IESG has approved the following document:
- 'IPv4 Service Continuity Prefix'
  (draft-ietf-v6ops-clatip-04.txt) as Proposed Standard

This document is the product of the IPv6 Operations Working Group.

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-v6ops-clatip/





Technical Summary

  DS-Lite, defined in RFC 6333,  directs IANA to reserve 192.0.0.0/29
  for the B4 element.  This memo directs IANA to generalize that
  reservation to include other cases where a non-routed IPv4 interface
  must be numbered as part of an IPv6 transition solution.

Working Group Summary

There was support in the working group for the draft, and little if any 
dissent.

Document Quality

This is not a protocol; it is advice to implementers of 464xlat that the
prefix set aside for use with DS-Lite may also be used by them. Per 
Lorenzo Colitti, it is implemented in the Android OS, and works.

Personnel

Document Shepherd: Fred Baker 
Responsible Area Director: Joel Jaeggli

Protocol Action: 'IPv4 Service Continuity Prefix'… The IESG