464XLAT Optimization
draft-palet-v6ops-464xlat-opt-cdn-caches-03

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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)
v6ops                                                  J. Palet Martinez
Internet-Draft                                          The IPv6 Company
Intended status: Informational                               A. D'Egidio
Expires: January 9, 2020                                      Telecentro
                                                            July 8, 2019

                          464XLAT Optimization
              draft-palet-v6ops-464xlat-opt-cdn-caches-03

Abstract

   This document proposes possible solutions to avoid certain drawbacks
   of IP/ICMP Translation Algorithm (SIIT) when the destinations are
   available with IPv6.  When SIIT is used as a NAT46 and IPv4-only
   devices or applications initiate traffic flows to dual-stack CDNs
   (Content Delivery Networks), Caches or other network resources (in
   the operator network or Internet), those flows will be translated
   back to IPv4 by a NAT64.  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 January 9, 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 & D'EgidioExpires January 9, 2020                [Page 1]
Internet-Draft         464XLAT/NAT46 Optimization              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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   4
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Solution Approaches . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Approach 1: DNS/Routing-based Solution  . . . . . . . . .   6
     4.2.  Approach 2: NAT46/CLAT/DNS-proxy-EAM-based Solution . . .   7
       4.2.1.  Detection of IPv4-only devices or applications  . . .   7
       4.2.2.  Detection of IPv6-enabled service . . . . . . . . . .   8
       4.2.3.  Creation of EAMT entries  . . . . . . . . . . . . . .   8
       4.2.4.  Forwarding path for existing EAMT entries . . . . . .  10
       4.2.5.  Maintenance of the EAMT entries . . . . . . . . . . .  10
       4.2.6.  Usage example . . . . . . . . . . . . . . . . . . . .  10
       4.2.7.  Behavior in case of multiple A/AAAA RRs . . . . . . .  10
       4.2.8.  Behavior in presence/absence of DNS64 . . . . . . . .  11
       4.2.9.  Behavior when using literal addreses or non
               IPv6-compliant APIs . . . . . . . . . . . . . . . . .  11
       4.2.10. False detection of a dual-stack host as IPv4-only . .  11
       4.2.11. Behaviour in presence of Happy Eyeballs . . . . . . .  11
       4.2.12. Behavior in case of Foreign DNS . . . . . . . . . . .  12
     4.3.  Approach 3: NAT46/CLAT-provider-EAM-based Solution  . . .  13
   5.  IPv6-only Services become accessible to IPv4-only
       devices/apps  . . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Different transition mechanisms, typically in the group of the so-
   called IPv6-only with IPv4aaS (IPv4-as-a-Service), such as 464XLAT
   ([RFC6877]) or MAP-T ([RFC7599]), allow IPv4-only devices or
   applications to connect with IPv4 services in Internet, by means of a
Show full document text