Hi all,
I spent some time thinking about how to make the redaction problem less
complex by focusing on the places where redaction is most likely to to
be found, in "personal data". Within RDAP, that appears to always be
conveyed in JSON strings. Reducing the scope reduces the complexity, at
least in my opinion.
Included is an example with the ICANN redaction policies, which are the
only published redaction policies that I know of. If others are
published, please send me a link and I'll see about working up an example.
Anyway, I am curious what people think.
-andy
-------- Forwarded Message --------
Subject: New Version Notification for
draft-newton-regext-rdap-simple-redaction-00.txt
Date: Mon, 17 Jun 2024 05:51:39 -0700
From: internet-dra...@ietf.org
To: Andy Newton <a...@hxr.us>
A new version of Internet-Draft
draft-newton-regext-rdap-simple-redaction-00.txt has been successfully
submitted by Andy Newton and posted to the
IETF repository.
Name: draft-newton-regext-rdap-simple-redaction
Revision: 00
Title: RDAP Simple Redaction
Date: 2024-06-17
Group: Individual Submission
Pages: 19
URL:
https://www.ietf.org/archive/id/draft-newton-regext-rdap-simple-redaction-00.txt
Status:
https://datatracker.ietf.org/doc/draft-newton-regext-rdap-simple-redaction/
HTML:
https://www.ietf.org/archive/id/draft-newton-regext-rdap-simple-redaction-00.html
HTMLized:
https://datatracker.ietf.org/doc/html/draft-newton-regext-rdap-simple-redaction
Abstract:
This document defines a simple redaction extension for the
Registration Data Access Protocol (RDAP).
The IETF Secretariat
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
