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

Version Negotiation doesn't have a packet number #1078

Merged
merged 2 commits into from Jan 30, 2018
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions draft-ietf-quic-transport.md
Expand Up @@ -2376,11 +2376,11 @@ Unlike TCP SACKs, QUIC acknowledgements are irrevocable. Once a packet has
been acknowledged, even if it does not appear in a future ACK frame,
it remains acknowledged.

A client MUST NOT acknowledge Version Negotiation or Retry packets. Version
Negotiation packets don't contain a packet number and Retry packets include the
packet number from the Initial packet it responds to. Rather than relying on
ACK frames, these packets are implicitly acknowledged by the next Initial packet
sent by the client.
A client MUST NOT acknowledge Retry packets. Retry packets include the packet
number from the Initial packet it responds to. Version Negotiation packets
cannot be acknowledged because they do not contain a packet number. Rather than
relying on ACK frames, these packets are implicitly acknowledged by the next
Initial packet sent by the client.

A sender MAY intentionally skip packet numbers to introduce entropy into the
connection, to avoid opportunistic acknowledgement attacks. The sender SHOULD
Expand Down