Internet Assigned Numbers Authority

PTI/ICANN 12025 Waterfront Drive Los Angeles 90094 United States of America kim.davies@iana.org

Internet Assigned Numbers Authority

PTI/ICANN 12025 Waterfront Drive Los Angeles 90094 United States of America amanda.baber@iana.org

Internet-Draft 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.

The “int” top-level domain 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 . 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).

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 .

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 .

The nsap.int domain name was specified to experimentally map Open Systems Interconnection (OSI) Network Service Access Points to domain names .

The rdi.int domain name experimentally mapped OSI Inter-Domain Routing Protocol’s Routing Domain Identifiers to the domain name system.

The reg.int domain name hosted an experimental mechanism for publishing IANA registration values in the domain name system.

The tpc.int domain name hosted an experimental remote printing service that served as a gateway between Internet mail and facsimile transmission .

The specification for tpc.int should be deemed historic as it no longer functions as described in the document.

The use of the “int” top-level domain for international databases should be deemed historic given the transfer of these functions to the “arpa” top-level domain .

The specification for nsap.int 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.

This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard. This memo provides some information on the structure of the names in the Domain Name System (DNS), specifically the top-level domain names; and on the administration of domains. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This document defines the format of one new Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR may be used with any NSAP address format. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document advises of the deprecation of the use of "ip6.int" for Standards Conformant IPv6 implementations. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

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.