<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="+1"><font face="Lucida Grande">As a veteran of that
[ridiculous] IAG process, I can confirm that the procedure
suggested does not make much sense in terms of how data
protection law is understood and enforced. Nevertheless, the
procedure and report was passed, and the GNSO accepted it
despite the fact that the registrars knew it would not work.
Another IAG is being struck in the fall, with a different
Charter, and we will have to pay close attention to that one
to ensure that it makes more sense than the last one did.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie Perrin</font></font></p>
<p><font size="+1"><font face="Lucida Grande">PS that committee and
process currently has won the prize in my experience (which
includes 30 years in government, chalking up a few committees
that offered a tough record to beat) for utterly useless and
senseless going in circles. Nevertheless, I am going to join
the next one...either to beat the previous record holder, or
validate that old saw about repeating something being the triumph
of hope over experience....please join, it will be fun!</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-04-19 06:59, Ayden Férdeline
wrote:<br>
</div>
<blockquote
cite="mid:UsPEuEZIzwon-dJ4D19FSr-VrJt6JMgIY1jncGEqwj9YjPYWGVea4vI9bTEv4t-d4MXLyIZ9jbb52Ko0GqFf-IKTQXa8FK8q4pbwx4mbZaY=@ferdeline.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div>An updated procedure for Handling WHOIS Conflicts with
Privacy Laws has been published on the ICANN website. In
practice, however, it is still bordering on the impossible for
anyone to make use of. The level of granularity expected by
ICANN in order to make use of the alternative trigger (see the <a
moz-do-not-send="true" rel="nofollow" title="redlined file"
href="https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedure-redline-18apr17-en.pdf">redlined
file</a> here) strikes me as very unreasonable.<br>
</div>
<div><br>
</div>
<div class="protonmail_signature_block ">
<div class="protonmail_signature_block-user ">
<div>Ayden Férdeline<br>
</div>
<div><a moz-do-not-send="true"
title="http://www.linkedin.com/in/ferdeline"
href="http://www.linkedin.com/in/ferdeline">linkedin.com/in/ferdeline</a><br>
</div>
</div>
<div class="protonmail_signature_block-proton
protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<blockquote type="cite" class="protonmail_quote">
<div>-------- Original Message --------<br>
</div>
<div>Subject: Daily Digest of ICANN.org<br>
</div>
<div>Local Time: 19 April 2017 12:30 AM<br>
</div>
<div>UTC Time: 18 April 2017 23:30<br>
</div>
<div>From: <a class="moz-txt-link-abbreviated" href="mailto:no-reply@icann.org">no-reply@icann.org</a><br>
</div>
<div>To: Ayden Férdeline <a class="moz-txt-link-rfc2396E" href="mailto:ayden@ferdeline.com"><ayden@ferdeline.com></a><br>
</div>
<div><br>
</div>
<div class="u-emailContainer">
<div class="head-wrapper">
<table class="head-wrap">
<tbody>
<tr>
<td width="50px"><img moz-do-not-send="true"
alt="ICANN"
src="http://icann.org/assets/icann_button.png"><br>
</td>
<td align="left">
<h1>Daily Digest of ICANN.org<br>
</h1>
</td>
</tr>
</tbody>
</table>
</div>
<div class="u-centeredContainer">
<table class="body-wrap">
<tbody>
<tr>
<td>
<div class="DigestList">
<h3>News & Announcements<br>
</h3>
<div>
<hr><br>
</div>
<div class="DigestEntry">
<h4><a moz-do-not-send="true" rel="noreferrer
nofollow noopener"
href="http://icann.org/news/announcement-2017-04-18-en">Updated
ICANN Procedure for Handling WHOIS Conflicts
with Privacy Laws Now Available</a><br>
</h4>
<p class="DigestEntry-summary"><br>
</p>
<div>LOS ANGELES – 18 April 2017 – The Internet
Corporation for Assigned Names and Numbers
(ICANN) today published the updated Procedure
for Handling WHOIS Conflicts with Privacy Laws
(WHOIS Procedure), which is effective
immediately.
Read the Revised WHOIS Procedure.
The WHOIS Procedure has been revised to
incorporate an alternative trigger to invoke
the WHOIS Procedure. The current trigger in
the WHOIS Procedure allows a registry operator
or ICANN-accredited registrar to invoke the
procedure if the contracted party is in
receipt of a notification of an action that
its compliance wit...<br>
</div>
<div><a moz-do-not-send="true" rel="noreferrer
nofollow noopener"
href="http://icann.org/news/announcement-2017-04-18-en">Read
more</a><br>
</div>
<p><br>
</p>
<div>
<hr><br>
</div>
</div>
<p class="u-linkArrow"><a moz-do-not-send="true"
rel="noreferrer nofollow noopener"
href="http://icann.org/news">BROWSE ALL NEWS</a><br>
</p>
</div>
<div class="DigestList">
<h3>From the ICANN Blog<br>
</h3>
<div>
<hr><br>
</div>
<div class="DigestEntry">
<h4><a moz-do-not-send="true" rel="noreferrer
nofollow noopener"
href="http://icann.org/news/blog/q-a-what-the-retirement-of-google-site-search-means-for-icann">Q&A:
What the Retirement of Google Site Search
Means for ICANN</a><br>
</h4>
<p class="DigestEntry-summary"><br>
</p>
<div>ICANN’s Community Collaboration Services
team provides digital services to the ICANN
community, which includes the ICANN
organization and community websites. Google
recently announced a change in direction that
affects the entire ICANN website ecosystem. As
director of this group, I’d like to share the
impact of this change – and the steps ICANN is
taking to minimize the disruption.
What is Google changing?
Google recently announced that starting 1
April 2017 (or at the end of any existing
contracts), it would begin retiring a commonly
used paid product called Google S...<br>
</div>
<div><a moz-do-not-send="true" rel="noreferrer
nofollow noopener"
href="http://icann.org/news/blog/q-a-what-the-retirement-of-google-site-search-means-for-icann">Read
more</a><br>
</div>
<p><br>
</p>
<div>
<hr><br>
</div>
</div>
<p class="u-linkArrow"><a moz-do-not-send="true"
rel="noreferrer nofollow noopener"
href="http://icann.org/news/blog">BROWSE ALL
BLOG ARTICLES</a><br>
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<div class="footer">
<table class="footer-wrap">
<tbody>
<tr>
<td>
<p><br>
</p>
<div>This message was sent to <a class="moz-txt-link-abbreviated" href="mailto:ayden@ferdeline.com">ayden@ferdeline.com</a>
from:<br>
</div>
<p>ICANN | 12025 Waterfront Drive Suite 300 | Los
Angeles, CA 90094-2536<br>
</p>
</td>
</tr>
</tbody>
</table>
<p><a moz-do-not-send="true" rel="noreferrer nofollow
noopener"
href="http://icann.org/user/account_setting/edit?section=news">Manage
Your Subscription</a><br>
</p>
</div>
</div>
</blockquote>
<div><br>
</div>
</blockquote>
<br>
</body>
</html>