Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 7C58250; Thu, 08 Oct 2026 15:59:26 +0000 (UTC) Authentication-Results: mx.ietf.org; dkim=pass header.d=akayla.com header.s=pair-202402141610 header.b=breyXh26; spf=pass (mx.ietf.org: domain of peter@akayla.com designates 66.39.134.11 as permitted sender) smtp.mailfrom=peter@akayla.com; dmarc=none Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id EBA4E16047A; Thu, 8 Oct 2026 11:59:19 -0400 (EDT) Received: from [192.168.168.225] (server.houseofyee.com [173.8.184.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 42D98126F12; Thu, 8 Oct 2026 11:59:19 -0400 (EDT) User-Agent: Microsoft-MacOutlook/16.113.26091740 Date: Thu, 08 Oct 2026 08:59:16 -0700 From: Peter Yee To: "Karstens, Nate" , "gen-art@ietf.org" Message-ID: <53DC3231-5124-4A33-BBAD-0E2624774A4A@akayla.com> Thread-Topic: [pim] draft-ietf-pim-ipv6-zeroconf-assignment-12 ietf last call Genart review References: <179126056725.296333.12275206801827357724@dt-datatracker-6f6546fbc7-hm9tb> In-Reply-To: Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3874294759_1473579836" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akayla.com; h=date:subject:from:to:cc:message-id:references:in-reply-to:mime-version:content-type; s=pair-202402141610; bh=vk/L8Wwo942Kar3pKqCQIPBqi76JsXVR8DPhL6MPy/U=; b=breyXh26jIsMcLWEiKBkKj88XAQ9cd0TfiosGQSwnx7RQh22XnIir/oRiar87kn6n1vC+AiH0LS29ZNRzw8Oa6+IPAzyWOf9xMGP7W8uN56dS1inmksfxgFznVp9Kr4w3Ogz/QvGWeL6ntPLQb4ekG+Ob/HZqlOEgEm2L9+42+holw9C79hcIePSDM7fB1nPSubqHov0uRnhYmYpUCUUhYIAkkpNvGO0JT7TgRYIK/C1HZa5dpJQnYqRllKnLrreI0Pijf9UPmz0N6waIwckLh90IB6JslK8JSlfw3ITkMDnnrvqBg6yngcrfU9Ou/zFwQMHvtNY3vof7vaATXmdHg== X-Scanned-By: mailmunge 3.11 on 66.39.134.11 X-Spamd-Bar: ------------------ Message-ID-Hash: 7WY3F743QIOMKW4XHF7ULACBBW2KRUAM X-Message-ID-Hash: 7WY3F743QIOMKW4XHF7ULACBBW2KRUAM X-MailFrom: forwardingalgorithm@dmarc.ietf.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-gen-art.ietf.org-0; header-match-gen-art.ietf.org-1; header-match-gen-art.ietf.org-2; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "draft-ietf-pim-ipv6-zeroconf-assignment.all@ietf.org" , "last-call@ietf.org" , "pim@ietf.org" X-Mailman-Version: 3.3.10 Precedence: list Subject: [Gen-art] Re: [pim] draft-ietf-pim-ipv6-zeroconf-assignment-12 ietf last call Genart review List-Id: "GEN-ART: General Area Review Team" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3874294759_1473579836 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable Thanks for addressing my concerns, Nate. Looks good to me. =20 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -Peter =20 On 10/8/26, 7:46=E2=80=AFAM, "Karstens, Nate" wrote: =20 Thanks, Peter! =20 We submitted draft-ietf-pim-ipv6-zeroconf-assignment-13 (https://datatracke= r.ietf.org/doc/draft-ietf-pim-ipv6-zeroconf-assignment/) to address your fee= dback. =20 Please see responses below. =20 Cheers, =20 Nate =20 From: Peter Yee via Datatracker =20 Sent: Monday, October 5, 2026 23:23 To: gen-art@ietf.org Cc: draft-ietf-pim-ipv6-zeroconf-assignment.all@ietf.org; last-call@ietf.or= g; pim@ietf.org Subject: [pim] draft-ietf-pim-ipv6-zeroconf-assignment-12 ietf last call Ge= nart review =20 Document: draft-ietf-pim-ipv6-zeroconf-assignment Title: Zero-Configuration= Assignment of IPv6 Multicast Addresses Using mDNS Reviewer: Peter Yee Revie= w result: Ready with Issues I am the assigned Gen-ART reviewer for this draf= t. The General =20 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 =20 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. =20 For more information, please see the FAQ at =20 . =20 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 =20 Summary: This draft is well written, specifying a means of using mDNS in th= e dynamic assignment of IPv6 multicast addresses. While I have no major issue= s with the document, I do have some questions that I=E2=80=99ve noted as minor issu= es. [Ready with issues] =20 Major issues: None =20 Minor issues: =20 Page 6, section 2.7, 2nd sentence: How does the host network stack notify t= he application that a multicast Ethernet/IPv6 address has been detected? =20 NK> This is an implementation detail, but many mDNS implementations use API= s where the caller provides a callback to execute when a given action is com= plete. With the mdns-zeroconf-mcast proof-of-concept mentioned in =C2=A77, Avahi= gives a callback on line 113 that indicates the address registration was su= ccessful (https://github.com/nkarstens/mdns-zeroconf-mcast/blob/5478b2dd7325= a7384fcc0b10ec191501b8c9e376/mdns-zeroconf-mcast.c#L113). =20 Page 8, 1st paragraph: Some network infrastructure components are not capab= le 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 l= ayer 2. =20 NK> Practically speaking, switches that support multicast snooping need to = be managed switches, with their own host. =20 Nits/editorial comments: =20 General: =20 It would be better to use a section number or a combination of section numb= er 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 supp= osed to indicate a link. I notice this because I review using the text version o= f the draft. Obviously, this doesn't matter when using the HTML version. =20 Specific: =20 Page 4, last paragraph before section 2.1: change the colon to a period. =20 NK> Done! =20 Page 10, section 5.1, 2nd paragraph, 1st sentence: change =E2=80=9Csignficant=E2=80=9D = to =E2=80=9Csignificant=E2=80=9D. =20 NK> Done! =20 _______________________________________________ pim mailing list -- pim@ietf.org To unsubscribe send an email to pim-leave@ietf.org =20 CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use= of the intended recipient(s) and contain information that may be Garmin con= fidential and/or Garmin legally privileged. If you have received this email = in error, please notify the sender by reply email and delete the message. An= y disclosure, copying, distribution or use of this communication (including = attachments) by someone other than the intended recipient is prohibited. Tha= nk you. --B_3874294759_1473579836 Content-type: text/html; charset="UTF-8" Content-transfer-encoding: quoted-printable

Thanks for addressing my concerns, Nate. Lo= oks good to me.

 

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 = -Peter

 

On 10/8/26, 7:46=E2=80=AFAM, "Karstens, Na= te" <Nate.Karstens@garmin.= com> wrote:

 

Thanks, Peter!

 

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

 

Please see responses below.

 

Cheers,

<= span style=3D'font-size:11.0pt'> 

Nate

 

= From: Peter Yee via Datatracker <noreply@ietf.org>
Sent: Mon= day, October 5, 2026 23:23
To: gen-art@ietf.org
Cc: draf= t-ietf-pim-ipv6-zeroconf-assignment.all@ietf.org; last-call@ietf.org; pim@ie= tf.org
Subject: [pim] draft-ietf-pim-ipv6-zeroconf-assignment-12 i= etf 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 as= signed Gen-ART reviewer for this draft. The General

 

Document: dr=
aft-ietf-pim-ipv6-zeroconf-assignment
Title: Zero-Configuratio=
n Assignment of IPv6 Multicast Addresses Using mDNS
<= pre>Reviewer: = Peter Yee
Review result: Ready with Issues
=
 
I am the assigned Gen-ART reviewer for this draft. The Gener=
al 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://url=
defense.com/v3/__https://wiki.ietf.org/en/group/gen/GenArtFAQ__;!!EJc4YC3iFm=
Q!TKas4oDACX5ScSCtujRR-jerc5WQ8Mb8qn_7a0oWlD_SvlnZnox2juPey8V_VhTkEp2txb5wVd=
JZqFSXCQ$>.
 
Document: draft-ietf-p=
im-ipv6-zeroconf-assignment-12
Reviewer: Peter Yee<=
/span>
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 u=
sing mDNS in the
dynamic assignment of IPv6 multicast addresse=
s. While I have no major issues
with the document, I do have s=
ome questions that I=E2=80=99ve noted as minor issues.
[Ready with i=
ssues]
 
Major issues: None
<=
o:p> 
Minor issues:
 
Page 6,=
 section 2.7, 2nd sentence: How does the host network stack notify the<=
/o:p>
application that a multicast Ethernet/IPv6 address has been detecte=
d?
 
NK> This is an implem=
entation detail, but many mDNS implementations use APIs where the caller pro=
vides a callback to execute when a given action is complete. With the mdns-z=
eroconf-mcast proof-of-concept mentioned in =C2=A77, Avahi gives a callback on l=
ine 113 that indicates the address registration was successful (http=
s://github.com/nkarstens/mdns-zeroconf-mcast/blob/5478b2dd7325a7384fcc0b10ec=
191501b8c9e376/mdns-zeroconf-mcast.c#L113).
&n=
bsp;
Page 8, 1st paragraph: Some network infrastructure components =
are not capable
of publishing veto records. The example compon=
ent given in section 3.1, 1st
paragraph is a network switch, w=
hich might not have a network stack above layer
=
2.<=
/span>
 
NK> Practically speaking, switches =
that support multicast snooping need to be managed switches, with their own =
host.
 
Nits/editorial comments:=

 
General:
 
It woul=
d be better to use a section number or a combination of section number<=
/o:p>
and section name for links because not all RFC formats support hype=
rlinks, and
it may not be obvious that a capitalized section n=
ame in a sentence is supposed
to indicate a link. I notice thi=
s because I review using the text version of
the draft. Obviou=
sly, this doesn't matter when using the HTML version.
&nb=
sp;
Specific:
 
Page 4, last parag=
raph before section 2.1: change the colon to a period.
&n=
bsp;
NK> Done!
 
=
Page 10, section 5.1, 2nd paragraph, 1st sentence: change =E2=80=9Csignficant=E2=80=9D t=
o
=E2=80=9Csignificant=E2=80=9D.
 
NK> Done!
 
____________________=
___________________________
pim mailing list -- pim@ietf.org
To unsubscribe send an email =
to pim-leave@ietf.org
 =

=


CONFIDENTIALITY NOTICE: This email and any attachments ar=
e 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 re=
ceived this email in error, please notify the sender by reply email and dele=
te the message. Any disclosure, copying, distribution or use of this communi=
cation (including attachments) by someone other than the intended recipient =
is prohibited. Thank you.

=
--B_3874294759_1473579836--