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

A zero-length connection ID is always good #4335

Merged
merged 2 commits into from Nov 10, 2020
Merged

A zero-length connection ID is always good #4335

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bce5cb2
A zero-length connection ID is always good
martinthomson Nov 5, 2020
4b93601
issuance, for all paths or any path
martinthomson Nov 9, 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
5 changes: 5 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1163,6 +1163,11 @@ SHOULD ensure that the pool of connection IDs available to its peer allows the
peer to use a new connection ID on migration, as the peer will be unable to
respond if the pool is exhausted.

An endpoint that selects a zero-length connection ID during the handshake
cannot issue a new connection ID. A zero-length Destination Connection ID
field is used in all packets sent toward such an endpoint over any network
path.
Copy link
Contributor

@mirjak mirjak Dec 1, 2020 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I know this has been merged already but I thought this is easier than open a new issue.

How can you use a connection with zero-length Conn ID over different paths? Doesn't an address change without Conn ID mean that the connections breaks?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The peer could still change its address, right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you have changed the address and don't have a conn ID, you cannot associate the packet to an existing connection anymore, no?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see your point. You can still associate it in theory, though it might be fragile - this is left to the implementation ultimately. I agree with you that the "over any network path" is mostly redundant, but I am not sure that it hurts because I don't think it suggests something that is impossible.



### Consuming and Retiring Connection IDs {#retire-cid}

Expand Down