Document: draft-ietf-detnet-controller-plane-framework Title: Deterministic Networking (DetNet) Controller Plane Framework Reviewer: Stewart Bryant Review result: Ready 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-detnet-controller-plane-framework-12 Reviewer: Stewart Bryant Review Date: 2025-07-14 IETF LC End Date: 2025-07-15 IESG Telechat date: Not scheduled for a telechat Summary:From a GenART perspective I would register that the use of the term controller plane is likely to confuse some readers who would be more comfortable with the term "control and management plane(s)" or some similar term. However, "Controller" is the term that the project chose to use and it would be highly disruptive to change it. In that context I think that in addition to the clarification of the term "controller" in the Introduction (which might itself be usefully highlighted in some way, perhaps though a subsection) it might be helpful to include a short clarification in the abstract. The document is well written. It has a few very minor editorials but these will get picked up by the RFC Editor in the normal course of their post processing. Major issues: None Minor issues: None Nits/editorial comments: There are three instance where quoted strings are non-ascii: “LSP graph”, “traditional MPLS”, “traditional IP”. This causes nits issues. The DetNet data plane is defined - "The" is missing -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
