Skip to main content

Last Call Review of draft-ietf-teas-pce-central-control-04
review-ietf-teas-pce-central-control-04-secdir-lc-miller-2017-08-30-00

Request Review of draft-ietf-teas-pce-central-control
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-08-24
Requested 2017-08-10
Authors Adrian Farrel , Quintin Zhao , Zhenbin Li , Chao Zhou
I-D last updated 2017-08-30
Completed reviews Rtgdir Last Call review of -03 by Thomas Morin (diff)
Genart Last Call review of -03 by Elwyn B. Davies (diff)
Opsdir Last Call review of -03 by Tianran Zhou (diff)
Secdir Last Call review of -04 by Matthew A. Miller (diff)
Genart Telechat review of -04 by Elwyn B. Davies (diff)
Assignment Reviewer Matthew A. Miller
State Completed
Request Last Call review on draft-ietf-teas-pce-central-control by Security Area Directorate Assigned
Reviewed revision 04 (document currently at 05)
Result Has nits
Completed 2017-08-30
review-ietf-teas-pce-central-control-04-secdir-lc-miller-2017-08-30-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.

Document:
Reviewer: Matthew A. Miller
Review Date: 2017-08-30
IETF LC End Date: 2017-08-25
IESG Telechat date: 2017-08-31

Summary:

This document is ready for publication as Informational, with one potential nit.

This document describes an overall architecture (with some variants) utilizing
central PCE-based controller for SDN, and its implication on PCEP.  The
document notes the tradeoffs between the variants, including some of the
vulnerabilities.

My nit is in the Security Considerations; I'm not sure how likely in practice
a central controller architecture will be operated with "higher level of
security", and therefore not sure it's worth calling out like this.

I can see how a central controller makes management easier, and that has a
potential benefit of better visibility into the network's operation and
finding problems (including security-related) sooner and better.

Otherwise I think the rest of this section addresses the concerns that a
central controller architecture has.