<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; "><blockquote type="cite"><div lang="DE" link="blue" vlink="purple" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "></div></blockquote><div><br></div>Good afternoon:<div><br></div><div>Allow me to recapitulate some of the issues associated with this ICANN announcement.</div><div><br></div><div>1.<span class="Apple-tab-span" style="white-space:pre"> </span>The corresponding IAG completed its work nearly one year ago. It is quite unsatisfactory that after substantial community input in the IAG, ICANN spends such a long time (presumably in GNSO Council and in ICANN Legal - I am not sure) apparently making no relevant improvements before finally issuing a revised procedure (however unacceptable that may be.)</div><div><br></div><div>2.<span class="Apple-tab-span" style="white-space:pre"> </span>The dissenting opinions in the IAG by Stephanie Perrin and myself (Annexe 4 in the above document) have been completely ignored and suppressed by iCANN. I find that quite unacceptable.</div><div>Allow me to recall that I had proposed that ICANN should either adopt international best practice for privacy protection or issue a block exemption for all EU based Registries and Registrars.</div><div>Neither option was entertained by the ICANN staff at the time.</div><div><br></div><div>Background to these matters will be forwarded in a separate mail.</div><div><br></div><div>3.<span class="Apple-tab-span" style="white-space:pre"> </span>Meanwhile, presumably in response to the EU GDPR, ICANN has finally and belatedly initiated a discussion with the Data Protection Commissioners at ICANN58.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Thus, I rather expect that this revised procedure will prove to be obsolete before it begins.</div><div><br></div><div>Accordingly, the Conclusion to the revised procedure (Step 6) that ICANN will 'review the … process annually' may well prove to be an anachronism.</div><div><br></div><div>Regards</div><div><br></div><div><br></div><div>CW</div><div><br></div><div><br></div><div><br></div><div><br></div><div><div><div>On 19 Apr 2017, at 11:50, "Mühlberg, Annette" <<a href="mailto:annette.muehlberg@verdi.de">annette.muehlberg@verdi.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<title>ICANN News Alert</title>
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Überschrift 2 Zchn";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Überschrift 3 Zchn";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.floatcenter, li.floatcenter, div.floatcenter
{mso-style-name:floatcenter;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
text-align:center;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.floatleft, li.floatleft, div.floatleft
{mso-style-name:floatleft;
margin-top:0cm;
margin-right:12.0pt;
margin-bottom:12.0pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.floatright, li.floatright, div.floatright
{mso-style-name:floatright;
margin-top:0cm;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:12.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.box, li.box, div.box
{mso-style-name:box;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:12.0pt;
margin-left:0cm;
background:#F8F8F8;
border:none;
padding:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.dark, li.dark, div.dark
{mso-style-name:dark;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.medium, li.medium, div.medium
{mso-style-name:medium;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.light, li.light, div.light
{mso-style-name:light;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.dark1, li.dark1, div.dark1
{mso-style-name:dark1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
background:#DEDEDE;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.medium1, li.medium1, div.medium1
{mso-style-name:medium1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
background:#EFEFEF;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.light1, li.light1, div.light1
{mso-style-name:light1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
background:#F8F8F8;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.berschrift2Zchn
{mso-style-name:"Überschrift 2 Zchn";
mso-style-priority:9;
mso-style-link:"Überschrift 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.berschrift3Zchn
{mso-style-name:"Überschrift 3 Zchn";
mso-style-priority:9;
mso-style-link:"Überschrift 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.E-MailFormatvorlage32
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="DE" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;-webkit-line-break: after-white-space">
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Dear all,
<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">we decided in our phone call yesturday to discuss in our next EURALO telco the WHOIS issue in context of the implementation of the EU General Data Protection
Regulation (GDPR). So this (see below) is interesting material in this context. <o:p>
</o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Annette<o:p></o:p></span></p>
<div><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">***<o:p></o:p></span></p><p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">Annette Mühlberg
<o:p></o:p></span></b></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">ver.di Bundesverwaltung, Ressort 1<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">Politik und Planung<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">Digitale Arbeit, Netzpolitik, E-Government<b><o:p></o:p></b></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; ">Leiterin der ver.di-Projektgruppe "Digitalisierung"<o:p></o:p></span></p>
</div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:alac-announce-bounces@atlarge-lists.icann.org">alac-announce-bounces@atlarge-lists.icann.org</a> [mailto:alac-<a href="mailto:announce-bounces@atlarge-lists.icann.org">announce-bounces@atlarge-lists.icann.org</a>]
<b>Im Auftrag von </b>ICANN At-Large Staff<br>
<b>Gesendet:</b> Mittwoch, 19. April 2017 10:09<br>
<b>An:</b> ALAC Announce<br>
<b>Betreff:</b> [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available<o:p></o:p></span></p>
</div>
</div><p class="MsoNormal"><o:p> </o:p></p>
<div><p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; "> </span></p>
</div>
<div>
<div>
<div style="border:solid #CCCCCC 1.0pt;padding:8.0pt 8.0pt 8.0pt 8.0pt">
<div><p class="MsoNormal" style="background:white"><span style="font-family: Arial, sans-serif; "><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=hsrBi_CR3TLGOV-Rd042QZLZiVb5_XjdhTOlbGRbmlE&e="><span style="border:solid windowtext 1.0pt;padding:0cm;text-decoration:none"><span><~WRD000.jpg></span></span>[icann.org]</a>
<o:p></o:p></span></p>
<h2 style="background:white"><span style="font-family: Arial, sans-serif; ">News Alert<o:p></o:p></span></h2><p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:7.5pt;margin-left:0cm;background:white">
<span style="font-family: Arial, sans-serif; "><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D04-2D18-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=xZ6w4HR7Kmj4hdbDPa0pl3Sr2fZyyXiuqgGRXs1g6i0&e=">https://www.icann.org/news/announcement-2017-04-18-en[icann.org]</a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="margin-top:15.0pt;text-align:center;background:white">
<span style="font-family: Arial, sans-serif; ">
<hr size="2" width="100%" align="center">
</span></div>
<h2 style="margin-bottom:0cm;margin-bottom:.0001pt;background:white"><span style="font-family: Arial, sans-serif; ">Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available<o:p></o:p></span></h2><p style="mso-margin-top-alt:11.25pt;margin-right:0cm;margin-bottom:0cm;margin-left:0cm;margin-bottom:.0001pt;background:white">
<span style="font-family: Arial, sans-serif; ">18 April 2017<o:p></o:p></span></p><p style="background:white"><span style="font-family: Arial, sans-serif; ">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.<o:p></o:p></span></p><p style="background:white"><strong><span style="font-family: Arial, sans-serif; "><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D2008-2D01-2D17-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=jrmS1HdvfMEhBbPTuLW34ztf9fVA4toDQ8ncnzDHsys&e=">Read
the Revised WHOIS Procedure[icann.org]</a>.</span></strong><span style="font-family: Arial, sans-serif; "><o:p></o:p></span></p><p style="background:white"><span style="font-family: Arial, sans-serif; ">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 with WHOIS obligations is prevented by local laws. With the additional trigger, a registry operator or ICANN-accredited
registrar may now also invoke the WHOIS Procedure by providing ICANN with a written statement from the applicable government agency responsible for enforcing its data privacy laws and indicating that a WHOIS obligation in an ICANN contract conflicts with such
applicable national law.<o:p></o:p></span></p><p style="background:white"><span style="font-family: Arial, sans-serif; ">The modification to the WHOIS Procedure is based on input from the community and the work of an Implementation Advisory Group (IAG), which was tasked with reviewing possible
changes to the WHOIS Procedure and providing the Generic Names Supporting Organization (GNSO) with recommendations to facilitate resolution of issues where WHOIS requirements conflict with applicable laws.<o:p></o:p></span></p><p style="background:white"><span style="font-family: Arial, sans-serif; ">In May 2016, the IAG submitted its
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_drafts_iag-2Dreview-2Dwhois-2Dconflicts-2Dprocedure-2D23may16-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=lfKB9ouJmAmJ3VAcZqKNXqTgVvHUJsVsA7YwpXsELJw&e=">
final report[gnso.icann.org]</a> [PDF, 155 KB] and recommendation to the GNSO Council. In February 2017, the GNSO Council passed a
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_resolutions-23201703&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=3cwNSUYaNBIjVfmk880P2VyhMSlA8fs7JPLY2GaU4bM&e=">
resolution[gnso.icann.org]</a> adopting IAG's recommendation and confirmed that the modification to the WHOIS Procedure does not change the intent of the original GNSO policy recommendations.<o:p></o:p></span></p>
<h3 style="background:white"><span style="font-family: Arial, sans-serif; ">Background<o:p></o:p></span></h3><p style="background:white"><span style="font-family: Arial, sans-serif; ">In November 2005, the GNSO
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issues_whois-2Dprivacy_council-2Drpt-2D18jan06.htm&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=MOYbTnOkoDT69LHCxZ03POnSMj_imLej3y2jxLb9Fhc&e=">
concluded a policy development process (PDP)[gnso.icann.org]</a> establishing a Procedure to allow gTLD registry operators and registrars to demonstrate when they are prevented by local laws from fully complying with the provisions of their respective ICANN
contracts regarding personal data in WHOIS. The ICANN Board of Directors adopted the recommendations in May 2006 and directed staff to develop such a procedure. A contracted party that credibly demonstrates that it is legally prevented from complying with
its WHOIS obligations can invoke the procedure, which became effective in January 2008. To date, the procedure has never been invoked. ICANN launched a
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dconflicts-2Dprocedure-2D2014-2D05-2D22-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=DS2cpoUbNG6nrt3BuRFtqD1G06BIiLssAkV2FCnxi8A&e=">
review[icann.org]</a> of the procedure in May 2014 and has concluded this review with this update to the WHOIS Procedure.<o:p></o:p></span></p><p style="background:white"><span style="font-family: Arial, sans-serif; ">Following a
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2014-2D10-2D14-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=n17aP_T9JJWAjzYJrhXRwaguwo5lb1igdZXtG579A4U&e=">
Call for Volunteers[icann.org]</a> addressed to all interested parties, an IAG was formed to review the implementation of the policy recommendations and began its work in January 2015. The IAG devoted most of its time to discussing whether additional triggers
to invoke the Procedure should be incorporated and, if so, how to ensure that they remain consistent with the existing policy.<o:p></o:p></span></p>
<h3 style="background:white"><span style="font-family: Arial, sans-serif; ">About ICANN<o:p></o:p></span></h3><p style="background:white"><em><span style="font-family: Arial, sans-serif; ">ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer
- a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community
with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other
unique Internet identifiers. For more information please visit: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=oLJzki4MqdSchXd-Kr9hrJaCrpe-aq5QgqKF3udB6Yk&e=">
www.icann.org[icann.org]</a>.</span></em><span style="font-family: Arial, sans-serif; "><o:p></o:p></span></p>
</div>
</div><p class="MsoNormal" style="background:white"><span style="font-family: Arial, sans-serif; "><br>
<br>
<span style="border:solid windowtext 1.0pt;padding:0cm"><span><image001.jpg></span></span><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>ALAC-Announce mailing list<br><a href="mailto:ALAC-Announce@atlarge-lists.icann.org">ALAC-Announce@atlarge-lists.icann.org</a><br>https://atlarge-lists.icann.org/mailman/listinfo/alac-announce<br><br>At-Large Official Site: http://www.atlarge.icann.org_______________________________________________<br>EURO-Discuss mailing list<br>EURO-Discuss@atlarge-lists.icann.org<br>https://atlarge-lists.icann.org/mailman/listinfo/euro-discuss<br><br>Homepage for the region: http://www.euralo.org</blockquote></div><br></div></body></html>