idnits 2.17.1 draft-iana-arpa-authoritative-servers-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 04, 2021) is 1206 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Davies 3 Internet-Draft IANA 4 Updates: RFC3172 (if approved) J. Arkko 5 Intended status: Best Current Practice Ericsson 6 Expires: July 8, 2021 January 04, 2021 8 Nameservers for the Address and Routing Parameter Area ("arpa") Domain 9 draft-iana-arpa-authoritative-servers-02 11 Abstract 13 This document describes revisions to operational practices to 14 separate function of the "arpa" top-level domain in the DNS from its 15 historical operation alongside the DNS root zone. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on July 8, 2021. 34 Copyright Notice 36 Copyright (c) 2021 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Requirements for the "arpa" zone . . . . . . . . . . . . . . 3 53 3. Transition Process . . . . . . . . . . . . . . . . . . . . . 3 54 3.1. Dedicated nameserver hostnames . . . . . . . . . . . . . 3 55 3.2. Separation of infrastructure . . . . . . . . . . . . . . 4 56 3.3. Zone administration . . . . . . . . . . . . . . . . . . . 4 57 3.4. Conclusion of process . . . . . . . . . . . . . . . . . . 4 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 62 6.2. Informative References . . . . . . . . . . . . . . . . . 5 63 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 The "arpa" top-level domain [RFC3172] is designated as an 69 "infrastructure domain" to support techniques defined by Internet 70 standards. Zones under the "arpa" domain provide various mappings, 71 such as IP addresses to domain names and E.164 numbers to URIs. It 72 also contains special use names such as "home", which is a non-unique 73 name used in residential networks. 75 Historically, the "arpa" zone has been hosted on almost all of the 76 root name servers, and [RFC3172] envisages the "arpa" domain to be 77 "sufficiently critical that the operational requirements for the root 78 servers apply to the operational requirements of the "arpa" servers". 79 To date, this has been implemented by serving the "arpa" domain 80 directly on a subset of the root server infrastructure. 82 This bundling of root server and "arpa" server operations has 83 entwined management of the zones contents and their infrastructure. 84 As a result, some proposals under consideration by the IETF involving 85 the "arpa" zone have been discarded due to the risk of conflict with 86 root operations. 88 The separation described in this document resolves operational 89 impacts of synchronizing edits to the root zone and the "arpa" zone 90 by eliminating the current dependency and allowing more tailored 91 operations based on the unique requirements of each zone. 93 2. Requirements for the "arpa" zone 95 The "arpa" domain continues to play a role in critical Internet 96 operations, and this change does not propose weakening operational 97 requirements described in [RFC3172] for the domain. Future 98 operational requirements for the "arpa" domain are encouraged to 99 follow strong baseline requirements such as those documented in 100 [RFC7720]. 102 Changes to the administration of the "arpa" zone do not alter the 103 management practices of other zones delegated within the "arpa" 104 namespace. For example, "ip6.arpa" would continue to be managed in 105 accordance with [RFC5855]. 107 3. Transition Process 109 The process will dedicate new hostnames to the servers authoritative 110 for the "arpa" zone, but will initially serve the "arpa" zone from 111 the same hosts. 113 Once completed, subsequent transitional phases could include using 114 new hosts to replace or augment the existing root server hosts, and 115 separation of the editing and distribution of the "arpa" zone from 116 necessarily being connected to the root zone. Any future management 117 considerations regarding how such changes may be performed are beyond 118 the scope of this document. 120 3.1. Dedicated nameserver hostnames 122 Consistent with the use of the "arpa" namespace itself to host name 123 servers for other delegations in the "arpa" zone ([RFC5855]), this 124 document specifies a new namespace of "ns.arpa", with the nameserver 125 set for the "arpa" zone to be labelled as follows: 127 a.ns.arpa 128 b.ns.arpa 129 c.ns.arpa 130 ... 132 Dedicated hostnames eliminate a logical dependency that requires the 133 coordinated editing of the nameservers for the "arpa" zone and the 134 root zone. This component of this transition does not require the 135 underlying hosts that provide "arpa" name service (that is, the root 136 servers) be altered. The "arpa" zone will initially map the new 137 hostnames to the same IP addresses that already provide service under 138 the respective hostnames within root-servers.net. 140 Because these nameservers are completely in-bailiwick of the "arpa" 141 zone, they will require glue records in the root zone. This is 142 consistent with current practice and requires no operational changes 143 to the root zone. 145 3.2. Separation of infrastructure 147 After initially migrating the "arpa" zone to use hostnames that are 148 not shared with the root zone, the underlying name service is 149 expected to evolve such that it no longer directly aligns to a subset 150 of root server instances. With no shared infrastructure between the 151 root servers and the "arpa" servers, future novel applications for 152 the "arpa" zone may be possible. 154 Any subsequent changes to the parties providing name service for the 155 zone is considered a normal management responsibility, and would be 156 performed in accordance with [RFC3172]. 158 3.3. Zone administration 160 Publication of the "arpa" zone file to the authoritative "arpa" name 161 servers is currently undertaken alongside the root zone maintenance 162 functions. Upon the separation of the "arpa" infrastructure from the 163 root server infrastructure, publication of the "arpa" zone no longer 164 necessarily needs to be technically linked or inter-related to the 165 root zone publication mechanisms. 167 3.4. Conclusion of process 169 Full technical separation of "arpa" operations from root operations 170 minimally requires the following to be satisfied: 172 o The "arpa" zone no longer shares any hostnames in its NS-set with 173 the root zone; 175 o The hosts that provide authoritative name service are not the same 176 hosts as the root servers, do not share any IPv4 or IPv6 addresses 177 with the root servers, and are sufficiently separately provisioned 178 such that any unique "arpa" zone requirements can be deployed 179 without affecting how root zone service is provided; 181 o The editorial and publication process for the "arpa" zone has any 182 common dependencies with the root zone process removed, so that 183 the "arpa" zone can be managed, edited and provisioned wholly 184 independently of the root zone. 186 Such separation is ultimately sought to allow for novel uses of the 187 "arpa" zone without the risk of inadvertantly impacting root zone and 188 root server operations. It is recognized that achieving this state 189 requires a deliberative process involving significant coordination to 190 ensure impacts are minimized. 192 4. IANA Considerations 194 The IANA shall coordinate the creation of the "ns.arpa" namespace and 195 populate it with address records that reflect the IP addresses of the 196 contemporary root servers documented within "root-servers.net" as its 197 initial state. 199 The IANA will initially migrate the 12 NS records for the "arpa" zone 200 to point to their respective new entries in the "ns.arpa" domain. 202 Subsequently, the IAB and IANA will consult and coordinate with all 203 relevant parties on activity to reduce or eliminate reliance upon 204 root zone and root server infrastructure for serving the "arpa" zone. 205 Such changes will be performed in compliance with [RFC3172] and shall 206 be conducted with all due care and deliberation to mitigate potential 207 impacts on critical infrastructure. 209 5. Security Considerations 211 The security of the "arpa" zone is not necessarily impacted by any 212 aspects of these changes. Robust practices associated with 213 administering the content of the zone (including signing operations) 214 as well as its distribution will continue to be necessary. 216 6. References 218 6.1. Normative References 220 [RFC3172] Huston, G., Ed., "Management Guidelines & Operational 221 Requirements for the Address and Routing Parameter Area 222 Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172, 223 September 2001, . 225 6.2. Informative References 227 [RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6 228 Reverse Zones", BCP 155, RFC 5855, DOI 10.17487/RFC5855, 229 May 2010, . 231 [RFC7720] Blanchet, M. and L-J. Liman, "DNS Root Name Service 232 Protocol and Deployment Requirements", BCP 40, RFC 7720, 233 DOI 10.17487/RFC7720, December 2015, 234 . 236 Acknowledgments 238 Thank you Alyssa Cooper, Michelle Cotton, Lars-John Liman, Wes 239 Hardaker, Ted Hardie, Paul Hoffman, Russ Housley, Oscar Robles-Garay, 240 Duane Wessels and Suzanne Woolf for providing review and feedback. 242 Authors' Addresses 244 Kim Davies 245 Internet Assigned Numbers Authority 246 PTI/ICANN 247 12025 Waterfront Drive 248 Los Angeles 90094 249 United States of America 251 Email: kim.davies@iana.org 253 Jari Arkko 254 Ericsson Research 255 02700 Kauniainen 256 Finland 258 Email: jari.arkko@ericsson.com