Reviewer: Xufeng Liu Review result: Ready with Nits 3.2. Code Components The “file name” after the "<CODE BEGINS>" tag is something described as “SHOULD” be included. If there is no such a “file name”, the tool “rfcstrip” will not extract the correct file. Should we consider making this “file name” a “MUST”? 3.5.1. YANG Module Classification In the section “Network model”, the term "Network model” is described as “relevant protocols operating at the link and network layers”. Can a network model be designed for other layers, such as OTN or MPLS? If so, such a description seems to be too narrow. RFC 8309 clarifies the “Service Model”, which is the section before this one. Is there a definition of the “network model” in RFC 8309? 3.8. IANA Considerations Section The “YANG Module Names” registry is defined in RFC 6020, but not RFC 7950. Many YANG module writers mistakenly used RFC 7950. Should we consider bringing this up with special attention? 4.5. Conditional Statements An example not preferred is given, but there is no preferred fix. Would it be better to provide the proffered solution? -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
