Alternative Context Resolution Pointers

Document Type Active Internet-Draft (individual)
Last updated 2016-10-28
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)
Network Working Group                                          T. Hardie
Internet-Draft                                          October 28, 2016
Intended status: Informational
Expires: May 1, 2017

                Alternative Context Resolution Pointers


   In RFC 2826, the IAB set out the benefits of a globally unique public
   name space.  As alternative contexts of resolution emerge, such as
   those implied by RFC 7686, maintaining a single namespace for the
   Internet requires a method to indicate the context of resolution for
   a name.  This document proposes a registry for such alternative
   resolution contexts as well as a set of pointer resource record types
   useful for allowing conformant resolvers which query for the name in
   the DNS to be redirected to the appropriate alternative resolution

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

   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 May 1, 2017.

Copyright Notice

   Copyright (c) 2016 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
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Hardie                     Expires May 1, 2017                  [Page 1]
Internet-Draft                arc-pointers                  October 2016

   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.

1.  Introduction

   RFC 2826[RFC2826] begins "To remain a global network, the Internet
   requires the existence of a globally unique public name space".  At
   the time it was written, that global name space was expressed almost
   completely in the DNS, which achieves uniqueness by descent from a
   single root.

   As new naming methods have emerged, the distinction between a DNS
   name and a name in the Internet name space but not in the DNS has
   been difficult to draw.  The Special Use Names registry [RFC6761] has
   been used to note some alternative name resolution contexts, for
   example those used by TOR [RFC7686].  This registry is, however,
   problematic for this use because it permanently links a particular
   name or label with the resolution method.  It is also strongly
   focused on resolution systems which occupy a place parallel to names
   in the root zone, creating policy considerations which would not
   apply to other parts of the Internet name space.

   This document proposes a set of mechanisms to address the addition of
   alternative contexts of resolution, with the intent that this be
   possible at multiple levels of the Internet namespace.

2.  Basic Approach

   This document proposes the creation of a registry for alternative
   resolution contexts which share the Internet's global name space.
   Entry into this registry will be specification required, with the
   IESG as the approver of new entries.

   This document also proposes the creation of a subdomain under .arpa,  Each label under will have an ARC resource record
   storing a URN from the IETF protocol parameter registry [RFC3553]
   that identifies the registry entry for the alternative resolution
   context.  Lastly, this document propose the creation of an ARCPOINTER
   resource recorder.

   To indicate that part of the Internet namespace uses an alternative
   resolution context, an ARCPOINTER resource record is placed at the
   appropriate label.  The ARCPOINTER resource record should be the only
   resource record for that label other than those needed to secure the

Hardie                     Expires May 1, 2017                  [Page 2]
Internet-Draft                arc-pointers                  October 2016

Show full document text