Support.
Some comments that I have on this draft: 3.1.1 Last paragraph: Worth Mentioning that it is currently not only about Encrypted SNI that is being discussed, but also about encrypting the client hello (ECH). Beside the SNI, this also means that more fields like ALPN in the Client hello are also encrypted in the future. https://datatracker.ietf.org/doc/draft-ietf-tls-esni/ 3.1.3 , 3.1.4: Correct for TLS 1.3 as it is today. With ECH, this would have additional impact, but I think this is not in scope for this draft as ECH is not yet standardized. Toby From: OPSEC <[email protected]> on behalf of Ron Bonica <[email protected]> Date: Friday, 5. June 2020 at 17:05 To: OPSEC <[email protected]> Subject: [OPSEC] Call For Adoption: draft-camwinget-opsec-ns-impact Folks, This email begins a call for adoption on draft-camwinget-opsec-ns-impact. The call for adoption will end on 6/19/2020. Ron and Jen Juniper Business Use Only
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OPSEC mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsec
