Skip to main content

IETF Last Call Review of draft-ietf-detnet-controller-plane-framework-12
review-ietf-detnet-controller-plane-framework-12-opsdir-lc-barguil-2025-07-07-01

Request Review of draft-ietf-detnet-controller-plane-framework
Requested revision No specific revision (document currently at 15)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2025-07-15
Requested 2025-07-02
Requested by Mohamed Boucadair
Authors Andrew G. Malis , Xuesong Geng , Mach Chen , Balazs Varga , Carlos J. Bernardos
I-D last updated 2026-03-14 (Latest revision 2025-09-24)
Completed reviews Rtgdir Early review of -07 by Daniele Ceccarelli (diff)
Tsvart IETF Last Call review of -12 by Kyle Rose (diff)
Opsdir IETF Last Call review of -12 by Samier Barguil (diff)
Genart IETF Last Call review of -12 by Stewart Bryant (diff)
Secdir Telechat review of -12 by Dave Thaler (diff)
Assignment Reviewer Samier Barguil
State Completed
Request IETF Last Call review on draft-ietf-detnet-controller-plane-framework by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/q6SUHMMS60w8B7OyyvUZkgU1wFE
Reviewed revision 12 (document currently at 15)
Result Has nits
Completed 2025-07-07
review-ietf-detnet-controller-plane-framework-12-opsdir-lc-barguil-2025-07-07-01
Hello,

I have been selected as the Operations Directorate (opsdir) reviewer for this
draft. The Operations Directorate reviews all operational and
management-related drafts to ensure alignment with operational best practices.
More "Guidelines for Considering Operations and Management in IETF
Specifications" can be found at
https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/. While these
comments are primarily for the OPS ADs, the authors should consider them
alongside other feedback and address them through updates or discussions.

Document: draft-ietf-detnet-controller-plane-framework-12
Reviewer: Samier Barguil
Review Date: 2025-07-07
IETF LC End Date: 2025-07-15
Intended Status: Informational

Summary:

Minor concerns/nits that should be resolved before publication.

This document It is intended to provide a framework overview for the DetNet
controller plane, discussing concepts and requirements that could form the
basis for future solution specifications. The authors did a great work
identifying key requirements and architectural models, while clearly stating
that detailed protocol solutions and necessary extensions are subjects for
future work

Nits:

In Section 3.1, "Distributed Control Plane and Signaling Protocols"

r/ RSVT-TE / RSVP-TE

In Section 6, "Multidomain Aspects"

I suggest to replace as "multi-domain" (with a hyphen) or "multi domain" (as
two words).

In Section 5.2.1.2, "Passive PM"

r / affect / effect