Skip to main content

Registration Data Access Protocol (RDAP) Partial Response
draft-ietf-regext-rdap-partial-response-16

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Jasdip Singh <jasdips@arin.net>, The IESG <iesg@ietf.org>, barryleiba@gmail.com, draft-ietf-regext-rdap-partial-response@ietf.org, jasdips@arin.net, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Registration Data Access Protocol (RDAP) Partial Response' to Proposed Standard (draft-ietf-regext-rdap-partial-response-16.txt)

The IESG has approved the following document:
- 'Registration Data Access Protocol (RDAP) Partial Response'
  (draft-ietf-regext-rdap-partial-response-16.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working
Group.

The IESG contact persons are Murray Kucherawy and Barry Leiba.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-partial-response/


Ballot Text

Technical Summary

The Registration Data Access Protocol (RDAP) does not include
capabilities to request partial responses.  In fact, according to the
user authorization, the server can only return full responses.  A partial
response capability, especially in the case of search queries, could
bring benefits to both clients and servers.  This document describes an
RDAP query extension that allows clients to specify their preference for
obtaining a partial response.


Working Group Summary

There was some constructive feedback but nothing controversial. The
authors have addressed the feedback in the latest draft.


Document Quality

The document quality is high. Both IIT-CNR/Registro.it and APNIC have
implemented this draft.


Personnel

Document Shepherd: Jasdip Singh (jasdips@arin.net)
Area Director: Barry Leiba (barryleiba@gmail.com)

RFC Editor Note