Local-use IPv4/IPv6 Translation Prefix
draft-ietf-v6ops-v4v6-xlat-prefix-02

Document Type Active Internet-Draft (v6ops WG)
Last updated 2017-08-21 (latest revision 2017-06-20)
Replaces draft-anderson-v6ops-v4v6-xlat-prefix
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews GENART will not review this version
Stream WG state Submitted to IESG for Publication (wg milestone: Nov 2017 - Prefix for use by IP... )
Document shepherd Fred Baker
Shepherd write-up Show (last changed 2017-05-02)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to draft-ietf-v6ops-v4v6-xlat-prefix.all@ietf.org, Fred Baker <fredbaker.ietf@gmail.com>
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state AUTH48-DONE
IPv6 Operations                                              T. Anderson
Internet-Draft                                            Redpill Linpro
Intended status: Standards Track                           June 20, 2017
Expires: December 22, 2017

                 Local-use IPv4/IPv6 Translation Prefix
                  draft-ietf-v6ops-v4v6-xlat-prefix-02

Abstract

   This document reserves the IPv6 prefix 64:ff9b:1::/48 for local use
   within domains that enable IPv4/IPv6 translation mechanisms.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on December 22, 2017.

Copyright Notice

   Copyright (c) 2017 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
   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.

Anderson                Expires December 22, 2017               [Page 1]
Internet-Draft   Local-use IPv4/IPv6 Translation Prefix        June 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Why 64:ff9b:1::/48? . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Prefix Length . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Prefix Value  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Deployment Considerations . . . . . . . . . . . . . . . . . .   4
   6.  Checksum Neutrality . . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document reserves 64:ff9b:1::/48 for local use within domains
   that enable IPv4/IPv6 translation mechanisms.  This facilitates the
   co-existence of multiple IPv4/IPv6 translation mechanisms in the same
   network without requiring the use of a Network-Specific Prefix
   assigned from the operator's allocated global unicast address space.

2.  Terminology

   This document makes use of the following terms:

   Network-Specific Prefix (NSP)
      A globally unique prefix assigned by a network operator for use
      with an IPv4/IPv6 translation mechanism [RFC6052].

   Well-Known Prefix (WKP)
      The prefix 64:ff9b::/96, which is reserved for use with the
      [RFC6052] IPv4/IPv6 address translation algorithm.

3.  Problem Statement

   Since the WKP 64:ff9b::/96 was reserved by [RFC6052], several new
   IPv4/IPv6 translation mechanisms have been defined by the IETF, such
   as [RFC6146] and [RFC7915].  These mechanisms target various
   different use cases.  An operator might therefore wish to make use of
   several of them simultaneously.

   The WKP is reserved specifically for use with the algorithm specified
   in [RFC6052].  More recent IETF documents describe IPv4/IPv6

Anderson                Expires December 22, 2017               [Page 2]
Internet-Draft   Local-use IPv4/IPv6 Translation Prefix        June 2017

   translation mechanisms that use different algorithms.  An operator
   deploying such mechanisms can not make use of the WKP in a legitimate
Show full document text