attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>I'm assuming this is TLS or DTLS...</div><div><br></div><div>R.</div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from my Verizon Wireless 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: Ira McDonald <blueroofmusic@gmail.com> <br>Date:01/03/2014 3:43 PM (GMT-05:00) <br>To: pwg-announce@pwg.org,Ira McDonald <blueroofmusic@gmail.com> <br>Subject: [PWG-Announce] Fwd: IETF advancing SNMP over TLS to full Internet Standard <br><br><div dir="ltr"><div><div><div><div>Hi,<br><br></div>Expect classic SNMPv3 (with the unique and costly security<br>configuration) to disappear in the next year.<br><br></div>SNMPv3 over TLS will become dominant.<br><br></div>
Cheers,<br></div>- Ira<br><br clear="all"><div><div><div><div><div><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div>
<div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">The IESG</b> <span dir="ltr"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br>
Date: Fri, Jan 3, 2014 at 2:14 PM<br>Subject: [Isms] Last Call: Progressing RFCs 5343, 5590, 5591, and 6353 to Internet Standard<br>To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
Cc: <a href="mailto:isms@ietf.org">isms@ietf.org</a><br><br><br><br>
The IESG has received a request from an individual participant to make<br>
the following status changes:<br>
<br>
- RFC5343 from Draft Standard to Internet Standard<br>
(Simple Network Management Protocol (SNMP) Context EngineID<br>
Discovery)<br>
<br>
- RFC5590 from Draft Standard to Internet Standard<br>
(Transport Subsystem for the Simple Network Management Protocol<br>
(SNMP))<br>
<br>
- RFC6353 from Draft Standard to Internet Standard<br>
(Transport Layer Security (TLS) Transport Model for the Simple<br>
Network Management Protocol (SNMP))<br>
<br>
- RFC5591 from Draft Standard to Internet Standard<br>
(Transport Security Model for the Simple Network Management Protocol<br>
(SNMP))<br>
<br>
The supporting document for this request can be found here:<br>
<br>
<a href="http://datatracker.ietf.org/doc/status-change-5343-5590-5591-6353-to-internet-standard/" target="_blank">http://datatracker.ietf.org/doc/status-change-5343-5590-5591-6353-to-internet-standard/</a><br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2014-01-31. Exceptionally, comments may be<br>
sent to <a href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
The affected documents can be obtained via<br>
<a href="http://datatracker.ietf.org/doc/rfc5343/" target="_blank">http://datatracker.ietf.org/doc/rfc5343/</a><br>
<a href="http://datatracker.ietf.org/doc/rfc5590/" target="_blank">http://datatracker.ietf.org/doc/rfc5590/</a><br>
<a href="http://datatracker.ietf.org/doc/rfc6353/" target="_blank">http://datatracker.ietf.org/doc/rfc6353/</a><br>
<a href="http://datatracker.ietf.org/doc/rfc5591/" target="_blank">http://datatracker.ietf.org/doc/rfc5591/</a><br>
<br>
IESG discussion of this request can be tracked via<br>
<a href="http://datatracker.ietf.org/doc/status-change-5343-5590-5591-6353-to-internet-standard/ballot/" target="_blank">http://datatracker.ietf.org/doc/status-change-5343-5590-5591-6353-to-internet-standard/ballot/</a><br>
<br>
The are no downrefs in RFCs 5343, 5590, and 5591.<br>
<br>
RFC 6353 includes the following down refs:<br>
<br>
[RFC4347] Rescorla, E. and N. Modadugu, "Datagram Transport Layer<br>
Security", RFC 4347, April 2006.<br>
<br>
[RFC4366] Blake-Wilson, S., Nystrom, M., Hopwood, D., Mikkelsen,<br>
J., and T. Wright, "Transport Layer Security (TLS) Extensions", RFC 4366,<br>
April 2006.<br>
<br>
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS)<br>
Protocol Version 1.2", RFC 5246, August 2008.<br>
<br>
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R.,<br>
and W. Polk, "Internet X.509 Public Key Infrastructure Certificate and<br>
Certificate Revocation List (CRL) Profile", RFC 5280, May 2008.<br>
<br>
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for<br>
IPv6 Address Text Representation", RFC 5952, August 2010.<br>
_______________________________________________<br>
Isms mailing list<br>
<a href="mailto:Isms@ietf.org">Isms@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/isms" target="_blank">https://www.ietf.org/mailman/listinfo/isms</a><br>
</div><br></div></div></div></div></div></div>
</body>