This repository has been archived by the owner on May 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
draft-davies-int-historic.txt
280 lines (183 loc) · 9.88 KB
/
draft-davies-int-historic.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
Network Working Group K. Davies
Internet-Draft A. Baber
Updates: 1528, 1706 (if approved) IANA
Intended status: Informational November 28, 2022
Expires: June 1, 2023
Deprecating infrastructure "int" domains
draft-davies-int-historic-05
Abstract
The document deprecates the use of any "int" domain names that were
designated for infrastructure purposes by the IETF, and identifies
them for removal from the "int" top-level domain. Any implementation
that involves these domains should be considered deprecated. This
document also requests moving the status of RFC 1528 and RFC 1706 to
historic.
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 June 1, 2023.
Copyright Notice
Copyright (c) 2022 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
Davies & Baber Expires June 1, 2023 [Page 1]
Internet-Draft Infrastructure .int domains November 2022
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
1. Introduction
The "int" top-level domain [RFC1591] is a specialized domain
designated for intergovernmental organizations, which are
organizations established by international treaties between or among
national governments.
Historically, the "int" domain was also used for Internet
infrastructure related purposes. This practice ended in 2001 when
the "arpa" domain was declared the appropriate home for
infrastructural identifier spaces [RFC3172]. In conjunction with
this change, the eligibility for "int" domains was limited to only
intergovernmental treaty organizations.
The documented uses of infrastructural identifiers in the "int"
domain were largely experimental and are now in practice obsolete.
This document requests moving the related specifications to historic
status, along with removing any associated delegations from the "int"
zone in the domain name system.
2. Historical infrastructural uses
The following domains were used for infrastructural identifier
purposes that are now considered historic. Although each of these
names was either delegated or documented at one time, the parties
administering them have long since stopped using them.
2.1. atma.int
The atma.int domain was experimentally defined to implement address
lookups for Asynchronous Transfer Mode (ATM), including ATM End
System Addresses (AESAs). [ANS]
2.2. ip4.int
The ip4.int domain was described as providing an alternative to in-
addr.arpa domain for mapping host IPv4 addresses to host names. The
in-addr.arpa domain zone continues to be administered for this
purpose [RFC1035].
2.3. ip6.int
The ip6.int domain was originally delegated for mapping host IPv6
addresses to host names. It was subsequently removed from the "int"
zone, having been replaced by ip6.arpa for this purpose [RFC4159].
Davies & Baber Expires June 1, 2023 [Page 2]
Internet-Draft Infrastructure .int domains November 2022
2.4. nsap.int
The nsap.int domain name was specified to experimentally map Open
Systems Interconnection (OSI) Network Service Access Points to domain
names [RFC1706].
2.5. rdi.int
The rdi.int domain name experimentally mapped OSI Inter-Domain
Routing Protocol's Routing Domain Identifiers [ISO10747] to the
domain name system.
2.6. reg.int
The reg.int domain name hosted an experimental mechanism for
publishing IANA registration values in the domain name system.
2.7. tpc.int
The tpc.int domain name hosted an experimental remote printing
service that served as a gateway between Internet mail and facsimile
transmission [RFC1528].
3. Updates to other RFC Series documents
3.1. RFC 1528
The specification for tpc.int [RFC1528] should be deemed historic as
it no longer functions as described in the document.
3.2. RFC 1706
The specification for nsap.int [RFC1706] should be deemed historic as
it no longer functions as described in the document.
4. IANA Considerations
The IANA shall coordinate the removal of any of the historical "int"
domains discussed in this document that are still delegated in the
"int" zone.
5. Security Considerations
Some old systems might have one or more subdomains of these names
hardwired and expect a positive response for at least the second-
level domain. This is, of course, true for any name in the DNS and
should not be the sole basis to retain obsolete names.
Davies & Baber Expires June 1, 2023 [Page 3]
Internet-Draft Infrastructure .int domains November 2022
Existing applications should eliminate any reliance upon these zones
for their historic purpose. The operator of the "int" domain should
be cautious about any potential re-use of these domains for
intergovernmental treaty organizations.
6. Additional Information
This document is the result of an comprehensive inventory conducted
by the IANA team of .int domains to accurately establish and record
their purpose based on historical documentation. As part of this
inventory, the domains delegated for infrastructure identifier
related purposes were studied. Query patterns in the DNS for these
domains were analyzed and judged to be insignificant, and preliminary
outreach was conducted to the contacts for the associated domains.
The assessment concluded that these domains are highly likely to be
obsolete and this document is intended to formalize that assessment.
There are a small number of existing "int" domains nominally for
"international databases" that are not defined by any standards
documentation, and are assigned to entities rather than for an
identifier purpose. While they would not qualify for a "int" domain
under current criteria, their disposition is beyond the scope of this
memo.
7. Informative References
[ANS] "ATM Name Service Specification Version 1.0", ATM Forum
AF-SAA-0069.000, November 1996, <https://www.broadband-
forum.org/technical/download/af-saa-0069.000.pdf>.
[ISO10747]
"Protocol for exchange of inter-domain routeing
information among intermediate systems to support
forwarding of ISO 8473 PDUs", ISO/IEC 10747:1994, October
1994, <https://www.iso.org/standard/21417.html>.
[RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <https://www.rfc-editor.org/info/rfc1035>.
[RFC1528] Malamud, C. and M. Rose, "Principles of Operation for the
TPC.INT Subdomain: Remote Printing -- Technical
Procedures", RFC 1528, DOI 10.17487/RFC1528, October 1993,
<https://www.rfc-editor.org/info/rfc1528>.
[RFC1591] Postel, J., "Domain Name System Structure and Delegation",
RFC 1591, DOI 10.17487/RFC1591, March 1994,
<https://www.rfc-editor.org/info/rfc1591>.
Davies & Baber Expires June 1, 2023 [Page 4]
Internet-Draft Infrastructure .int domains November 2022
[RFC1706] Manning, B. and R. Colella, "DNS NSAP Resource Records",
RFC 1706, DOI 10.17487/RFC1706, October 1994,
<https://www.rfc-editor.org/info/rfc1706>.
[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>.
[RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
DOI 10.17487/RFC4159, August 2005,
<https://www.rfc-editor.org/info/rfc4159>.
Notes (for removal before publication)
I-D source is maintained at: https://github.com/kjd/draft-davies-int-
historic
Acknowledgments
This document was compiled with help from Ted Hardie and Michelle
Cotton, with additional input from Jari Arkko, John Klensin, Warren
Kumari, Pete Resnick, George Michaelson and Toerless Eckert.
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
Amanda Baber
Internet Assigned Numbers Authority
PTI/ICANN
12025 Waterfront Drive
Los Angeles 90094
United States of America
Email: amanda.baber@iana.org
Davies & Baber Expires June 1, 2023 [Page 5]