Hi Tim,
Thank you very much for your review!
We just updated the draft to 16 version to add statistics according to Eric's suggestion.
It's great you will review the newest version and give us improvement suggestion.
Thank you!
Best regards,
Sandy
Original
From: TimChownviaDatatracker <noreply@xxxxxxxx>
To: ops-dir@xxxxxxxx <ops-dir@xxxxxxxx>;
Cc: draft-ietf-rift-yang.all@xxxxxxxx <draft-ietf-rift-yang.all@xxxxxxxx>;last-call@xxxxxxxx <last-call@xxxxxxxx>;rift@xxxxxxxx <rift@xxxxxxxx>;
Date: 2024年07月22日 03:22
Subject: [Rift] Opsdir last call review of draft-ietf-rift-yang-15
Reviewer: Tim Chown
Review result: Has Nits
Hi,
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 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.
The document defines a YANG data model for the configuration and management of
RIFT (routing in fat trees) protocol.
I am not a YANG expert, but the document appears to follow a similar style and
layout to other YANG data model documents I have read. The associated security
text seems appropriate.
The nits are simply down to the large number of typos and mainly grammatical
errors in the text, many around use or non-use of plurals. There is no
semantic ambiguity in any that I saw, but it would be good to correct these
rather than put that load on the RFC Editor.
Tim
_______________________________________________
RIFT mailing list -- rift@xxxxxxxx
To unsubscribe send an email to rift-leave@xxxxxxxx
Review result: Has Nits
Hi,
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 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.
The document defines a YANG data model for the configuration and management of
RIFT (routing in fat trees) protocol.
I am not a YANG expert, but the document appears to follow a similar style and
layout to other YANG data model documents I have read. The associated security
text seems appropriate.
The nits are simply down to the large number of typos and mainly grammatical
errors in the text, many around use or non-use of plurals. There is no
semantic ambiguity in any that I saw, but it would be good to correct these
rather than put that load on the RFC Editor.
Tim
_______________________________________________
RIFT mailing list -- rift@xxxxxxxx
To unsubscribe send an email to rift-leave@xxxxxxxx
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
