In SNMPv1 and v2c, if there is any authentication failure on the agent,
it can send an authenticationFailure trap to the sender of the SNMP
request. Shouldn't we be doing the same even in the case of an SNMPv3
agent. The RFC seems to be vague or left it to the implementation of the
calling module, as what to do in this case. If we need to be backwards
compatible to v1 or v2c, I don't see why the calling module shouldn't be
sending an authenticationFailure trap, in the above case, even in
SNMPv3. Any clarification is highly appreciated.
Thanks,
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
