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

Editorial suggestions from Benjamin Kaduk (recovery) #4685

Merged
merged 16 commits into from Jan 13, 2021
Merged
9 changes: 5 additions & 4 deletions draft-ietf-quic-recovery.md
Expand Up @@ -130,10 +130,11 @@ In-flight packets:
All transmissions in QUIC are sent with a packet-level header, which indicates
the encryption level and includes a packet sequence number (referred to below as
a packet number). The encryption level indicates the packet number space, as
described in {{QUIC-TRANSPORT}}. Packet numbers never repeat within a packet
number space for the lifetime of a connection. Packet numbers are sent in
monotonically increasing order within a space, preventing ambiguity. It is
permitted for some packet numbers to never be used, leaving intentional gaps.
described in Section 12.3 in {{QUIC-TRANSPORT}}. Packet numbers never repeat
within a packet number space for the lifetime of a connection. Packet numbers
are sent in monotonically increasing order within a space, preventing ambiguity.
It is permitted for some packet numbers to never be used, leaving intentional
gaps.

This design obviates the need for disambiguating between transmissions and
retransmissions; this eliminates significant complexity from QUIC's
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.