On Wed, 2005-06-15 at 19:23, Srini Kode (skode) wrote: > I saw that new set of rfcs (rfc3410 to rfc3415) have come out.
A couple of years ago, yes. > These [obsolete] (rfc2570 to rfc2575). Correct. This is part of the normal transition along the standards track. RFC 2570ff were released as "Draft Standards" (replacing the previous "Proposed Standards" RFC 2271ff) Sufficient experience has now been gained with SNMPv3 that it has been promoted to "Full Standard", and re-issued as a new set of documents (RFC 3410ff) > Does the new rfcs have significant changes No - otherwise they would not have advanced from Draft to Full Standard. If there had been any significant changes, the new versions would have been re-issued as Draft Standards again. This is all part of the IETF quality control procedures. The new RFCs don't mean a new version of the protocol. (There are a number of minor clarifications, but nothing significant - see the Revision History clauses in the MODULE-IDENTITY definitions, and the Change Log section in RFCs 3414 and 3415). > We use netsnmp-5.1. What rfcs does 5.1 support? Either of them. > Does the new rfcs have significant changes, which will make > 5.1 agent NOT compliant with latest SNMPv3. No. Dave ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
