Hi all,
this version harmonizes the "paging_metadata" element for the two
pagination methods.
In my opinion, both methods have strengths and weaknesses. Therefore,
since the "paging_metadata" element keeps the same structure and
basically clients make use of the paging links as they are provided by
the server, this specification envisages that operators may implement a
method according to their needs, the user access levels, the submitted
queries.
More detailed descriptions of both "sorting_metadata" and
"paging_metadata" elements are provided.
With regard to the possibility for clients to indentify which
capabilities a server supports, this is still an open issue as it was
pointed out by Andy at the last meeting. Currently, the rdapConformance
array can only be used to identify the additional elements in the
response. On this point, I have submitted a presentation to the ROW
committee about a possible solution enabling servers to provide clients
with their own specification.
Many thanks, James and Andy, for your interest.
I look forward to further reviews.
Cheers,
mario
-------- Messaggio Inoltrato --------
Oggetto: [regext] I-D Action:
draft-ietf-regext-rdap-sorting-and-paging-01.txt
Data: Thu, 11 Apr 2019 01:08:39 -0700
Mittente: internet-dra...@ietf.org
Rispondi-a: regext@ietf.org
A: i-d-annou...@ietf.org
CC: regext@ietf.org
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Registration Protocols Extensions WG of
the IETF.
Title : Registration Data Access Protocol (RDAP) Query Parameters for
Result Sorting and Paging
Authors : Mario Loffredo
Maurizio Martinelli
Scott Hollenbeck
Filename : draft-ietf-regext-rdap-sorting-and-paging-01.txt
Pages : 26
Date : 2019-04-11
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 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-ietf-regext-rdap-sorting-and-paging/
There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-regext-rdap-sorting-and-paging-01
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-sorting-and-paging-01
A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-rdap-sorting-and-paging-01
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.
Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
