attachment
<div dir="ltr"><div><br clear="all"></div><font size="2">FYI - Update of RFC 6353 for TLS/1.3 - very relevant for network printers.</font><br><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Kenneth Vaughn</b> <span dir="auto"><<a href="mailto:kvaughn@trevilon.com">kvaughn@trevilon.com</a>></span><br>Date: Mon, Mar 29, 2021 at 7:46 PM<br>Subject: [Secdispatch] TLSTM Update Draft<br>To: <<a href="mailto:secdispatch@ietf.org">secdispatch@ietf.org</a>><br></div><br><br><div style="word-wrap:break-word;line-break:after-white-space"><div>Hello,</div><div><br>I would like to present <a href="https://datatracker.ietf.org/doc/draft-vaughn-tlstm-update/" target="_blank">https://datatracker.ietf.org/doc/draft-vaughn-tlstm-update/</a> </div><div><br></div><div>This document is a proposal to update to RFC 6353 (<i>TLS Transport Model for SNMP</i>) to reflect the needs of TLS 1.3. </div><div><br></div><div>As a little bit of background, SNMP is widely used within Intelligent Transportation Systems (ITS) to monitor, manage and control field devices, as defined in the National Transportation Communication for ITS Protocols (NTCIP) standards, ISO standards, and specifications in the United Kingdom. As you may know, CISA has declared the transportation infrastructure to be “critical infrastructure”, and the ITS community is very interested in ensuring that this infrastructure is adequately protected, especially as these systems are increasingly relied upon by modern connected vehicles. </div><div><br></div><div>RFC 6353 defines how to use (D)TLS 1.2 authentication to control data access within SNMP. Unfortunately, its design is not entirely compatible with TLS 1.3. As such, the ITS community is interested in producing an update to RFC 6353 and believes it would be in everyone's best interests to produce this document as an IETF publication, assuming that its development can proceed in a timely manner. </div><div><br></div><div>In an effort to promote further discussion on this topic, the NTCIP and ISO communities have requested that I reach out to the IETF to initiate a conversation on this topic and I have been informed that this email list is the appropriate location to start such discussions. There is also a presentation available at <a href="https://trevilon.com/download/RFC6353Proposal.pptx" target="_blank">https://trevilon.com/download/RFC6353Proposal.pptx</a> that explains the motivation behind this update proposal. </div><div><br></div><div>Many thanks for your considerations and I look forward to our future discussions. Please let me know if you have any questions.</div><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><span style="border-collapse:separate;font-family:Arial;font-variant-ligatures:normal;font-variant-east-asian:normal;line-height:normal;border-spacing:0px"><div style="word-wrap:break-word;line-break:after-white-space"><span style="border-collapse:separate;font-family:Arial;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word;line-break:after-white-space"><span style="border-collapse:separate;font-family:Arial;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word;line-break:after-white-space"><span style="border-collapse:separate;font-family:Arial;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="word-wrap:break-word;line-break:after-white-space"><span style="border-collapse:separate;font-family:Arial;font-size:10px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;border-spacing:0px"><div style="color:rgb(0,0,0);font-weight:normal"><br>Regards,</div><div style="color:rgb(0,0,0);font-weight:normal">Ken Vaughn</div><div style="color:rgb(0,0,0);font-weight:normal"><span style="text-align:-webkit-auto">Trevilon LLC</span></div><div style="color:rgb(0,0,0);font-weight:normal"><br></div></span></div></span></div></span></div></span></div></span></div>
</div>
<br></div>_______________________________________________<br>
Secdispatch mailing list<br>
<a href="mailto:Secdispatch@ietf.org" target="_blank">Secdispatch@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/secdispatch" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/secdispatch</a><br>
</div></div></div>