[pim] Re: Deb Cooley's Discuss on draft-ietf-pim-zeroconf- mcast-addr-alloc-ps-09: (with DISCUSS and COMMENT)

Deb,

Thanks for your comments! Please see replies inline and denoted with [NLK]. We posted version -10 for further consideration.

Best Regards,

Nate

From: Deb Cooley via Datatracker <[email protected]>
Sent: Thursday, November 20, 2025 06:15
To: The IESG <[email protected]>
Cc: [email protected]; [email protected]; [email protected]
Subject: [pim] Deb Cooley's Discuss on draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-09: (with DISCUSS and COMMENT)

Deb Cooley has entered the following ballot position for draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-09: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free


Deb Cooley has entered the following ballot position for

draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-09: Discuss



When responding, please keep the subject line intact and reply to all

email addresses included in the To and CC lines. (Feel free to cut this

introductory paragraph, however.)





Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!Tb1-qOrjAWHrUiQjjttgN8j0GwcAl9SBPMfVlNi72qrMio3lNnVkyJj5k6H1j4y6H0CGz-x-hg3ZbbDWzw$<https://urldefense.com/v3/__https:/www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!EJc4YC3iFmQ!Tb1-qOrjAWHrUiQjjttgN8j0GwcAl9SBPMfVlNi72qrMio3lNnVkyJj5k6H1j4y6H0CGz-x-hg3ZbbDWzw$>

for more information about how to handle DISCUSS and COMMENT positions.





The document, along with other ballot positions, can be found here:

https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/__;!!EJc4YC3iFmQ!Tb1-qOrjAWHrUiQjjttgN8j0GwcAl9SBPMfVlNi72qrMio3lNnVkyJj5k6H1j4y6H0CGz-x-hg2Bf5ihxQ$<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-pim-zeroconf-mcast-addr-alloc-ps/__;!!EJc4YC3iFmQ!Tb1-qOrjAWHrUiQjjttgN8j0GwcAl9SBPMfVlNi72qrMio3lNnVkyJj5k6H1j4y6H0CGz-x-hg2Bf5ihxQ$>







----------------------------------------------------------------------

DISCUSS:

----------------------------------------------------------------------



This should be easily addressed, it is a common issue for Informational

specifications:



With the exception of BCP 14, there are no normative references.  It would seem

that there should be at least a couple?  Perhaps RFC 3307, since the draft

doesn't actually define what a 'multicast address' is?  There might be others

as well.  I encourage the authors to consider this.  Any reference that is

necessary to understand the specification should be normative.



[NLK] Yes, I struggled with this. In the -10 document we moved several of the references into the normative section. Hopefully that helps.



----------------------------------------------------------------------

COMMENT:

----------------------------------------------------------------------



Thanks to Joe Salowey for their secdir review.  Like Paul Wouters and Joe have

stated, it appears that the security considerations doesn't really address this

potential issues.



Why not MUST?:  There are a number of SHOULDs where the rationale for why one

might not take that action is missing.



[NLK] We updated the preface to our recommendations with the underlined text:



In addition to the above, the following characteristics are considered desirable, but are left as recommendations to allow for flexibility in solution design:



Does that help?

_______________________________________________

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.

_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]