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

Invariant nits #3772

Merged
merged 1 commit into from Jun 18, 2020
Merged

Invariant nits #3772

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-quic-invariants.md
View file
Open in desktop
Expand Up @@ -202,7 +202,7 @@ field and is between 0 and 255 bytes in length. Connection IDs are described in
{{connection-id}}.

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
that follows it. This length is encoded as an 8-bit unsigned integer. The
Source Connection ID field follows the Source Connection ID Length field and is
between 0 and 255 bytes in length.

Expand Down Expand Up @@ -295,8 +295,8 @@ contains no other fields. An endpoint MUST ignore a packet that contains no
Supported Version fields, or a truncated Supported Version.

Version Negotiation packets do not use integrity or confidentiality protection.
A specific QUIC version might authenticate the packet as part of its connection
establishment process.
Specific QUIC versions define mechanisms to authenticate the packet as part of
the connection establishment process.

An endpoint MUST include the value from the Source Connection ID field of the
packet it receives in the Destination Connection ID field. The value for Source
Expand Down Expand Up @@ -350,7 +350,7 @@ a new version is deployed.

This section lists a sampling of incorrect assumptions that might be made based
on knowledge of QUIC version 1. Some of these statements are not even true for
QUIC version 1. This is not an exhaustive list, it is intended to be
QUIC version 1. This is not an exhaustive list; it is intended to be
illustrative only.

The following statements are NOT guaranteed to be true for every QUIC version:
Expand Down