Signaling that a domain name is an alias of another one
draft-bortzmeyer-bundled-signaling-alias-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-14
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                      S. Bortzmeyer
Internet-Draft                                                     AFNIC
Intended status: Informational                         November 14, 2016
Expires: May 18, 2017

        Signaling that a domain name is an alias of another one
              draft-bortzmeyer-bundled-signaling-alias-00

Abstract

   This document suggests a light-weight and semantics-free way to
   signal, in the DNS itself, that a domain name is actually an alias of
   another one (and therefore that they are member of the same bundle).

   REMOVE BEFORE PUBLICATION: this document should be discussed in the
   dnsbundled maiing list <https://www.ietf.org/mailman/listinfo/
   bundled-domain-names>.  The source of the document, as well as a list
   of open issues, is currently kept at Github [1].

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 May 18, 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
   (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.  Code Components extracted from this document must

Bortzmeyer                Expires May 18, 2017                  [Page 1]
Internet-Draft               Signaling alias               November 2016

   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.  Introduction and background . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The ALIAS RR type . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Reverse aliasing  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Deployability . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Implementation status - RFC EDITOR: REMOVE BEFORE PUBLICATION   5
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
     10.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  A TXT alternative to the new RR type . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction and background

   There are often requests that a domain name be regarded as a mere
   alias for another one, so it can be substituted by this another
   domain.  The reasons to do so are many
   [I-D.yao-bundled-name-problem-statement] and not discussed here.

   The problem is much more complicated than it seems and it is
   difficult to imagine a solution that will satisfy every use case.  We
   do not attempt to define such a solution.  Instead, we choose the
   path of least resistance and propose just to signal, in the DNS, this
   "aliasing" relationship.  This signaling is not accompanied by a
   specification of the semantics of this relationship, and this is a
   deliberate design decision.

   Existing solutions are insufficient: CNAMEs ([RFC1034], section
   3.6.2) only alias one domain name, not a subtree, and cannot be at
   the apex of a domain, where most people would want it (TODO
   Cloudflare article).  DNAMEs ([RFC6672]) alias a subtree but not the
   owner name, only its subdomains.  BNAMEs ([I-D.yao-dnsext-bname]) are
   not yet standardized and raise several issues (TODO describe).

Bortzmeyer                Expires May 18, 2017                  [Page 2]
Show full document text