title

draft-ietf-dnsop-svcb-https-00

charset

utf-8

X-UA-Compatible

IE=edge

viewport

width=device-width, initial-scale=1

description

Service binding and parameter specification via the DNS (DNS SVCB and HTTPS RRs) (Internet-Draft, 2020)

og:title

Service binding and parameter specification via the DNS (DNS SVCB and HTTPS RRs)

og:url

https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-00

og:site_name

IETF Datatracker

og:description

This document specifies the "SVCB" and "HTTPS" DNS resource record (RR) 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 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.

og:type

article

twitter:card

summary_large_image

alternate

/feed/document-changes/draft-ietf-dnsop-svcb-https/

apple-touch-icon

https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png

canonical

https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-00

icon

https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png

icon

https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png