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

Document Type Active Internet-Draft (individual)
Authors Kim Davies  , Amanda Baber 
Last updated 2021-03-25
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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: RFC1591 (if approved)                                      IANA
Intended status: Informational                            March 25, 2021
Expires: September 26, 2021

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

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.

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 September 26, 2021.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Davies & Baber         Expires September 26, 2021               [Page 1]
Internet-Draft         Infrastructure .int domains            March 2021

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

   The ip6.int domain was similarly delegated, and subsequently removed
   from the "int" zone, having been replaced by ip6.arpa for the purpose
   of mapping host IPv6 addresses to host names [RFC4159].

Davies & Baber         Expires September 26, 2021               [Page 2]
Internet-Draft         Infrastructure .int domains            March 2021

2.3.  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.4.  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.5.  reg.int

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

2.6.  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
Show full document text