>>>>> On Mon, 05 Sep 2005 11:50:43 +0100, Dave Shield <[EMAIL PROTECTED]> said:
>> 0) protocol (SNMP, AgentX, SMUX, internal callback, etc) >> 1) protocol type (v1, v2c, v3) >> 2) security model (comm(v1,v2c), usm, etc) >> 3) security level >> 4) security name Dave> Yes - the attributes of the request probably do need to be Dave> available to the MIB handling code (and I believe they are Dave> with the v5 API). Sure, they might be available. But you can't make rational and safe decisions based on them. How do you decide whether or not you want to do something differently when all you know is that it's coming in over AgentX? 99.9% of the time people want to do that is because they want to do something that contexts let you do or that VACM already lets you do. Find a case where this isn't true ;-) -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- 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
