Hi Ran, Thanks for the review. I have one comment; your first nit is: > -I suggest BCP14 (may=> MAY, should=>SHOULD, must => MUST) change I would strongly caution against blindly doing replacements as described; RFC 2119 keywords are supposed to be used sparingly. Quoting RFC 2119 Section 6, Imperatives of the type defined in this memo must be used with care and sparingly. Indeed, if you use the all-caps version everywhere those words occur, I can almost guarantee pushback during IESG review. Of course, if there are specific places in the present document where a keyword would help, that’s fine. (I did look for such things during my review and it seemed fine, but I’m fallible.) Thanks, —John > On Mar 5, 2025, at 10:07 AM, Ran Chen via Datatracker <noreply@xxxxxxxx> wrote: > > [External Email. Be cautious of content] > > > Reviewer: Ran Chen > Review result: Has Nits > > # 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)/ > > > -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
