Re: [OPSAWG] CALL FOR ADOPTION: Transport Layer Security Verion 1.3 (TLS 1.3) Transport Model for the Simple Network Management Protocol Version 3 (SNMPv3)

Without a doubt, the review of this document requires both SNMP experts and TLS experts. Based on my presentations to both areas (SecDispatch and OPSAWG), it would appear that both have concerns that they do not have adequate expertise - nonetheless, there appears to be consensus that the work needs to be done. In short, we need a home and we need to make sure that we then outreach to ensure adequate expertise. 

It should be noted that this is largely how my draft was developed. With the aid of limited USDOT funding, I was able to gain the assistance of Dr. Michaela Vanderveen, who is a security expert, whereas I made sure the MIB and other aspects were properly aligned with SNMP. While I do not speak for the USDOT, I suspect if there is a need for more targeted assistance that it can be acquired - but ideally, we can find experts from the IETF community to provide input. In either case, I am confident that we can get this properly reviewed by the necessary experts.

Regards,
Ken Vaughn

Trevilon LLC
6606 FM 1488 RD #148-503
Magnolia, TX 77354
+1-936-647-1910
+1-571-331-5670 cell
kvaughn@trevilon.com
www.trevilon.com

> On Nov 20, 2021, at 9:24 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Joe Clarke \(jclarke\) <jclarke=40cisco.com@dmarc.ietf.org> wrote:
>> Hello, WG.  Kenneth presented
>> https://datatracker.ietf.org/doc/draft-vaughn-tlstm-update/ at IETF112
>> to us, and this was previously presented at SecDispatch at IETF111.  The
>> feeling there was that this work had merit, but Sec didn't have enough
>> SNMP experience to be the owner.  At the AD level, the feeling was that
>> perhaps opsawg did have the expertise and could pick this up.
> 
> I guess I missed this from IETF111.
> I scanned the document briefly, and I don't see that much that requires
> *SNMP*-fu, so much as it requires TLS-fu.
> 
> I think that the document will get lost in OPSAWG.
> 
> Traditionally, WGs do their own MIB modules... so I don't understand why it
> is not in TLS.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>           Sandelman Software Works Inc, Ottawa and Worldwide
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg