Re: [OPSAWG] CALL FOR ADOPTION: draft-reddy-opsawg-mud-tls

["Joe Clarke (jclarke)" <[e-mail]>]

The call for adoption has closed.  It has not been without discussion to be sure.  There have been concerns expressed from the TLS working group that it might benefit malware authors and that it could lead to “ossification” in use of the TLS protocol.

That said, there has been considerable support expressed for (and active willingness to work in) moving this work forward.  Therefore, this document has been adopted by the opsawg working group.  The authors have already been active in addressing some concerns brought up during the CFA, and the chairs encourage the authors and those interested in the progression of this work to continue to work with the TLS WG to fully shore up the text and YANG module.

Additionally, it might be good to get a more formal early review of this work from SecDir so that the WG can focus on additional items required to move the work forward.

Authors, please rename this draft, draft-ietf-opsawg-mud-tls and resubmit it to DataTracker as a -00.  DO NOT change any other text.  Within DT, mark this draft as replacing draft-reddy-opsawg-mud-tls.

Thanks.

Joe

> On Sep 2, 2020, at 11:05, Joe Clarke (jclarke) <jclarke=[e-mail]> wrote:
> 
> Hello, opsawg.  This draft as underwent a number of revisions based on reviews and presentations at the last few IETF meetings.  The authors feel they have addressed the issues and concerns from the WG in their latest posted -05 revision.  As a reminder, this document describes how to use (D)TLS profile parameters with MUD to expose potential unauthorized software or malware on an endpoint.
> 
> To that end, this serves as a two-week call for adoption for this work.  Please reply with your support and/or comments by September 16, 2020.
> 
> Thanks.
> 
> Joe and Tianran
> _______________________________________________
> OPSAWG mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/opsawg