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

ACK frames PN space editorial #3313

Merged
merged 7 commits into from
Jan 8, 2020
Merged

ACK frames PN space editorial #3313

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
84a3a43
ACK frames PN space editorial
ianswett Dec 30, 2019
8cc7826
Update draft-ietf-quic-transport.md
ianswett Dec 30, 2019
a925d9c
Update draft-ietf-quic-transport.md
ianswett Jan 2, 2020
73b9b04
Martin's suggestion
ianswett Jan 2, 2020
6be2552
Update draft-ietf-quic-transport.md
janaiyengar Jan 7, 2020
a570bfb
ekr's suggestion
janaiyengar Jan 7, 2020
5fe4a8f
Update draft-ietf-quic-transport.md
janaiyengar Jan 7, 2020
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
9 changes: 5 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4747,10 +4747,11 @@ QUIC acknowledgements are irrevocable. Once acknowledged, a packet remains
acknowledged, even if it does not appear in a future ACK frame. This is unlike
TCP SACKs ({{?RFC2018}}).

It is expected that a sender will reuse the same packet number across different
packet number spaces. ACK frames only acknowledge the packet numbers that were
transmitted by the sender in the same packet number space of the packet that the
ACK was received in.
Packets from different packet number spaces can be identified using the same
numeric value. An acknowledgment for a packet needs to indicate both a packet
number and a packet number space. This is accomplished by having each ACK frame
only acknowledge packet numbers in the same space as the packet in which the
ACK frame is contained.

Version Negotiation and Retry packets cannot be acknowledged because they do not
contain a packet number. Rather than relying on ACK frames, these packets are
Expand Down