Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify zero-length CIDs and active_connection_id_limit TP #3426

Merged
merged 7 commits into from May 17, 2020
12 changes: 7 additions & 5 deletions draft-ietf-quic-transport.md
Expand Up @@ -4697,11 +4697,13 @@ active_connection_id_limit (0x000e):
to store. This value includes the connection ID received during the handshake,
that received in the preferred_address transport parameter, and those received
in NEW_CONNECTION_ID frames.
Unless a zero-length connection ID is being used, the value of the
active_connection_id_limit parameter MUST be no less than 2. If this
transport parameter is absent, a default of 2 is assumed.
When a zero-length connection ID is being used, the active_connection_id_limit
parameter MUST NOT be sent.
The value of the active_connection_id_limit parameter MUST be at least 2.
nharper marked this conversation as resolved.
Show resolved Hide resolved
An endpoint that receives a value less than 2 MUST close the connection
with an error of type TRANSPORT_PARAMETER_ERROR.
If this transport parameter is absent, a default of 2 is assumed. If an
endpoint issues a zero-length connection ID, it will never send a
NEW_CONNECTION_ID frame and therefore ignores the active_connection_id_limit
value received from its peer.

martinthomson marked this conversation as resolved.
Show resolved Hide resolved
If present, transport parameters that set initial flow control limits
(initial_max_stream_data_bidi_local, initial_max_stream_data_bidi_remote, and
Expand Down