Merged
Conversation
CarolYeh910
reviewed
Nov 18, 2025
jmayclin
reviewed
Nov 21, 2025
CarolYeh910
approved these changes
Nov 24, 2025
alexw91
approved these changes
Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal
Create 4 new security policies that provides a "transition path" for servers to safely migrate to strict RFC9151 requirement
Why
A direct transition from non-RFC9151 compliant policies to RFC9151 compliant policies would break compatibility for clients that don't support RFC9151 TLS options. To safely migrate to RFC9151 compliance, servers need to understand current client behaviors. These transition policies enable this by supporting both legacy TLS (non-RFC9151) options and RFC9151 TLS options, with RFC9151 options being preferred.
How
Four new transition policies are added:
These are in order from most restrictive (closest to RFC9151) to most permissive:
Callouts
Testing
Regenerated policy snapshot. Other existing tests continue to pass.
Related
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.