search

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

Internet Drafts for WebTransport
Other
40 stars 12 forks source link

Negotiation of flow control #150

Open DavidSchinazi opened 6 months ago

DavidSchinazi commented 6 months ago

As mentioned by @marten-seemann on the list, making flow control optional requires the ability to negotiate it. We should add that to the protocol, using HTTP headers or SETTINGS.

martinthomson commented 3 months ago

My preference is to make it non-optional. Negotiation is - at least in engineering time for our implementation - roughly equivalent in expense to adding some more flow control. As a browser, of course, we're probably on the hook to implement anyway.

ekinnear commented 3 months ago

Discussed in editor's meeting: Flip back the other way and have the client send MAX_SESSIONS, if either end is >1 Flow Control is happening, if either side is just 1, no flow control, if 0, no WT.

ekinnear commented 3 months ago

(Can locally set the limits really high when you see 1 from the other side, which causes you to ignore all other frames)

afrind commented 3 months ago

How does adding the ability to negotiate flow control-off in some cases help?