A Procedure for Cautious Delegation of a DNS Name
draft-kolkman-cautious-delegation-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Authors Olaf Kolkman  , Andrew Sullivan  , Warren Kumari 
Last updated 2013-06-27
Stream (None)
Intended RFC status (None)
Formats 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                                         O. Kolkman
Internet-Draft                                                NLnet Labs
Intended status: Informational                               A. Sullivan
Expires: December 28, 2013                                     Dyn, Inc.
                                                               W. Kumari
                                                            Google, Inc.
                                                           June 26, 2013

           A Procedure for Cautious Delegation of a DNS Name
                  draft-kolkman-cautious-delegation-01

Abstract

   Sometimes, a DNS name is known to be in use in the wild even though
   it was never properly delegated.  This situation appears
   particularly, but not only, true in certain domains near the root of
   the tree: people have independently used those non-existent top-level
   domains as private namespaces.  If those names are to be delegated in
   the public DNS, prudence dictates that collisions between the private
   uses and the public use be minimized.  We outline a procedure to
   evaluate the harm of delegation.

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 http://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 December 28, 2013.

Copyright Notice

   Copyright (c) 2013 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

Kolkman, et al.         Expires December 28, 2013               [Page 1]
Internet-Draft             Cautious Delegation                 June 2013

   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.

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Background and Introduction . . . . . . . . . . . . . . . . . . 3
     2.1.  Search-path interaction.  . . . . . . . . . . . . . . . . . 4
   3.  Predelegation determination of use of a name  . . . . . . . . . 4
     3.1.  Predelegation testing is needed . . . . . . . . . . . . . . 5
     3.2.  Determining the names of concern  . . . . . . . . . . . . . 5
       3.2.1.  Mode 1: Prior to any delegation . . . . . . . . . . . . 6
       3.2.2.  Mode 2: After delegation  . . . . . . . . . . . . . . . 6
   4.  Parameters for operation of this procedure  . . . . . . . . . . 7
     4.1.  Median or Mean  . . . . . . . . . . . . . . . . . . . . . . 7
     4.2.  Discussion of Alternatives  . . . . . . . . . . . . . . . . 7
   5.  Security considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   7.  Informative References  . . . . . . . . . . . . . . . . . . . . 8
   Appendix A.  Document Editing Details . . . . . . . . . . . . . . . 8
     A.1.  version 00  . . . . . . . . . . . . . . . . . . . . . . . . 8
     A.2.  version 01  . . . . . . . . . . . . . . . . . . . . . . . . 9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Kolkman, et al.         Expires December 28, 2013               [Page 2]
Internet-Draft             Cautious Delegation                 June 2013

1.  Terminology

   NXDOMAIN:  an alternate expression for the "Name Error" RCODE as
         described in [[RFC1035] Section 4.1.1].  The two terms are used
         interchangeably in this document. (definition from [RFC2308])

   In this document we will be using the terms zone, domain and sub-
   domain.  When envisioning the domain namespace as a tree, with nodes
   at the places where the dots separate the labels in a domain name,
   then:

   a 'domain'  is an entire branch. e.g.  The .org domain is the branch
         of the domain name tree for which all names end in .org.
   a 'sub-domain'  is a subordinate namespace of a given domain. e.g.
         all names ending in example.org are in the domain example.org
         which is a sub-domain of .org
Show full document text