RE: Capabilities and MIBs

["McDonald, Ira" <imcdonald@sharplabs.com>]

Hi Randy,

Actually, a URL to a network copy of an AGENT-CAPABILITIES
and/or to an optional MODULE-COMPLIANCE statement would be
a good method of being very clear.

But most vendors (maybe only many) don't seem to have ever
written MODULE-COMPLIANCE statements.

So a lighter weight solution is just to name the MIB and
the version (by URL to an RFC or a private vendor MIB).

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com

> -----Original Message-----
> From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org]On
> Behalf Of Randy Presuhn
> Sent: Wednesday, February 15, 2006 3:45 PM
> To: netconf@ops.ietf.org
> Subject: Re: Capabilities and MIBs 
> 
> 
> Hi -
> 
> > From: "Phil Shafer" <phil@juniper.net>
> > To: "Vincent Cridlig" <vincent.cridlig@loria.fr>
> > Cc: <netconf@ops.ietf.org>
> > Sent: Wednesday, February 15, 2006 5:28 AM
> > Subject: Re: Capabilities and MIBs 
> >
> > Vincent Cridlig writes:
> > >Is it acceptable ?
> > 
> > Absolutely.  You might want some sort of versioning information
> > also, which could be done by including the rfc number in the
> > capability string.
> ...
> 
> Do you see a need for anything analogous to a reference to an
> AGENT-CAPABILITIES or MODULE-COMPLIANCE, whether coming from
> an RFC or from some other source?
> 
> Randy
> 
> 
> --
> to unsubscribe send a message to netconf-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/netconf/>
> 

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>