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

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

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
af69bf6
Allow Retry in response to 0-RTT packets
martinthomson Jul 12, 2018
452d1ee
ekr's inversion of the sentence
martinthomson Jul 14, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -594,7 +594,9 @@ of subsequent packets that it sends.
A Retry packet does not include a packet number and cannot be explictly
acknowledged by a client.

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.


If the Original Destination Connection ID field does not match the Destination
Connection ID from the most recent Initial packet it sent, clients MUST discard
Expand Down