On Sun, Jul 5, 2015 at 11:57 PM, Juergen Schoenwaelder < j.schoenwael...@jacobs-university.de> wrote:
> On Fri, Jul 03, 2015 at 02:12:30PM -0700, Andy Bierman wrote: > > > I propose this text in the conformance leaf: > > > > For import statements that do not specify a revision > > date, the most recent revision in the library SHOULD > > be used by the server."; > > > > It seems like a lot of data will be needed to model the dependency tree > > for every import-stmt in every module. Don't forget every include-stmt > > as well, since submodules can import with or without revision. > > > > IMO "SHOULD use latest" is good enough. > > Perhaps modules should use import-by-revision when they > > are published as RFCs (as Lada suggested). > > This sounds like "lets pretend the world is simple so we have less > work to do". > > No -- YANG currently says if there is no revision date then the implementation can use any revision, This is also good enough. Prove that this is causing interoperability problems. I don't think it is -- especially not such that the server has to model all its imports so the client can retrieve the data. > /js > Andy > > -- > Juergen Schoenwaelder Jacobs University Bremen gGmbH > Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany > Fax: +49 421 200 3103 <http://www.jacobs-university.de/> >
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
