Hi folks, Apologies for the delay in concluding this adoption call. To close the loop here, it doesn’t look like we have sufficient support to adopt the document as a WG item.
The chairs would like to recommend AD sponsorship as a viable path forward for this document. This should achieve the desired end goal of moving change control from the fine folks maintaining NSS to the IETF while also nailing down the now widely supported format used in production. Best, Chris, for the chairs > On Nov 28, 2022, at 1:41 PM, Sean Turner <s...@sn3rd.com> wrote: > > Hi! > > At TLS@IETF115, the sense of the room was that there was WG support to adopt > draft-thomson-tls-keylogfile [1]. This message is to judge consensus on > whether the WG should adopt draft-thomson-tls-keylogfile. Please indicate > whether you do or do not support adoption of this I-D by 2359UTC on 12 > December 2022. If do not support adoption, please indicate why. > > Cheers, > Chris, Joe, and Sean > > [1] https://datatracker.ietf.org/doc/draft-thomson-tls-keylogfile/ > _______________________________________________ > 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
