Setting initial flow-control limits for individual stream types

[rzikm]

Describe the feature you'd like supported

We are considering exposing more QUIC configuration options from .NET side, and I notice that MsQuic exposes only one option for setting initial stream max_data (which applies to all 3 types). Was there a specific reason behind this choice?

We would like to expose limits for all three types (unidirectional, remotely/locally initiated bidirectional) limits to be in line with other QUIC implementations.

Proposed solution

Since there already is QUIC_SETTINGS.StreamRecvWindowDefault which covers all three stream types, the only proposal I came up with is adding the new values as separate options and have a precedence-fallback relationship between them. E.g. if QUIC_SETTINGS.UnidiStreamRecvWindowDefault is set, than it takes precedence over the potential value set in QUIC_SETTINGS.StreamRecvWindowDefault.

Additional context

If approved, I am willing to contribute the change. Just tell me upfront if you have preferences about option naming.

[nibanks]

We just never had any reason to expose them individually before. I'm curious if you have an actual ask from someone to do so?

[rzikm]

we don't have a request specifically for separate limits for individual stream types, but ASP.NET requested adding more connection options to allow them get HTTP/3 configuration more on par with HTTP/2.