[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 draft-ietf-v6ops-clatip

INTERNET-DRAFT                                             Cameron Byrne
Intended Status: Informational                               T-Mobile US
Expires: July 1, 2014                                  December 28, 2013


               IPv6 Transitional Technology IPv4 Prefix
                      draft-byrne-v6ops-clatip-01


Abstract

   DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the B4
   element.  This memo generalizes that reservation to include other
   cases where a non-routed IPv4 interface must be numbered in an IPv6
   transition solution.


Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html


Copyright and License Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents



Byrne                     Expires July 1, 2014                  [Page 1]


INTERNET DRAFT          Transitional IPv4 Prefix       December 28, 2013


   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.



Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2  The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Choosing 192.0.0.0/29  . . . . . . . . . . . . . . . . . . . .  3
   4  Security Considerations . . . . . . . . . . . . . . . . . . . .  3
   5  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  3
   6  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     6.1  Normative References  . . . . . . . . . . . . . . . . . . .  4
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  4

































Byrne                     Expires July 1, 2014                  [Page 2]


INTERNET DRAFT          Transitional IPv4 Prefix       December 28, 2013


1  Introduction

   DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the B4
   element.  This memo generalizes that IANA reservation to include
   other cases where a non-routed IPv4 interface must be numbered in an
   IPv6 transition solutions.  IANA shall list 192.0.0.0/29 to be
   reserved for IPv6 Transitional Technology IPv4 Prefix.  The result is
   that 192.0.0.0/29 may be used in any system that requires IPv4
   addresses for backward compatibility with IPv4 communications, but
   does not emit IPv4 packets "on the wire".

2  The Case of 464XLAT

   464XLAT [RFC6877] describes an architecture for providing IPv4
   communication over an IPv6-only access network.  One of the methods
   described in [RFC6877] is for the client side translator (CLAT) to be
   embedded in the host, such as a smartphone.  In this scenario, the
   host must have an IPv4 address configured to present to the network
   stack and for applications to bind sockets.

3.  Choosing 192.0.0.0/29

   To avoid conflicts with any other network that may communicate with
   the CLAT, a locally unique address must be assigned.

   IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333],
   which is dedicated for DS-lite.  As defined in [RFC6333], this subnet
   is only present between the B4 and the AFTR and never emits packets
   from this prefix "on the wire".  464XLAT has the same need for a non-
   routed IPv4 prefix.  It is most prudent and effective to generalize
   192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6
   transition technologies rather than reserving a prefix for every
   possible solution.

4  Security Considerations

   No new security considerations beyond what is described [RFC6333] and
   [RFC6877].


5  IANA Considerations

   IANA is directed to generalize the reservation of 192.0.0.0/29 from
   DS-lite to "IPv6 Transitional Technology IPv4 Prefix".


6  References




Byrne                     Expires July 1, 2014                  [Page 3]


INTERNET DRAFT          Transitional IPv4 Prefix       December 28, 2013


6.1  Normative References

   [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
              Stack Lite Broadband Deployments Following IPv4
              Exhaustion", RFC6333, August 2011.

   [RFC6877]  Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
              Combination of Stateful and Stateless Translation",
              RFC6877, April 2013.



Authors' Addresses


              Cameron Byrne
              Bellevue, WA, USA
              Email: Cameron.Byrne@T-Mobile.com

































Byrne                     Expires July 1, 2014                  [Page 4]


Html markup produced by rfcmarkup 1.129c, available from https://tools.ietf.org/tools/rfcmarkup/