Local-Use IPv4/IPv6 Translation Prefix
RFC 8215

Document Type RFC - Proposed Standard (August 2017; No errata)
Last updated 2017-08-22
Replaces draft-anderson-v6ops-v4v6-xlat-prefix
Stream IETF
Formats plain text 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 8215 (Proposed Standard)
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
Internet Engineering Task Force (IETF)                       T. Anderson
Request for Comments: 8215                                Redpill Linpro
Category: Standards Track                                    August 2017
ISSN: 2070-1721

                 Local-Use IPv4/IPv6 Translation Prefix

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 is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8215.

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                     Standards Track                    [Page 1]
RFC 8215         Local-Use IPv4/IPv6 Translation Prefix      August 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
   coexistence 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 uses 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 algorithms.

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 those defined in [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 algorithms
   specified in [RFC6052].  More recent RFCs describe IPv4/IPv6

Anderson                     Standards Track                    [Page 2]
RFC 8215         Local-Use IPv4/IPv6 Translation Prefix      August 2017

   translation mechanisms that use different algorithms.  An operator
   deploying such mechanisms cannot make use of the WKP in a legitimate
   fashion.

   Also, because the WKP is a /96, an operator preferring to use the WKP
   over an NSP can do so for only one of their IPv4/IPv6 translation
   mechanisms.  All others must necessarily use an NSP.
Show full document text