Skip to content

Add more considerations around greasing version negotiation #59

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

Merged
tfpauly merged 3 commits into from
Mar 2, 2026
Merged

Add more considerations around greasing version negotiation #59

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3d54208
Add more considerations around greasing version negotiation
dthaler Feb 27, 2026
740c941
Update draft-iab-protocol-greasing.md
dthaler Feb 28, 2026
6dae545
Update draft-iab-protocol-greasing.md
dthaler Feb 28, 2026
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
11 changes: 9 additions & 2 deletions draft-iab-protocol-greasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -384,8 +384,15 @@ There are also intrinsic and well-documented issues related to testing version
negotiation of protocols; see {{?EXTENSIBILITY=RFC6709}} and {{Sections 2.1 and
3.2 of VIABILITY}}.

This section will be expanded with advice for protocol
designers and implementers about how to approach these problems.
One way to grease protocol versions is to have a protocol pass
a list of supported versions or features (e.g., cipher suites), along with a grease
value, such that the grease value will not impact the actual version
or features chosen, since it will not be selected by the receiving entity.

Another method is to have a protocol include a recovery mechanism (e.g., an extra
round trip to try with another option) for cases when an unsupported version or feature
is attempted. In this case, a grease value might be attempted at some
frequency or opportunity that would not adversely affect performance.

# Security Considerations

Expand Down