On 28/10/2022 07:31, Hongji Zhao wrote: > Hi Tom > > Thanks a lot for your comments. > > The last submission time for the I-D submission was 2022-10-24 23:59 UTC, so I couldn't update the draft now. I will update it as long as I-D submission is available. You might want to wait until the end of Last Call so that all comments are made against the same version, even if the same comments are made more than once. Some ADs like this approach, others like the I-D to be updated as it goes. I do not know what the answer is for addresses in IPv4 examples, short of writing an I-D to ask IANA to assign a block (when the submission window opens:-). This is not an issue for most WG but seems to be so here. I see other uses of 225. but think that wrong. Tom Petch > BR/Hongji > > -----Original Message----- > From: tom petch <daedulus@xxxxxxxxxxxxx> > Sent: 2022年10月27日 19:57 > > On 25/10/2022 20:27, The IESG wrote: >> >> The IESG has received a request from the Protocols for IP Multicast WG >> (pim) to consider the following document: - 'A Yang Data Model for IGMP/MLD Proxy' >> <draft-ietf-pim-igmp-mld-proxy-yang-07.txt> as Proposed Standard >> >> The IESG plans to make a decision in the next few weeks, and solicits >> final comments on this action. Please send substantive comments to the >> last-call@xxxxxxxx mailing lists by 2022-11-15. Exceptionally, >> comments may be sent to iesg@xxxxxxxx instead. In either case, please >> retain the beginning of the Subject line to allow automated sorting. > > The formatting of this I-D seems a little out w.r.t newlines (an unsolved problem of the Internet). It was present to a small extent in > -06 but is present more here, as in for example Security Considerations where the paragraphs starting 'Under...' are double line-spaced. > > The examples use an address of 225.0.0 which is reserved and I do not think should be used. AFAICT there are no multicast addresses reserved for documentation use - I note that RFC8916 uses 233.252 > > The YANG module references the Simplified BSD license which should now be the Revised BSD License (although the tool set is not very helpful here) > > s.3.1 and s.3.2 mention that there is a constraint on the upstream interface to make sure it is not configured to use PIM. The YANG has 'must not' which seems fine but the YANG description clause says 'should not', which, in IETF jargon, is not the same thing. > > > Tom Petch > > >> Abstract >> >> This document defines a YANG data model that can be used to >> configure and manage Internet Group Management Protocol (IGMP) or >> Multicast Listener Discovery (MLD) proxy devices. The YANG module in >> this document conforms to Network Management Datastore Architecture >> (NMDA). >> >> The file can be obtained via >> https://datatracker.ietf.org/doc/draft-ietf-pim-igmp-mld-proxy-yang/ >> >> No IPR declarations have been submitted directly on this I-D. >> >> _______________________________________________ >> IETF-Announce mailing list >> IETF-Announce@xxxxxxxx >> https://www.ietf.org/mailman/listinfo/ietf-announce >> . > . > -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
