<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Thanks Alan<div><br></div><div>Maybe we should set up a wiki page o keep the comments in one place. I note Carlton has already provided comments as well, and even though the call for 'feedback’ is a formal process, we need to coordinate our ‘feedback’</div><div><br></div><div>Holly<br><div><div>On 15 Jan 2018, at 3:36 pm, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
In my mind, there is no question that we need to respond. <br><br>
The models are NOT what I was expecting, but that is not particularly
relevant at this point. ICANN's challenge is to attempt to saitisfy data
commissioners, who will not likely tell us ahead of time that they agree
with us or not, But to do that while to the extent prossible, maintaining
WHOIS so it can at least partially satisfy the ongoing important uses of
WHOIS, particularly with respect to fighting DNS abuse and malicious
activities. <br><br>
So for example, Model 3 certainly satisfies privacy concerns (although we
could endlessly debate whether the expiration date is private information
or not), but it shuts down virtually all other uses of WHOIS (including
trade mark protection and the UDRP) and I find including it as one of the
proposed models rather ludicrous. It is certainly easy to implement. And
cheap. <br><br>
Alan<br><br>
At 14/01/2018 03:24 PM, Holly Raiche wrote:<br><br>
<blockquote type="cite" class="cite" cite="">So you do support responding -
whatever it is called?<br><br>
Thanks<br><br>
Holly<br>
On 15 Jan 2018, at 7:15 am, Sebicann Bachollet
<<a href="mailto:sebicann@bachollet.fr">sebicann@bachollet.fr</a>>
wrote:<br><br>
<blockquote type="cite" class="cite" cite="">Yes Holly<br>
It is exactly what I was pointing out.<br>
SeB<br><br>
<br>
<blockquote type="cite" class="cite" cite="">Le 14 janv. 2018 à 20:35, Holly
Raiche
<<a href="mailto:h.raiche@internode.on.net">
h.raiche@internode.on.net</a>> a écrit :<br><br>
Hi Sebastian<br><br>
I did read the words. But seriously, he is asking for a response -
whatever it is called. And given the importance of the issue,
we should respond - whatever we call it.<br><br>
Holly<br>
On 15 Jan 2018, at 3:05 am, Sebicann Bachollet
<<a href="mailto:sebicann@bachollet.fr">sebicann@bachollet.fr</a>>
wrote:<br><br>
<blockquote type="cite" class="cite" cite="">No comment but feedback ;)<br>
"To help inform this, please provide <b>your feedback by 29 January
2018</b>. Please send your feedback to
<a href="mailto:gdpr@icann.org">gdpr@icann.org</a>. »<br>
<a href="https://www.icann.org/news/blog/data-protection-and-privacy-update-seeking-community-feedback-on-proposed-compliance-models">
https://www.icann.org/news/blog/data-protection-and-privacy-update-seeking-community-feedback-on-proposed-compliance-models</a>
<br>
SeB<br><br>
<blockquote type="cite" class="cite" cite="">Le 14 janv. 2018 à 16:39, Glenn
McKnight
<<a href="mailto:mcknight.glenn@gmail.com">mcknight.glenn@gmail.com</a>
> a écrit :<br><br>
Hi Holly<br>
Interesting you mentioned this issue, two things to share with
you<br><br>
1. NCUC did a session at the IGF and curious if anyone followed
their tread. they had a good google doc on the issues<br>
2. NARALO is having monthly hot topics during the second half of our
monthly membership calls. I was thinking of this issue as a topic for
March since I have Cybersecurity as the February topic. I
will need someone to level set the issue. We had Net Neutrality for
January<br><br>
Glenn<br><br>
Glenn McKnight<br>
NARALO Secretariat<br>
<a href="mailto:mcknight.glenn@gmail.com">mcknight.glenn@gmail.com</a><br>
skype gmcknight<br>
twitter gmcknight<br>
289-830 6259<br>
.<br><br>
On Sun, Jan 14, 2018 at 1:07 AM, Holly Raiche
<<a href="mailto:h.raiche@internode.on.net">
h.raiche@internode.on.net</a>> wrote:<br>
<dl>
<dd>Folks<br><br>
</dd><dd>Two days ago, Goran’s blog posted ICANN’s proposed there models for
addressing the issue of RDS information and the EU Data Protection
rules. According to the blog, 'community input' is being sought -
by the end of January.<br><br>
</dd><dd>Given the significance of this discussion on the information that
registries/registrars collect and display, I am assuming that ALAC will
be making comments? We should, at the least, have a page on the wiki for
comments???<br><br>
</dd><dd>Holly<br>
</dd><dd>_______________________________________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dd></dl><br>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><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/">http://www.atlarge.icann.org</a>
<br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
</blockquote></blockquote></blockquote></blockquote><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;YQXPR0101MB1589;27:VKdvj5FaSMKqurXWxPSs+5KrD7bDD/z8Moc1vJY/5HGcetDlA7ssVCV/YElAUh7SGN24GFL4MjoTHmpx97pl9ljfUuFYftyzmxdiPED3xH0Yuhq0n312NRn8xUkI1sHN<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
jEucbbUatzmeUElwm8qHyl9PflMj0MX5zDILXM3lJZqNG+Qw6mRWfuvCa7BJkfZPBvWUFPdAfb+KZZ6q9cvWmtDVfaoxUVOj39PuvHHusgWHqVhxcOuKs+OgEvaoDljUn0N5yfBbgrkmusOJV/r0yA==<br>
<br>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><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></div>
</blockquote></div><br></div></body></html>