Additional Reserved Top Level Domains
draft-chapin-additional-reserved-tlds-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-01-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Internet Engineering Task Force                               L. Chapin
Internet-Draft                                                Interisle
Intended Status: Informational                              M. McFadden
Expires: July 2014                          InterConnect Communications
                                                        January 7, 2014

                   Additional Reserved Top Level Domains
                 draft-chapin-additional-reserved-tlds-00

Abstract

   The Internet Domain Name System (DNS) defines a tree of names
   starting with root, ".", immediately below which are top level
   domain (TLD) names such as ".com" and ".us". In June 1999 RFC2606
   reserved a small number of TLD names for use in documentation
   examples, private testing, experiments, and other circumstances in
   which it is desirable to avoid conflict with current or future
   actual TLD names in the DNS.

   There has been significant evolution of Internet engineering and
   operation practices since RFC2606 was published. In February 2013
   RFC6761 defined criteria and procedures for reserving a domain name
   for special use, and established an IANA registry for such names.
   This document reserves eight domain name labels for special use in
   accordance with the criteria and procedures of RFC6761: localdomain,
   domain, lan, home, host, corp, mail, and exchange.

   It is important to note that TLD names may be reserved, in other
   contexts, for policy, political, or other reasons that are distinct
   from the IETF's concern with Internet engineering and operations.
   This document reserves TLD names only for operational and
   engineering reasons.

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), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet-
   Drafts.

Chapin                   Expires July 7, 2014                  [Page 1]
Internet-Draft  draft-chapin-additional-reserved-tlds      January 2014

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on July 8, 2014.

Copyright Notice

   Copyright (c) 2014 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
   (http://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.

Table of Contents

   1. Introduction...................................................4
   2. Conventions used in this document..............................5
   3. New top-level domain name reservations.........................5
   4. Security Considerations........................................6
   5. IANA Considerations............................................6
      5.1. Domain Name Reservation Considerations for "localdomain"..7
         5.1.1. Users:...............................................7
         5.1.2. Application Software:................................7
         5.1.3. Name Resolution APIs and Libraries:..................8
         5.1.4. Caching DNS Servers:.................................8
         5.1.5. Authoritative DNS Servers:...........................8
         5.1.6. DNS Server Operators:................................8
         5.1.7. DNS Registries/Registrars:...........................9
      5.2. Domain Name Reservation Considerations for "domain".......9
         5.2.1. Users:...............................................9
         5.2.2. Application Software:................................9
         5.2.3. Name Resolution APIs and Libraries:.................10
         5.2.4. Caching DNS Servers:................................10
         5.2.5. Authoritative DNS Servers:..........................10
         5.2.6. DNS Server Operators:...............................10

Chapin                   Expires July 7, 2014                  [Page 2]
Internet-Draft  draft-chapin-additional-reserved-tlds      January 2014

         5.2.7. DNS Registries/Registrars:..........................11
      5.3. Domain Name Reservation Considerations for "lan".........11
         5.3.1. Users:..............................................11
         5.3.2. Application Software:...............................12
Show full document text