Re: [NGO] external module properties

Hi,

"Randy Presuhn" <randy_presuhn@mindspring.com> wrote:
> > From: "Martin Bjorklund" <mbj@tail-f.com>
> > Suppose module A rev 1 gets published in an rfc, and module B which
> > imports A rev 1 in another.  Now, A is updated to rev 2.  If a vendor
> > wants to implement A rev 2 and B, that doesn't work, unless B is also
> > updated to rev 2 as soon as A is updated.
> 
> In my opinion, this is a feature, rather than a bug.
> (But there's no "as soon as" requirement.  There's no need to update
> B until someone wants a version that includes the behavioural changes
> that would result from using the newer version of A.)

The problem is when a vendor needs to implement A rev 2 in a device,
and also B.  B imports A rev 1.  So the device needs to implement A
rev 1 *and* A rev 2.   This is something that we have talked about
before, and dismissed as being too complicated in general.

But you talk about behavioural changes.  In the current design of
YANG, the idea has been that a module cannot be updated in a way that
changes the behaviour for importers and includers.  Thus you don't
have to rev B just b/c A is updated.

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