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

Allow Retry in response to 0-RTT packets #1552

Merged
merged 2 commits into from
Jul 31, 2018
Merged

Allow Retry in response to 0-RTT packets #1552

merged 2 commits into from
Jul 31, 2018

Conversation

martinthomson
Copy link
Member

Closes #1547.

(Note the target of this PR. This is blocked on #1498.)

@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Jul 12, 2018
A server MUST only send a Retry in response to a client Initial packet.
A server MUST NOT send a Retry in response to packets other than Initial
or 0-RTT packets. A server MAY discard 0-RTT packets and only send Retry in
response to Initial packets.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would invert this last sentence:

"A server MAY choose to send Retry in response to Initial packets and discard or buffer 0-RTT packets corresponding to unvalidated client addresses."

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, that it better. Thanks.

@martinthomson martinthomson changed the base branch from move-retry to master July 31, 2018 05:14
@martinthomson martinthomson merged commit 890bc01 into master Jul 31, 2018
@martinthomson martinthomson deleted the retry-0rtt branch July 31, 2018 05:14
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.

None yet

3 participants