Special Use Domain Name 'ipv4only.arpa'
draft-cheshire-sudn-ipv4only-dot-arpa-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Stuart Cheshire  , David Schinazi 
Last updated 2016-05-19
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
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)
Network Working Group                                        S. Cheshire
Internet-Draft                                               D. Schinazi
Updates: 7050 (if approved)                                   Apple Inc.
Intended status: Standards Track                            May 19, 2016
Expires: November 20, 2016

                Special Use Domain Name 'ipv4only.arpa'
                draft-cheshire-sudn-ipv4only-dot-arpa-01

Abstract

   The document "Discovery of the IPv6 Prefix Used for IPv6 Address
   Synthesis" [RFC7050] specifies the Special Use Domain Name
   'ipv4only.arpa', with certain precise special properties, but,
   perversely, the Domain Name Reservation Considerations section
   [RFC6761] in that document then goes on to deny the specialness of
   that name, and (as of May 2016) the name 'ipv4only.arpa' does not
   appear in the Special-Use Domain Names registry.

   This document updates RFC 7050 with a more appropriate summary of the
   legitimate and useful special properties of the name ipv4only.arpa.

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 November 20, 2016.

Copyright Notice

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

Cheshire & Schinazi     Expires November 20, 2016               [Page 1]
Internet-Draft                  Dot Home                        May 2016

   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.

1.  Introduction

   The document "Discovery of the IPv6 Prefix Used for IPv6 Address
   Synthesis" [RFC7050] specifies the Special Use Domain Name
   'ipv4only.arpa', with certain precise special properties, but,
   perversely, the Domain Name Reservation Considerations section
   [RFC6761] in that document denies the specialness of that name, and
   (as of May 2016) the name 'ipv4only.arpa' does not appear in the
   Special-Use Domain Names registry [SUDN].

   As a result of the name 'ipv4only.arpa' being formally declared to
   have no special properties, there was no mandate for software to
   treat this name specially.  Consequently, queries for this name have
   to be handled normally, and result in a large volume of unnecessary
   queries to the 'arpa' name servers.

   At times, for reasons that are as yet unclear, the 'arpa' name
   servers have been observed to be slow or unresponsive.  The failures
   of these 'ipv4only.arpa' queries result in failures of software that
   depends on them for NAT64 address synthesis.

   Having millions of devices around the world issue these queries
   generates pointless additional load on the 'arpa' name servers, which
   is completely unnecessary when this name is defined, by Internet
   Standard, to have only two address records, 192.0.0.170 and
   192.0.0.171, and no other records.

   To remedy this situation, this document updates RFC 7050 with a more
   appropriate Domain Name Reservation Considerations section [RFC6761]
   that properly lists the desirable and beneficial special handling for
   ipv4only.arpa.

2.  Conventions and Terminology Used in this Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   "Key words for use in RFCs to Indicate Requirement Levels" [RFC2119].

Cheshire & Schinazi     Expires November 20, 2016               [Page 2]
Internet-Draft                  Dot Home                        May 2016

3.  Security Considerations

   Hard-coding the answers for ipv4only.arpa queries avoids the risk of
   malicious devices intercepting those queries and returning incorrect
   answers.

   DNSSEC signing issues for the ipv4only.arpa address records don't
   apply, since the only use of the ipv4only.arpa name is to trigger
Show full document text