Learning NAT64 PREFIX64s using Port Control Protocol (PCP)
draft-ietf-pcp-nat64-prefix64-05

The information below is for an old version of the document
Document Type Active Internet-Draft (pcp WG)
Last updated 2014-02-20 (latest revision 2014-02-03)
Replaces draft-boucadair-pcp-nat64-prefix64-option
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Dave Thaler
Shepherd write-up Show (last changed 2013-10-21)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Telechat date
Responsible AD Ted Lemon
Send notices to pcp-chairs@tools.ietf.org, draft-ietf-pcp-nat64-prefix64@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
IANA action state None
PCP Working Group                                           M. Boucadair
Internet-Draft                                            France Telecom
Intended status: Standards Track                       February 04, 2014
Expires: August 8, 2014

       Learning NAT64 PREFIX64s using Port Control Protocol (PCP)
                    draft-ietf-pcp-nat64-prefix64-05

Abstract

   This document defines a new Port Control Protocol (PCP) option to
   learn the IPv6 prefix(es) used by a PCP-controlled NAT64 device to
   build IPv4-converted IPv6 addresses.  This option is needed for
   successful communications when IPv4 addresses are used in referrals.

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 August 8, 2014.

Copyright Notice

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

Boucadair                Expires August 8, 2014                 [Page 1]
Internet-Draft                 PCP & NAT64                 February 2014

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Issues  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .   3
       3.2.1.  AAAA Synthesis by the DNS Stub-resolver . . . . . . .   3
       3.2.2.  Application Referrals . . . . . . . . . . . . . . . .   4
   4.  PREFIX64 Option . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  Server's Behavior . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Client's Behavior . . . . . . . . . . . . . . . . . . . .   8
   5.  Flow Examples . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  TCP Session Initiated from an IPv6-only Host  . . . . . .   9
     5.2.  SIP Flow Example  . . . . . . . . . . . . . . . . . . . .  10
     5.3.  Mapping of IPv4 Address Ranges to IPv6 Prefixes . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   According to [RFC6146], NAT64 uses Pref64::/n to construct
   IPv4-Converted IPv6 addresses as defined in [RFC6052].

   This document defines a new PCP (Port Control Protocol) option
   [RFC6887] to inform PCP clients about the Pref64::/n and suffix
   [RFC6052] used by a PCP-controlled NAT64 device [RFC6146].  It does
   so by defining a new PREFIX64 option.

   This PCP option is a deterministic solution to help establish
   communications between IPv6-only hosts and remote IPv4-only hosts.
   Unlike [RFC7050], this option solves all the issues identified in
   [RFC7051].

   Some illustration examples are provided in Section 5.  Detailed
   experiments conducted to assess the applicability of the PREFIX64
   option for services, such as access to a video server behind NAT64
   and SIP-based sessions, are available at
   [I-D.boucadair-pcp-nat64-experiments].

   The use of this PCP option for NAT64 load balancing purposes is out
Show full document text