Re: [DNSOP] I-D Action: draft-ietf-dnsop-svcb-https-01.txt

[Ben Schwartz <[e-mail]>]

I wanted to highlight some changes since the previous version, for folks
who don't want to try to parse the diff:

Substantive:
*  Added a "mandatory" SvcParamKey. The "mandatory" key allows the
publisher to indicate that some extensions can't be ignored.  If the client
gets a record with an unrecognized extension that is marked as mandatory,
it ignores the whole record.  This will allow publishers to selectively
break backwards compatibility, on a per-endpoint basis.

*  Adjusted resolution and ALPN algorithms.  The descriptions of the SVCB
client, recursive resolver, and TLS client behavior have all been improved
based on expert input.

*  Added the ability to indicate that a service does not exist.  Based on a
suggestion from Mark Andrews, we incorporated the ability to publish a
record indicating that the requested service is not available or does not
exist, paralleling several existing RR types.

Editorial:
*  Major terminology revisions:
"origin" -> "service" and other changes to align with URI terminology
instead of appropriating HTTP terminology
SvcDomainName -> TargetName, SvcFieldValue -> SvcParams, AliasForm ->
AliasMode, and other changes to the CamelCase names.

*  Revised ABNF description for precision and alignment with implementations

On Mon, Jul 13, 2020 at 4:36 PM <[e-mail]> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations WG of the
> IETF.
>
>         Title           : Service binding and parameter specification via
> the DNS (DNS SVCB and HTTPS RRs)
>         Authors         : Ben Schwartz
>                           Mike Bishop
>                           Erik Nygren
>         Filename        : draft-ietf-dnsop-svcb-https-01.txt
>         Pages           : 42
>         Date            : 2020-07-13
>
> Abstract:
>    This document specifies the "SVCB" and "HTTPS" DNS resource record
>    (RR) types to facilitate the lookup of information needed to make
>    connections to network services, such as for HTTPS origins.  SVCB
>    records allow a service to be provided from multiple alternative
>    endpoints, each with associated parameters (such as transport
>    protocol configuration and keys for encrypting the TLS ClientHello).
>    They also enable aliasing of apex domains, which is not possible with
>    CNAME.  The HTTPS 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: This document is being collaborated on in Github at:
>    https://github.com/MikeBishop/dns-alt-svc [1].  The most recent
>    working version of the document, open issues, etc. should all be
>    available there.  The authors (gratefully) accept pull requests.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dnsop-svcb-https-01
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-01
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-svcb-https-01
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> _______________________________________________
> DNSOP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dnsop
>