Discovery of a Network-Specific NAT64 Prefix using a Well-Known Name
draft-ietf-behave-nat64-discovery-heuristic-05

The information below is for an old version of the document
Document Type Active Internet-Draft (behave WG)
Last updated 2012-01-25 (latest revision 2011-12-20)
Replaces draft-savolainen-heuristic-nat64-discovery
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Behave WG                                                  T. Savolainen
Internet-Draft                                                     Nokia
Intended status: Standards Track                             J. Korhonen
Expires: July 28, 2012                            Nokia Siemens Networks
                                                                 D. Wing
                                                           Cisco Systems
                                                        January 25, 2012

  Discovery of a Network-Specific NAT64 Prefix using a Well-Known Name
           draft-ietf-behave-nat64-discovery-heuristic-05.txt

Abstract

   This document describes a method for detecting presence of DNS64 and
   for learning IPv6 prefix used for protocol translation on an access
   network without explicit support from the access network.  The method
   depends on existence of a well-known IPv4-only domain name
   "ipv4only.arpa".  The information learned enables applications and
   hosts to perform local IPv6 address synthesis and on dual-stack
   accesses avoid traversal through NAT64.

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 July 28, 2012.

Copyright Notice

   Copyright (c) 2012 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 July 28, 2012                 [Page 1]
Internet-Draft           NSP Discovery using WKN            January 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements and Terminology . . . . . . . . . . . . . . . . .  3
     2.1.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Host behavior  . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Learning NAT64 prefix securely by using DNSSEC . . . . . .  5
       3.1.1.  Requirements for the network . . . . . . . . . . . . .  6
       3.1.2.  Host behavior  . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Connectivity check . . . . . . . . . . . . . . . . . . . .  7
       3.2.1.  No connectivity checks against ipv4only.arpa . . . . .  8
     3.3.  Alternative domain names . . . . . . . . . . . . . . . . .  8
   4.  Operational considerations for hosting the IPv4-only
       well-known name  . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  DNS(64) entity considerations  . . . . . . . . . . . . . . . .  9
   6.  Exit strategy  . . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
     8.1.  About the IPv4 address for the well-known name . . . . . . 10
   9.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   10. Normative References . . . . . . . . . . . . . . . . . . . . . 11
   Appendix A.  Example of DNS record configuration . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Savolainen, et al.        Expires July 28, 2012                 [Page 2]
Internet-Draft           NSP Discovery using WKN            January 2012

1.  Introduction

   As part of the transition to IPv6 NAT64 [RFC6146] and DNS64 [RFC6147]
   technologies will be utilized by some access networks to provide IPv4
   connectivity for IPv6-only hosts.  The DNS64 utilizes IPv6 address
   synthesis to create local IPv6 presentations of peers having only
   IPv4 addresses, hence allowing DNS-using IPv6-only hosts to
   communicate with IPv4-only peers.

   However, DNS64 cannot serve applications not using DNS, such as those
   receiving IPv4 address literals as referrals.  Such applications
Show full document text