search

ietf-wg-webtrans / draft-ietf-webtrans-http3

Internet Drafts for WebTransport
Other
40 stars 12 forks source link

Replace SETTINGS_ENABLE_WEBTRANSPORT with SETTINGS_WEBTRANSPORT_MAX_SESSIONS #129

Closed ekinnear closed 1 year ago

ekinnear commented 1 year ago

Replace SETTINGS_ENABLE_WEBTRANSPORT with SETTINGS_WEBTRANSPORT_MAX_SESSIONS

Fixes #125

vasilvv commented 1 year ago

I don't believe this addresses the main reason we've not done this yet, which is the fact that SETTINGS_WEBTRANSPORT_MAX_SESSIONS is only sent from the server to the client, making it not particularly useful for version negotiation.

ekinnear commented 1 year ago

SETTINGS_WEBTRANSPORT_MAX_SESSIONS is only sent from the server to the client, making it not particularly useful for version negotiation.

The intent was that this is rectified by the new text in this PR, if that doesn't seem to be the case, then let's fix it!

For example:

When an HTTP/3 connection is established, both the client and server have to
send a SETTINGS_WEBTRANSPORT_MAX_SESSIONS setting in order to indicate that
they both support WebTransport over HTTP/3.
DavidSchinazi commented 1 year ago

Long term, once this has shipped as RFC and all browsers have dropped support for pre-RFC drafts, is the plan to have clients send SETTINGS_WEBTRANSPORT_MAX_SESSIONS forever or to stop sending it? If the goal is to only do this during the draft period, we should have "to be removed by RFC editor" notes explaining that

ekinnear commented 1 year ago

Long term, once this has shipped as RFC and all browsers have dropped support for pre-RFC drafts, is the plan to have clients send SETTINGS_WEBTRANSPORT_MAX_SESSIONS forever or to stop sending it? If the goal is to only do this during the draft period, we should have "to be removed by RFC editor" notes explaining that

Filed #130 to discuss this

ekinnear commented 1 year ago

Discussed in editor's meeting, moved follow-ups out to an issue and merging.