Skip to main content

Last Call Review of draft-ietf-pce-stateful-pce-vendor-08
review-ietf-pce-stateful-pce-vendor-08-secdir-lc-dunbar-2024-10-14-00

Request Review of draft-ietf-pce-stateful-pce-vendor
Requested revision No specific revision (document currently at 13)
Type IETF Last Call Review
Team Security Area Directorate (secdir)
Deadline 2024-10-10
Requested 2024-09-26
Authors Cheng Li , Haomian Zheng , Siva Sivabalan , Samuel Sidor , Zafar Ali
I-D last updated 2025-04-07 (Latest revision 2024-11-25)
Completed reviews Opsdir Early review of -04 by Xiao Min (diff)
Rtgdir Early review of -05 by Mike McBride (diff)
Secdir IETF Last Call review of -08 by Linda Dunbar (diff)
Opsdir IETF Last Call review of -08 by Xiao Min (diff)
Genart IETF Last Call review of -09 by Susan Hares (diff)
Intdir Telechat review of -09 by Wassim Haddad (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request IETF Last Call review on draft-ietf-pce-stateful-pce-vendor by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/Q3hDsf98junAmCjlf6zVRYhoBIE
Reviewed revision 08 (document currently at 13)
Result Has nits
Completed 2024-10-14
review-ietf-pce-stateful-pce-vendor-08-secdir-lc-dunbar-2024-10-14-00
I have reviewed this document as part of the SEC area 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

Summary: this document extends the vendor-specific information in the Stateless
PCE communication protocol for the Stateful PECP message. The document is very
clear and easy to read.

Just a minor NITS with the Security Consideration:

The method described in the Security Consideration to mitigate the security
issue of "covert channel" relies on operators noticing that vendor-specific
information is being used and then reaching out to the vendor for decoding
mechanisms. This is a reactive approach rather than a proactive one. By the
time the operator detects the use of vendor-specific information and obtains
the necessary decoding tools, malicious or harmful actions could have already
occurred.

It would be useful to add more description on how can operator be proactive to
prevent the issue.

Best Regards,
Linda Dunbar