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

Suggestion that Retry might not change CID #2465

Closed
MikeBishop opened this issue Feb 14, 2019 · 1 comment
Closed

Suggestion that Retry might not change CID #2465

MikeBishop opened this issue Feb 14, 2019 · 1 comment
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@MikeBishop
Copy link
Contributor

In 17.2.3, the transport draft says:

Receiving a Retry packet, especially a Retry that changes the connection ID used for subsequent packets, indicates a strong possibility that 0-RTT packets could be lost.

However, in 17.2.5:

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.

The subordinate clause in the first is unnecessary, as that statement is true of all Retry packets. In the second, should that be "MUST NOT" rather than "MUST not"?
@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels Feb 14, 2019
@martinthomson
Copy link
Member

OBE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @MikeBishop