Subject: Re: [regext] I-D Action: draft-loffredo-regext-rdap-sorting-and-paging-00.txt

From: "Hollenbeck, Scott" <[email-masked]>
Date: Thu, 25 May 2017 12:45:32 +0000

> -----Original Message-----
> From: I-D-Announce [mailto:[email-masked]] On Behalf Of
> [email-masked]
> Sent: Thursday, May 25, 2017 8:34 AM
> To: [email-masked]
> Subject: [EXTERNAL] I-D Action: draft-loffredo-regext-rdap-sorting-and-
> paging-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : Registration Data Access Protocol (RDAP) Query
> Parameters for Result Sorting and Paging
>         Authors         : Mario Loffredo
>                           Maurizio Martinelli
>                           Scott Hollenbeck
>       Filename        : draft-loffredo-regext-rdap-sorting-and-paging-
> 00.txt
>       Pages           : 17
>       Date            : 2017-05-25
>
> Abstract:
>    The Registration Data Access Protocol (RDAP) does not include core
>    functionality for clients to provide sorting and paging (subsetting)
>    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
>    response values.  This document describes RDAP query extensions that
>    allow clients to specify their preferences for sorting and paging
>    result sets.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-sorting-and-
> paging/

This document should be of interest to anyone who cares about addressing RDAP's "feature" of limited-to-no result set control. It describes query parameters that allow a client to ask a server to return multi-valued result sets in certain ways. Please note that there a few places in the text where the authors are looking for discussion and feedback. We're hoping that people will read the draft, help us fill in those gaps, and share feedback on the utility of these features.

Scott, Mario, and Maurizio