Re: [NGO] external module properties

Schema discovery cannot discover what isn't said ;-)
Someplace in the schema, we need a good version identifier.
I think we might need the capability of specifying version in the
include statement (if the version dependency is important, but it
should be able to be left out when it is not important)

A dependency tree could be complex, and might be able to be avoided by
tightening the rules about how a module can be updated. OR we can try
to utilize some existing standards about handling dependencies.

dbh

> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com] 
> Sent: Tuesday, April 29, 2008 4:01 PM
> To: ietfdbh@comcast.net
> Cc: ietf@andybierman.com; ngo@ietf.org
> Subject: Re: [NGO] external module properties
> 
> Hi,
> 
> "David Harrington" <ietfdbh@comcast.net> wrote:
> > Hi,
> > 
> > My concern also includes multiple instances of a vlan module
running
> > within a single (master/subagent) environment. This might 
> be found in
> > a router chassis that supports new and legacy blades, or an x86 PC
> > server that can support disk drives from different vendors. 
> 
> I agree that this is a difficult problem, and I'd be happy to
discuss
> this more.  Is this something we want to work on?  But I think it is
> orthogonal to the issue about how a module is identified.  BTW, this
> problem touches other ongoing work, like schema discovery.
> 
> 
> /martin
> 

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo