Re: [NGO] external module properties

[Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>]

On Mon, Apr 28, 2008 at 01:27:59PM -0400, David Harrington wrote:
 
> It is important for an NMS to be able to tell which version of a data
> model is supported by a managed element, so when it makes changes to a
> configuration, it can make changes appropriate to the version
> supported.

> On a side note, keep in mind that some managed elements may have
> multiple components, such as blades in a chassis, and the versions
> supported might differ, so a Netconf server might also need to know
> which version to use to perform validation.

I seems you are talking about version information you won't get from
the YANG module itself; at least as long as we do not do versioned
imports. I hear you saying you want a definition of what the various
thingies in a managed element actually support; which is was we called
agent capabilities in the SMIv2. In fact, if you look how SMIv2
compliance and agent capabilities work, you will see that they do not
even refer to a specific version of a MIB module.

Perhaps people have a different versioning model in mind than what
SMIv2 used to have. Then I think this needs to be discussed first.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
NGO mailing list
NGO at ietf.org
https://www.ietf.org/mailman/listinfo/ngo