Last Call Review of draft-ietf-pim-light-08
review-ietf-pim-light-08-opsdir-lc-hares-2024-10-20-00
Request | Review of | draft-ietf-pim-light |
---|---|---|
Requested revision | No specific revision (document currently at 10) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2024-10-18 | |
Requested | 2024-10-04 | |
Authors | Hooman Bidgoli , Stig Venaas , Mankamana Prasad Mishra , Zhaohui (Jeffrey) Zhang , Mike McBride | |
I-D last updated | 2024-10-20 | |
Completed reviews |
Rtgdir Last Call review of -06
by Henning Rogge
(diff)
Genart Last Call review of -08 by Mallory Knodel (diff) Secdir Last Call review of -08 by Chris M. Lonvick (diff) Opsdir Last Call review of -08 by Susan Hares (diff) Tsvart Last Call review of -08 by Michael Tüxen (diff) |
|
Assignment | Reviewer | Susan Hares |
State | Completed | |
Request | Last Call review on draft-ietf-pim-light by Ops Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/rD4o2ZnsOmQuoUMDJOy3gw8nFJc | |
Reviewed revision | 08 (document currently at 10) | |
Result | Has issues | |
Completed | 2024-10-20 |
review-ietf-pim-light-08-opsdir-lc-hares-2024-10-20-00
Summary Statement: I'm pleased to see this work combining PIM domains and Bier domains. The one technical issue is how operators tell if things go wrong. Technical Issue: This is one document that needs a manageability section. Can you include answers to the following question an operator might ask before deployment? 1) How do I detect if the PLI interface is misconfigured or has an error in the following cases: a) DR election error b) packet duplication c) unexpected repeated drops d) failures in PIM domains. Editorial issues: 1. Section 3.2.2, paragraph 2, sentences 1, and 2. Error: Run-on sentence with errors in comma usage Old text:/ For instance, in a BIER domain connecting two PIM networks, a PLI can be used between BIER edge routers solely for multicast state communication, transmitting only PIM Join/Prune messages. To prevent multicast stream duplication, PIM routers on either side of the BIER domain should establish PIM adjacency as per [RFC7761] to ensure DR election at the edge of BIER domain, as an example DR election between router D and F in above figure. / New text:/ For instance, in a BIER domain connecting two PIM networks, a PLI can be used between BIER edge routers solely for multicast state communication and transmit only PIM Join/Prune messages. To prevent multicast stream duplication, PIM routers on either side of the BIER domain should establish PIM adjacency as per [RFC7761] to ensure DR election at the edge of BIER domain. An example of this DR election could be DR election between router D and F in above figure./ 2. Section 3.3, sentence 2, lack of logic clarity If the PLI is enabled on an interface and Join/Prune message arrive, what other options exist except to process the message or to drop the message? If there are others, then this sentence needs to be changed. 3. section 3.4 paragraph 3, starting In another example, grammar error. Old text:/ In another example, if PLI is configured automatically, as an example in BIER case, when the downstream BIER Edge Router (DBER) is no longer reachable, the upstream BIER Edge Router (UBER) which is also a PIM Light Router can prune the <S,G> advertised toward the source on the PIM domain to stop the transmission of the multicast stream./ The commas and the run-on sentence make this paragraph unclear. Due to the text's unclear nature, I cannot understand the technical point. 4. Section 3.5, paragraph 4, sentence 1, wrong use of active verb (lacking) Old text:/ PIM Light lacking Hello messages, the PLI can be configured with the Connection ID IPv4 or IPv6 addresses used to establish the SCTP or TCP connection. / New text: PIM Light lacks Hello messages, the PLI can be configured with the Connection ID IPv4 or IPv6 addresses used to establish the SCTP or TCP connection./