Debian Codegraph @

rfc1591.html

raw
1 <pre>Network Working Group J. Postel
2 Request for Comments: 1591 ISI
3 Category: Informational March 1994
4
5
6 <span class="h1">Domain Name System Structure and Delegation</span>
7
8
9 Status of this Memo
10
11 This memo provides information for the Internet community. This memo
12 does not specify an Internet standard of any kind. Distribution of
13 this memo is unlimited.
14
15 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
16
17 This memo provides some information on the structure of the names in
18 the Domain Name System (DNS), specifically the top-level domain
19 names; and on the administration of domains. The Internet Assigned
20 Numbers Authority (IANA) is the overall authority for the IP
21 Addresses, the Domain Names, and many other parameters, used in the
22 Internet. The day-to-day responsibility for the assignment of IP
23 Addresses, Autonomous System Numbers, and most top and second level
24 Domain Names are handled by the Internet Registry (IR) and regional
25 registries.
26
27 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Top Level Structure of the Domain Names</span>
28
29 In the Domain Name System (DNS) naming of computers there is a
30 hierarchy of names. The root of system is unnamed. There are a set
31 of what are called "top-level domain names" (TLDs). These are the
32 generic TLDs (EDU, COM, NET, ORG, GOV, MIL, and INT), and the two
33 letter country codes from ISO-3166. It is extremely unlikely that
34 any other TLDs will be created.
35
36 Under each TLD may be created a hierarchy of names. Generally, under
37 the generic TLDs the structure is very flat. That is, many
38 organizations are registered directly under the TLD, and any further
39 structure is up to the individual organizations.
40
41 In the country TLDs, there is a wide variation in the structure, in
42 some countries the structure is very flat, in others there is
43 substantial structural organization. In some country domains the
44 second levels are generic categories (such as, AC, CO, GO, and RE),
45 in others they are based on political geography, and in still others,
46 organization names are listed directly under the country code. The
47 organization for the US country domain is described in <a href="./rfc1480">RFC 1480</a> [<a href="#ref-1" title="&quot;The US Domain&quot;">1</a>].
48
49
50
51
52 <span class="grey">Postel [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
55
56
57 Each of the generic TLDs was created for a general category of
58 organizations. The country code domains (for example, FR, NL, KR,
59 US) are each organized by an administrator for that country. These
60 administrators may further delegate the management of portions of the
61 naming tree. These administrators are performing a public service on
62 behalf of the Internet community. Descriptions of the generic
63 domains and the US country domain follow.
64
65 Of these generic domains, five are international in nature, and two
66 are restricted to use by entities in the United States.
67
68 World Wide Generic Domains:
69
70 COM - This domain is intended for commercial entities, that is
71 companies. This domain has grown very large and there is
72 concern about the administrative load and system performance if
73 the current growth pattern is continued. Consideration is
74 being taken to subdivide the COM domain and only allow future
75 commercial registrations in the subdomains.
76
77 EDU - This domain was originally intended for all educational
78 institutions. Many Universities, colleges, schools,
79 educational service organizations, and educational consortia
80 have registered here. More recently a decision has been taken
81 to limit further registrations to 4 year colleges and
82 universities. Schools and 2-year colleges will be registered
83 in the country domains (see US Domain, especially K12 and CC,
84 below).
85
86 NET - This domain is intended to hold only the computers of network
87 providers, that is the NIC and NOC computers, the
88 administrative computers, and the network node computers. The
89 customers of the network provider would have domain names of
90 their own (not in the NET TLD).
91
92 ORG - This domain is intended as the miscellaneous TLD for
93 organizations that didn't fit anywhere else. Some non-
94 government organizations may fit here.
95
96 INT - This domain is for organizations established by international
97 treaties, or international databases.
98
99 United States Only Generic Domains:
100
101 GOV - This domain was originally intended for any kind of government
102 office or agency. More recently a decision was taken to
103 register only agencies of the US Federal government in this
104 domain. State and local agencies are registered in the country
105
106
107
108 <span class="grey">Postel [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
111
112
113 domains (see US Domain, below).
114
115 MIL - This domain is used by the US military.
116
117 Example country code Domain:
118
119 US - As an example of a country domain, the US domain provides for
120 the registration of all kinds of entities in the United States
121 on the basis of political geography, that is, a hierarchy of
122 &lt;entity-name&gt;.&lt;locality&gt;.&lt;state-code&gt;.US. For example,
123 "IBM.Armonk.NY.US". In addition, branches of the US domain are
124 provided within each state for schools (K12), community colleges
125 (CC), technical schools (TEC), state government agencies
126 (STATE), councils of governments (COG),libraries (LIB), museums
127 (MUS), and several other generic types of entities (see <a href="./rfc1480">RFC 1480</a>
128 for details [<a href="#ref-1" title="&quot;The US Domain&quot;">1</a>]).
129
130 To find a contact for a TLD use the "whois" program to access the
131 database on the host rs.internic.net. Append "-dom" to the name of
132 TLD you are interested in. For example:
133
134 whois -h rs.internic.net us-dom
135 or
136 whois -h rs.internic.net edu-dom
137
138 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Administration of Delegated Domains</span>
139
140 The Internet Assigned Numbers Authority (IANA) is responsible for the
141 overall coordination and management of the Domain Name System (DNS),
142 and especially the delegation of portions of the name space called
143 top-level domains. Most of these top-level domains are two-letter
144 country codes taken from the ISO standard 3166.
145
146 A central Internet Registry (IR) has been selected and designated to
147 handled the bulk of the day-to-day administration of the Domain Name
148 System. Applications for new top-level domains (for example, country
149 code domains) are handled by the IR with consultation with the IANA.
150 The central IR is INTERNIC.NET. Second level domains in COM, EDU,
151 ORG, NET, and GOV are registered by the Internet Registry at the
152 InterNIC. The second level domains in the MIL are registered by the
153 DDN registry at NIC.DDN.MIL. Second level names in INT are
154 registered by the PVM at ISI.EDU.
155
156 While all requests for new top-level domains must be sent to the
157 Internic (at [email protected]), the regional registries are
158 often enlisted to assist in the administration of the DNS, especially
159 in solving problems with a country administration. Currently, the
160 RIPE NCC is the regional registry for Europe and the APNIC is the
161
162
163
164 <span class="grey">Postel [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
167
168
169 regional registry for the Asia-Pacific region, while the INTERNIC
170 administers the North America region, and all the as yet undelegated
171 regions.
172
173 The contact mailboxes for these regional registries are:
174
175 INTERNIC [email protected]
176 APNIC [email protected]
177 RIPE NCC [email protected]
178
179 The policy concerns involved when a new top-level domain is
180 established are described in the following. Also mentioned are
181 concerns raised when it is necessary to change the delegation of an
182 established domain from one party to another.
183
184 A new top-level domain is usually created and its management
185 delegated to a "designated manager" all at once.
186
187 Most of these same concerns are relevant when a sub-domain is
188 delegated and in general the principles described here apply
189 recursively to all delegations of the Internet DNS name space.
190
191 The major concern in selecting a designated manager for a domain is
192 that it be able to carry out the necessary responsibilities, and have
193 the ability to do a equitable, just, honest, and competent job.
194
195 1) The key requirement is that for each domain there be a designated
196 manager for supervising that domain's name space. In the case of
197 top-level domains that are country codes this means that there is
198 a manager that supervises the domain names and operates the domain
199 name system in that country.
200
201 The manager must, of course, be on the Internet. There must be
202 Internet Protocol (IP) connectivity to the nameservers and email
203 connectivity to the management and staff of the manager.
204
205 There must be an administrative contact and a technical contact
206 for each domain. For top-level domains that are country codes at
207 least the administrative contact must reside in the country
208 involved.
209
210 2) These designated authorities are trustees for the delegated
211 domain, and have a duty to serve the community.
212
213 The designated manager is the trustee of the top-level domain for
214 both the nation, in the case of a country code, and the global
215 Internet community.
216
217
218
219
220 <span class="grey">Postel [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
223
224
225 Concerns about "rights" and "ownership" of domains are
226 inappropriate. It is appropriate to be concerned about
227 "responsibilities" and "service" to the community.
228
229 3) The designated manager must be equitable to all groups in the
230 domain that request domain names.
231
232 This means that the same rules are applied to all requests, all
233 requests must be processed in a non-discriminatory fashion, and
234 academic and commercial (and other) users are treated on an equal
235 basis. No bias shall be shown regarding requests that may come
236 from customers of some other business related to the manager --
237 e.g., no preferential service for customers of a particular data
238 network provider. There can be no requirement that a particular
239 mail system (or other application), protocol, or product be used.
240
241 There are no requirements on subdomains of top-level domains
242 beyond the requirements on higher-level domains themselves. That
243 is, the requirements in this memo are applied recursively. In
244 particular, all subdomains shall be allowed to operate their own
245 domain name servers, providing in them whatever information the
246 subdomain manager sees fit (as long as it is true and correct).
247
248 4) Significantly interested parties in the domain should agree that
249 the designated manager is the appropriate party.
250
251 The IANA tries to have any contending parties reach agreement
252 among themselves, and generally takes no action to change things
253 unless all the contending parties agree; only in cases where the
254 designated manager has substantially mis-behaved would the IANA
255 step in.
256
257 However, it is also appropriate for interested parties to have
258 some voice in selecting the designated manager.
259
260 There are two cases where the IANA and the central IR may
261 establish a new top-level domain and delegate only a portion of
262 it: (1) there are contending parties that cannot agree, or (2) the
263 applying party may not be able to represent or serve the whole
264 country. The later case sometimes arises when a party outside a
265 country is trying to be helpful in getting networking started in a
266 country -- this is sometimes called a "proxy" DNS service.
267
268 The Internet DNS Names Review Board (IDNB), a committee
269 established by the IANA, will act as a review panel for cases in
270 which the parties can not reach agreement among themselves. The
271 IDNB's decisions will be binding.
272
273
274
275
276 <span class="grey">Postel [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
279
280
281 5) The designated manager must do a satisfactory job of operating the
282 DNS service for the domain.
283
284 That is, the actual management of the assigning of domain names,
285 delegating subdomains and operating nameservers must be done with
286 technical competence. This includes keeping the central IR (in
287 the case of top-level domains) or other higher-level domain
288 manager advised of the status of the domain, responding to
289 requests in a timely manner, and operating the database with
290 accuracy, robustness, and resilience.
291
292 There must be a primary and a secondary nameserver that have IP
293 connectivity to the Internet and can be easily checked for
294 operational status and database accuracy by the IR and the IANA.
295
296 In cases when there are persistent problems with the proper
297 operation of a domain, the delegation may be revoked, and possibly
298 delegated to another designated manager.
299
300 6) For any transfer of the designated manager trusteeship from one
301 organization to another, the higher-level domain manager (the IANA
302 in the case of top-level domains) must receive communications from
303 both the old organization and the new organization that assure the
304 IANA that the transfer in mutually agreed, and that the new
305 organization understands its responsibilities.
306
307 It is also very helpful for the IANA to receive communications
308 from other parties that may be concerned or affected by the
309 transfer.
310
311 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Rights to Names</span>
312
313 1) Names and Trademarks
314
315 In case of a dispute between domain name registrants as to the
316 rights to a particular name, the registration authority shall have
317 no role or responsibility other than to provide the contact
318 information to both parties.
319
320 The registration of a domain name does not have any Trademark
321 status. It is up to the requestor to be sure he is not violating
322 anyone else's Trademark.
323
324 2) Country Codes
325
326 The IANA is not in the business of deciding what is and what is
327 not a country.
328
329
330
331
332 <span class="grey">Postel [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1591">RFC 1591</a> Domain Name System Structure and Delegation March 1994</span>
335
336
337 The selection of the ISO 3166 list as a basis for country code
338 top-level domain names was made with the knowledge that ISO has a
339 procedure for determining which entities should be and should not
340 be on that list.
341
342 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
343
344 Security issues are not discussed in this memo.
345
346 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
347
348 Many people have made comments on draft version of these descriptions
349 and procedures. Steve Goldstein and John Klensin have been
350 particularly helpful.
351
352 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Author's Address</span>
353
354 Jon Postel
355 USC/Information Sciences Institute
356 4676 Admiralty Way
357 Marina del Rey, CA 90292
358
359 Phone: 310-822-1511
360 Fax: 310-823-6714
361 EMail: [email protected]
362
363 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
364
365 [<a id="ref-1">1</a>] Cooper, A., and J. Postel, "The US Domain", <a href="./rfc1480">RFC 1480</a>,
366 USC/Information Sciences Institute, June 1993.
367
368 [<a id="ref-2">2</a>] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1340">RFC 1340</a>,
369 USC/Information Sciences Institute, July 1992.
370
371 [<a id="ref-3">3</a>] Mockapetris, P., "Domain Names - Concepts and Facilities", STD
372 13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November 1987.
373
374 [<a id="ref-4">4</a>] Mockapetris, P., "Domain Names - Implementation and
375 Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences
376 Institute, November 1987.
377
378 [<a id="ref-6">6</a>] Partridge, C., "Mail Routing and the Domain System", STD 14, <a href="./rfc974">RFC</a>
379 <a href="./rfc974">974</a>, CSNET CIC BBN, January 1986.
380
381 [<a id="ref-7">7</a>] Braden, R., Editor, "Requirements for Internet Hosts --
382 Application and Support", STD 3, <a href="./rfc1123">RFC 1123</a>, Internet Engineering
383 Task Force, October 1989.
384
385
386
387
388 Postel [Page 7]
389 </pre>