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

Why grease #4341

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
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
8 changes: 6 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -4327,7 +4327,9 @@ reserved for use in future IETF consensus documents.
Versions that follow the pattern 0x?a?a?a?a are reserved for use in forcing
version negotiation to be exercised. That is, any version number where the low
four bits of all bytes is 1010 (in binary). A client or server MAY advertise
support for any of these reserved versions.
support for any of these reserved versions. These values are allocated sparsely
across the entire version number space to discourage endpoint implementations
from conditioning on them.

Reserved version numbers will never represent a real protocol; a client MAY use
one of these version numbers with the expectation that the server will initiate
Expand Down Expand Up @@ -5113,7 +5115,9 @@ included in the cryptographic handshake.
Transport parameters with an identifier of the form `31 * N + 27` for integer
values of N are reserved to exercise the requirement that unknown transport
parameters be ignored. These transport parameters have no semantics, and may
carry arbitrary values.
carry arbitrary values. These values are allocated sparsely across the entire
identifier space to discourage endpoint implementations from conditioning on
them.


## Transport Parameter Definitions {#transport-parameter-definitions}
Expand Down