Skip to main content

Last Call Review of draft-ietf-pce-pcep-extension-native-ip-32
review-ietf-pce-pcep-extension-native-ip-32-genart-lc-knodel-2024-08-05-00

Request Review of draft-ietf-pce-pcep-extension-native-ip
Requested revision No specific revision (document currently at 39)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2024-08-12
Requested 2024-07-29
Authors Aijun Wang , Boris Khasanov , Sheng Fang , Ren Tan , Chun Zhu
I-D last updated 2024-08-05
Completed reviews Opsdir Early review of -29 by Sheng Jiang (diff)
Secdir Early review of -29 by Ned Smith (diff)
Rtgdir Early review of -23 by Ines Robles (diff)
Genart Last Call review of -32 by Mallory Knodel (diff)
Secdir Last Call review of -34 by Magnus Nyström (diff)
Secdir Telechat review of -36 by Magnus Nyström (diff)
Assignment Reviewer Mallory Knodel
State Completed
Request Last Call review on draft-ietf-pce-pcep-extension-native-ip by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/OL_XqN1dmJRBYFfP3cD213QDOmw
Reviewed revision 32 (document currently at 39)
Result Ready w/issues
Completed 2024-08-05
review-ietf-pce-pcep-extension-native-ip-32-genart-lc-knodel-2024-08-05-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-pce-pcep-extension-native-ip-32
Reviewer: Mallory Knodel
Review Date: 2024-08-05
IETF LC End Date: 2024-08-12
IESG Telechat date: Not scheduled for a telechat

Summary: I've reviewed this document and I want to focus my feedback on the
security considerations section, though there are several nits within the
document that I imagine will be picked up during the editorial process.

Major issues: None.

Minor issues: Security considerations are helpful because they provide pointers
to other RFCs that contain relevant security considerations in related drafts.
However, a reader does not have a useful overview of what those security issues
are. I would encourage the authors to provide a short summary of the security
considerations for this specification as well as linking to the primary source
that goes into more depth about those considerations and how to mitigate them.
That will give the reader more of an idea about which additional documents they
should read, instead of asking them to read all of them and decide for
themselves. I believe the experts who have authored this specification could
provide more guidance to implementers about what are the security issues with
this specification as well as guidance on where to look for deeper explanations
(eg the already cited RFCs).

Nits/editorial comments: The document requires significant and thorough
copyediting, which would be nice to do before passing along to the RFC Editor.
Automated spelling and grammar tools could catch many of these.