Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
draft-ietf-behave-nat64-discovery-heuristic-16

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2013-03-12
Replaces draft-savolainen-heuristic-nat64-discovery
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs 5 more YES or NO OBJECTION positions to pass.
Responsible AD Martin Stiemerling
IESG note Document Shepherd: Dave Thaler (dthaler@microsoft.com)
Send notices to behave-chairs@tools.ietf.org, draft-ietf-behave-nat64-discovery-heuristic@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
Behave WG                                                  T. Savolainen
Internet-Draft                                                     Nokia
Intended status: Standards Track                             J. Korhonen
Expires: September 13, 2013                       Nokia Siemens Networks
                                                                 D. Wing
                                                           Cisco Systems
                                                          March 12, 2013

      Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis
           draft-ietf-behave-nat64-discovery-heuristic-16.txt

Abstract

   This document describes a method for detecting the presence of DNS64
   and for learning the IPv6 prefix used for protocol translation on an
   access network.  The method depends on the existence of a well-known
   IPv4-only fully qualified domain name "ipv4only.arpa".  The
   information learned enables nodes to perform local IPv6 address
   synthesis and to potentially avoid NAT64 on dual-stack and multi-
   interface deployments.

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 http://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 September 13, 2013.

Copyright Notice

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

Savolainen, et al.     Expires September 13, 2013               [Page 1]
Internet-Draft            Pref64::/n Discovery                March 2013

   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 and Terminology  . . . . . . . . . . . . . . . .   3
     2.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Node Behavior . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Validation of Discovered Pref64::/n . . . . . . . . . . .   6
       3.1.1.  DNSSEC Requirements for the Network . . . . . . . . .   6
       3.1.2.  DNSSEC Requirements for the Node  . . . . . . . . . .   7
     3.2.  Connectivity Check  . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  No Connectivity Checks Against ipv4only.arpa  . . . .   9
     3.3.  Alternative Fully Qualified Domain Names  . . . . . . . .   9
     3.4.  Message Flow Illustration . . . . . . . . . . . . . . . .  10
   4.  Operational Considerations for Hosting the IPv4-Only Well-
       Known Name  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Operational Considerations for DNS64 Operator . . . . . . . .  12
     5.1.  Mapping of IPv4 Address Ranges to IPv6 Prefixes . . . . .  12
   6.  Exit Strategy . . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Domain Name Reservation Considerations  . . . . . . . . .  14
     8.2.  IPv4 Address Allocation Considerations  . . . . . . . . .  15
     8.3.  IAB Statement Regarding This .arpa Request  . . . . . . .  16
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     10.2.  Informative References . . . . . . . . . . . . . . . . .  17
   Appendix A.  Example of DNS Record Configuration  . . . . . . . .  17
   Appendix B.  About the IPv4 Address for the Well-Known Name . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  19

1.  Introduction
Show full document text