Deprecating infrastructure "int" domains
draft-davies-int-historic-02

Document Type Active Internet-Draft (individual)
Authors Kim Davies  , Amanda Baber 
Last updated 2021-10-14
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          K. Davies
Internet-Draft                                                  A. Baber
Updates: 1591 (if approved)                                         IANA
Intended status: Informational                          October 14, 2021
Expires: April 17, 2022

                Deprecating infrastructure "int" domains
                      draft-davies-int-historic-02

Abstract

   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 updates RFC 1591 by removing the documented use of
   "int" for international databases.

Status of This Memo

   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 April 17, 2022.

Copyright Notice

   Copyright (c) 2021 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 Simplified BSD License text as described in Section 4.e of

Davies & Baber           Expires April 17, 2022                 [Page 1]
Internet-Draft         Infrastructure .int domains          October 2021

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   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.

2.  Historical infrastructural uses

   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.

2.1.  atma.int

   The atma.int domain was experimentally defined to implement address
   lookups for Asynchronous Transfer Mode (ATM), including ATM End
   System Addresses (AESAs).  [ANS]

2.2.  ip4.int

   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].

2.3.  ip6.int

   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].

Davies & Baber           Expires April 17, 2022                 [Page 2]
Internet-Draft         Infrastructure .int domains          October 2021

2.4.  nsap.int

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

2.5.  rdi.int

   The rdi.int domain name experimentally mapped OSI Inter-Domain
   Routing Protocol's Routing Domain Identifiers [ISO10747] to the
   domain name system.

2.6.  reg.int

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

2.7.  tpc.int

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

3.  IANA Considerations

   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.

4.  Security Considerations

   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.

5.  Additional Information

   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

Davies & Baber           Expires April 17, 2022                 [Page 3]
Internet-Draft         Infrastructure .int domains          October 2021

   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.

6.  Informative References

   [ANS]      "ATM Name Service", ATM Forum AF/95-1532R3, n.d..

   [ISO10747]
              "Protocol for exchange of inter-domain routeing
              information among 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
              specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
              November 1987, <https://www.rfc-editor.org/info/rfc1035>.

   [RFC1528]  Malamud, C. and M. Rose, "Principles of Operation for the
              TPC.INT Subdomain: Remote Printing -- Technical
              Procedures", RFC 1528, DOI 10.17487/RFC1528, October 1993,
              <https://www.rfc-editor.org/info/rfc1528>.

   [RFC1591]  Postel, J., "Domain Name System Structure and Delegation",
              RFC 1591, DOI 10.17487/RFC1591, March 1994,
              <https://www.rfc-editor.org/info/rfc1591>.

   [RFC1706]  Manning, B. and R. Colella, "DNS NSAP Resource Records",
              RFC 1706, DOI 10.17487/RFC1706, October 1994,
              <https://www.rfc-editor.org/info/rfc1706>.

   [RFC3172]  Huston, G., Ed., "Management Guidelines & Operational
              Requirements for the Address and Routing Parameter Area
              Domain ("arpa")", BCP 52, RFC 3172, DOI 10.17487/RFC3172,
              September 2001, <https://www.rfc-editor.org/info/rfc3172>.

   [RFC4159]  Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
              DOI 10.17487/RFC4159, August 2005,
              <https://www.rfc-editor.org/info/rfc4159>.

Davies & Baber           Expires April 17, 2022                 [Page 4]
Internet-Draft         Infrastructure .int domains          October 2021

Notes (for removal before publication)

   I-D source is maintained at: https://github.com/kjd/draft-davies-int-
   historic

Acknowledgments

   This document was compiled with help from Ted Hardie and Michelle
   Cotton, with additional input by Jari Arkko and Warren Kumari.

Authors' Addresses

   Kim Davies
   Internet Assigned Numbers Authority
   PTI/ICANN
   12025 Waterfront Drive
   Los Angeles  90094
   United States of America

   Email: kim.davies@iana.org

   Amanda Baber
   Internet Assigned Numbers Authority
   PTI/ICANN
   12025 Waterfront Drive
   Los Angeles  90094
   United States of America

   Email: amanda.baber@iana.org

Davies & Baber           Expires April 17, 2022                 [Page 5]