Document: draft-ietf-pim-zeroconf-mcast-addr-alloc-ps Title: Zeroconf Multicast Address Allocation Problem Statement and Requirements Reviewer: Joel Halpern 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-zeroconf-mcast-addr-alloc-ps-07 Reviewer: Joel Halpern Review Date: 2025-10-07 IETF LC End Date: 2025-10-17 IESG Telechat date: Not scheduled for a telechat Summary: This document is readable and in good shape. I have a minor comment for your consideration Major issues: N/A Minor issues: Section 2i s called "Address Collision. Seeing as tis is an IETF draft, I had started out assuming this was about two groups self-assigning the same IP Multicast address. However, the text is entirely about collision on the derived MAC address. Could the title be clarified? I am not sure, but it may be that the document assumes there is already a way to provide zeroconf IP multicast address that are collision free. In which case the only colissions are MAAC level. If that is the assumption, it should be stated with references. If that is not assumed, then some discussion of the IP level allocation requirements would seem appropriate. Nits/editorial comments: _______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
