[ech] custom TLS client hello extensions

[Stephen]

Hiya,

On 02/03/2023 15:30, David Benjamin wrote:
> There was some previous discussion of this here:
> https://github.com/tlswg/draft-ietf-tls-esni/issues/398#issuecomment-796287240

Yep, another argument I lost:-)

> For existing API callers, I think the two reasonable options are to put it
> in both or just in the inner ClientHello.

Question for ya: does boring support the same custom
extension handling APIs as openssl?

If so, I guess we should do the same thing and have
you done anything for that already?

Ta,
S.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0xE4D8E9F997A833DD.asc
Type: application/pgp-keys
Size: 1197 bytes
Desc: OpenPGP public key
URL: <https://mta.openssl.org/pipermail/ech/attachments/20230302/b0a1c2cb/attachment.asc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://mta.openssl.org/pipermail/ech/attachments/20230302/b0a1c2cb/attachment.sig>