Skip to main content

Last Call Review of draft-ietf-pim-explicit-rpf-vector-07

Request Review of draft-ietf-pim-explicit-rpf-vector
Requested revision No specific revision (document currently at 09)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2015-12-23
Requested 2015-12-10
Authors Javed Asghar , IJsbrand Wijnands , Sowmya Krishnaswamy , Apoorva Karan , Vishal Arya
I-D last updated 2015-12-22
Completed reviews Secdir Last Call review of -07 by Rifaat Shekh-Yusef (diff)
Assignment Reviewer Rifaat Shekh-Yusef
State Completed
Request Last Call review on draft-ietf-pim-explicit-rpf-vector by Security Area Directorate Assigned
Reviewed revision 07 (document currently at 09)
Result Has issues
Completed 2015-12-22
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 Security Consideration section points to the security consideration

of the ietf-pim-rfc4601bis document, which seems reasonable as this document 

adds new attribute to the existing PIM Join message.

The document then states the following:

"In order to minimize the risk of a malicious node injecting an incorrect

Explicit RPF vector stack, it should be used within a single management


You might want to elaborate a bit on how does a single management domain

help minimize this risk.

Also, the security consideration section in ietf-pim-rfc4601bis document

discusses the impact of a forget Join message and its implication on the

multicast traffic. You might want to add some text to explain if this new

attribute, defined in this document, changes the implication of a forged

Join message or not; if it does, you might want to explain how.