From: Christian Hopps <[email protected]> Sent: 27 March 2020 17:39 > On Mar 27, 2020, at 1:09 PM, tom petch <[email protected]> wrote: > > Kent > > Not Ready > > e.g. > IANA considerations does not register the namespace so there is no module Will add. <tp> RFC8344 gets that right - note the reference to RFC6020
> Security Considerations does not use template (which other grouping modules > such as Kent's do) I've pinged Kent for a pointer. <tp> and Kent has responded > No YANG version This means it defaults to 1.0 I thought. <tp> RFC8407 template has 1.1 and says that that is a SHOULD > Wrong prefix for ietf-yang-types Will change the groupings use from "types" to "yang". <tp> yes please that is a MUST in RFC8407 > No reference clause for yang types Do you mean inside the import ietf-yang-types statement? <tp> yes that is a SHOULD in RFC8407 > 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? <tp> A good starting point is any reference in the body of the I-D should be in the YANG module too in a reference clause, such as www.iau.org, IS6709, WGS84 and may be more than once for different description clauses. velocity could include the formula or refer back to RFCXXXX perhaps timestamp too. RFC8344 has enough (but not too many IMHO). > 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. <tp> Normative reference for an import is MUST in RFC8407 and you will need to add a reference in the body of the I-D to avoid unused reference; RFC8344 s.4 gets that right > 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. :) <tp> Note the point about naming, a two tier structure with the top level being key. Historically, many significant registries have been given unfortunate names making the data scattered and hard to find (SNMP). Whether this should be a top level on its own of whether it should fall under something more generic, such as orphan YANG registries, I would be interested to hear other views on. Tom Petch 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
