Reviewer: Vijay Gurbani Review result: Almost Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-6tisch-msf-10 Reviewer: Vijay K. Gurbani Review Date: 2020-02-14 IETF LC End Date: 2020-02-27 IESG Telechat date: Not scheduled for a telechat Summary: The draft is almost ready to be published as a Proposed Standard. Major issues: 1 Minor issues: 0 Nits/editorial comments: 1 Sn below stands for "Section n". Major: - S2, paragraph 4: The text says that "...a node implementing MSF SHOULD enforce some rules for limiting the traffic broadcast frames...". It goes ahead and gives an example of the "Trickle" operation, but in the very next sentence, it says, "This behavior is out of the scope for MSF." I am confused since the paragraph does not seem self consistent. The paragraph is asking the implementor to use normative strength (SHOULD) to enforce "some" rules, but does not enumerate the rules. To be fair, the paragraph gives one example of such a rule, but immediately invalidates that example! What would an implementor do? Where would he or she go to get an idea of "some" rules that can be used to limit the traffic of broadcast frames? Perhaps some reference could be provided to a document that contains these rules? Nits: - S6: s/It is calculated/The timeout value is calculated/ Thank you. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
