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

Keep the packet number after Retry #2182

Closed
wants to merge 1 commit into from
Closed

Keep the packet number after Retry #2182

wants to merge 1 commit into from

Conversation

martinthomson
Copy link
Member

Closes #2179.

@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Dec 14, 2018
@marten-seemann
Copy link
Contributor

This seems unnecessarily complex. Why don’t we just require the server to generate a new connection ID for a Retry, and then just start at packet number 0 again?

@martinthomson
Copy link
Member Author

Oh, stupid me....

The server includes a connection ID of its choice in the Source Connection ID field. This value MUST not be equal to the Destination Connection ID field of the packet sent by the client.

@martinthomson martinthomson deleted the increase-pn-retry branch December 17, 2018 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@martinthomson @marten-seemann