s2n-quic
s2n-quic copied to clipboard
Decide how to handle peer-provided active_connection_id_limit transport param Limit
Pr https://github.com/awslabs/s2n-quic/pull/1043 adds the active_connection_id_limit transport param to the ClientHello.
This value was previously loaded from the peer-provided Limits: https://github.com/awslabs/s2n-quic/blob/main/quic/s2n-quic-core/src/transport/parameters/mod.rs#L1343. However the peer-provided limits also doesnt make sense since the value in the peer_id_registry is hardcoded to 3
Determine:
- should the peer-provided active_connection_id_limit or the hardcoded value be used for the transport param
- what value should be used for peer_id_registry
- if unused, should active_connection_id_limit be removed from
Limits