Browse Prior Art Database

Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP) (RFC7225)

IP.com Disclosure Number: IPCOM000236824D
Publication Date: 2014-May-17
Document File: 34 page(s) / 40K

Publishing Venue

The IP.com Prior Art Database

Related People

M. Boucadair: AUTHOR

Abstract

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

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                      M. Boucadair Request for Comments: 7225                                France Telecom Category: Standards Track                                       May 2014 ISSN: 2070-1721

  Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)

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

   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/rfc7225.

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                    Standards Track                    [Page 1]
 RFC 7225                       PCP & NAT64                      May 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 . . . . . . .   4

       3.2.2.  Application Referrals . . . . . . . . . . . . . . . .   4

   4.  PREFIX64 Option . . . . . . . . . . . . . . . . . . . . . . .   5

     4.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .  ...