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

Fixup old reference to 31-bit packet number #983

Merged
merged 1 commit into from
Dec 4, 2017
Merged

Fixup old reference to 31-bit packet number #983

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -574,9 +574,9 @@ unless it has received a packet from the server. If the client has received a
packet from the server, the connection ID field uses the value provided by the
server.

The first Initial packet that is sent by a client contains a random 31-bit
packet number. All subsequent packets contain a packet number that is
incremented by one, see ({{packet-numbers}}).
The first Initial packet that is sent by a client contains a randomized packet
number. All subsequent packets contain a packet number that is incremented by
one, see ({{packet-numbers}}).

The payload of a Initial packet consists of a STREAM frame (or frames)
for stream 0 containing a cryptographic handshake message, with enough PADDING
Expand Down