Document: draft-ietf-pim-ipv6-zeroconf-assignment Title: Zero-Configuration Assignment of IPv6 Multicast Addresses Using mDNS Reviewer: Peter Yee Review result: Ready with Issues
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://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-pim-ipv6-zeroconf-assignment-12 Reviewer: Peter Yee Review Date: 2026-10-05 IETF LC End Date: 2026-10-06 IESG Telechat date: Not scheduled for a telechat Summary: This draft is well written, specifying a means of using mDNS in the dynamic assignment of IPv6 multicast addresses. While I have no major issues with the document, I do have some questions that I’ve noted as minor issues. [Ready with issues] Major issues: None Minor issues: Page 6, section 2.7, 2nd sentence: How does the host network stack notify the application that a multicast Ethernet/IPv6 address has been detected? Page 8, 1st paragraph: Some network infrastructure components are not capable of publishing veto records. The example component given in section 3.1, 1st paragraph is a network switch, which might not have a network stack above layer 2. Nits/editorial comments: General: It would be better to use a section number or a combination of section number and section name for links because not all RFC formats support hyperlinks, and it may not be obvious that a capitalized section name in a sentence is supposed to indicate a link. I notice this because I review using the text version of the draft. Obviously, this doesn't matter when using the HTML version. Specific: Page 4, last paragraph before section 2.1: change the colon to a period. Page 10, section 5.1, 2nd paragraph, 1st sentence: change “signficant” to “significant”. _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
