RE: snmpv2 manager capabilities

David Perkins <dperkins@scruznet.com> Fri, 23 May 1997 15:13 UTC

Received: from cnri by ietf.org id aa10136; 23 May 97 11:13 EDT
Received: from portal.ex.tis.com by CNRI.Reston.VA.US id aa07544; 23 May 97 11:13 EDT
Received: (from majordom@localhost) by portal.ex.tis.com (8.8.2/8.8.2) id KAA25258 for snmpv3-outgoing; Fri, 23 May 1997 10:56:43 -0400 (EDT)
Date: Fri, 23 May 97 08:03:22 pdt
From: David Perkins <dperkins@scruznet.com>
Subject: RE: snmpv2 manager capabilities
To: snmp2@tis.com, Pedro Palma Santos Silva Mendes <ppsdsm@ulb.ac.be>, snmpv3@tis.com
X-Mailer: Chameleon V0.05, TCP/IP for Windows, NetManage Inc.
Message-ID: <Chameleon.970523080445.dperkins@dperkins4.sj.scruznet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-snmpv3@ex.tis.com
Precedence: bulk

HI

There is a mechanism in SMIv2 that specifies the objects that a network
management application uses. It is called the "MODULE-COMPLIANCE"
construct.

Note that the SNMPv3 effort has NOTHING to do with the SMI. The SNMPv3
effort is ONLY to define a new SNMP message format to allow secure
SNMP message exchange and access control.
On Fri, 23 May 1997 12:17:55 +0200 (DST)  Pedro Palma Santos Silva Mendes wrote:
>Hi,
>
>
>I would like to know if there are any mechanism, in SNMPV2, that defines 
>the manager capabilities ?
>
>If not, will SNMPV3 have one ?
>
>
>
>Thanks.
>
>
>Pedro Silva Mendes.
>

/dperkins@scruznet.com, David T. Perkins
Date: 05/23/97, Time: 08:03:22