<html>
<body>
Holly I have been travelling and am ties up in meetings all day (Brussels
time), but I hope to add some comments later tonight.<br><br>
I caution care in interpreting the Article 29 letter. Despite some valid
concerns, it shows an astounding lack of knowledge of the Internet and
ICANN's mission. As a prime example is their advice to just focus on our
own business and not that of others such as law enforcement or those
combatting cyber issues. Our mission is to protect the DNS and that
includes making it reliable and safe. But we do not have the ability to
do that ourselves and thus must provide the tools for others to do that.
If we fail, we are NOT carrying out our mission. <br><br>
This will get more interesting in coming weeks.<br><br>
Alan<br><br>
<br><br>
At 16/04/2018 07:58 PM, Holly Raiche wrote:<br><br>
<blockquote type=cite class=cite cite="">Folks<br><br>
We are fast running out of time to develop any kind of response to the
accreditation model, even though the deadline for a response has been
extended to this Friday. And in the interim, ICANN has received advice
from Article 29 on the Interim model. (Article 29 is an advisory Group
made up of a data protection authority from each EU member state).
Their letter to ICANN, and Marby’s response, are on the home page of
ICANN - and for those interested in the issue, I highly recommend reading
both. Clearly, the implications of the Article 29 letter are that
the Interim Model that we did comment on still raises concerns with
them. Those concerns fall under the headings:
<ul>
<li>Breadth of purpose - saying the proposed purposes are too widely
drawn
<li>the link of purpose to processing - again, because the Whois data has
been used does not qualify it as a purpose
<li>publication of the data must be linked to the original (and narrowly
defined) purpose
<li>any access should be limited - not blanket access
<li>discussion about the length of retention of data
<li>discussion about the transfer of data
<li>Accreditation (particularly important in this context) - should only
be for legitimate purpose, limited to the original purpose, not blanket
access, and under limited conditions
</ul><br>
Below, I have copied in an email from Scott Hollenbeck, a long standing
member of ICANN and one of those involved in the development of the RDAP
(access protocol that would allow gated access to registration data) -
simply because he has been involved in this issue for a long time and
shows he has already worked on a technical solution to this issue - how
access to data could work under GDPR.<br><br>
I will try to attend as much as possible of the capacity building webinar
on this issue, but have been scheduled to attend an all-day course in the
Sydney CBD so may have to miss some of the discussion. I imagine
Tom will be very up to date on these issues, but I would like to have
been attending the whole of the webinar myself <br><br>
In any case, if at all possible, we should be saying something.
Quite apart from the original contribution from the IPC/BC model, the
NCSG and Registrars have also made comments (largely challenging the
IPC/BC model). I hope we are the one constituency that doesn’t make
comments - although I realise that agreement on what to say will be
difficult at the best of times.<br><br>
And if it isn’t too late - maybe put this issue on the ALAC policy page -
and with it, links to the Article 29 letter, Marby’s response, the
registrars’ response and the NCSG response (and any others I have missed
- I have copies if that helps)<br><br>
Holly<br><br>
<br><br>
<br><br>
<blockquote type=cite class=cite cite="">
<blockquote type=cite class=cite cite="">
<blockquote type=cite class=cite cite=""><br>
Hi all.<br><br>
After reading the Article 29 WP letter to ICANN<br>
(<a href="awbs://www.icann.org/en/system/files/correspondence/jelinek-to-marby-">
awbs://www.icann.org/en/system/files/correspondence/jelinek-to-marby-</a>
<br>
11apr18-en.pdf), I started envisioning what process and system could<br>
achieve GDPR compliance. What I came to is a token-based system,
which<br>
would work like this:<br>
- Every request is analyzed by a human at an "RDS
Clearinghouse". Each<br>
request can be for a single data element (like "owner of domain
X") or to<br>
multiple data elements (like "domains owned by the same owner of
domain<br>
X"), but requests for multiple data elements are only foreseen to
be<br>
processed by contracted parties with "Search WHOIS" contract
requirements.<br>
- Clearinghouse issues a token with query parameters, data elements<br>
authorized for response, identity of authorized party, reason for<br>
authorization, validity (probably in the order of days), also
informing<br>
which endpoint to go to.<br>
- Authorized party uses that token to access that endpoint, managed by
the<br>
party with most data about that element (usually a registrar).<br><br>
Note that is not a replacement for credentialing; credentials would
still<br>
be necessary to get tokens. This is also orthogonal to discussions
like<br>
which use cases are legitimate or not, GDPR-compliant or not etc.;
it's<br>
just a more granular approach to authorization that looks more inline
with<br>
privacy-oriented guidelines including but not limited to
GDPR.</blockquote><br>
Rubens, at a high level you just described how OpenID and OAuth work,
except for the "Every request is analyzed by a human"
part.</blockquote><br>
Scott,<br><br>
I believe you are right, although most OAuth models I saw were not that
granular to the point of saying "example.TLD, owner, e-mail address,
valid until April 20 2018". That's not an OAuth limitation though,
just common usage, and it probably could be made to work like this. <br>
And some level of asynchronous communications could even make way for a
quick look human analysis. <br><br>
<br>
Rubens</blockquote><br>
I have this very model, with human involvement, up and running right now
as part of the gTLD RDAP Pilot. All of the attributes you mentioned can
be encoded as OAuth claims. The model is described in an Internet-Draft
that I first wrote in 2015. Just search for “draft Hollenbeck RDAP
OpenID” using your favorite search engine.<br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;YTOPR01MB0396;27:E+eV2ZOSHNubNtVECuy/VM/L0xhmfXbZcuSQZbzTXSXqae7LUG8EA97rPf+2WwLbTntAgo7cpRKp5nw8d8T6ebvY8Vy/iFaEy7AJW3LXmiMa8o52Hh4X6vuxt8b9Dc+H<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
mbIfSQV0+eZC39ENiUAspKdQkF0+JSTZwhHzgGzIJcnMTMtI1YFjxfAYUWl5x8Xsb0hCkvQc7VzC4AbTCpUbUGRQU6RcE5UUx1wEGk3WXKVvz27yXSf3osNfP8UwExDIUIL1xB46d04FaxAvbFZx3V7Y2ZVoGnlOF9jsJrXvgUSoJT4DsABV8smZdk4vNHRjunBYHmX/Uyc08KK5W5zM0fDRY7NEhuy8gp+3GzVz4A/5TqlICRbEqPiDy4iZWnOAaPiE4ELCAfZPmhMusibjqJno9CcaR04f9ovSYOL+LGRVBVtQ1M9b/SxTHtnAjl+ENjnGKfOC/j1+ryUspB55Z6d0P1zabIZYAwo87l1z4xMWzu3tmPExSwczo7sS129laKLyfrpQKQl6gt36u0ia78/RPd+UH+swgobcmXrp+pNPCIV60r6mKu9CLHxwfljZtI62wcXHykdzvBpIoyKjBQ==<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
ALAC@atlarge-lists.icann.org<br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" eudora="autourl">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" eudora="autourl">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote></body>
</html>