RFC 8977: Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8977
- Published
- January 2021
- Authors
- M. Loffredo; M. Martinelli; S. Hollenbeck
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8982Registration Data Access Protocol (RDAP) Partial ResponseCurrent
February 2021
- RFC 8521Registration Data Access Protocol (RDAP) Object TaggingCurrent
November 2018
- RFC 9536Registration Data Access Protocol (RDAP) Reverse SearchCurrent
April 2024
- RFC 9560Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID ConnectCurrent
April 2024
- RFC 8605vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)Current
May 2019
- RFC 7481Security Services for the Registration Data Access Protocol (RDAP)Current
March 2015
- RFC 6724Default Address Selection for Internet Protocol Version 6 (IPv6)Current
September 2012
- RFC 4790Internet Application Protocol Collation RegistryCurrent
March 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?