ftp://ftp.cisco.com/fred/rreq-03.txt

["Craig A. Finseth" <[e-mail]>]

	...
   (assuming another version follows this one).  Given these, I suggest
   that mentioning SNMPv2 is reasonable, but conditionally, as in:

       "When SNMPv2 reaches Full Standard, you MUST implement it.  You MAY
       continue to implement SNMPv1 at that point, but you MUST not allow
       use of SNMPv1 to compromise the security constraints imposed by
       SNMPv2".
	...

I would think people would be very uncomfortable _requiring_ the use
of a mechanism that is neither standardized nor widely implemented.

As with any major protocol change, i would expect a period of
improving quality.  This wording appears to mandate a hard cut.

According to this wording, when vendor X does its first new release
after the SNMPv2 becomes standardized, it MUST use SNMPv2 and can not
use SNMPv1 for management.  This means that every network management
package and utility must also be upgraded to SNMPv2 _simultaneously_.
We all know that's a bad idea.

Perhaps something like

	...You MAY provide a configuration option to restore use of
	SNMPv1, or a range of such options to facilitate the
	transition.  However such options MUST default to SNMPv2
	with no compromise.

I think this would achieve the same end goal without breaking every
network in the world along the way...

Craig