IETF Last Call Review of draft-ietf-pim-ipv6-zeroconf-assignment-15
review-ietf-pim-ipv6-zeroconf-assignment-15-opsdir-lc-liu-2026-10-26-00
review-ietf-pim-ipv6-zeroconf-assignment-15-opsdir-lc-liu-2026-10-26-00
Hi, I have been selected as the Operational Directorate (opsdir) reviewer for this Internet-Draft. The Operational Directorate reviews all operational and management-related Internet-Drafts to ensure alignment with operational best practices and that adequate operational considerations are covered. A complete set of _"Guidelines for Considering Operations and Management in IETF Specifications"_ can be found at https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5706bis/. While these comments are primarily for the Operations and Management Area Directors (Ops ADs), the authors should consider them alongside other feedback received. - Document: [draft-karstens-pim-ipv6-zeroconf-assignment-13] - Reviewer: [Will LIU] - Review Date: [Oct 8] - Intended Status: [Standards Track] --- ## Summary - Has Nits: This document is basically ready for publication but has nits that should be considered prior to publication. --- This document defines a zero-configuration method for dynamically assigning multicast addresses with mDNS. The protocol procedures are well described and clear in scope. However, from an OPSDIR perspective, the draft currently lacks a dedicated Operational Considerations section, as suggested by draft-ietf-opsawg-rfc5706bis. Such a section is essential to help network operators understand the real-world deployment, monitoring, and management aspects of this protocol. 1.Missing Dedicated Operational Considerations Section: In accordance with draft-ietf-opsawg-rfc5706bis, the draft should include a dedicated Operational Considerations section.The protocol deployment involves real-world multicast and mDNS interactions that operators need guidance on, particularly regarding troubleshooting, visibility, and network impact. 2.Leveraging and Expanding RFC 10019 Evaluation Points: Section 5 provides useful statements on how the protocol satisfies the requirements set forth in RFC 10019.Several of these statements—such as Zero User Configuration and Coexistence with Multicast Address Allocation Solutions—have strong operational implications. These relevant points should be further discussed and integrated into the new Operational Considerations section rather than confined solely to requirement evaluation. 3.Reorganization of Section 5.1: Section 5.1 contains deployment-relevant insights and discussions. It would fit much more naturally if moved into the proposed Operational Considerations section to provide a centralized reference for operators.