> On Mar 22, 2019, at 12:07, Lou Berger <[email protected]> wrote: > > Hi, > > Thank you all for the good input on this thread. > > With the understanding that a 00 working group document is a starting point > for the working group rather than a document that is ready for last call - we > believe there is sufficient support to adopt this document as a starting > point for the requirements we wish to address on this topic. > > It is clear that there is still work to be done on this document before we > can declare consensus on it and, not surprisingly, that there is more work to > be done on the solution. > > Authors, > > Please resubmit this document as draft-ietf-netmod-yang-revision-reqs-00 with > the only change being the name and publication date. The -01 version should > focus on resolving issues raised during adoption. Of course the document is > subject to normal WG input and processing. > > Please note the 'file' name change -this is to indicate that the requirements > are not presupposing a specific solution. It is also consistent with how > versioning is defined within the document currently. > > Note: we would like to try to continue the list discussion in next week's > session and ask the Authors/DT to summarize issues raised during the adoption > call and lead a discussion to help resolve these issues. > I think this meeting is great opportunity to decide what steps need to be taken to advance the document within the working group.
Martin specifically objects to the presence of of Non-Backward-Compatible changes. Many modules outside the IETF are already incompatible with roc 7950 yang 1.1 revision rules. So that cat may be out of the bag at least with respect to the real world. the question remains what to do about that?
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
