DHCPv6 Options for Discovery NAT64 Prefixes
draft-li-intarea-nat64-prefix-dhcp-option-02

Document Type Active Internet-Draft (individual)
Last updated 2019-04-20
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
intarea Working Group                                              L. Li
Internet-Draft                                                    Y. Cui
Intended status: Standards Track                                  C. Liu
Expires: October 22, 2019                                          J. Wu
                                                     Tsinghua University
                                                                F. Baker

                                                       J. Palet Martinez
                                                        The IPv6 Company
                                                          April 20, 2019

              DHCPv6 Options for Discovery NAT64 Prefixes
              draft-li-intarea-nat64-prefix-dhcp-option-02

Abstract

   Several IPv6 transition mechanisms require the usage of stateless or
   stateful translators (commonly named as NAT64) able to allow IP/ICMP
   communication between IPv4 and IPv6 networks.

   Those translators are using either a default Well-Known Prefix (WKP),
   and/or one or several additional Network Specific Prefixes (NSP),
   which need to be configured into the nodes willing to use the
   translator.  Different translators will likely have different IPv6
   prefixes, to attract traffic to the correct translator.  Thus, an
   automatic translator prefix discovery method is necessary.

   This document defines a DHCPv6-based method to inform DHCPv6 clients
   the set of IPv6 and IPv4 prefixes it serves.  This DHCPv6 option can
   be used by several transition mechanisms such as SIIT, 464XLAT, EAM.

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 https://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 October 22, 2019.

Li, et al.              Expires October 22, 2019                [Page 1]
Internet-Draft      NAT64 Prefix Discovery by DHCPv6          April 2019

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  New DHCPv6 Option . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  NAT64 Prefix List Option Format . . . . . . . . . . . . .   4
     3.2.  NAT64 Prefix Option Format  . . . . . . . . . . . . . . .   5
   4.  Client Behavior . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Message Flow Illustration . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Stateless IP/ICMP Translation (SIIT) [RFC7915], describes the basic
   translation mechanism (NAT64), which is actually used as the base for
   many of the related translation protocols.

   Stateful NAT64 [RFC6146], describes a stateful IPv6 to IPv4
   translation mechanism, which allows IPv6-only hosts to communicate
   with IPv4-only servers using unicast UDP, TCP, or ICMP, by means of
   IPv4 public addresses sharing, among multiple IPv6-only hosts.
   Unless otherwise stated, references in the rest of this document to
   NAT64 (function) should be interpreted as to Stateful NAT64.

   The translation of the packet headers is done using the IP/ICMP
   translation algorithm defined in [RFC7915] and algorithmically
   translating the IPv4 addresses to IPv6 addresses and vice versa,
Show full document text