If you're a vendor that supports the nodes that are being made if-feature conditional in 9127-bis and you want to ship 9127 as your supported module? Go for it. This entire discussion is weird. For all of your hand wringing, absolutely none of this discussion can force a future implementor to choose to support one version of a module over another. The trend will ideally be to support newer versions of models because they include features they want. But perhaps they want older base-level stuff. If that implementation is somewhere between? Deviation modules will be crafted for that implementation. If you think this minor bit of work creates compatibility issues even though it doesn't move or rename a single leaf? Then you'd be for a rather rude awakening at how other organizations do this stuff. Those other organizations don't have to give a damn about supporting the entire set of possible features or arbitrary vendor quirks. They get to pick and choose. The trend there isn't to use features, it's to force the deviations. We have it easy. -- Jeff |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
