Re: [quicwg/base-drafts] Static table negotiation (#1343)

[Lucas Pardue <[e-mail]>]

To expand on Mike's comment after thinking further, the quirk of Alt-Svc also becomes that it effectively defines a host-level static table rather than a connection-one. This introduces some weird (although perhaps not undesirable) synergies between QUIC session resumption and Alt-Svc freshness i.e a client that accepts an alternative as valid could continue to use it's static table across different QUIC connections to the same host.

Thinking about the negotiation more generally. The proposals are connection-level. There is potential merit in an ability for different API endpoints to have different table contexts, however differentiating endpoints by URL path is not presently possible. And to take this concept further, you could imagine some benefit (in a multipath world) of different paths having different table contexts. However, this could all be TFH, with questionable real world benefit.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1343#issuecomment-388255397