I strongly support this work as it represents capabilities that are being developed, deployed and used in practice. It has good intentions and provides a good approach in the context of defense in depth approaches. No security cannot be just on both ends of the communication. One can dream about it but that is not how reality is. Removing this possibility is a limit to the overall defense.
I do not understand the reasons behind ignoring reality and the IETF would have, in my naive mind, a strong interest in getting this work under good community adoption so that it is kept in good control with validated best practices. Everyone would win. I support this draft Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday 23 July 2020 03:30, Jen Linkova <furr...@gmail.com> wrote: > One thing to add here: the chairs would like to hear active and > explicit support of the adoption. So please speak up if you believe > the draft is useful and the WG shall work on getting it published. > > On Mon, Jul 20, 2020 at 3:35 AM Ron Bonica > rbonica=40juniper....@dmarc.ietf.org wrote: > > > Folks, > > This email begins a Call For Adoption on draft-wang-opsec-tls-proxy-bp. > > Please send comments to op...@ietf.org by August 3, 2020. > > > > Ron > > > > > > Juniper Business Use Only > > > > OPSEC mailing list > > op...@ietf.org > > https://www.ietf.org/mailman/listinfo/opsec > > -- > > SY, Jen Linkova aka Furry > > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
