Last Call Review of draft-ietf-teas-rsvp-ingress-protection-13
review-ietf-teas-rsvp-ingress-protection-13-secdir-lc-salowey-2018-02-27-00

Request Review of draft-ietf-teas-rsvp-ingress-protection
Requested rev. no specific revision (document currently at 17)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2018-03-01
Requested 2018-02-15
Authors Huaimo Chen, Raveendra Torvi
Draft last updated 2018-02-27
Completed reviews Rtgdir Last Call review of -11 by Tomonori Takeda (diff)
Secdir Last Call review of -13 by Joseph Salowey (diff)
Genart Last Call review of -13 by Robert Sparks (diff)
Assignment Reviewer Joseph Salowey
State Completed
Review review-ietf-teas-rsvp-ingress-protection-13-secdir-lc-salowey-2018-02-27
Reviewed rev. 13 (document currently at 17)
Review result Ready
Review completed: 2018-02-27

Review
review-ietf-teas-rsvp-ingress-protection-13-secdir-lc-salowey-2018-02-27

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.

In general I felt that the document was a bit difficult to read and the issues raised in the Genart and RTG reviews should be addressed.  

From a security point of view I believe the document is ready, but I have a comment below that might improve the document. 

I find the security considerations as reference to other documents a bit unsettling, however, based on my somewhat limited understanding of RSVP it think it is accurate in this case.  The problem I have with the security considerations as reference is that most implementors are probably are not going to follow the links to the other documents to find out what security wisdom lies therein.   If the document pointed to specific considerations in other documents that were particularly relevant to this document that would be an improvement.  I couldn't work my way back through the chain of references to something specific, but someone with a bit more RSVP domain knowledge may be able to make some specific recommendations.