HI, And while I'm at it, I should also submit a replacement for the target and notification MIB modules found in RFC 3413. (The proxy MIB module probably also needs to be replaced, but I don't have experience with its implementation and usage).
Oh wait! Before I can start on making real progress resolving real problems I've got to get approval by the SNMPv3 architectual, terminology, and preservation board. Oh no, changes might result in people believing that the specifications for SNMPv3 are not stable, and result in causing delay in incorporation and deployment of SNMPv3/USM. So, maybe, for the good of humanity that I should not work on anything that would result in what might appear to cause SNMPv3 specs to be unstable, and instead go work on helping victims of huricane Katrina. On Mon, 5 Sep 2005, Wes Hardaker wrote: > >>>>> On Mon, 5 Sep 2005 09:46:07 -0700 (PDT), "David T. Perkins" <[EMAIL > >>>>> PROTECTED]> said: > > David> And I hope that part of "doing the right thing" is to replace > David> the implementation of RFC 3014 (the log MIB) with another > David> logging mechanism. > > Feel free to submit a MIB and code for us to review ;-) > > -- > Wes Hardaker > Sparta, Inc. > Regards, /david t. perkins ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
