Address-specific DNS aliases (ANAME)
draft-ietf-dnsop-aname-02

Document Type Active Internet-Draft (dnsop WG)
Last updated 2018-10-19
Replaces draft-hunt-dnsop-aname
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
DNS Operations                                                  T. Finch
Internet-Draft                                   University of Cambridge
Intended status: Standards Track                                 E. Hunt
Expires: April 22, 2019                                              ISC
                                                             P. van Dijk
                                                                PowerDNS
                                                                 A. Eden
                                                                DNSimple
                                                        October 19, 2018

                  Address-specific DNS aliases (ANAME)
                       draft-ietf-dnsop-aname-02

Abstract

   This document defines the "ANAME" DNS RR type, to provide similar
   functionality to CNAME, but only for type A and AAAA queries.  Unlike
   CNAME, an ANAME can coexist with other record types.  The ANAME RR
   allows zone owners to make an apex domain name into an alias in a
   standards compliant manner.

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 April 22, 2019.

Copyright Notice

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

Finch, et al.            Expires April 22, 2019                 [Page 1]
Internet-Draft                    ANAME                     October 2018

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  The ANAME resource record . . . . . . . . . . . . . . . . . .   5
     2.1.  Presentation and wire format  . . . . . . . . . . . . . .   5
     2.2.  Coexistence with other types  . . . . . . . . . . . . . .   5
   3.  Additional section processing . . . . . . . . . . . . . . . .   5
     3.1.  Address queries . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  ANAME queries . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Substituting ANAME sibling address records  . . . . . . . . .   6
   5.  ANAME processing by primary masters . . . . . . . . . . . . .   7
     5.1.  Implications  . . . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Alternatives  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  ANAME processing by resolvers . . . . . . . . . . . . . . . .   9
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security considerations . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  12
   Appendix B.  Implementation status  . . . . . . . . . . . . . . .  12
   Appendix C.  Historical note  . . . . . . . . . . . . . . . . . .  12
   Appendix D.  On preserving TTLs . . . . . . . . . . . . . . . . .  13
     D.1.  Query bunching  . . . . . . . . . . . . . . . . . . . . .  14
     D.2.  Upstream caches . . . . . . . . . . . . . . . . . . . . .  14
     D.3.  ANAME chains  . . . . . . . . . . . . . . . . . . . . . .  15
     D.4.  TTLs and zone transfers . . . . . . . . . . . . . . . . .  15
   Appendix E.  Answer vs Additional sections  . . . . . . . . . . .  15
   Appendix F.  Changes since the last revision  . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   It can be desirable to provide web sites (and other services) at a
   bare domain name (such as "example.com") as well as a service-
Show full document text