We should do this. It's good work and it completes the work we've already done here. The status is correct.
I don't think that we need new security considerations about compiling this in or any of that. What is in the draft is pretty good. My only real suggestion is that perhaps -- for a server -- ECH_CONFIG might be included only once for each unique value that the server supports. This might be done with a special value for the ClientHello.random field (all zeros perhaps, or repeating the config ID 32 times). That would save a lot of space in a server log. Lookup would need to use the public name and config id, though I imagine that config id might be enough in many cases. On Thu, Jul 25, 2024, at 09:15, IETF Secretariat wrote: > The TLS WG has placed draft-rosomakho-tls-ech-keylogfile in state > Call For Adoption By WG Issued (entered by Sean Turner) > > The document is available at > https://datatracker.ietf.org/doc/draft-rosomakho-tls-ech-keylogfile/ > > Comment: > At IETF 120 there was support in the room to adopt, but we need to verify > that on list. > > _______________________________________________ > TLS mailing list -- tls@ietf.org > To unsubscribe send an email to tls-le...@ietf.org _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
