Document: draft-ietf-lisp-rfc6831bis Title: The Locator/ID Separation Protocol (LISP) for Multicast Environments Reviewer: Dave Thaler Review result: Ready with Issues
I am the assigned int-dir reviewer for this draft. These comments were written with the intent of improving the Internet area aspects of the IETF drafts. Please treat these comments just like any other last call comments. For background on int-dir, please see the [FAQ](https://wiki.ietf.org/en/group/intdir). Overall I found the document to be well written and fairly easy to read, at least for someone familiar with multicast terminology and protocols :) That said, there were a number of typos and grammatical errors throughout. A marked up PDF with my comments inline is at https://tinyurl.com/dthaler I won't repeat the editorial nits here, they're in the marked up PDF. Non-trivial comments include: 1. The last paragraph of the ITR definition implies an ITR can be on the path between a source in the site, and receivers in the same site. Assuming that is intentional, it could be worded more clearly to show it is intended. 2. The ETR definition on page 6 implies that PIM is the only multicast protocol supported within a site. If true, I'd recommend stating that explicitly on or before page 6. 3. Section 7.1 uses two references in a way that appears normative but the references are in the informative references section. 4. Section 9.1.5 ends with stating two solution space options, which comes across (to me anyway) as implying it's an open issue in this draft. How is the choice between these options made? Who decides? Is it left for future work? Is the answer somewhere in this draft? (If so, I missed it.) 5. Section 12 also talks about behavior that is "to be determined" so similarly comes across as an open issue. For this one, I think just saying "left for future work" instead of "to be determined" would suffice, although it does leave a real operational gap in my view. Dave _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
