First of all my apologies for a delay.

The document is nicely written and easy to understand even by someone who is not an YANG expert.
I believe that the mechanism defined in this document solves an important operational issue and would allow operators to use YANG-driven protocols more effient, especially when dealing with large amount of data.

I have a few minor comments and questions.

1. Section 3.1.3 says that "If a query supplies "locale" and not "sort-by", error-type application and error-tag "invalid-value" is returned". At the same time, neither section 3.1.1 nor 3.1.2 define what the server is supposed to return if the query parameter is not supported. Is it intentional/defined somewhere else? (My apologies, I'm not very familiar with the area, so maybe it's obvious for an educated reader?)


2. Section3.1.6

"The "cursor" query parameter MUST be supported for all "config true" lists and SHOULD be supported for all "config false" lists. It is however optional to support the "cursor" query parameter for "config false" lists and the support must be signaled by the server per list."
                    

May I suggest slight rephrasing, for example:

The "cursor" query parameter MUST be supported for all "config true" lists and SHOULD be supported for all "config false" lists. As the "cursor" query parameter support for "config false" lists is optional, the support must be signaled by the server per list." 

Also, the second sentence uses lower-case must. Is it intentional?

Cheers, Jen Linkova