This repository has been archived by the owner on Nov 13, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
draft-iab-arpa-authoritative-servers.txt
336 lines (214 loc) · 12.4 KB
/
draft-iab-arpa-authoritative-servers.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
Network Working Group K. Davies
Internet-Draft IANA
Updates: 3172 (if approved) J. Arkko
Intended status: Informational Ericsson
Expires: January 13, 2022 July 12, 2021
Nameservers for the Address and Routing Parameter Area ("arpa") Domain
draft-iab-arpa-authoritative-servers-01
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 January 13, 2022.
Copyright Notice
Copyright (c) 2021 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 January 13, 2022 [Page 1]
Internet-Draft Nameservers for the .arpa Domain July 2021
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 . . . . . . . . . . . . . . 4
3.3. Zone administration . . . . . . . . . . . . . . . . . . . 4
3.4. Conclusion of process . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
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 networks.
Historically, the "arpa" zone has been hosted on almost all of the
root nameservers, and [RFC3172] envisages the "arpa" domain to be
"sufficiently critical that the operational requirements for the root
nameservers 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 nameserver and "arpa" nameserver 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
operations associated with managing the content of the root zone, or
administering the root nameservers.
The separation described in this document resolves operational
impacts of synchronizing edits to the root zone and the "arpa" zone
by eliminating the current dependency and allowing more tailored
operations based on the unique requirements of each zone.
Davies & Arkko Expires January 13, 2022 [Page 2]
Internet-Draft Nameservers for the .arpa Domain July 2021
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
requirements described in [RFC3172] for the domain. Future
operational requirements for the "arpa" domain are encouraged to
follow strong baseline requirements such as those documented in
[RFC7720].
Changes to the administration of the "arpa" zone do not alter the
management practices of other zones delegated within the "arpa"
namespace. For example, "ip6.arpa" would continue to be managed in
accordance with [RFC5855].
3. Transition Process
The process will dedicate new hostnames to the servers authoritative
for the "arpa" zone, but will initially serve the "arpa" zone from
the same hosts.
Once completed, subsequent transitional phases could include using
new hosts to replace or augment the existing root nameserver hosts,
and separation of the editing and distribution of the "arpa" zone
from necessarily being connected to the root zone. Any future
management considerations regarding how such changes may be performed
are beyond the scope of this document.
3.1. Dedicated nameserver hostnames
Consistent with the use of the "arpa" namespace itself to host name
servers for other delegations in the "arpa" zone ([RFC5855]), this
document specifies a new namespace of "ns.arpa", with the nameserver
set for the "arpa" zone to be initially labelled as follows:
a.ns.arpa
b.ns.arpa
c.ns.arpa
...
Dedicated hostnames eliminate a logical dependency that requires the
coordinated editing of the nameservers for the "arpa" zone and the
root zone. This component of this transition does not require the
underlying hosts that provide "arpa" name service (that is, the root
nameservers) be altered. The "arpa" zone will initially map the new
hostnames to the same IP addresses that already provide service under
the respective hostnames within root-servers.net.
Davies & Arkko Expires January 13, 2022 [Page 3]
Internet-Draft Nameservers for the .arpa Domain July 2021
Because these nameservers are completely within the "arpa" zone, they
will require glue records in the root zone. This is consistent with
current practice and requires no operational changes to the root
zone.
3.2. Separation of infrastructure
After initially migrating the "arpa" zone to use hostnames that are
not shared with the root zone, the underlying name service is
expected to evolve such that it no longer directly aligns to a subset
of root nameserver instances. With no shared infrastructure between
the root nameservers and the "arpa" nameservers, future novel
applications for the "arpa" zone may be possible.
Any subsequent changes to the parties providing name service for the
zone is considered a normal management responsibility, and would be
performed in accordance with [RFC3172].
3.3. Zone administration
Publication of the "arpa" zone file to the authoritative "arpa" name
servers is currently undertaken alongside the root zone maintenance
functions. Upon the separation of the "arpa" infrastructure from the
root nameserver infrastructure, publication of the "arpa" zone no
longer necessarily needs to be technically linked or inter-related to
the root zone publication mechanisms.
3.4. Conclusion of process
Full technical separation of operations of the "arpa" zone and root
zone minimally requires the following to be satisfied:
o The "arpa" zone no longer shares any hostnames in its NS-set with
the root zone;
o The hosts that provide authoritative name service are not the same
hosts as the root nameservers, do not share any IPv4 or IPv6
addresses with the root servers, and are sufficiently separately
provisioned such that any unique "arpa" zone requirements can be
deployed without affecting how root zone service is provided;
o The editorial and publication process for the "arpa" zone has any
common dependencies with the root zone process removed, so that
the "arpa" zone can be managed, edited and provisioned wholly
independently of the root zone.
Such separation is ultimately sought to allow for novel uses of the
"arpa" zone without the risk of inadvertantly impacting root zone and
Davies & Arkko Expires January 13, 2022 [Page 4]
Internet-Draft Nameservers for the .arpa Domain July 2021
root server operations. It is recognized that achieving this state
requires a deliberative process involving significant coordination to
ensure impacts are minimized.
4. IANA Considerations
The IANA shall coordinate the creation of the "ns.arpa" namespace and
populate it with address records that reflect the IP addresses of the
contemporary root servers documented within "root-servers.net" as its
initial state. The namespace may either be provisioned directly
within the "arpa" zone (as an empty non-terminal), or through
establishing a dedicated "ns.arpa" zone, according to operational
requirements.
The IANA will initially migrate the 12 NS records for the "arpa" zone
to point to their respective new entries in the "ns.arpa" domain.
Subsequently, the IAB and IANA will consult and coordinate with all
relevant parties on activity to reduce or eliminate reliance upon
root zone and root server infrastructure for serving the "arpa" zone.
Such changes will be performed in compliance with [RFC3172] and shall
be conducted with all due care and deliberation to mitigate potential
impacts on critical infrastructure.
5. Security Considerations
The security of the "arpa" zone is not necessarily impacted by any
aspects of these changes. Robust practices associated with
administering the content of the zone (including signing the zone
with DNSSEC) as well as its distribution will continue to be
necessary.
6. References
6.1. Normative References
[RFC3172] Huston, G., Ed., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172,
September 2001, <https://www.rfc-editor.org/info/rfc3172>.
6.2. Informative References
[RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6
Reverse Zones", BCP 155, RFC 5855, DOI 10.17487/RFC5855,
May 2010, <https://www.rfc-editor.org/info/rfc5855>.
Davies & Arkko Expires January 13, 2022 [Page 5]
Internet-Draft Nameservers for the .arpa Domain July 2021
[RFC7720] Blanchet, M. and L-J. Liman, "DNS Root Name Service
Protocol and Deployment Requirements", BCP 40, RFC 7720,
DOI 10.17487/RFC7720, December 2015,
<https://www.rfc-editor.org/info/rfc7720>.
Acknowledgments
Thank you Alyssa Cooper, Michelle Cotton, Lars-Johan Liman, Wes
Hardaker, Ted Hardie, Paul Hoffman, Russ Housley, Oscar Robles-Garay,
Duane Wessels and Suzanne Woolf for providing review and feedback.
Authors' Addresses
Kim Davies
Internet Assigned Numbers Authority
PTI/ICANN
12025 Waterfront Drive
Los Angeles 90094
United States of America
Email: kim.davies@iana.org
Jari Arkko
Ericsson Research
02700 Kauniainen
Finland
Email: jari.arkko@ericsson.com
Davies & Arkko Expires January 13, 2022 [Page 6]