I oppose adoption of draft-thomson-tls-keylogfile. The stated goal was to find a permanent, discoverable location for this document, other than NSS project's repository. Perhaps it's fine to create an RFC for this purpose, but then I'd argue that it should not be an Informational RFC.
Standards-track RFC that promotes the export of TLS secrets in clear-text sends the wrong message, can (and will) be used to push TLS stack vendors to implement this. Cheers, Andrei -----Original Message----- From: TLS <[email protected]> On Behalf Of Salz, Rich Sent: Monday, November 28, 2022 10:54 AM To: Sean Turner <[email protected]>; TLS List <[email protected]> Subject: [EXTERNAL] Re: [TLS] Call for adoption of draft-thomson-tls-keylogfile I support adoption. I assume the wireshark folk(s), etc., will review ... _______________________________________________ TLS mailing list [email protected] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Ftls&data=05%7C01%7CAndrei.Popov%40microsoft.com%7Ce5d4a41309dd44fe5e2108dad172043a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638052584901610518%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=ffuQE0lqf5IzkYWzizCPKXA4lEHU6e9Nh5kJ4gwd998%3D&reserved=0 _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
