[DNSOP] SVCB and HTTPSSVC records: draft-nygren-dnsop-svcb-httpssvc-00

Erik Nygren <erik+ietf@nygren.org> Tue, 24 September 2019 13:18 UTC

Return-Path: <nygren@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 1CD4B1201EA for <dnsop@ietfa.amsl.com>; Tue, 24 Sep 2019 06:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.026, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uQyXzij6nUBn for <dnsop@ietfa.amsl.com>; Tue, 24 Sep 2019 06:18:13 -0700 (PDT)
Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01A8112003E for <dnsop@ietf.org>; Tue, 24 Sep 2019 06:18:12 -0700 (PDT)
Received: by mail-wr1-f65.google.com with SMTP id y19so1917883wrd.3 for <dnsop@ietf.org>; Tue, 24 Sep 2019 06:18:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=5ljgqy+3drWActJpfZ+dKUPBWpAgZd0tamYWDpRWZBc=; b=InGlTpFydqDTE/LPVdkan3uSIl58GYR8bcmWKHnjmNn4MLG6xwhS6xM4BWSU1/y08R bi9Abh8yyBoP8h1tJ3I/v8pW9/PvIeD86AnJmWqHHNLSvr4cPlvoyidq6QlJr2cguhJB zKQVXqA97C+424O9PErl+CLM2d0B2rAs2SyL5WjH1y7P+eJauKwQJWXr/7uX+2HThX7/ +vmiIZdlywezJgsuqUzoGxb4KTArrxOg08DTobvx0ygIBVDKzqn4I7Sbe8Obt1htsNCk NiekFYAwRnYW5+YCW+5Fb4msuB+UMRoOVIRKcRqhA1IpUtiikYi5i/fHwDqicqdZ7bwq sljw==
X-Gm-Message-State: APjAAAXwWY9IHmsMffBpZ2taD/sJ/6UKcf7+poPW12aiiNUN9UtUgPuI LzVtDq9+a5QY7DQiFNBQShskc08q2ivqQPA5ulmZh65P
X-Google-Smtp-Source: APXvYqxyw4eyscEKfZmku3XfYrnEQ5YXlGtoAKsoxkIjirspImUU2HgjSZG5V8czDwUB0Xx5cQGTL5SiVsYcu+oYX4M=
X-Received: by 2002:a5d:42cb:: with SMTP id t11mr2154387wrr.99.1569331091012; Tue, 24 Sep 2019 06:18:11 -0700 (PDT)
MIME-Version: 1.0
References: <156927967091.17209.1946223190141713793.idtracker@ietfa.amsl.com>
In-Reply-To: <156927967091.17209.1946223190141713793.idtracker@ietfa.amsl.com>
From: Erik Nygren <erik+ietf@nygren.org>
Date: Tue, 24 Sep 2019 09:17:59 -0400
Message-ID: <CAKC-DJi4EHz5CCAqRj_cYTVygiuo0s2QGaPLCct6e9Bh1mXaXQ@mail.gmail.com>
To: dnsop WG <dnsop@ietf.org>, Ben Schwartz <bemasc@google.com>, Mike Bishop <mbishop@evequefou.be>
Content-Type: multipart/alternative; boundary="0000000000003702b405934c5ed9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rF7zcVGEpZqP9h0zHC4TG_-OqKc>
Subject: [DNSOP] SVCB and HTTPSSVC records: draft-nygren-dnsop-svcb-httpssvc-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2019 13:18:16 -0000

Following discussions around the "HTTPSSVC" record proposal in Montreal
with the DNSOP, HTTP and TLS WGs, we've updated what was previously
"draft-nygren-httpbis-httpssvc-03".  The new version is
"draft-nygren-dnsop-svcb-httpssvc-00".   This incorporates much of the
feedback from the WG discussions, as well as feedback from discussions with
the TLS WG (as we'd like to see this replace the need for a separate ESNI

In particular, it generalizes the record into a new "SVCB" record which
doesn't have any protocol-specific semantics.  It also defines an
"HTTPSSVC" record that is compatible with SVCB (sharing a wire-format and
parameter registry) and which defines the HTTP(S)-specific semantics such
as bindings to Alt-Svc.  Other protocols can either define bindings
directly to SVCB or can define their own RR Type (which should only ever be
needed if there is a need to use the record at a zone apex).

We'd like to see this adopted by the DNSOP WG.  Until then, issues and PRs
can go against:  https://github.com/MikeBishop/dns-alt-svc

Major changes from "draft-nygren-httpbis-httpssvc-03" include:

* Separation into the SVCB and HTTPSSVC RR Types  (and separated all of the
HTTPS-specific functionality and text to its own portion of the document).
* Elimination of the SvcRecordType field (and making the SvcRecordType
* Changing the wire format of parameters from being in Alt-Svc text format
to a more general binary key/value pair format (with a mapping to Alt-Svc
* Adding optional "ipv4hint" and "ipv6hint" parameters.
* Quite a few cleanups and clarifications based on input (and we
undoubtedly have more left to go)

This retains support for all of the use-cases that the previous HTTPSSVC
record had (such as for covering the ANAME / CNAME-at-the-zone-apex

Feedback is most welcome.  If the TLS WG is going to use this instead of a
separate ESNI record, there is a desire to make progress on this fairy


---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Sep 23, 2019 at 7:01 PM
Subject: New Version Notification for
To: Mike Bishop <mbishop@evequefou.be>be>, Erik Nygren <erik+ietf@nygren.org>rg>,
Benjamin Schwartz <bemasc@google.com>

A new version of I-D, draft-nygren-dnsop-svcb-httpssvc-00.txt
has been successfully submitted by Benjamin Schwartz and posted to the
IETF repository.

Name:           draft-nygren-dnsop-svcb-httpssvc
Revision:       00
Title:          Service binding and parameter specification via the DNS
Document date:  2019-09-22
Group:          Individual Submission
Pages:          33

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

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat