Doesn't "snmpinform" implementation violate RFC 3414 (re SNMPv3 engine discovery)?

The description of the snmptrap command (found at
http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html)
indicates this about INFORMS with SNMPv3:
"The snmptrap program discovers the remote engineID just like the rest
of the applications would do ..."
This must mean the entity running snmptrap has stored the non-localized
key (which gets localized when the discovery process executes). And
normally I assume this entity running snmptrap would be an agent. 

But RFC 3414 says that agents do not store non-localized keys: 
"a user's password or non-localized key MUST NOT be stored on a managed
device/node". 
In other words, RFC 3414 is saying the agent sending INFORMS must know
a-priori (e.g. via configuration) the engine ID of the device the INFORM
is to be sent to, contrary to how the first quote indicates that
Net-SNMP's snmptrap command will behave.

So what am I missing? Something is amiss somewhere -I'd appreciate any
pointers on the real problem here (including faulty logic on my part!?).

Regards,
CPC




-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users