Telechat Review of draft-ietf-roll-dao-projection-39
review-ietf-roll-dao-projection-39-opsdir-telechat-chen-2025-03-05-00
| Request | Review of | draft-ietf-roll-dao-projection |
|---|---|---|
| Requested revision | No specific revision (document currently at 40) | |
| Type | Telechat Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2025-03-04 | |
| Requested | 2025-01-23 | |
| Authors | Pascal Thubert , Rahul Jadhav , Michael Richardson | |
| I-D last updated | 2026-01-29 (Latest revision 2025-03-11) | |
| Completed reviews |
Rtgdir IETF Last Call review of -32
by Susan Hares
(diff)
Secdir IETF Last Call review of -31 by Klaas Wierenga (diff) Tsvart Telechat review of -36 by Michael Scharf (diff) Opsdir Telechat review of -39 by Ran Chen (diff) |
|
| Assignment | Reviewer | Ran Chen |
| State | Completed | |
| Request | Telechat review on draft-ietf-roll-dao-projection by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/B0dSM0R1fWbV8-SuOY_RCCzEWg4 | |
| Reviewed revision | 39 (document currently at 40) | |
| Result | Has nits | |
| Completed | 2025-03-05 |
review-ietf-roll-dao-projection-39-opsdir-telechat-chen-2025-03-05-00
# OPSDIR review of draft-ietf-roll-dao-projection I have reviewed this document 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 the 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. This document extends RFC 6550, RFC 6553, and RFC 8138, introducing the DAO Projection mechanism to enhance RPL. It enables the RPL root or an external controller to proactively install optimized routes, improving routing efficiency, reliability, and resource utilization. Additionally, the draft addresses backward compatibility, all nodes involved in P-DAO processing must support this specification. The document is clear and well-written. The motivation is described well. The document is almost ready for publication. ## Nits -I suggest BCP14 (may=> MAY, should=>SHOULD, must => MUST) change -The document use TrackID, Trackid, trackID, it is recommended to unify them. -s/additional paths betwwen nodes/ additional paths between nodes/ -s/ oriented From Ingress / oriented from Ingress / -s/ Building Tracks With RPL/ Building Tracks with RPL/ -s/ edges leads to/ edges lead to/ -s /may be ommitted/ may be omitted/ -s/ The latter is often is preferred/ The latter is often preferred/ -s/ the position preceeding the one/ the position preceding the one/ -s/ The (suggected)/ The (suggested)/