Sue, Thanks for your comments and your offer to work this out in a videoconference. I’ve reached out a few times to set this up and didn’t hear back – perhaps it’s being blocked as SPAM?
Replies to your individual points are below, marked [NLK]. We uploaded a new version of the document to reflect your comments: https://datatracker.ietf.org/doc/draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id/ Cheers, Nate From: Sue Hares via Datatracker <[email protected]> Sent: Tuesday, December 9, 2025 16:35 To: [email protected] Cc: [email protected]; [email protected]; [email protected] Subject: [pim] draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07 ietf last call Genart review Document: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id Title: Updates to Dynamic IPv6 Multicast Address Group IDs Reviewer: Sue Hares Review result: Not Ready I am the assigned Gen-ART reviewer for this draft. The General Area Review Team Document: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id Title: Updates to Dynamic IPv6 Multicast Address Group IDs Reviewer: Sue Hares Review result: Not Ready 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://urldefense.com/v3/__https://wiki.ietf.org/en/group/gen/GenArtFAQ__;!!EJc4YC3iFmQ!XujEKwW94bOsbQyHUugAP45xRcFq9MvUm_YodYZJBLkmHNMy6uwpjDIAs0DogkRnkBJJ50p_czkUg8Y0hA$<https://urldefense.com/v3/__https:/wiki.ietf.org/en/group/gen/GenArtFAQ__;!!EJc4YC3iFmQ!XujEKwW94bOsbQyHUugAP45xRcFq9MvUm_YodYZJBLkmHNMy6uwpjDIAs0DogkRnkBJJ50p_czkUg8Y0hA$>>. Document: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-?? Reviewer: Sue Hares Review Date: 2025-12-09 IETF LC End Date: 2025-11-28 IESG Telechat date: Not scheduled for a telechat Summary: Not Ready Two Major issues bring the draft to this state: 1) alignment with IANA considerations guidelines in RFC8126 (see RFC9778's interpretation of RFC8126). 2) I'm confused by how this document updates the registries in the IPv6 Multicast Address space. I am happy to work with the author team on a video conference to help them quickly resolve this issue. Major issues: 1) Alignment with IANA considerations guidelines in RFC8126 (see RFC9778's interpretation of RFC8126) Section 4 contains a registry group (IPv6 Multicast Address Space Registry) and the new registry name (Dynamic Multicast Group IDs). However, it does not put all the information into the formats I expected. It goes against the guidelines from RFC8126 by not putting all the information needed in the IANA considerations section. [NLK] The main thing that was missing was description of the fields in the registry. This has been added by the latest version. Please let me know if there was something else we missed as well. 2) Updating the current registries in the IPv6 Multicast Address Space Registry. I cannot determine from the text how the current registries (IPv6 Multicast Address Scopes, Node-Local Scope Multicast Addresses, Link-Local Scope Multicast Addresses, Site-Local Scope Multicast Addresses, and Variable Scope Multicast Addresses) interact with the new registry. [NLK] These registries are all related to values used to construct IPv6 multicast addresses. IPv6 Multicast Address Scopes is related to the second octet in the address. The other registries you listed are related to the last 32 bits of the address (the group ID), each scope getting its own registry. The values assigned in these registries should be constrained to 0-0x3FFFFFFF to reflect the “Permanent IPv6 Multicast Addresses” outlined in RFC 3307. The one entry that seems to deviate from this is for “ISO 25750 Secured Ship Network”, which was added after the initial draft of our document. We will follow up with this. [/NLK] There is overlap in the proposed address ranges (0xFF000000 to 0xFFFFFFFF), and this draft's text does not clearly describe how the existing registries interact with the new table. [NLK] Table 1 of this document reflects current effective assignments and notes an overlap in address ranges. Table 2 reflects the initial values for the new registry and there should not be any remaining entries that overlap. The authors may have thought through this carefully, but I cannot determine this interaction. 3) After the authors finish reworking the text to fix issues 1 and 2, please remember to go through how the "Unicast-based (Including SSM) Multicsat Group IDs" registry needs to be updated. [NLK] The changes to this registry recommended don’t necessarily reflect a formal “update”, it provides more information about an existing entry. Either way, I could be mistaken in how I’m reading this, but only the first entry requires expert review: FF3X:0:0:0:0:0:4000:0-FF3X:0:0:0:0:0:7FFF:FFFF - Expert Review; see registry at [https://www.iana.org/assignments/perm-mcast-groupids] The second entry just contains a note: FF3X:0:0:0:0:0:8000:0-FF3X:0:0:0:0:0:FFFF:FFFF - Dynamically allocated by hosts when needed [RFC4607]. [/NLK] in the IPv6 Multicast Address Space Minor issues: none Nits/editorial comments: The sentence structure of the Abstract lacks subjects in sentences 1, 2, and 3. This makes reading the text like reading a bullet list rather than a description. Possible fixes: sentence 1: Old: /Describes/ New: /This document describes/ sentence 2: Old: /Recommends/ New: /It Recommends/ Sentence 3: Old: / Suggests/ New: /It also suggests/ _______________________________________________ pim mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]> ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.
_______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
