Last Call Review of draft-ietf-pce-stateful-hpce-10
review-ietf-pce-stateful-hpce-10-rtgdir-lc-mizrahi-2019-07-07-00

Request Review of draft-ietf-pce-stateful-hpce
Requested rev. no specific revision (document currently at 15)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2019-07-09
Requested 2019-06-21
Requested by Deborah Brungard
Authors Dhruv Dhody, Young Lee, Daniele Ceccarelli, Jongyoon Shin, Daniel King
Draft last updated 2019-07-07
Completed reviews Rtgdir Last Call review of -10 by Tal Mizrahi (diff)
Secdir Last Call review of -11 by Stephen Farrell (diff)
Genart Last Call review of -11 by Paul Kyzivat (diff)
Comments
Prep for IETF Last Call
Assignment Reviewer Tal Mizrahi
State Completed
Review review-ietf-pce-stateful-hpce-10-rtgdir-lc-mizrahi-2019-07-07
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/JVUBMsGKDdzfc3c4GKf6YYuf8fE
Reviewed rev. 10 (document currently at 15)
Review result Ready
Review completed: 2019-07-07

Review
review-ietf-pce-stateful-hpce-10-rtgdir-lc-mizrahi-2019-07-07

Hello,

I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through IETF last call and IESG review, and sometimes
on special request. The purpose of the review is to provide assistance to
the Routing ADs. For more information about the Routing Directorate, please
see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it
would be helpful if you could consider them along with any other IETF Last
Call comments that you receive, and strive to resolve them through
discussion or by updating the draft.

Document: draft-ietf-pce-stateful-hpce
Reviewer: Tal Mizrahi
Review Date: July, 2019
Intended Status: Informational

Summary:
No issues found. This document is ready for publication.

Nits:
-Section 1.1. is the only subsection of Section 1. Please consider adding a
subsection "Background" that will consist of the text before the current
1.1.
-"(previously computed paths" - there is no matching ")"
-Section 6.3 - please consider if this should be moved to the security
considerations section, or add a reference from the security considerations
section to this one.

Best regards,
Tal.