> On Mar 27, 2020, at 1:09 PM, tom petch <[email protected]> wrote: > > Kent > > Not Ready > > I thought that so obvious that it was not worth saying:-) > > e.g. > IANA considerations does not register the namespace so there is no module
Will add. > Security Considerations does not use template (which other grouping modules > such as Kent's do) I've pinged Kent for a pointer. > No YANG version This means it defaults to 1.0 I thought. > Wrong prefix for ietf-yang-types Will change the groupings use from "types" to "yang". > No reference clause for yang types Do you mean inside the import ietf-yang-types statement? > A wholesale lack of YANG reference clauses; perhaps half a dozen needed I can see 2 places I might could put these, in the "astronomical-body" leaf that references the IAU and in the "geodetic-system" for the default value. We are creating an IANA registry for the values in geodetic-system though so perhaps you are asking for an IANA reference instead? I don't see 4 more obvious places for external references, could you help point them out? > No Normative reference for yang-types We add normative document references for imported modules that are not mentioned anywhere else in the actual document? I have no problem doing so, but I haven't done that before. > Insufficient information for IANA - I infer they are being asked to create a > registry but details seem lacking compared to the requirements in RFC8126 Thanks for pointing this out, I'll add this instead of waiting for IANA to complain. :) Thanks, Chris. > > At which point I stop and await a fresh revision before having another go. > > Tom Petch > > ________________________________________ > From: netmod <[email protected]> on behalf of Kent Watsen > <[email protected]> > Sent: 26 March 2020 18:46 > > Dear All, > > This WGLC has received zero responses, which is insufficient to progress the > document at this time. The WGLC is therefore being extended for another > week, now ending April 1st (the day before our Virtual Meeting on April 2nd). > > Again, positive comments, e.g., "I've reviewed this document and believe it > is ready for publication", are welcomed. This is useful and important, even > from authors. Objections, concerns, and suggestions are also welcomed at > this time. > > FWIW, the YANG Doctor review was completed on 3/23 (thanks Mahesh) with the > “Ready with Nits” status: > https://datatracker.ietf.org/doc/review-ietf-netmod-geo-location-04-yangdoctors-lc-jethanandani-2020-03-23. > > Kent // as shepherd and co-chair > > > > On Mar 9, 2020, at 6:30 PM, Kent Watsen > <[email protected]<mailto:[email protected]>> wrote: > > This message begins an almost two-week WGLC for > draft-ietf-netmod-geo-location-04 ending on March 22nd (the day before the > NETMOD sessions). Here is a direct link to the HTML version of the draft: > > https://tools.ietf.org/html/draft-ietf-netmod-geo-location-04 > > Positive comments, e.g., "I've reviewed this document and believe it is ready > for publication", are welcome! This is useful and important, even from > authors. Objections, concerns, and suggestions are also welcomed at this time. > > Thank you, > NETMOD Chairs > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod > > > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
