Subject: [netmod] import-by-revision

From: Andy Bierman <[email-masked]>
Date: Wed, 27 Aug 2008 12:32:02 -0700

Hi,

I am trying to figure out how clever tools and change control
rules can support import by revision automatically.

The first CLR: all modules MUST contain a new correct revision
date, each time they are published.  This can be enforced in
IETF data models, and should be mandated for vendor data models
as well (like YANG default is mandatory, making it useful,
as opposed to SMI DEFVAL and REVISION being optional and useless.)

With this CLR, a tool can eliminate imports and submodules
that have a newer data than the current module.  The tool
can look for the first revision date older than the target module.

This covers most cases I think.
It works better with minimal module publication churn.
The revision date should be changed to a full date-and-time,
(optional time) to be as precise as possible.
This assumes some really strict change control rules,
and does not (yet) allow for any manual overrides.

Open issue: all-or-nothing import design.
Can the module 'foo' import 2 different versions
of the 'bar' module directly, or indirectly.
The details for chained import differences needs a
lot of work, especially wrt/ groupings.

IMO, if  foo imports B and C.n, then B MUST use <= C.n
if it uses C at all.

Andy

_______________________________________________
netmod mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/netmod