Reviewer: Shwetha Bhandari Review result: Has Nits 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. Summary: This is a Standards Track document that defines an RPC operation to compare management datastores and returns diffs between the datastores as a yang-patch. While most access management of the RPC, ensuring availability of the server by rate limiting are considered I have an open question to authors: where/how will operational metrics such as rate of requests received, errors, rate limiting if applied, server resources consumed to process the request etc, about this new RPC be defined and reported? This is useful information for server operation where this RPC is enabled. Nits: The RESTCONF example content-type is json but it is set to application/yang-d that is not present in the registry - should it be application/yang-patch+json? -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
