Re: Alt-Svc interaction with HTTPS/SVCB DNS records

I think that it would be helpful to write a page or two about the motivation and rationale behind the decision.  That text is quite dense and not at all clear.  An explanation of how the pieces fit together at a high level and the consequences of that for the design of the protocol (and it's impact on how people configure servers or build clients) would be very helpful.

On Fri, Jun 18, 2021, at 09:00, Erik Nygren wrote:
> The HTTPS/SVCB DNS record draft past WGLC in DNSOP.
> There has been a bunch of discussion in this pull-request recently
> on improving the interaction between Alt-Svc and HTTPS RRs.
> Much of the discussion is here:
> 
>    https://github.com/MikeBishop/dns-alt-svc/pull/329/files
> 
> Most of the resulting text is now in -06 in Section 8.3:
> 
>    
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-06#section-8.3
> 
> Given how this is at the borderline of HTTP Alt-Svc and DNS,
> we had a discussion in the Interim today that this could use
> more visibility from the HTTP WG.  
> 
> More broadly, while it hasn't changed recently, Section 6.1
> (for "alpn" SvcParam handling) takes into account some experience
> from clients with challenges with ALPN handling with Alt-Svc
> and some of the proposed text in it may want to be included
> in an Alt-Svc-bis:
> 
>    
> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-06#section-6.1
> 
> The chairs are discussing whether we may want to have a call on this,
> but in the meantime feedback and comments are most welcome.
> 
>       Erik
> 
> 
> 
>

Received on Thursday, 17 June 2021 23:17:25 UTC