Re: [NGO] external module properties

Phil Shafer <phil@juniper.net> wrote:
> "David Harrington" writes:
> >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)
> 
> I keep coming back to this also, for the "import" statement.
> Consider this scenario/timeline:
> 
> - module A defines a cool feature
> - modules B and C import A to use that feature
> - module A gets rev'd to add a new leaf to a grouping
> - module B wants the new leaf
> - module C doesn't want it
> 
> Without revision-specific imports, this scenario is unworkable.
> 
> With revisions, module B would get rev'd to import the new revision
> of A.  Module C would continue to import the previous revision.

But with revisions, you have to explicitly rev all importers of a
module when the module is updated.

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.

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