Re: Capabilities and MIBs

["David T. Perkins" <dperkins@dsperkins.com>]

HI,

I believe that you should put the MIB module name (it starts
with an uppercase letter), and include for version the value
from the LAST-UPDATED clause in the MODULE-IDENTITY definition
for modules in SMIv2 format, and an associated date for modules
in the SMIv1 format.
Note that MIB module names are not globally unique, and
they need to be quallified. I believe the best qualifier
is the organization's "IANA Enterprise Number". Technically,
a system advertises what capabilities it has with
AGENT-CAPABILITIES definitions (a definition descriptor
that is qualified by Enterprise number, module name,
and last-update date).
Also, if you want a manager to tell the system what it
needs, you can you MODULE-COMPLIANCE definitions
(a definition descriptor that is qualified by 
Enterprise number, module name, and last-update date)

On Wed, 15 Feb 2006, Vincent Cridlig wrote:
> Hi,
> 
> I would like that our agent advertises its supported "MIBs".
> Are capabilities the regular way to do it ?
> 
> Like, for example, for the agent to advertise that it supports "bgp" MIB, "routes" MIB and "network interfaces" MIB.
> 
> <hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>   <capabilities>
>     <capability>urn:ietf:params:netconf:base:1.0</capability>
>     <capability>urn:ietf:params:netconf:capability:startup:1.0</capability>
>     <capability>urn:madynes:module:bgp</capability>
>     <capability>urn:madynes:module:routes</capability>
>     <capability>urn:madynes:module:interfaces</capability>
>   </capabilities>
>   <session-id>4</session-id>
> </hello>
> 
> Is it acceptable ?
> 
> Thanks for your help.
> Vincent Cridlig

Regards,
/david t. perkins



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