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
|
<pre>Internet Engineering Task Force (IETF) M. Blanchet
Request for Comments: 7720 Viagenie
BCP: 40 L-J. Liman
Obsoletes: <a href="./rfc2870">2870</a> Netnod
Category: Best Current Practice December 2015
ISSN: 2070-1721
<span class="h1">DNS Root Name Service Protocol and Deployment Requirements</span>
Abstract
The DNS root name service is a critical part of the Internet
architecture. The protocol and deployment requirements for the DNS
root name service are defined in this document. Operational
requirements are out of scope.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
BCPs is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7720">http://www.rfc-editor.org/info/rfc7720</a>.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Blanchet & Liman Best Current Practice [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7720">RFC 7720</a> Root Name Service Requirements December 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Relationship to <a href="./rfc2870">RFC 2870</a> . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Protocol Requirements . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Deployment Requirements . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. Informative References . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC2870">RFC2870</a>] discusses protocol and operational requirements for root
name servers for the Internet's domain name system (DNS) protocol
[<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>]. Since its publication, both protocol and operational
requirements have evolved. It makes more sense now to separate the
two sets of requirements into two separate documents. This document
only defines the protocol requirements and some deployment
requirements. The operational requirements that were defined in <a href="./rfc2870">RFC</a>
<a href="./rfc2870">2870</a> have been removed. Operational requirements are now defined by
the Root Server System Advisory Committee of ICANN and are documented
in [<a href="#ref-RSSAC-001" title=""Service Expectations of Root Servers"">RSSAC-001</a>].
The root servers are authoritative servers of the unique [<a href="./rfc2826" title=""IAB Technical Comment on the Unique DNS Root"">RFC2826</a>]
root zone (".") [<a href="#ref-ROOTZONE" title=""Root Zone"">ROOTZONE</a>]. They currently also serve the root-
servers.net zone. Some also serve the zone for the .arpa top-level
domain [<a href="#ref-ARPAZONE" title="".ARPA Zone Management"">ARPAZONE</a>] [<a href="./rfc3172" title=""Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("">RFC3172</a>]. This document describes the external
interface of the root name servers from a protocol viewpoint of the
service. It specifies basic requirements for the Internet that DNS
clients meet when interacting with a root name service over the
public Internet.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Relationship to <a href="./rfc2870">RFC 2870</a></span>
This document obsoletes [<a href="./rfc2870" title=""Root Name Server Operational Requirements"">RFC2870</a>].
This document and [<a href="#ref-RSSAC-001" title=""Service Expectations of Root Servers"">RSSAC-001</a>] together functionally replace
[<a href="./rfc2870" title=""Root Name Server Operational Requirements"">RFC2870</a>].
<span class="grey">Blanchet & Liman Best Current Practice [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7720">RFC 7720</a> Root Name Service Requirements December 2015</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Protocol Requirements</span>
This section describes the minimum high-level protocol requirements.
Operative details are documented in [<a href="#ref-RSSAC-001" title=""Service Expectations of Root Servers"">RSSAC-001</a>].
The root name service:
o MUST implement core DNS [<a href="./rfc1035" title=""Domain names - implementation and specification"">RFC1035</a>] and clarifications to the DNS
[<a href="./rfc2181" title=""Clarifications to the DNS Specification"">RFC2181</a>].
o MUST support IPv4 [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>] and IPv6 [<a href="./rfc2460" title=""Internet Protocol, Version 6 (IPv6) Specification"">RFC2460</a>] transport of DNS
queries and responses.
o MUST support UDP [<a href="./rfc768" title=""User Datagram Protocol"">RFC768</a>] and TCP [<a href="./rfc793" title=""Transmission Control Protocol"">RFC793</a>] transport of DNS
queries and responses.
o MUST generate checksums when sending UDP datagrams and MUST verify
checksums when receiving UDP datagrams containing a non-zero
checksum.
o MUST implement DNSSEC [<a href="./rfc4035" title=""Protocol Modifications for the DNS Security Extensions"">RFC4035</a>] as an authoritative name service.
o MUST implement extension mechanisms for DNS (EDNS(0)) [<a href="./rfc6891" title=""Extension Mechanisms for DNS (EDNS(0))"">RFC6891</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Deployment Requirements</span>
The root name service:
o MUST answer queries from any entity conforming to [<a href="./rfc1122" title=""Requirements for Internet Hosts - Communication Layers"">RFC1122</a>] with a
valid IP address.
o MUST serve the unique [<a href="./rfc2826" title=""IAB Technical Comment on the Unique DNS Root"">RFC2826</a>] root zone [<a href="#ref-ROOTZONE" title=""Root Zone"">ROOTZONE</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document does not specify a new protocol. However, the root
name service is a key component of the Internet architecture and play
a key role into the overall security of the Internet [<a href="./rfc2826" title=""IAB Technical Comment on the Unique DNS Root"">RFC2826</a>].
Specific security considerations on the DNS protocols are discussed
in their respective specifications. The security considerations on
the operational side of the root name servers are discussed in
[<a href="#ref-RSSAC-001" title=""Service Expectations of Root Servers"">RSSAC-001</a>].
<span class="grey">Blanchet & Liman Best Current Practice [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7720">RFC 7720</a> Root Name Service Requirements December 2015</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Informative References</span>
[<a id="ref-ARPAZONE">ARPAZONE</a>] IANA, ".ARPA Zone Management",
<<a href="http://www.iana.org/domains/arpa">http://www.iana.org/domains/arpa</a>>.
[<a id="ref-RFC768">RFC768</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>,
DOI 10.17487/RFC0768, August 1980,
<<a href="http://www.rfc-editor.org/info/rfc768">http://www.rfc-editor.org/info/rfc768</a>>.
[<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>,
DOI 10.17487/RFC0791, September 1981,
<<a href="http://www.rfc-editor.org/info/rfc791">http://www.rfc-editor.org/info/rfc791</a>>.
[<a id="ref-RFC793">RFC793</a>] Postel, J., "Transmission Control Protocol", STD 7,
<a href="./rfc793">RFC 793</a>, DOI 10.17487/RFC0793, September 1981,
<<a href="http://www.rfc-editor.org/info/rfc793">http://www.rfc-editor.org/info/rfc793</a>>.
[<a id="ref-RFC1035">RFC1035</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, DOI 10.17487/RFC1035,
November 1987, <<a href="http://www.rfc-editor.org/info/rfc1035">http://www.rfc-editor.org/info/rfc1035</a>>.
[<a id="ref-RFC1122">RFC1122</a>] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>,
DOI 10.17487/RFC1122, October 1989,
<<a href="http://www.rfc-editor.org/info/rfc1122">http://www.rfc-editor.org/info/rfc1122</a>>.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2181">RFC2181</a>] Elz, R. and R. Bush, "Clarifications to the DNS
Specification", <a href="./rfc2181">RFC 2181</a>, DOI 10.17487/RFC2181, July
1997, <<a href="http://www.rfc-editor.org/info/rfc2181">http://www.rfc-editor.org/info/rfc2181</a>>.
[<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, DOI 10.17487/RFC2460,
December 1998, <<a href="http://www.rfc-editor.org/info/rfc2460">http://www.rfc-editor.org/info/rfc2460</a>>.
[<a id="ref-RFC2826">RFC2826</a>] Internet Architecture Board, "IAB Technical Comment on
the Unique DNS Root", <a href="./rfc2826">RFC 2826</a>, DOI 10.17487/RFC2826, May
2000, <<a href="http://www.rfc-editor.org/info/rfc2826">http://www.rfc-editor.org/info/rfc2826</a>>.
[<a id="ref-RFC2870">RFC2870</a>] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak,
"Root Name Server Operational Requirements", <a href="https://www.rfc-editor.org/bcp/bcp40">BCP 40</a>,
<a href="./rfc2870">RFC 2870</a>, DOI 10.17487/RFC2870, June 2000,
<<a href="http://www.rfc-editor.org/info/rfc2870">http://www.rfc-editor.org/info/rfc2870</a>>.
<span class="grey">Blanchet & Liman Best Current Practice [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7720">RFC 7720</a> Root Name Service Requirements December 2015</span>
[<a id="ref-RFC3172">RFC3172</a>] Huston, G., Ed., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area
Domain ("arpa")", <a href="https://www.rfc-editor.org/bcp/bcp52">BCP 52</a>, <a href="./rfc3172">RFC 3172</a>, DOI 10.17487/RFC3172,
September 2001, <<a href="http://www.rfc-editor.org/info/rfc3172">http://www.rfc-editor.org/info/rfc3172</a>>.
[<a id="ref-RFC4035">RFC4035</a>] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security
Extensions", <a href="./rfc4035">RFC 4035</a>, DOI 10.17487/RFC4035, March 2005,
<<a href="http://www.rfc-editor.org/info/rfc4035">http://www.rfc-editor.org/info/rfc4035</a>>.
[<a id="ref-RFC6891">RFC6891</a>] Damas, J., Graff, M., and P. Vixie, "Extension Mechanisms
for DNS (EDNS(0))", STD 75, <a href="./rfc6891">RFC 6891</a>,
DOI 10.17487/RFC6891, April 2013,
<<a href="http://www.rfc-editor.org/info/rfc6891">http://www.rfc-editor.org/info/rfc6891</a>>.
[<a id="ref-ROOTZONE">ROOTZONE</a>] "Root Zone", <<a href="ftp://rs.internic.net/domain/root.zone">ftp://rs.internic.net/domain/root.zone</a>>.
[<a id="ref-RSSAC-001">RSSAC-001</a>] Root Server System Advisory Committee (RSSAC), "Service
Expectations of Root Servers", November 2014,
<<a href="https://www.icann.org/en/system/files/files/rssac-001-root-service-expectations-04dec15-en.pdf">https://www.icann.org/en/system/files/files/</a>
<a href="https://www.icann.org/en/system/files/files/rssac-001-root-service-expectations-04dec15-en.pdf">rssac-001-root-service-expectations-04dec15-en.pdf</a>>.
Acknowledgements
Some text was taken from [<a href="./rfc2870" title=""Root Name Server Operational Requirements"">RFC2870</a>]. The editors of this document
would like to sincerely thank the following individuals for valuable
contributions to the text: Andrew Sullivan, Simon Perreault,
Jean-Philippe Dionne, Dave Thaler, Russ Housley, Alissa Cooper, Joe
Abley, Joao Damas, Daniel Karrenberg, Jacques Latour, Eliot Lear,
Bill Manning, David Conrad, Paul Hoffman, Terry Manderson, Jari
Arkko, and Mark Andrews.
<span class="grey">Blanchet & Liman Best Current Practice [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7720">RFC 7720</a> Root Name Service Requirements December 2015</span>
Authors' Addresses
Marc Blanchet
Viagenie
246 Aberdeen
Quebec, QC G1R 2E1
Canada
Email: Marc.Blanchet@viagenie.ca
URI: <a href="http://viagenie.ca">http://viagenie.ca</a>
Lars-Johan Liman
Netnod Internet Exchange
Box 30194
SE-104 25 Stockholm
Sweden
Email: liman@netnod.se
URI: <a href="http://www.netnod.se/">http://www.netnod.se/</a>
Blanchet & Liman Best Current Practice [Page 6]
</pre>
|
