Hello Tom, Thank you for your review and your comments! They truly help us improve this document. Please find my answers below (prefixed with [IP]). Note that the diff after handing your comments and those of Esko Dijk and Juergen Schoenwaelder can be found at [1].
Best regards, Ivaylo [1]: https://tools.ietf.org/rfcdiff?url1=draft-ietf-core-sid&url2=http://core-wg.github.io/yang-cbor/draft-ietf-core-sid-latest.txt On Mon, Mar 30, 2020 at 1:16 PM tom petch <[email protected]> wrote: > Some YANG admin for core-sid > > import must have a reference clause > [IP]: Fixed. such reference must be Normative References for the I-D > [IP]: Fixed. no RFC Editor note to update the date (I know, they will fix that :-) > [IP]: Fixed. contact lacks e-mail of WG > [IP]: Fixed. > IANA Considerations fails to register namespace > [IP]: Fixed. IANA Considerations does not specify a Group name; a well-chosen group name > makes a registry easy to find. Many if not most of the existing Group > names are not well-chosen. Please choose with care. e.g. is this for > constrained devices or for all; is it specific to YANG and will there be > other uses? .... > [IP]: That is a very good point. I am not sure how it is supposed to work - IANA will ask us about the group name when they create the registries or there is some text that we can write to request this. I will follow with a question to the working group with a few options for possible group names. Tom Petch > ________________________________________ > From: netmod <[email protected]> on behalf of Carsten Bormann < > [email protected]> > Sent: 09 March 2020 13:04 > To: core > Cc: [email protected] > Subject: [netmod] π WG Last Call of CORECONF drafts: > draft-ietf-core-yang-cbor-12, -sid-11, -comi-09, -yang-library-01 > > It took us a long time to get the four CORECONF drafts in sync, > but now we are ready for WGLC. > > This starts a working group last call for > β draft-ietf-core-yang-cbor-12 > β draft-ietf-core-sid-11 > β draft-ietf-core-comi-09 > β draft-ietf-core-yang-library-01 > > ending on > > 24:00 UTC on Tuesday, March 31, 2020. > > (This includes some extra time for the IETF week and for cross-WG > coordination.) > > This WGLC is copied to the netmod WG mailing list; please do have a look > at these drafts as they are slated to become a part of the greater > YANG/NETCONF/RESTCONF family. We intend the discussion to be on the > CoRE mailing list, but if you find a fundamental issue with YANG or > RESTCONF, feel free to discuss that on netmod instead. > > Please start a new email thread for each major issue that will need > discussion and make sure the subject line includes the draft name and > some sort of name for the issue. (Minor issues such as typos can also > be sent to the authors.) > > If you read the draft and think it looks fine, please send a one line > email to the list or to the chairs letting us know that so we can get > a feel of how broad the review has been. > > (To reviewers and authors:) If you are aware of any patent claims that > might apply to systems that implement these drafts, please review BCP 78 > and BCP 79 and make any appropriate IPR declaration before the last-call > ends. If you are not sure whether you need to make a declaration or not, > please talk to the chairs and we will help. > > GrΓΌΓe, Carsten > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod > _______________________________________________ > core mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/core >
_______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
