W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

Re: Alt-SvcB

From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 26 Oct 2022 00:25:09 +0100
Message-ID: <CALGR9oaBx4qHKVJiEaE6uXF6e9=HVqt6ew+uu0_9CpgT9OmGDw@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Tommy Pauly <tpauly@apple.com>, Ian Swett <ianswett@google.com>, Martin Thomson <mt@lowentropy.net>, HTTP Working Group <ietf-http-wg@w3.org>
Hey,

On Wed, 26 Oct 2022, 00:21 David Schinazi, <dschinazi.ietf@gmail.com> wrote:

> h3 hints are a great example of something that needs to be added to
> Alt-Svc. It might be the last tweak we need, but it also might not.
> Deprecating it will get in our way if we find something that we do want to
> tweak later. What's the motivation for deprecating apart from preventing
> future work on it?
>

The thing is, the way Alt-Svc is designed is broken for some common types
of deployment. This isnt hypothetical, I see misdirected QUIC Initials due
to this design flaw every day. Adding h3 hints could make that problem even
more prevalent

We have a suitable replacement in HTTPS RR. The things we might like to add
to Alt-Svc, would require surgery and effort to fix it properly first.
That's effort we coild spend elsewhere, in order to adress some subset of
the client population. Can somebody quantify the relative proportion of
clients that can't do HTTPS RR?

Cheers
Lucas
Received on Tuesday, 25 October 2022 23:25:39 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 28 January 2023 21:29:46 UTC