Redacted Fields in the Registration Data Access Protocol (RDAP) Response
draft-ietf-regext-rdap-redacted-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: The IESG <iesg@ietf.org>, andy@hxr.us, draft-ietf-regext-rdap-redacted@ietf.org, gustavo.lozano@icann.org, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'Redacted Fields in the Registration Data Access Protocol (RDAP) Response' to Proposed Standard (draft-ietf-regext-rdap-redacted-16.txt)

The IESG has approved the following document:
- 'Redacted Fields in the Registration Data Access Protocol (RDAP)
   Response'
  (draft-ietf-regext-rdap-redacted-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 Francesca Palombini.

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

Ballot Text

Technical Summary

   This document describes an RDAP extension for specifying methods of
   redaction of RDAP responses and explicitly identifying redacted RDAP
   response fields, using JSONPath as the default expression language.

Working Group Summary

This document reached broad agreement with many reviews by working group 
participants.

Consensus for this document was NOT particularly rough. Many reviewers did find 
technical errors with examples, but these have all been corrected. Working group 
discussions on other topics which were much more controversial did become 
intertwined with this document, but those other issues are not directly related to RDAP 
redaction. Such discussions did demonstrate the working groups attention to how this 
document fits into the larger architecture of RDAP.

No appeal is threatened.

Document Quality


This document has one known, non-production server implementation, and no known 
client implementations. Many gTLD registries and registrars will be implementing 
servers with this specification for servers under a forth-coming ICANN policy, and 
ICANN has indicated its intention to implement this specification for its ICANN 
command line client (https://github.com/icann/icann-rdap) and web-based lookup tool 
(https://lookup.icann.org/en).

Personnel

   The Document Shepherd for this document is Andy Newton. The Responsible
   Area Director is Murray Kucherawy.

RFC Editor Note