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

Packet number encoding appendix #4315

Merged
merged 7 commits into from Nov 3, 2020
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -7411,7 +7411,7 @@ The EncodePacketNumber function takes two arguments:

* full_pn is the full packet number of the packet being sent.
* largest_acked is the largest packet number which has been acknowledged by the
MikeBishop marked this conversation as resolved.
Show resolved Hide resolved
recipient in the current packet number space, if any
peer in the current packet number space, if any
martinthomson marked this conversation as resolved.
Show resolved Hide resolved

~~~
EncodePacketNumber(full_pn, largest_acked):
Expand All @@ -7433,7 +7433,7 @@ EncodePacketNumber(full_pn, largest_acked):
For example, if an endpoint has received an acknowledgment for packet 0xabe8bc
and is sending a packet with a number of 0xac5c02, there are 29,519 (0x734f)
outstanding packets. In order to represent at least twice this range (59,038
packets, or 0xe69e), 16 bits will be required.
packets, or 0xe69e), 16 bits are required.

In the same state, sending a packet with a number of 0xace8fe uses the 24-bit
encoding, because at least 18 bits are required to represent twice the range
Expand Down