<div dir="ltr"><div class="gmail_default" style="font-family:garamond,serif;font-size:large">FYI</div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="garamond, serif" size="4">--<br>Kind regards,<br>Bartlett D. Morgan<br></font><br></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">ICANN At-Large Staff</b> <span dir="ltr"><<a href="mailto:staff@atlarge.icann.org">staff@atlarge.icann.org</a>></span><br>Date: 19 April 2017 at 04:08<br>Subject: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available<br>To: ALAC Announce <<a href="mailto:alac-announce@atlarge-lists.icann.org">alac-announce@atlarge-lists.icann.org</a>><br><br><br>
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<span id="m_5578513316086408961OLK_SRC_BODY_SECTION">
<div>
<div style="background-color:#ffffff;font-family:arial;font-size:small">
<div style="width:758px;padding:10px;border:1px solid #cccccc;margin-left:auto;margin-right:auto">
<div style="width:738px;margin-left:auto;margin-right:auto"><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=" target="_blank"><img alt="ICANN" src="https://www.icann.org/sites/default/files/assets/icann-primary-logo-94x94-en.png" style="border:0px;width:94px;height:94px;float:left;margin-top:0px;margin-right:10px">[icann.org]</a>
<h2>News Alert</h2>
<p style="margin:0px 0px 10px 0px;font-family:arial;font-size:small"><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=" target="_blank">https://www.icann.org/news/<wbr>announcement-2017-04-18-en[<wbr>icann.org]</a></p>
<hr style="margin:20px 0px 0px 0px">
<h2 style="clear:left;margin-bottom:0px">Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available</h2>
<p style="margin:15px 0px 0px 0px">18 April 2017</p>
<p>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.</p>
<p><strong><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=" target="_blank">Read
the Revised WHOIS Procedure[icann.org]</a>.</strong></p>
<p>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.</p>
<p>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.</p>
<p>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=" target="_blank">
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=" target="_blank">
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.</p>
<h3>Background</h3>
<p>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=" target="_blank">
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=" target="_blank">
review[icann.org]</a> of the procedure in May 2014 and has concluded this review with this update to the WHOIS Procedure.</p>
<p>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=" target="_blank">
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.</p>
<h3>About ICANN</h3>
<p><em>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=" target="_blank">
www.icann.org[icann.org]</a>.</em></p>
</div>
</div>
<br>
<br>
<img src="http://click.icptrack.com/icp/track.php?msgid=1003147&act=CWP8&r=28876652&c=165637" width="1" height="1"></div>
</div>
</span>
</div>
<br>______________________________<wbr>_________________<br>
ALAC-Announce mailing list<br>
<a href="mailto:ALAC-Announce@atlarge-lists.icann.org">ALAC-Announce@atlarge-lists.<wbr>icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-announce" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac-<wbr>announce</a><br>
<br>
At-Large Official Site: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br></div><br></div>