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

Note that state needs to be maintained for each issued CID if the peer chooses to use it #3557

Merged
merged 2 commits into from
Apr 20, 2020

Conversation

erickinnear
Copy link
Contributor

Add another note when cautioning endpoints about how many CIDs to issue: in this case to note that if you issue a CID you need to be willing for the other endpoint to use 100% of the issued CIDs, which comes with an implicit willingness to maintain state for each path on which that CID could be used. (That's one per path, but # paths == # CIDs in the worst case.)

Fixes #3489.

@erickinnear erickinnear changed the title Note that state probably needs to be maintained for each issued CID if the peer chooses to use it Note that state needs to be maintained for each issued CID if the peer chooses to use it Mar 30, 2020
@ianswett
Copy link
Contributor

This adds a MAY and the issue is already marked design, so I'm inclined to mark this design and do a consensus call on the issue with the next batch.

@erickinnear
Copy link
Contributor Author

We could also leave this as might choose, which seems completely reasonable as well. The only reason I went for MAY was because the previous sentence is the same level of advisory and we also used MAY there.

@ianswett
Copy link
Contributor

@erickinnear I'd prefer you keep it as is. The process isn't going to cause an appreciable delay in this case.

@ianswett ianswett requested a review from kazuho March 30, 2020 18:13
@ianswett ianswett added the design An issue that affects the design of the protocol; resolution requires consensus. label Mar 31, 2020
Co-Authored-By: Mike Bishop <mbishop@evequefou.be>
@martinthomson martinthomson merged commit db65357 into quicwg:master Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How many probed paths should a server remember?
7 participants