Skip to main content

IETF Last Call Review of draft-ietf-pim-zeroconf-mcast-addr-alloc-ps-07
review-ietf-pim-zeroconf-mcast-addr-alloc-ps-07-secdir-lc-salowey-2025-10-13-00

Request Review of draft-ietf-pim-zeroconf-mcast-addr-alloc-ps
Requested revision No specific revision (document currently at 13)
Type IETF Last Call Review
Team Security Area Directorate (secdir)
Deadline 2025-10-17
Requested 2025-10-03
Authors Nathan Karstens , Dino Farinacci , Mike McBride
I-D last updated 2026-02-26 (Latest revision 2026-02-17)
Completed reviews Secdir IETF Last Call review of -07 by Joseph A. Salowey (diff)
Tsvart IETF Last Call review of -07 by Dr. Joseph D. Touch (diff)
Genart IETF Last Call review of -07 by Joel M. Halpern (diff)
Opsdir Telechat review of -07 by Gabriele Galimberti (diff)
Intdir Telechat review of -07 by Benson Muite (diff)
Rtgdir Telechat review of -07 by Zhaohui (Jeffrey) Zhang (diff)
Assignment Reviewer Joseph A. Salowey
State Completed
Request IETF Last Call review on draft-ietf-pim-zeroconf-mcast-addr-alloc-ps by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/UzSZX4KWgmCg70Pjnwu862TpkjU
Reviewed revision 07 (document currently at 13)
Result Has issues
Completed 2025-10-13
review-ietf-pim-zeroconf-mcast-addr-alloc-ps-07-secdir-lc-salowey-2025-10-13-00
I have 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
editors and WG chairs should treat these comments just like any other last call
comments.

The summary of the review is the document has issues.

This document is providing requirements for Zeroconf Multicast Address
Allocation. The document's security considerations section is rather light in
that is says security will be addressed by future documents. It seems that a
requirements document should cover security aspects.

For example, it seems that address collisions could cause denial of services
issues and perhaps other security issues. It seems these consequences should be
discussed in the security considerations along with considerations for what
solutions should address to thwart and attacker from reaching these outcomes.

I don't think it needs to be a lot of text, but some guidance for solutions
derived from this document would be good.