idnits 2.17.1 draft-davies-int-historic-00.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 : ---------------------------------------------------------------------------- == 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 (March 25, 2021) is 1129 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 1528 (Obsoleted by RFC 9121) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Davies 3 Internet-Draft A. Baber 4 Updates: RFC1591 (if approved) IANA 5 Intended status: Informational March 25, 2021 6 Expires: September 26, 2021 8 Deprecating infrastructure "int" domains 9 draft-davies-int-historic-00 11 Abstract 13 The document marks as historic any "int" domain names that were 14 designated for infrastructure purposes, and identifies them for 15 removal from the "int" top-level domain. Any implementation that 16 involves these domains should be considered deprecated. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on September 26, 2021. 35 Copyright Notice 37 Copyright (c) 2021 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 The "int" top-level domain [RFC1591] is a specialized domain 53 designated for intergovernmental organizations, which are 54 organizations established by international treaties between or among 55 national governments. 57 Historically, the "int" domain was also used for Internet 58 infrastructure related purposes. This practice ended in 2001 when 59 the "arpa" domain was declared the appropriate home for 60 infrastructural identifier spaces [RFC3172]. In conjunction with 61 this change, the eligibility for "int" domains was limited to only 62 intergovernmental treaty organizations. 64 The documented uses of infrastructural identifiers in the "int" 65 domain were largely experimental and in practice obsolete. This 66 document formalizes moving the related specifications to historic 67 status, along with removing any associated delegations from the "int" 68 zone in the domain name system. 70 2. Historical infrastructural uses 72 The following domains were used for infrastructural identifier 73 purposes that are now considered historic. Although each of these 74 names was either delegated or documented at one time, the parties 75 administering them have long since stopped using them. 77 2.1. atma.int 79 The atma.int domain was experimentally defined to implement address 80 lookups for Asynchronous Transfer Mode (ATM), including ATM End 81 System Addresses (AESAs). [ANS] 83 2.2. ip4.int 85 The ip4.int domain was described as providing an alternative to in- 86 addr.arpa domain for mapping host IPv4 addresses to host names. The 87 in-addr.arpa domain zone continues to be administered for this 88 purpose [RFC1035]. 90 The ip6.int domain was similarly delegated, and subsequently removed 91 from the "int" zone, having been replaced by ip6.arpa for the purpose 92 of mapping host IPv6 addresses to host names [RFC4159]. 94 2.3. nsap.int 96 The nsap.int domain name was specified to experimentally map Open 97 Systems Interconnection (OSI) Network Service Access Points to domain 98 names [RFC1706]. 100 2.4. rdi.int 102 The rdi.int domain name experimentally mapped OSI Inter-Domain 103 Routing Protocol's Routing Domain Identifiers [ISO10747] to the 104 domain name system. 106 2.5. reg.int 108 The reg.int domain name hosted an experimental mechanism for 109 publishing IANA registration values in the domain name system. 111 2.6. tpc.int 113 The tpc.int domain name hosted an experimental remote printing 114 service that served as a gateway between Internet mail and facsimile 115 transmission [RFC1528]. 117 3. IANA Considerations 119 The IANA shall coordinate the removal of the following "int" domains: 121 o atma.int 123 o ip4.int 125 o nsap.int 127 o rdi.int 129 o reg.int 131 o tpc.int 133 4. Security Considerations 135 Some old systems might have one or more subdomains of these names 136 hardwired and expect a positive response for at least the second- 137 level domain. This is, of course, true for any name in the DNS and 138 should not be the sole basis to retain obsolete names. 140 Existing applications should eliminate any reliance upon these zones 141 for their historic purpose. The operator of the "int" domain should 142 be cautious about any potential re-use of these domains for 143 intergovernmental treaty organizations. 145 5. Informative References 147 [ANS] "ATM Name Service", ATM Forum AF/95-1532R3, n.d.. 149 [ISO10747] 150 "Protocol for exchange of inter-domain routeing 151 information among intermediate systems to support 152 forwarding of ISO 8473 PDUs", ISO/IEC 10747:1994, October 153 1994, . 155 [RFC1035] Mockapetris, P., "Domain names - implementation and 156 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 157 November 1987, . 159 [RFC1528] Malamud, C. and M. Rose, "Principles of Operation for the 160 TPC.INT Subdomain: Remote Printing -- Technical 161 Procedures", RFC 1528, DOI 10.17487/RFC1528, October 1993, 162 . 164 [RFC1591] Postel, J., "Domain Name System Structure and Delegation", 165 RFC 1591, DOI 10.17487/RFC1591, March 1994, 166 . 168 [RFC1706] Manning, B. and R. Colella, "DNS NSAP Resource Records", 169 RFC 1706, DOI 10.17487/RFC1706, October 1994, 170 . 172 [RFC3172] Huston, G., Ed., "Management Guidelines & Operational 173 Requirements for the Address and Routing Parameter Area 174 Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172, 175 September 2001, . 177 [RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159, 178 DOI 10.17487/RFC4159, August 2005, 179 . 181 Notes (for removal before publication) 183 This document is the result of an comprehensive inventory conducted 184 by the IANA team of .int domains to accurately establish and record 185 their purpose based on historical documentation. Following this 186 review, the remaining domains delegated for infrastructure identifier 187 related purposes were brought to the IETF leadership for a 188 preliminary discussion on how they should be treated. It was 189 assessed that these domains are highly likely to be obsolete and this 190 document is intended to formalize that assessment. 192 There are a small number of existing "int" domains nominally for 193 "international databases" that are not defined by any standards 194 documentation, and are assigned to entities rather than for an 195 identifier purpose. While they would not qualify for a "int" domain 196 under current criteria, their disposition is beyond the scope of this 197 memo. 199 I-D source is maintained at: https://github.com/kjd/draft-davies-int- 200 historic 202 Acknowledgments 204 This document was compiled with help from Ted Hardie and Michelle 205 Cotton. 207 Authors' Addresses 209 Kim Davies 210 Internet Assigned Numbers Authority 211 PTI/ICANN 212 12025 Waterfront Drive 213 Los Angeles 90094 214 United States of America 216 Email: kim.davies@iana.org 218 Amanda Baber 219 Internet Assigned Numbers Authority 220 PTI/ICANN 221 12025 Waterfront Drive 222 Los Angeles 90094 223 United States of America 225 Email: amanda.baber@iana.org