Service binding and parameter specification via the DNS (DNS SVCB and HTTPSSVC)
draft-ietf-dnsop-svcb-httpssvc-01

Document Type Active Internet-Draft (dnsop WG)
Last updated 2019-11-04
Replaces draft-nygren-dnsop-svcb-httpssvc
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
On Agenda dnsop at IETF-106
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DNSOP Working Group                                          B. Schwartz
Internet-Draft                                                    Google
Intended status: Standards Track                               M. Bishop
Expires: May 7, 2020                                           E. Nygren
                                                     Akamai Technologies
                                                        November 4, 2019

 Service binding and parameter specification via the DNS (DNS SVCB and
                               HTTPSSVC)
                   draft-ietf-dnsop-svcb-httpssvc-01

Abstract

   This document specifies the "SVCB" and "HTTPSSVC" DNS resource record
   types to facilitate the lookup of information needed to make
   connections for origin resources, such as for HTTPS URLs.  SVCB
   records allow an origin to be served from multiple network locations,
   each with associated parameters (such as transport protocol
   configuration and keying material for encrypting TLS SNI).  They also
   enable aliasing of apex domains, which is not possible with CNAME.
   The HTTPSSVC DNS RR is a variation of SVCB for HTTPS and HTTP
   origins.  By providing more information to the client before it
   attempts to establish a connection, these records offer potential
   benefits to both performance and privacy.

   TO BE REMOVED: This proposal is inspired by and based on recent DNS
   usage proposals such as ALTSVC, ANAME, and ESNIKEYS (as well as long
   standing desires to have SRV or a functional equivalent implemented
   for HTTP).  These proposals each provide an important function but
   are potentially incompatible with each other, such as when an origin
   is load-balanced across multiple hosting providers (multi-CDN).
   Furthermore, these each add potential cases for adding additional
   record lookups in-addition to AAAA/A lookups.  This design attempts
   to provide a unified framework that encompasses the key functionality
   of these proposals, as well as providing some extensibility for
   addressing similar future challenges.

   TO BE REMOVED: The specific name for this RR type is an open topic
   for discussion.  "SVCB" and "HTTPSSVC" are meant as placeholders as
   they are easy to replace.  Other names might include "B", "SRV2",
   "SVCHTTPS", "HTTPS", and "ALTSVC".

Status of This Memo

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

Schwartz, et al.           Expires May 7, 2020                  [Page 1]
Internet-Draft        SVCB and HTTPSSVC RRs for DNS        November 2019

   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 7, 2020.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Introductory Example  . . . . . . . . . . . . . . . . . .   5
     1.2.  Goals of the SVCB RR  . . . . . . . . . . . . . . . . . .   6
     1.3.  Overview of the SVCB RR . . . . . . . . . . . . . . . . .   7
     1.4.  Parameter for ESNI  . . . . . . . . . . . . . . . . . . .   8
     1.5.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   8
   2.  The SVCB record type  . . . . . . . . . . . . . . . . . . . .   8
     2.1.  Parameter specification via ServiceFieldValue . . . . . .   9
       2.1.1.  Presentation format . . . . . . . . . . . . . . . . .   9
     2.2.  SVCB RDATA Wire Format  . . . . . . . . . . . . . . . . .  10
     2.3.  SVCB owner names  . . . . . . . . . . . . . . . . . . . .  10
     2.4.  SvcRecordType . . . . . . . . . . . . . . . . . . . . . .  11
     2.5.  SVCB records: AliasForm . . . . . . . . . . . . . . . . .  11
     2.6.  SVCB records: ServiceForm . . . . . . . . . . . . . . . .  12
       2.6.1.  Special handling of "." for SvcDomainName in
Show full document text