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.

Sign up for GitHub

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

Jump to bottom

#3348 Clarify that you can use any issued CID at any time, even during the handshake #3438

Merged
merged 2 commits into from Feb 11, 2020
Merged

#3348 Clarify that you can use any issued CID at any time, even during the handshake #3438

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
059773c
Clarify that you can use any issued CID at any time, even during the …
ekinnear Feb 6, 2020
8e532b0
Note that CIDs are valid in any packet type
ekinnear Feb 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 3 additions & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1002,7 +1002,9 @@ When an endpoint issues a connection ID, it MUST accept packets that carry this
connection ID for the duration of the connection or until its peer invalidates
the connection ID via a RETIRE_CONNECTION_ID frame
({{frame-retire-connection-id}}). Connection IDs that are issued and not
retired are considered active; any active connection ID can be used.
retired are considered active; any active connection ID is valid for use at any
time, in any packet type. This includes the connection ID issued by the server
via the preferred_address transport parameter.

An endpoint SHOULD ensure that its peer has a sufficient number of available and
unused connection IDs. Endpoints store received connection IDs for future use
Expand Down