Nameservers for the Address and Routing Parameter Area ("arpa") Domain
draft-iana-arpa-authoritative-servers-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Network Working Group                                          K. Davies
Internet-Draft                                                      IANA
Updates: RFC3172 (if approved)                                  J. Arkko
Intended status: Best Current Practice                          Ericsson
Expires: August 10, 2020                               February 07, 2020

 Nameservers for the Address and Routing Parameter Area ("arpa") Domain
                draft-iana-arpa-authoritative-servers-00

Abstract

   This document describes revisions to operational practices to
   separate function of the "arpa" top-level domain in the DNS from its
   historical operation alongside the DNS root zone.

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 August 10, 2020.

Copyright Notice

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

Davies & Arkko           Expires August 10, 2020                [Page 1]
Internet-Draft      Nameservers for the .arpa Domain       February 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements for the "arpa" zone  . . . . . . . . . . . . . .   3
   3.  Transition Process  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Dedicated nameserver hostnames  . . . . . . . . . . . . .   3
     3.2.  Separation of infrastructure  . . . . . . . . . . . . . .   3
     3.3.  Zone administration . . . . . . . . . . . . . . . . . . .   4
     3.4.  Conclusion of process . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Open Issues  . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The "arpa" top-level domain [RFC3172] is designated as an
   "infrastructure domain" to support techniques defined by Internet
   standards.  Zones under the "arpa" domain provide various mappings,
   such as IP addresses to domain names, and E.164 numbers to URIs.  It
   also contains special use names, such as "home", which is a non-
   unique name used in residential home networks.

   Historically, the "arpa" zone has been hosted on almost all of the
   root name servers, and [RFC3172] envisages the "arpa" domain to be
   "sufficiently critical that the operational requirements for the root
   servers apply to the operational requirements of the "arpa" servers".
   To date, this has been implemented by serving the "arpa" domain
   directly on a subset of the root server infrastructure.

   This bundling of root server and "arpa" server operations has
   entwined management of the zones contents and their infrastructure.
   As a result, some proposals under consideration by the IETF involving
   the "arpa" zone have been discarded due to the risk of conflict with
   root operations.

   The separation described in this document resolves operational
   impacts of synchronizing edits to the root zone and the "arpa" zone,
   eliminating the current dependency and allowing more tailored
   operations based on the unique requirements of each zone.

Davies & Arkko           Expires August 10, 2020                [Page 2]
Internet-Draft      Nameservers for the .arpa Domain       February 2020

2.  Requirements for the "arpa" zone

   The "arpa" domain continues to play a role in critical Internet
   operations, and this change does not propose weakening operational