tree aff7e8b69177ef028ed0b93ec0f79cd1e6d127d7
parent f8f35c95550e6796ab8b2c0f8e37e7ce4bc67302
author David Schinazi <dschinazi@google.com> 1610652349 -0800
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1610659353 +0000

Add support for the new QUIC TLS extension codepoint

IETF QUIC draft 33 is replacing the TLS extension
codepoint for QUIC transport parameters from 0xffa5
to 57. To support multiple versions of Chrome, we
need to support both codepoints in BoringSSL. This
CL adds support for the new codepoint in a way that
can be enabled on individual connections.

Note that when BoringSSL is not in QUIC mode, it
will error if it sees the new codepoint as a server
but it will ignore the legacy codepoint as that could
be a different private usage of that codepoint.

Change-Id: I314f8f0b169cedd96eeccc42b44153e97044388c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44704
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>