One document matched: draft-cheshire-sudn-ipv4only-dot-arpa-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<!-- Check output with <http://tools.ietf.org/tools/idnits/> -->

<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.35) -->

<!-- give errors regarding ID-nits and DTD validation -->
<?rfc strict="yes" ?>

<!-- control the table of contents (ToC) -->
<!-- generate a ToC -->
<?rfc toc="no"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<?rfc tocdepth="1"?>

<!-- control references -->
<!-- use anchors instead of numbers for refs, i.e, [RFC2119] instead of [1] -->
<?rfc symrefs="yes"?>
<!-- sort the reference entries alphabetically -->
<?rfc sortrefs="no" ?>

<!-- control vertical white space
     (using these PIs as follows is recommended by the RFC Editor) -->
<!-- do not start each main section on a new page -->
<?rfc compact="yes" ?>
<!-- keep one blank line between list items -->
<?rfc subcompact="no" ?>

<!-- encourage use of "xml2rfc" tool -->
<?rfc rfcprocack="yes" ?>
<!-- end of list of popular I-D processing instructions -->

<rfc category="std" docName="draft-cheshire-sudn-ipv4only-dot-arpa-00" ipr="trust200902" updates="7050">
  <front>
    <title abbrev="Dot Home">Special Use Domain Name 'ipv4only.arpa'</title>

    <author initials='S.' surname='Cheshire' fullname='Stuart Cheshire'>
      <organization>Apple Inc.</organization>
      <address>
        <postal>
          <street>1 Infinite Loop</street>
          <city>Cupertino</city>
          <region>California</region>
          <code>95014</code>
          <country>USA</country>
        </postal>
        <phone>+1 408 974 3207</phone>
        <email>cheshire@apple.com</email>
      </address>
    </author>

    <author initials='D.' surname='Schinazi' fullname='David Schinazi'>
      <organization>Apple Inc.</organization>
      <address>
        <postal>
          <street>1 Infinite Loop</street>
          <city>Cupertino</city>
          <region>California</region>
          <code>95014</code>
          <country>USA</country>
        </postal>
        <phone>+1 669 227 9921</phone>
        <email>dschinazi@apple.com</email>
      </address>
    </author>

    <date day='28' month='January' year='2016'/>

    <abstract>
      <t>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 neglected to include a
      Domain Name Reservation Considerations section [RFC6761]
      formalizing those special properties.
      This document updates RFC 7050 and formally specifies the
      Special Use Domain Name rules for ipv4only.arpa.</t>
    </abstract>
  </front>

  <middle>
    <?rfc needLines="10" ?>
    <section title="Introduction">
      <t>The document
      <xref target="RFC7050">"Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis"</xref>
      specifies the Special Use Domain Name 'ipv4only.arpa',
      with certain precise special properties, but neglected to include a
      <xref target="RFC6761">Domain Name Reservation Considerations section</xref>
      formally stating those special properties.</t>

      <t>As a result of the name 'ipv4only.arpa' not being formally declared to
      have special properties, there was no mandate for software to treat this
      name specially. Queries for this name are handled normally, and result in
      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. Also, having
      millions of devices around the world depend on these answers 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.</t>

      <t>To remedy this situation, this document updates RFC 7050 and specifies the
      formal Special Use Domain Name rules for ipv4only.arpa.</t>
    </section>

    <section anchor="terminology" title="Conventions and Terminology Used in this Document">
      <t>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" <xref target="RFC2119"/>.</t>
    </section>

    <?rfc needLines="7" ?>
    <section title="Security Considerations">
      <t>Hard-coding the answers for ipv4only.arpa queries avoids the risk of
      malicious devices intercepting those queries and returning incorrect answers.</t>
    </section>

    <section title="IANA Considerations">
      <t>[Once published, this should say]
      IANA has recorded the name 'ipv4only.arpa' in the
      <xref target="SUDN">Special-Use Domain Names registry</xref>.</t>

      <section title="Domain Name Reservation Considerations">
        <t>The name 'ipv4only.arpa' is special <xref target="RFC6761"/> in the following ways:

          <list style="numbers">
            <t>Users should never have reason to encounter the ipv4only.arpa
            domain nanme. If they do, queries for ipv4only.arpa should
            result in the answers specified in RFC 7050.
            Users have no need to know that ipv4only.arpa is special.</t>

            <t>Application software may explicitly use the name ipv4only.arpa for NAT64
            address synthesis, and expect to get the answers specified in RFC 7050.
            If application software encounters the name ipv4only.arpa as user input,
            the application software should resolve that name as usual and need not
            treat it in any special way.</t>

            <t>Name resolution APIs and libraries SHOULD NOT recognize
            ipv4only.arpa as special and SHOULD NOT treat it differently.
            Name resolution APIs SHOULD send queries for this name to
            their configured recursive/caching DNS server(s).</t>

            <t>Recursive/caching DNS servers SHOULD recognize ipv4only.arpa as special
            and SHOULD NOT, by default, attempt to look up NS records for it, or
            otherwise query authoritative DNS servers in an attempt to resolve this name.
            Instead, recursive/caching DNS servers SHOULD, by default, act as
            authoritative and generate immediate responses for all such queries.
            Traditional recursive/caching DNS servers that act as authoritative for this
            name MUST generate only the 192.0.0.170 and 192.0.0.171 responses for these
            queries, and no others.
            DNS64 recursive/caching DNS servers MUST generate the
            192.0.0.170 and 192.0.0.171 address record responses for these queries,
            and MUST generate the appropriate synthesized IPv6 address record responses for all AAAA queries.
            This is to avoid unnecessary load on the 'arpa' name servers.</t>

            <t>Traditional authoritative DNS servers SHOULD recognize ipv4only.arpa
            as special and SHOULD, by default, generate immediate
            negative responses for all such queries, unless explicitly
            configured otherwise by the administrator
            (which only applies to the administrators of the 'arpa' namespace).</t>

            <t>DNS server operators MUST understand that ipv4only.arpa is
            a special name, with answers specified by Internet Standard.</t>

            <t>DNS Registries/Registrars MUST understand that ipv4only.arpa is
            a special name, with answers specified by Internet Standard.</t>
          </list>
        </t>
      </section>
    </section>

  </middle>

  <back>
    <?rfc needLines="8" ?>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119" ?>
      <?rfc include="reference.RFC.6761" ?>
      <?rfc include="reference.RFC.7050" ?>
    </references>

    <references title="Informative References">

      <reference anchor="SUDN"
      target="http://www.iana.org/assignments/special-use-domain-names/">
        <front>
          <title>Special-Use Domain Names Registry</title>
          <author/>
          <date/>
        </front>
      </reference>

    </references>
  </back>
</rfc>