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

Which/how many unused CIDs SHOULD be provided? #333

Closed
mirjak opened this issue May 14, 2024 · 2 comments
Closed

Which/how many unused CIDs SHOULD be provided? #333

mirjak opened this issue May 14, 2024 · 2 comments
Labels
design duplicate This issue or pull request already exists explicit path ID

Comments

@mirjak
Copy link
Collaborator

mirjak commented May 14, 2024

In section https://quicwg.org/multipath/draft-ietf-quic-multipath.html#name-allocating-consuming-and-re we currently say:

"Endpoints SHOULD issue at least one unused connection ID with unused Path Identifier."

I don't think we can or should require to provide one unused Path ID. Instead this sentence originally intended to say that one unused CID should be provide to enable migration. As such this sentence should say:

"Endpoints SHOULD issue at least one unused connection ID with for each active path."

@mirjak mirjak added the design label May 14, 2024
@mirjak
Copy link
Collaborator Author

mirjak commented May 14, 2024

Further the text says the following:

When there is not enough unused Path Identifiers, endpoints SHOULD
send MAX_PATHS frame to inform the peer that new Path Identifiers are available.

However, it is fully unclear what "not enough" means. I therefore propose to remove this sentence.

@mirjak mirjak added explicit path ID duplicate This issue or pull request already exists labels May 24, 2024
@mirjak
Copy link
Collaborator Author

mirjak commented May 29, 2024

Continue discussion in #338

@mirjak mirjak closed this as completed May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design duplicate This issue or pull request already exists explicit path ID
Projects
None yet
Development

No branches or pull requests

1 participant