Deprecating Infrastructure "int" DomainsInternet Assigned Numbers AuthorityPTI/ICANN12025 Waterfront DriveLos AngelesCA90094United States of Americakim.davies@iana.orgInternet Assigned Numbers AuthorityPTI/ICANN12025 Waterfront DriveLos AngelesCA90094United States of Americaamanda.baber@iana.orgThis document deprecates the use of any "int" domain names that were
designated for infrastructure purposes by the IETF, and it identifies
them for removal from the "int" top-level domain. Any implementations
that involve these domains are now deprecated. This
document also changes the status of RFC 1528 and RFC 1706 to
Historic.Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
.
Copyright Notice
Copyright (c) 2023 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
() 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.
Table of Contents
. Introduction
. Historical Infrastructural Uses
. atma.int
. ip4.int
. ip6.int
. nsap.int
. rdi.int
. reg.int
. tpc.int
. Updates to Other RFC Series Documents
. RFC 1528
. RFC 1706
. IANA Considerations
. Security Considerations
. Additional Information
. Informative References
Acknowledgments
Authors' Addresses
IntroductionThe "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 purposes related to Internet infrastructure. 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 are now, in practice, obsolete. This document
changes the status of related specifications to Historic, and it
removes any associated delegations from the "int" zone in the
domain name system.Historical Infrastructural UsesThe 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.atma.intThe atma.int domain was experimentally defined to implement address
lookups for Asynchronous Transfer Mode (ATM), including ATM End System
Addresses (AESAs) .ip4.intThe ip4.int domain was described as providing an alternative to the
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
.ip6.intThe 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 .nsap.intThe nsap.int domain name was specified to experimentally map Open
Systems Interconnection (OSI) Network Service Access Points to domain
names .rdi.intThe rdi.int domain name experimentally mapped OSI Inter-Domain Routing
Protocol's Routing Domain Identifiers to the domain name
system.reg.intThe reg.int domain name hosted an experimental mechanism for publishing
IANA registration values in the domain name system.tpc.intThe tpc.int domain name hosted an experimental remote printing
service that served as a gateway between Internet mail and facsimile
transmission .Updates to Other RFC Series DocumentsRFC 1528The specification for tpc.int is Historic,
as it no longer functions as described in the document.RFC 1706The specification for nsap.int is Historic,
as it no longer functions as described in the document.IANA ConsiderationsIANA has removed the historical "int"
domains discussed in this document.Security ConsiderationsSome 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 for retaining obsolete names.Existing applications should eliminate any reliance upon these
zones. The operator of the "int" domain
should be cautious about any potential re-use of these domains for
intergovernmental treaty organizations.Additional InformationThis document is the result of a comprehensive inventory of .int domains
to accurately establish and record their
purpose based on historical documentation. As part of this inventory,
IANA studied the domains delegated for purposes related to infrastructure identifiers. Query patterns in the DNS for these domains were analyzed
and judged to be insignificant; preliminary outreach
to the contacts for the associated domains was conducted. The assessment concluded
that these domains are very likely obsolete. This document formalizes that assessment.There are a small number of nominal "int" domains for
"international databases" that are not defined by any standards
documentation. They are assigned to entities rather than for
identifier purposes. Their dispositions are beyond the scope of this
memo.
Informative ReferencesATM Name System Specification Version 1.0The ATM Forum Technical CommitteeInformation technology - Telecommunications and information exchange between systems - Protocol for exchange of inter-domain routeing information among intermediate systems to support forwarding of ISO 8473 PDUsISO/IECDomain names - implementation and specificationThis 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.Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical ProceduresThis 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.Domain Name System Structure and DelegationThis 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.DNS NSAP Resource RecordsThis 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.Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")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.Deprecation of "ip6.int"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.AcknowledgmentsThis 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' AddressesInternet Assigned Numbers AuthorityPTI/ICANN12025 Waterfront DriveLos AngelesCA90094United States of Americakim.davies@iana.orgInternet Assigned Numbers AuthorityPTI/ICANN12025 Waterfront DriveLos AngelesCA90094United States of Americaamanda.baber@iana.org