[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Standard way of referencing SNMP versions

To: mibs@ops.ietf.org
Subject: Re: Standard way of referencing SNMP versions
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Wed, 3 Apr 2002 09:25:17 +0200
In-reply-to: <Pine.GSO.4.33.0204021739140.4091-100000@rtp-cse-133.cisco.com>(message from Chris Elliott on Tue, 2 Apr 2002 17:40:42 -0500 (EST))
References: <Pine.GSO.4.33.0204021739140.4091-100000@rtp-cse-133.cisco.com>

>>>>> Chris Elliott writes:

>> 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.

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

And there are still books out there that many people read which
explain that SNMPv2 is what we call SNMPv2p today. I agree that the
confusion still exists and being precise helps.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

References:
- Re: Standard way of referencing SNMP versions
  - From: Chris Elliott <chelliot@cisco.com>

Prev by Date: Re: Standard way of referencing SNMP versions
Next by Date: Re: Psudo WG Last Call for: http://www.ietf.org/internet-drafts/draft-ietf-ops-taddress-mib-02.txt
Previous by thread: Re: Standard way of referencing SNMP versions
Index(es):
- Date
- Thread