| Internet-Draft | Infrastructure .int domains | January 2022 |
| Davies & Baber | Expires 9 July 2022 | [Page] |
The document marks as historic any "int" domain names that were designated for infrastructure purposes, and identifies them for removal from the "int" top-level domain. Any implementation that involves these domains should be considered deprecated. This document also marks RFC 1528 and RFC 1706 as historic, and updates RFC 1591 by removing the documented use of "int" for international databases.¶
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 9 July 2022.¶
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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
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 in practice obsolete. This document formalizes moving the related specifications to historic status, along with removing any associated delegations from the "int" zone in the domain name system.¶
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.¶
The atma.int domain was experimentally defined to implement address lookups for Asynchronous Transfer Mode (ATM), including ATM End System Addresses (AESAs). [ANS]¶
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].¶
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].¶
The nsap.int domain name was specified to experimentally map Open Systems Interconnection (OSI) Network Service Access Points to domain names [RFC1706].¶
The rdi.int domain name experimentally mapped OSI Inter-Domain Routing Protocol's Routing Domain Identifiers [ISO10747] to the domain name system.¶
The specification for tpc.int [RFC1528] should be deemed historic as it no longer functions as described in the document.¶
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.¶
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.¶
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.¶
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. Following this review, the remaining domains delegated for infrastructure identifier related purposes were reviewed. As part of this review, query patterns in the DNS were analyzed and judged to be insignificant. 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.¶
I-D source is maintained at: https://github.com/kjd/draft-davies-int-historic¶
This document was compiled with help from Ted Hardie and Michelle Cotton, with additional input by Jari Arkko and Warren Kumari.¶