Hi Qin,
> I am a little bit surprised that the proposed changes to > draft-yn-netmod-yang2 presented in IETF 125 (i..e, > https://author-tools.ietf.org/api/iddiff?url_1=https://netmod-wg.github.io/yang2/main/draft-yn-netmod-yang2-02.txt&url_2=https://netmod-wg.github.io/yang2/make-baseline/draft-yn-netmod-yang2-03.txt) > hasn’t been incorporated in. The merging is the `make-baseline` branch in happening. There have been a few PR-reviews already, with one "Approve" - yeah! Please recall that my Editor-criteria for merging is: - at least 3 Approves - no change requests - no unresolved issues - no objections on list Hopefully this explains the "surprise". > Also I am wondering whether all existing RFCs with RFC7950 update should > choose to factor out YANG specific part and fold into this YANG 2.0? This is something that could be considered. Each distinct opportunity should be added to the YANG-next issue tracking list, and prioritized per Rob's document. FWIW, I think there are a couple such issues already. Kent
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
