Re: Standard way of referencing SNMP versions

[Chris Elliott <chelliot@cisco.com>]

On Tue, 2 Apr 2002, Andy Bierman wrote:

> At 01:34 PM 4/2/2002, Randy Presuhn wrote:
> >Hi -
> >
> >> Message-ID: <3CA4A04A.1E6229DF@cisco.com>
> >> Date: Fri, 29 Mar 2002 12:11:38 -0500
> >> From: Kevin Lingle <klingle@cisco.com>
> >> To: "Baxter, Charles A" <CBaxter@crt.xerox.com>
> >> Cc: "'mibs@ops.ietf.org'" <mibs@ops.ietf.org>,
> >>         "Hopkins, Mark" <MHopkins@crt.xerox.com>
> >> Subject: Re: Standard way of referencing SNMP versions
> >> References: <C8B562D6473E5E44B47785438F3C517D302CB8@crte147.wc.eso.mc.xerox.com>
> >...
> >> i think  the most common convention is: SNMPv1, SNMPv2, SNMPv3.
> >...
> >
> >Please don't use the label "SNMPv2".  The differences between
> >some of the protocols under that banner are far too great.  It's
> >better to use the more precise SNMPv2c, SNMPv2p, SNMPv2*, etc.
>
> In theory, this precision is interesting.
> In reality, the only SNMPv2 that anybody is using is SNMPv2c,
> so calling it SNMPv2 is not really a problem.

We have a significant number of customers running 11.2 code or earlier
that implements SNMPv2p, so I do think it's a problem. I always use the
SNMPv2c term for the current accepted and implemented version.

Chris.

>
>
> > ------------------------------------------------------
> > Randy Presuhn          BMC Software, Inc.  1-3141
> > randy_presuhn@bmc.com  2141 North First Street
> > Tel: +1 408 546-1006   San Jose, California 95131  USA
> > ------------------------------------------------------
> > My opinions and BMC's are independent variables.
> > ------------------------------------------------------
>
> Andy
>
>
>
>

Chris Elliott  CCIE# 2013       |         |
Customer Diagnostic Engineer   |||       |||
RTP, NC, USA                  |||||     |||||
919-392-2146              .:|||||||||:|||||||||:.
chelliot@cisco.com        c i s c o S y s t e m s