Hiya,
The CH in TLS has a 3 octet length. The payload in ECH has a
2-octet length. Hopefully that'll never matter but it's an
inconsistency I don't recall coming up before. (Apologies if
I've forgotten, or if I've missed something in 8446 that
forbids bigger CH's.)
I'm fine with just leaving it
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Layer Security WG of the IETF.
Title : Guidance for External PSK Usage in TLS
Authors : Russ Housley
Jonathan Hoy
Moving to a three-byte length wouldn't do anything: extension bodies
themselves have two-byte lengths, so any longer lengths within an extension
is just a waste.
(To that end, because every field in a ClientHello has a two-byte length,
the longest possible syntactically valid ClientHello at all is
Sean and Joe:
The revision to address Ben' comments has now been posted.
I believe that all WGLC comments have been addressed. I think this document is
ready to go to the IESG.
Russ
> On Jan 22, 2021, at 3:27 PM, Russ Housley wrote:
>
> Ben:
>
> Thanks for you review and comments.
>
>> W
Issues
--
* tlswg/draft-ietf-tls-esni (+3/-2/💬12)
3 issues created:
- Update to HPKE-08 (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues/387
- Fixed-length values should probably be fixed-length (by chris-wood)
https://github.com/tlswg/draft-ietf-tls-esni/issues
