rfc9121.original   rfc9121.txt 
Network Working Group K. Davies Internet Engineering Task Force (IETF) K. Davies
Internet-Draft A. Baber Request for Comments: 9121 A. Baber
Updates: 1528, 1706 (if approved) IANA Obsoletes: 1528 IANA
Intended status: Informational 28 November 2022 Updates: 1706 April 2023
Expires: 1 June 2023 Category: Informational
ISSN: 2070-1721
Deprecating infrastructure "int" domains Deprecating Infrastructure "int" Domains
draft-davies-int-historic-05
Abstract Abstract
The document deprecates the use of any "int" domain names that were This document deprecates the use of any "int" domain names that were
designated for infrastructure purposes by the IETF, and identifies designated for infrastructure purposes by the IETF, and it identifies
them for removal from the "int" top-level domain. Any implementation them for removal from the "int" top-level domain. Any
that involves these domains should be considered deprecated. This implementations that involve these domains are now deprecated. This
document also requests moving the status of RFC 1528 and RFC 1706 to document also changes the status of RFC 1528 and RFC 1706 to
historic. Historic.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." 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.
This Internet-Draft will expire on 1 June 2023. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9121.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Historical infrastructural uses . . . . . . . . . . . . . . . 3 2. Historical Infrastructural Uses
2.1. atma.int . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. atma.int
2.2. ip4.int . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. ip4.int
2.3. ip6.int . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. ip6.int
2.4. nsap.int . . . . . . . . . . . . . . . . . . . . . . . . 3 2.4. nsap.int
2.5. rdi.int . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.5. rdi.int
2.6. reg.int . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.6. reg.int
2.7. tpc.int . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.7. tpc.int
3. Updates to other RFC Series documents . . . . . . . . . . . . 4 3. Updates to Other RFC Series Documents
3.1. RFC 1528 . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. RFC 1528
3.2. RFC 1706 . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. RFC 1706
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations
6. Additional Information . . . . . . . . . . . . . . . . . . . 4 6. Additional Information
7. Informative References . . . . . . . . . . . . . . . . . . . 5 7. Informative References
Notes (for removal before publication) . . . . . . . . . . . . . 5 Acknowledgments
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The "int" top-level domain [RFC1591] is a specialized domain The "int" top-level domain [RFC1591] is a specialized domain
designated for intergovernmental organizations, which are designated for intergovernmental organizations, which are
organizations established by international treaties between or among organizations established by international treaties between or among
national governments. national governments.
Historically, the "int" domain was also used for Internet Historically, the "int" domain was also used for purposes related to
infrastructure related purposes. This practice ended in 2001 when Internet infrastructure. This practice ended in 2001 when the "arpa"
the "arpa" domain was declared the appropriate home for domain was declared the appropriate home for infrastructural
infrastructural identifier spaces [RFC3172]. In conjunction with identifier spaces [RFC3172]. In conjunction with this change, the
this change, the eligibility for "int" domains was limited to only eligibility for "int" domains was limited to only intergovernmental
intergovernmental treaty organizations. treaty organizations.
The documented uses of infrastructural identifiers in the "int" The documented uses of infrastructural identifiers in the "int"
domain were largely experimental and are now in practice obsolete. domain were largely experimental and are now, in practice, obsolete.
This document requests moving the related specifications to historic This document changes the status of related specifications to
status, along with removing any associated delegations from the "int" Historic, and it removes any associated delegations from the "int"
zone in the domain name system. zone in the domain name system.
2. Historical infrastructural uses 2. Historical Infrastructural Uses
The following domains were used for infrastructural identifier The following domains were used for infrastructural identifier
purposes that are now considered historic. Although each of these purposes that are now considered historic. Although each of these
names was either delegated or documented at one time, the parties names was either delegated or documented at one time, the parties
administering them have long since stopped using them. administering them have long since stopped using them.
2.1. atma.int 2.1. atma.int
The atma.int domain was experimentally defined to implement address The atma.int domain was experimentally defined to implement address
lookups for Asynchronous Transfer Mode (ATM), including ATM End lookups for Asynchronous Transfer Mode (ATM), including ATM End
System Addresses (AESAs). [ANS] System Addresses (AESAs) [ANS].
2.2. ip4.int 2.2. ip4.int
The ip4.int domain was described as providing an alternative to in- The ip4.int domain was described as providing an alternative to the
addr.arpa domain for mapping host IPv4 addresses to host names. The in-addr.arpa domain for mapping host IPv4 addresses to host names.
in-addr.arpa domain zone continues to be administered for this The in-addr.arpa domain zone continues to be administered for this
purpose [RFC1035]. purpose [RFC1035].
2.3. ip6.int 2.3. ip6.int
The ip6.int domain was originally delegated for mapping host IPv6 The ip6.int domain was originally delegated for mapping host IPv6
addresses to host names. It was subsequently removed from the "int" addresses to host names. It was subsequently removed from the "int"
zone, having been replaced by ip6.arpa for this purpose [RFC4159]. zone, having been replaced by ip6.arpa [RFC4159].
2.4. nsap.int 2.4. nsap.int
The nsap.int domain name was specified to experimentally map Open The nsap.int domain name was specified to experimentally map Open
Systems Interconnection (OSI) Network Service Access Points to domain Systems Interconnection (OSI) Network Service Access Points to domain
names [RFC1706]. names [RFC1706].
2.5. rdi.int 2.5. rdi.int
The rdi.int domain name experimentally mapped OSI Inter-Domain The rdi.int domain name experimentally mapped OSI Inter-Domain
skipping to change at page 4, line 11 skipping to change at line 141
The reg.int domain name hosted an experimental mechanism for The reg.int domain name hosted an experimental mechanism for
publishing IANA registration values in the domain name system. publishing IANA registration values in the domain name system.
2.7. tpc.int 2.7. tpc.int
The tpc.int domain name hosted an experimental remote printing The tpc.int domain name hosted an experimental remote printing
service that served as a gateway between Internet mail and facsimile service that served as a gateway between Internet mail and facsimile
transmission [RFC1528]. transmission [RFC1528].
3. Updates to other RFC Series documents 3. Updates to Other RFC Series Documents
3.1. RFC 1528 3.1. RFC 1528
The specification for tpc.int [RFC1528] should be deemed historic as The specification for tpc.int [RFC1528] is Historic, as it no longer
it no longer functions as described in the document. functions as described in the document.
3.2. RFC 1706 3.2. RFC 1706
The specification for nsap.int [RFC1706] should be deemed historic as The specification for nsap.int [RFC1706] is Historic, as it no longer
it no longer functions as described in the document. functions as described in the document.
4. IANA Considerations 4. IANA Considerations
The IANA shall coordinate the removal of any of the historical "int" IANA has removed the historical "int" domains discussed in this
domains discussed in this document that are still delegated in the document.
"int" zone.
5. Security Considerations 5. Security Considerations
Some old systems might have one or more subdomains of these names Some old systems might have one or more subdomains of these names
hardwired and expect a positive response for at least the second- 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 level domain. This is, of course, true for any name in the DNS and
should not be the sole basis to retain obsolete names. should not be the sole basis for retaining obsolete names.
Existing applications should eliminate any reliance upon these zones Existing applications should eliminate any reliance upon these zones.
for their historic purpose. The operator of the "int" domain should The operator of the "int" domain should be cautious about any
be cautious about any potential re-use of these domains for potential re-use of these domains for intergovernmental treaty
intergovernmental treaty organizations. organizations.
6. Additional Information 6. Additional Information
This document is the result of an comprehensive inventory conducted This document is the result of a comprehensive inventory of .int
by the IANA team of .int domains to accurately establish and record domains to accurately establish and record their purpose based on
their purpose based on historical documentation. As part of this historical documentation. As part of this inventory, IANA studied
inventory, the domains delegated for infrastructure identifier the domains delegated for purposes related to infrastructure
related purposes were studied. Query patterns in the DNS for these identifiers. Query patterns in the DNS for these domains were
domains were analyzed and judged to be insignificant, and preliminary analyzed and judged to be insignificant; preliminary outreach to the
outreach was conducted to the contacts for the associated domains. contacts for the associated domains was conducted. The assessment
The assessment concluded that these domains are highly likely to be concluded that these domains are very likely obsolete. This document
obsolete and this document is intended to formalize that assessment. formalizes that assessment.
There are a small number of existing "int" domains nominally for There are a small number of nominal "int" domains for "international
"international databases" that are not defined by any standards databases" that are not defined by any standards documentation. They
documentation, and are assigned to entities rather than for an are assigned to entities rather than for identifier purposes. Their
identifier purpose. While they would not qualify for a "int" domain dispositions are beyond the scope of this memo.
under current criteria, their disposition is beyond the scope of this
memo.
7. Informative References 7. Informative References
[ANS] "ATM Name Service Specification Version 1.0", ATM Forum [ANS] The ATM Forum Technical Committee, "ATM Name System
AF-SAA-0069.000, November 1996, <https://www.broadband- Specification Version 1.0", ATM Forum af-saa-0069.000,
November 1996, <https://www.broadband-
forum.org/technical/download/af-saa-0069.000.pdf>. forum.org/technical/download/af-saa-0069.000.pdf>.
[ISO10747] "Protocol for exchange of inter-domain routeing [ISO10747] ISO/IEC, "Information technology - Telecommunications and
information among intermediate systems to support information exchange between systems - Protocol for
forwarding of ISO 8473 PDUs", ISO/IEC 10747:1994, October exchange of inter-domain routeing information among
1994, <https://www.iso.org/standard/21417.html>. 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 [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <https://www.rfc-editor.org/info/rfc1035>. November 1987, <https://www.rfc-editor.org/info/rfc1035>.
[RFC1528] Malamud, C. and M. Rose, "Principles of Operation for the [RFC1528] Malamud, C. and M. Rose, "Principles of Operation for the
TPC.INT Subdomain: Remote Printing -- Technical TPC.INT Subdomain: Remote Printing -- Technical
Procedures", RFC 1528, DOI 10.17487/RFC1528, October 1993, Procedures", RFC 1528, DOI 10.17487/RFC1528, October 1993,
<https://www.rfc-editor.org/info/rfc1528>. <https://www.rfc-editor.org/info/rfc1528>.
skipping to change at page 5, line 49 skipping to change at line 227
[RFC3172] Huston, G., Ed., "Management Guidelines & Operational [RFC3172] Huston, G., Ed., "Management Guidelines & Operational
Requirements for the Address and Routing Parameter Area Requirements for the Address and Routing Parameter Area
Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172, Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172,
September 2001, <https://www.rfc-editor.org/info/rfc3172>. September 2001, <https://www.rfc-editor.org/info/rfc3172>.
[RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159, [RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
DOI 10.17487/RFC4159, August 2005, DOI 10.17487/RFC4159, August 2005,
<https://www.rfc-editor.org/info/rfc4159>. <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 Acknowledgments
This document was compiled with help from Ted Hardie and Michelle This document was compiled with help from Ted Hardie and Michelle
Cotton, with additional input from Jari Arkko, John Klensin, Warren Cotton, with additional input from Jari Arkko, John Klensin, Warren
Kumari, Pete Resnick, George Michaelson and Toerless Eckert. Kumari, Pete Resnick, George Michaelson, and Toerless Eckert.
Authors' Addresses Authors' Addresses
Kim Davies Kim Davies
Internet Assigned Numbers Authority Internet Assigned Numbers Authority
PTI/ICANN PTI/ICANN
12025 Waterfront Drive 12025 Waterfront Drive
Los Angeles, 90094 Los Angeles, 90094
United States of America United States of America
Email: kim.davies@iana.org Email: kim.davies@iana.org
 End of changes. 27 change blocks. 
107 lines changed or deleted 101 lines changed or added

This html diff was produced by rfcdiff 1.48.