[TSG-Access-RD] Access Control Protocol in the Charter

[Murray S. Kucherawy]

On Wed, Dec 12, 2018 at 6:34 AM Hollenbeck, Scott via TSG-Access-RD <
tsg-access-rd at icann.org> wrote:

> I'd like to discuss the "Access Control Protocol" section of the draft
> charter a bit more...
> [...]
>

I have all of the same concerns.

Access Control Protocol
> 1. How could a centralized authorization interface operated by ICANN work?
>

Would this include delegation?  Someone mentioned a scenario like ICANN
approving M3AAWG as a secondary authorizing party, for example.

2. How could access to non-public registration data be granted only to
> clients that are authorized by ICANN?
> 3. How could ICANN, in its role as the authorizing party, receive a
> third-party request for access to non-public registration data?
> 4. Categorization/prioritization of RDS data fields: Should all the fields
> be collected in one place? If so, should we design a protocol that allows
> for the categorization of these fields and the prioritization of the
> request response?
>

And as you alluded, how can we determine which fields are public vs.
non-public at the time of the query, given that those sets can be changed
over time by policy action?

-MSK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tsg-access-rd/attachments/20181212/a331a348/attachment.html>