> On your question about proxies, here goes from memory. > The RFCs go into mind numming detail...
<wry grin> > First, thanks for updating the terminology. What the SNMP specs > say and what the code does (and what people generally say) > all concide. I think that's being a little optimistic! What the Net-SNMP documentation and code refers to as "proxying" does *not* coincide with what the SNMP specs mean by that. In fact, the model we use doesn't seem to be mentioned in RFC 3413 at all. Hence I've introduced a distinction between "proxy forwarding" (passing on a complete request) and "proxy delegation" (passing on selected varbinds). > As to the security issue, the specs say that only the "target > system" and not the proxy does authorization (access control) > of a request. Thanks - that's what I expected. So when a client first starts the engineID discovery process, it will receive the engineID and boot count/time values from the final (proxied) agent, rather than the intermediate (proxying) agent - correct? > From the standpoint of the specs, > only the engineId, context, and varBindList from the PDU > is transfered "unaltered" from a manager to/from the target system. That's the snmpEngineId, rather than (actually as well as) the contextEngineId - correct? Dave ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
