[pim] Re: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07 ietf last call Secdir review

Russ,

Thanks for reviewing the document! We addressed your concerns in draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-09, please let us know if you have any additional concerns.

Cheers,

Nate

From: Russ Housley via Datatracker <[email protected]>
Sent: Monday, November 24, 2025 09:27
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 Secdir review

Document: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id Title: Updates to Dynamic IPv6 Multicast Address Group IDs Reviewer: Russ Housley Review result: Ready I reviewed this document as part of the Security Directorate's ongoing effort to


Document: draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id

Title: Updates to Dynamic IPv6 Multicast Address Group IDs

Reviewer: Russ Housley

Review result: Ready



I reviewed this document as part of the Security Directorate's ongoing

effort to review all IETF documents being processed by the IESG.  These

comments were written primarily for the benefit of the Security Area

Directors.  Document authors, document editors, and WG chairs should

treat these comments just like any other IETF Last Call comments.



Document:          draft-ietf-pim-updt-ipv6-dyn-mcast-addr-grp-id-07

Reviewer: Russ Housley

Review Date: 2025-11-24

IETF LC End Date: 2025-11-28

IESG Telechat date: unknown



Summary: Ready





Major Concerns:  None





Minor Concerns:



Section 3:  This document point to RFC 3307, and RFC 3307 point to

RFC 2908 for a more in-depth discussion of the security issues

surrounding dynamic allocation of multicast addresses.  Be kind to

the reader and include the pointer to RFC 2908 here.





Nits:



Abstract: s/Describes/This document describes/



Abstract: s/Recommends/This document recommends/



Abstract: s/Suggests/This document suggests/



Section 2: s/[RFC3307], Section 4.3/Section 4.3 of [RFC3307]/ (twice)



Section 2: s/[RFC4291], Section 2.7.1/Section 2.7.1 of [RFC4291]/



Table 2: s/[RFC4291], Section 2.7.1/Section 2.7.1 of [RFC4291]/



Section 5: In the first paragraph "this research" is very unclear.  Since

this document is about address allocation, I would hope there is something

associated with the document that can be said.



Section 5: s/draft/document/







_______________________________________________

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]