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 fix for #2479 #2877

Merged
merged 8 commits into from
Jul 9, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
24 changes: 9 additions & 15 deletions draft-ietf-quic-invariants.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,21 +161,15 @@ All other bits in that byte are version specific.

The next four bytes include a 32-bit Version field (see {{version}}).

The next byte contains the length in bytes of the two Connection IDs (see
{{connection-id}}) that follow. Each length is encoded as a 4-bit unsigned
integer. The length of the Destination Connection ID (DCIL) occupies the high
bits of the byte and the length of the Source Connection ID (SCIL) occupies the
low bits of the byte. An encoded length of 0 indicates that the connection ID
is also 0 bytes in length. Non-zero encoded lengths are increased by 3 to get
the full length of the connection ID; the final value is therefore either 0 or
between 4 and 18 bytes in length (inclusive). For example, a byte with the
value 0xe0 describes a 17 byte Destination Connection ID and a zero byte Source
Connection ID.

The connection ID lengths are followed by two connection IDs. The connection
ID associated with the recipient of the packet (the Destination Connection ID)
is followed by the connection ID associated with the sender of the packet (the
Source Connection ID).
The next byte contains the length in bytes of the Destination Connection ID (see
{{connection-id}}) field that follows it. This length is encoded as an 8-bit
unsigned integer. The Destination Connection ID field follows the DCID Len
field and is between 0 and 255 bytes in length.

The next byte contains the length in bytes
of the Source Connection ID field that follows it. This length is encoded as
a 8-bit unsigned integer. The Source Connection ID field follows the SCID Len
field and is between 0 and 255 bytes in length.

The remainder of the packet contains version-specific content.

Expand Down
17 changes: 7 additions & 10 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -3503,16 +3503,13 @@ Version:

DCID Len:

: The byte following the version contains the lengths of the two connection ID
fields that follow it. These lengths are encoded as two 4-bit unsigned
integers. The Destination Connection ID Length (DCIL) field occupies the 4
high bits of the byte and the Source Connection ID Length (SCIL) field
occupies the 4 low bits of the byte. An encoded length of 0 indicates that
the connection ID is also 0 bytes in length. Non-zero encoded lengths are
increased by 3 to get the full length of the connection ID, producing a length
between 4 and 18 bytes inclusive. For example, a byte with the value 0x50
describes an 8-byte Destination Connection ID and a zero-length Source
Connection ID.
: The byte following the version contains the length in bytes of the Destination
Connection ID field that follows it. This length is encoded as an 8-bit
unsigned integer. In QUIC version 1, this value MUST NOT exceed 20.
Endpoints that receive a version 1 long header with a value larger than
20 MUST drop the packet. Servers SHOULD be able to read longer connection IDs
from other QUIC versions in order to properly form a version negotiation
packet.

Destination Connection ID:

Expand Down