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

Proposal for addressing interop issues with 9.2.2 #639

Closed
wants to merge 1 commit into from
Closed

Proposal for addressing interop issues with 9.2.2 #639

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion draft-ietf-httpbis-http2.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3712,7 +3712,15 @@ HTTP2-Settings = token68
Clients MAY advertise support of cipher suites that are prohibited by the above
restrictions in order to allow for connection to servers that do not support HTTP/2.
This enables a fallback to protocols without these constraints without the additional
latency imposed by using a separate connection for fallback.
latency imposed by using a separate connection for fallback. Prohibited cipher suites
MUST be advertised at a lower preference than permitted cipher suites.
</t>
<t>
Servers MAY allow unknown ciphers that are negotiated by a TLS 1.2 implementation.
This prevents potential interoperability issues involving future ciphers supported
by the underlying TLS 1.2 implementation, but are not yet understood by the server.
Due to the restrictions on clients above, prohibited cipher suites are still
prevented from use with HTTP/2.
</t>
</section>
</section>
Expand Down