464XLAT/NAT64 Optimization
draft-ietf-v6ops-464xlat-optimization-00

Document Type Active Internet-Draft (v6ops WG)
Last updated 2020-01-14
Replaces draft-palet-v6ops-464xlat-opt-cdn-caches
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
v6ops                                                  J. Palet Martinez
Internet-Draft                                          The IPv6 Company
Intended status: Informational                               A. D'Egidio
Expires: July 17, 2020                                        Telecentro
                                                        January 14, 2020

                       464XLAT/NAT64 Optimization
                draft-ietf-v6ops-464xlat-optimization-00

Abstract

   This document proposes possible solutions to avoid certain drawbacks
   of IP/ICMP Translation Algorithm (SIIT) when the destinations are
   already available with IPv6.  When SIIT is used as a stateless NAT46
   and IPv4-only devices or applications initiate traffic flows to dual-
   stack services (in the operator network or Internet), those flows
   will be translated back to IPv4 by a NAT64.  Avoiding this dual-
   translation will significantly reduce the usage of the NAT64 and the
   relevant logging, which may be a high impact when traffic flows are
   towards CDNs, caches or similar resources.  This is the case for
   464XLAT and MAP-T.

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 July 17, 2020.

Copyright Notice

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

Palet Martinez & D'Egidio Expires July 17, 2020                 [Page 1]
Internet-Draft         464XLAT/NAT64 Optimization           January 2020

   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 . . . . . . . . . . . . . . . . . . . .   3
   3.  Possible Optimization . . . . . . . . . . . . . . . . . . . .   3
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Solution Approaches . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Approach 1: DNS/Routing-based Solution  . . . . . . . . .   7
     5.2.  Approach 2: NAT46/CLAT/DNS-proxy-EAM-based Solution . . .   8
       5.2.1.  Detection of IPv4-only devices or applications  . . .   8
       5.2.2.  Detection of IPv6-enabled service . . . . . . . . . .   8
       5.2.3.  Creation of EAMT entries  . . . . . . . . . . . . . .   9
       5.2.4.  Forwarding path via stateful NAT for existing EAMT
               entries . . . . . . . . . . . . . . . . . . . . . . .  10
       5.2.5.  Maintenance of the EAMT entries . . . . . . . . . . .  11
       5.2.6.  Usage example . . . . . . . . . . . . . . . . . . . .  11
       5.2.7.  Behavior in case of multiple A/AAAA RRs . . . . . . .  11
       5.2.8.  Behavior in presence/absence of DNS64 . . . . . . . .  11
       5.2.9.  Behavior when using literal addresses or non
               IPv6-compliant APIs . . . . . . . . . . . . . . . . .  12
       5.2.10. False detection of a dual-stack host as IPv4-only . .  12
       5.2.11. Behavior in presence of Happy Eyeballs  . . . . . . .  12
       5.2.12. Behavior in case of Foreign DNS . . . . . . . . . . .  13
     5.3.  Approach 3: NAT46/CLAT-provider-EAM-based Solution  . . .  14
   6.  IPv6-only Services become accessible to IPv4-only
       devices/apps  . . . . . . . . . . . . . . . . . . . . . . . .  15
   7.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18
Show full document text