Skip to main content

Last Call Review of draft-ietf-lsr-pce-discovery-security-support-10
review-ietf-lsr-pce-discovery-security-support-10-opsdir-lc-liu-2022-09-15-00

Request Review of draft-ietf-lsr-pce-discovery-security-support
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2022-09-20
Requested 2022-09-06
Authors Diego Lopez , Qin Wu , Dhruv Dhody , Qiufang Ma , Daniel King
I-D last updated 2022-09-15
Completed reviews Secdir Last Call review of -05 by Yaron Sheffer (diff)
Rtgdir Last Call review of -05 by Ron Bonica (diff)
Opsdir Last Call review of -10 by Will (Shucheng) LIU (diff)
Intdir Telechat review of -12 by Carlos Pignataro (diff)
Opsdir Telechat review of -13 by Will (Shucheng) LIU
Assignment Reviewer Will (Shucheng) LIU
State Completed
Request Last Call review on draft-ietf-lsr-pce-discovery-security-support by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/TWvlwAQyhOa5vyrZ-MbvfklaQG0
Reviewed revision 10 (document currently at 13)
Result Has nits
Completed 2022-09-15
review-ietf-lsr-pce-discovery-security-support-10-opsdir-lc-liu-2022-09-15-00
Hi all,

I have reviewed draft-ietf-lsr-pce-discovery-security-support-10 as part of the
Operational directorate's ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that are not
addressed in last call may be included in AD reviews during the IESG review. 
Document editors and WG chairs should treat these comments just like any other
last call comments.

“When a Path Computation Element (PCE) is a Label Switching Router
   (LSR) participating in the Interior Gateway Protocol (IGP), or even a
   server participating in the IGP, its presence and path computation
   capabilities can be advertised using IGP flooding.  The IGP
   extensions for PCE discovery (RFC 5088 and RFC 5089) define a method
   to advertise path computation capabilities using IGP flooding for
   OSPF and IS-IS respectively.  However these specifications lack a
   method to advertise PCE Communication Protocol (PCEP) security (e.g.,
   Transport Layer Security (TLS), TCP Authentication Option (TCP-AO))
   support capability.”

My overall view of the document is almost 'Ready' for publication, except some
editorials below.

** Technical **

No.

** Editorial **

        • Section 1. Introduction
                ○ The fifth paragraph: s/This documents update [RFC5088]/This
                document updates [RFC5088]/
        • Section 3.1 Use of PCEP security capability support for PCE discovery
                ○ The last paragraph: s/If a client is configured to require
                that its PCE server support TCP-AO/If a client is configured to
                require that its PCE server supports TCP-AO; ○ s/If a client is
                configured to require that its PCE server support TLS/If a
                client is configured to require that its PCE server supports TLS
        • Section 5 Backward Compatibility Considerations
                ○ The second paragraph: How to understand "KEYNAME" here?
                s/KEYNAME/KEY-ID and KEY-CHAIN-NAME/?
        • The title of Section 8.1: s/PCE Capability Flag/PCE Capability Flags/
        • Section 9 Acknowledges
                ○ s/speical/special/

Regards,
Will (Shucheng LIU)