Invisible Canonical Name Implementation
draft-yaoyuan-dnsext-idr-adr-00

Document Type Active Internet-Draft (individual)
Last updated 2020-04-17
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Infrastructure System Engineering Group                          Y. Chen
Internet-Draft                                                     Baidu
Intended status: Informational                            April 17, 2020
Expires: October 17, 2020

               Invisible Canonical Name Implementation
                   draft-yaoyuan-dnsext-idr-adr-00

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as 
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on October 17, 2020.

Copyright Notice

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

Chen                  Expires October 17, 2020                  [Page 1]
Internet-Draft    Invisible Canonical Name Implementation     April 2020

Abstract

   To accomplish the goal that not exposing redundant and unuseful CNAME
   chains in answers responded to clients, this document describes two
   new DNS resource records called "IDR" and "ADR" for hiding CNAME
   iterative process and better safety consideration.

1.  Introduction

   The CNAME record presented in [RFC1034] and [RFC1035] nowadays is
   widely used to complete different functions. Simultaneously the
   record begins to show signs of weakness when helping engineers solve
   complex technical problems during increasingly complicated network
   environment. There are three fundamental flaws about CNAME and a
   scene which it cannot fit in:

      o Unnecessary and massive consumption of network bandwidth in
        traffic between clients and name resolvers if a chain with
        multi-CNAMEs is contained in answer section. Actually these
        CNAMEs are useless at all for clients.

      o The abuse of canonical names without authentication. Today we
        can easily configure a name redirected to a famous website
        without getting permission of the owner. Although website users
        with dns knowledge finally will know it is an alias after
        looking through the resolving process (someone not) and resource
        servers may take some security defence to deny illegal access,
        it still cause a tort about private intellectual property of
        real service providers. Maybe we can take some measures in dns
        layer.

      o CNAME chains in authoritative name servers MAY cause dns
        hijacking. As a name server will continue to find answers in
        internal cache, the upper servers could give answers those not
        equal to the real authoritative servers without validation.

      o In certain special circumstances or requirements, services
        providers closest to users side are not willing to present the
        intermediate process of the CNAMEs to customers. Certainly they
        MUST ask for permission of the original content administrators
        at first.

   To solve the above problems, we define two new DNS Resource Records
   with some extensions to current DNS rules.The changes are designed to
   be compatible with existing software. The existing support for CNAME
   and DNAME[RFC2672] is retained.

Chen                  Expires October 17, 2020                  [Page 2]
Internet-Draft    Invisible Canonical Name Implementation     April 2020

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, [RFC2119].

3.  The "IDR" and "ADR" Resource Record
  
   IDR means "Invisible Direct Reference", it looks like a transparent
   agent who borrows resource records from others. The users cannot feel
   the agency process in detail. IDR means "Allow Direct Reference",
Show full document text