HI, On Thu, 25 Aug 2005, Thomas Anders wrote: <stuff cut> > Not that it matters much, but is there a specific reason why your > engineid follows old-style (pre-SNMPv3) RFC1910 instead of new-style > RFC3411 although your engine *does* support SNMPv3? Just curious. > > RFC 3411 supports this format. It is #2 in the DESCRIPTION clause of TC SNMPengineID. It makes sense. It's workable, and MUCH better that choice 1 under #3. (The SNMP Research format has a field that indicates "manager" or "agent", the UDP port number, and the IP address. It is computable given the transport address, and unique. And it is persistent (as long as the transport address is persistent, which is the case for REAL networking devices).
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
