Skip to main content

Last Call Review of draft-ietf-teas-pce-native-ip-14
review-ietf-teas-pce-native-ip-14-secdir-lc-eastlake-2020-12-10-00

Request Review of draft-ietf-teas-pce-native-ip
Requested revision No specific revision (document currently at 17)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2020-12-10
Requested 2020-11-26
Authors Aijun Wang , Boris Khasanov , Quintin Zhao , Huaimo Chen
I-D last updated 2020-12-10
Completed reviews Rtgdir Last Call review of -09 by Loa Andersson (diff)
Secdir Last Call review of -14 by Donald E. Eastlake 3rd (diff)
Assignment Reviewer Donald E. Eastlake 3rd
State Completed
Request Last Call review on draft-ietf-teas-pce-native-ip by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/GkaNkma1cNdFsAbCDN2Zsr0sLVg
Reviewed revision 14 (document currently at 17)
Result Has issues
Completed 2020-12-07
review-ietf-teas-pce-native-ip-14-secdir-lc-eastlake-2020-12-10-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.  Document
editors and WG chairs should treat these comments just like any other last
call comments.

The summary of the review is Ready with Issues.

Security:
This is a very high level Informational document about a general method of
traffic engineering using multiple BGP sessions and PCE. The Security
Considerations section is adequate except that I would recommend adding a
reference for BGP security, perhaps to RFC 7454.

Other Issues:
The title of the document doesn't really make it clear what it is about and
does not spell out some acronyms. I suggest the following:

Path Computation Element (PCE) Traffic Engineering (TE) in Native IP
NetworkNetworks


Editorial:
There are a number of editorial/typo issues including the curious lack of
any expansion or definition for the first three acronyms listed in Section
2 on Terminology and what appears to be a line sliced off the bottom of
Figure 3. Also, I think a reference should be given where BGP Flowspec is
mentioned in Section 7.1, presumably to the rfc5575bis draft. See attached
for detailed change suggestions in MS Word with tracked changes and,
alternatively, as a PDF thereof.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com