Skip to main content

Last Call Review of draft-ietf-mpls-gmpls-lsp-reroute-
review-ietf-mpls-gmpls-lsp-reroute-secdir-lc-kelly-2009-09-03-00

Request Review of draft-ietf-mpls-gmpls-lsp-reroute
Requested revision No specific revision (document currently at 06)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2009-09-08
Requested 2009-08-17
Authors JP Vasseur , Dimitri Papadimitriou , Lou Berger
Draft last updated 2009-09-03
Completed reviews Secdir Last Call review of -?? by Scott G. Kelly
Assignment Reviewer Scott G. Kelly
State Completed
Review review-ietf-mpls-gmpls-lsp-reroute-secdir-lc-kelly-2009-09-03
Completed 2009-09-03
review-ietf-mpls-gmpls-lsp-reroute-secdir-lc-kelly-2009-09-03-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 abstract does a good job of summarizing: This document describes how 


Resource ReserVation Protocol (RSVP) PathErr Messages may be used to 


trigger rerouting of Multi-Protocol Label Switching (MPLS) and 


Generalized MPLS (GMPLS) point-to-point Traffic Engineering (TE) Label 


Switched Paths (LSPs) without first removing LSP state or resources.






The security considerations section says the document introduces no new 


security considerations as it describes usage of existing formats and 


mechanisms, and I agree. It also points the reader to the security 


considerations sections of RFC4920 and RFC4736, and these do seem to do 


a reasonable job of summarizing.




I see no issues of concern for the security area ADs with this document.

--Scott