Re: [NGO] external module properties

[Phil Shafer <phil at juniper.net>]

Andy Bierman writes:
>I don't see how multiple sub-agents within a single agent can implement
>different versions of the same module, without using different
>namespace URIs for each variant.  (Maybe somebody can explain
>it to me;-)

module A {
    revision 2008-01-01 { ... }
    grouping one {
        leaf foo { ... }
        leaf goo { ... }
    }
}

module A {
    revision 2008-04-01 { ... }
    grouping one {
        leaf foo { ... }
        leaf goo { ... }
        leaf super-cool { ... }
    }
}

module B {
    import A {
        revision 2008-01-01;
    }

    container zed {
        uses A:one;
    }
}

module C {
    import A {
         revision 2008-04-01;
    }
    import B { ... }

    container yancy {
        uses A:one;
    }
}

The use of A's one is a compile time issue, and the revision
on the import makes is clear what contents B and C want.
yancy will contain super-cool, which zed will not.

If there was no revision on import, would zed be forced to
contain super-cool as soon as the 2008-04-01 revision of
A is published?

If you're claiming that this wasn't a problem for MIBs,
could you please point me at a couple of MIBs that were
rev'd and the history of how successful these were?

Thanks,
 Phil
_______________________________________________
NGO mailing list
NGO at ietf.org
https://www.ietf.org/mailman/listinfo/ngo