<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true"><p><br></p><div>I'm pretty familiar with SNMP as I have worked with it for a number years.</div><div>I know Telcos like it, but I feel its a protocol that is near end of life. It hasn't</div><div>kept up on security guidelines. SNMPv1 and v2c are totally insecure and</div><div>SNMPv3 is barely usable. But even SNMPv3 still uses MD5 and SHA1.</div><div><br></div><div>That being said, the Alarm MIB would be my choice of MIB. A custom MIB</div><div>would be a mess and a nightmare to maintain. </div><div><br></div><div>Can pysnmp do v3 notifications? You might want to also consider informs</div><div>rather than traps since they are acknowledged.</div><br class="Apple-interchange-newline">
</div>
<br><div><div>On Apr 24, 2014, at 7:48 AM, Florian Haas <<a href="mailto:florian@hastexo.com">florian@hastexo.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, Apr 24, 2014 at 4:20 PM, Julien Danjou <<a href="mailto:julien@danjou.info">julien@danjou.info</a>> wrote:<br><blockquote type="cite">On Thu, Apr 24 2014, Florian Haas wrote:<br><br><blockquote type="cite">So for any inheriting subclass, the notify method signature is defined<br>such that action needs to be a URL. That doesn't make a whole lot of<br>sense for anything other than a ReSTful service. If we want to map<br>those to SNMP URIs, then there's RFC 4088 that describes that. But<br>those URIs, to the best of my knowledge, can't be used for traps.<br></blockquote><br>Actually you can use anything with URL, we could use something like:<br><br><a href="snmptrap://destination/oid?community=public&urgency=high">snmptrap://destination/oid?community=public&urgency=high</a><br><br>And that would do it.<br>(not sure about the parameters and all, I'm no SNMP trap connoiseur, you<br>get the idea)<br></blockquote><br>But that would be another case of wheel reinvention. To me the idea to<br>express an SNMP trap as a URI sounds rather ludicrous to begin with;<br>it doesn't get any more reasonable by *not* using the scheme that<br>someone else has already invented, and instead inventing one's own.<br><br>What does seem stranger to me in the first place is to require a<br>generic event action to be a URL.<br><br>What do others think?<br><br>Cheers,<br>Florian<br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=2CQc966BQ6s3Cdd6nQ79uvWP17nF9g%2FX4m3XppGg1xQ%3D%0A&m=V0NZf%2BbZTj22q3MpwBLku0eGaY9eOszAvPpch4xmjgs%3D%0A&s=3675ee624a6a24b0bad28a9027e19c458ba7422e38afb5e3fae71049259135cc<br></blockquote></div><br></body></html>