CNAME at apex - a website publisher perspective
draft-york-dnsop-cname-at-apex-publisher-view-01

Document Type Active Internet-Draft (individual)
Last updated 2018-11-06
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)
DNSOP Working Group                                              D. York
Internet-Draft                                          Internet Society
Intended status: Informational                         November 06, 2018
Expires: May 10, 2019

            CNAME at apex - a website publisher perspective
            draft-york-dnsop-cname-at-apex-publisher-view-01

Abstract

   There has been a large amount of discussion about the "CNAME at apex"
   issue within the DNSOP Working Group.  This draft provides the
   perspective of one publisher of multiple websites about why CNAME-
   like functionality is desirable at the apex of a domain zone.

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 May 10, 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
   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.

York                      Expires May 10, 2019                  [Page 1]
Internet-DraftCNAME at apex - a website publisher perspectiNovember 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Challenge . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Note  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  CNAME works for subdomains  . . . . . . . . . . . . . . . . .   4
   4.  CNAME at apex does not work . . . . . . . . . . . . . . . . .   4
   5.  Proprietary solutions . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Proprietary lockin  . . . . . . . . . . . . . . . . . . .   4
     5.2.  Restriction on using multiple CDNs  . . . . . . . . . . .   5
   6.  Existing and proposed solutions . . . . . . . . . . . . . . .   5
   7.  Author opinion  . . . . . . . . . . . . . . . . . . . . . . .   5
   8.  Past discussion . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Conventions and Definitions . . . . . . . . . . . . . . . . .   6
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   6
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     12.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   From the early days of the Web, publishers of websites generally
   operated their main public website using the "www" subdomain, as in
   "www.example.com".

   In recent years many organizations have moved to dropping the "www"
   and referring to their main website by simply the domain name, as in
   "example.com".  There are numerous reasons for this change, including
   the simplicity of saying or writing the name and also smaller address
   bars on mobile browsers.  If you are designing a large advertisement
   to display in, say, an airport hallway, you can make the domain name
   address larger and more visibile if you simply use "example.com" and
   drop the "www".  Additionally, some web browsers are no longer
   showing the full URL (or even any of the URL) and so the "www" is no
   longer visible.

   Regardless of the reasons, the fact is that many website publishers
   and marketing/communications teams are moving to using only the
   domain name without the "www" or other subdomains to reference their
   public website.

   The expectations from the marketing / communications teams are that:

   1.  users will be able to simply enter "example.com" into their
       browser; and

York                      Expires May 10, 2019                  [Page 2]
Internet-DraftCNAME at apex - a website publisher perspectiNovember 2018
Show full document text