Re: [regext] Fwd: New Version Notification for draft-ietf-regext-rdap-sorting-and-paging-07.txt

Mario,

here is my feedback on this draft:

general comment:

I think it would be easier to understand the document if the actual
specification and the reasoning would switch places (or even go into a kind
of appendix).

Section 1:

Just as a side note: you talk about users interacting with a web browser,
but I’m afraid by adding this extension to the RDAP response it is also not
easy to read in the browser…

Section 2.1:

Where it says “SHOULD provide additional information in their responses”
you could probably add which responses in particular.

Not sure if “At least one between” is the right term (2 occurrences).

For “totalCount” “It is provided if the query string contains the "count"
parameter;” suggestion: “It MUST be provided if the query string contains
the "count" parameter with a value of true”

Section 2.3.1: sorting of multiple IP addresses is underspecified.

What is not clear to me is if the client is allowed to send a limit in its
initial request (not knowing if the server even supports limit/offset)? Or
is it intended that the client does not send any preferences on the first
request and the response is done based on server policy and metadata is
added?

Anyway, having sorting and paging for RADP is certainly a good idea.

Best,

Karl Heinz

On Fri, Dec 20, 2019 at 12:30 PM Mario Loffredo <mario.loffredo@iit.cnr.it>
wrote:

> Hi folks,
>
> I just published a new version including a section about paging responses
> to POST requests.
>
>
> Best,
>
> mario
>
>
> -------- Messaggio Inoltrato --------
> Oggetto: New Version Notification for
> draft-ietf-regext-rdap-sorting-and-paging-07.txt
> Data: Fri, 20 Dec 2019 03:26:47 -0800
> Mittente: internet-drafts@ietf.org
> A: Maurizio Martinelli <maurizio.martinelli@iit.cnr.it>
> <maurizio.martinelli@iit.cnr.it>, Scott Hollenbeck
> <shollenbeck@verisign.com> <shollenbeck@verisign.com>, Mario Loffredo
> <mario.loffredo@iit.cnr.it> <mario.loffredo@iit.cnr.it>
>
>
> A new version of I-D, draft-ietf-regext-rdap-sorting-and-paging-07.txt
> has been successfully submitted by Mario Loffredo and posted to the
> IETF repository.
>
> Name: draft-ietf-regext-rdap-sorting-and-paging
> Revision: 07
> Title: Registration Data Access Protocol (RDAP) Query Parameters for
> Result Sorting and Paging
> Document date: 2019-12-20
> Group: regext
> Pages: 25
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-regext-rdap-sorting-and-paging-07.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-sorting-and-paging/
> Htmlized:
> https://tools.ietf.org/html/draft-ietf-regext-rdap-sorting-and-paging-07
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-sorting-and-paging
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-sorting-and-paging-07
>
> Abstract:
> The Registration Data Access Protocol (RDAP) does not include core
> functionality for clients to provide sorting and paging parameters
> for control of large result sets. This omission can lead to
> unpredictable server processing of queries and client processing of
> responses. This unpredictability can be greatly reduced if clients
> can provide servers with their preferences for managing large
> responses. This document describes RDAP query extensions that allow
> clients to specify their preferences for sorting and paging result
> sets.
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext
>