Additional NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks
draft-ietf-v6ops-nat64-deployment-08

Document Type Active Internet-Draft (v6ops WG)
Last updated 2019-07-23 (latest revision 2019-07-12)
Replaces draft-palet-v6ops-nat64-deployment
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Mikael Abrahamsson
Shepherd write-up Show (last changed 2019-06-07)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to Mikael Abrahamsson <swmike@swm.pp.se>
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
RFC Editor RFC Editor state EDIT
v6ops                                                  J. Palet Martinez
Internet-Draft                                          The IPv6 Company
Intended status: Informational                             July 11, 2019
Expires: January 12, 2020

     Additional NAT64/464XLAT Deployment Guidelines in Operator and
                          Enterprise Networks
                  draft-ietf-v6ops-nat64-deployment-08

Abstract

   This document describes how NAT64 (including 464XLAT) can be deployed
   in an IPv6 network, whether cellular ISP, broadband ISP, or
   enterprise, and possible optimizations.  The document also discusses
   issues to be considered when having IPv6-only connectivity,
   regarding: a) DNS64, b) applications or devices that use literal IPv4
   addresses or non-IPv6 compliant APIs, and c) IPv4-only hosts or
   applications.

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 January 12, 2020.

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

Palet Martinez          Expires January 12, 2020                [Page 1]
Internet-Draft          NAT64/464XLAT Deployment               July 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   5
   3.  NAT64 Deployment Scenarios  . . . . . . . . . . . . . . . . .   5
     3.1.  Known to Work . . . . . . . . . . . . . . . . . . . . . .   6
       3.1.1.  Service Provider NAT64 with DNS64 . . . . . . . . . .   6
       3.1.2.  Service Provider Offering 464XLAT, with DNS64 . . . .   8
       3.1.3.  Service Provider Offering 464XLAT, without DNS64  . .  12
     3.2.  Known to Work Under Special Conditions  . . . . . . . . .  14
       3.2.1.  Service Provider NAT64 without DNS64  . . . . . . . .  14
       3.2.2.  Service Provider NAT64; DNS64 in the IPv6 hosts . . .  16
       3.2.3.  Service Provider NAT64; DNS64 in the IPv4-only
               remote network  . . . . . . . . . . . . . . . . . . .  16
     3.3.  Comparing the Scenarios . . . . . . . . . . . . . . . . .  17
   4.  Issues to be Considered . . . . . . . . . . . . . . . . . . .  19
     4.1.  DNSSEC Considerations and Possible Approaches . . . . . .  19
       4.1.1.  Not using DNS64 . . . . . . . . . . . . . . . . . . .  20
       4.1.2.  DNSSEC validator aware of DNS64 . . . . . . . . . . .  21
       4.1.3.  Stub validator  . . . . . . . . . . . . . . . . . . .  22
       4.1.4.  CLAT with DNS proxy and validator . . . . . . . . . .  22
       4.1.5.  ACL of clients  . . . . . . . . . . . . . . . . . . .  22
       4.1.6.  Mapping-out IPv4 addresses  . . . . . . . . . . . . .  23
     4.2.  DNS64 and Reverse Mapping . . . . . . . . . . . . . . . .  23
     4.3.  Using 464XLAT with/without DNS64  . . . . . . . . . . . .  23
     4.4.  Foreign DNS . . . . . . . . . . . . . . . . . . . . . . .  24
       4.4.1.  Manual Configuration of DNS . . . . . . . . . . . . .  25
       4.4.2.  DNS Privacy/Encryption Mechanisms . . . . . . . . . .  25
       4.4.3.  Split DNS and VPNs  . . . . . . . . . . . . . . . . .  26
     4.5.  Well-Known Prefix (WKP) vs Network-Specific Prefix (NSP)   26
     4.6.  IPv4 literals and non-IPv6 Compliant APIs . . . . . . . .  26
     4.7.  IPv4-only Hosts or Applications . . . . . . . . . . . . .  27
     4.8.  CLAT Translation Considerations . . . . . . . . . . . . .  27
     4.9.  EAM Considerations  . . . . . . . . . . . . . . . . . . .  28
     4.10. Incoming Connections  . . . . . . . . . . . . . . . . . .  28
   5.  Summary of Deployment Recommendations for NAT64/464XLAT . . .  28
   6.  Deployment of 464XLAT/NAT64 in Enterprise Networks  . . . . .  31
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  33
Show full document text