Thanks, Peter!

We submitted draft-ietf-pim-ipv6-zeroconf-assignment-13 
(https://datatracker.ietf.org/doc/draft-ietf-pim-ipv6-zeroconf-assignment/) to 
address your feedback.

Please see responses below.

Cheers,

Nate

From: Peter Yee via Datatracker <[email protected]>
Sent: Monday, October 5, 2026 23:23
To: [email protected]
Cc: [email protected]; [email protected]; 
[email protected]
Subject: [pim] draft-ietf-pim-ipv6-zeroconf-assignment-12 ietf last call Genart 
review

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


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://urldefense.com/v3/__https://wiki.ietf.org/en/group/gen/GenArtFAQ__;!!EJc4YC3iFmQ!TKas4oDACX5ScSCtujRR-jerc5WQ8Mb8qn_7a0oWlD_SvlnZnox2juPey8V_VhTkEp2txb5wVdJZqFSXCQ$<https://urldefense.com/v3/__https:/wiki.ietf.org/en/group/gen/GenArtFAQ__;!!EJc4YC3iFmQ!TKas4oDACX5ScSCtujRR-jerc5WQ8Mb8qn_7a0oWlD_SvlnZnox2juPey8V_VhTkEp2txb5wVdJZqFSXCQ$>>.



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?



NK> This is an implementation detail, but many mDNS implementations use APIs 
where the caller provides a callback to execute when a given action is 
complete. With the mdns-zeroconf-mcast proof-of-concept mentioned in §7, Avahi 
gives a callback on line 113 that indicates the address registration was 
successful 
(https://github.com/nkarstens/mdns-zeroconf-mcast/blob/5478b2dd7325a7384fcc0b10ec191501b8c9e376/mdns-zeroconf-mcast.c#L113).



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.



NK> Practically speaking, switches that support multicast snooping need to be 
managed switches, with their own host.



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.



NK> Done!



Page 10, section 5.1, 2nd paragraph, 1st sentence: change “signficant” to

“significant”.



NK> Done!



_______________________________________________

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]

Reply via email to