<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="">
<title>ICANN News Alert</title>
<meta content="icann, internet, internet corporation for assigned names and numbers, iana" name="keywords">
<meta content="Internet Corporation for Assigned Names and Numbers" name="description">
<style type="text/css">
table.convey {
width: 100%;
font-family: Arial, Helvetica, sans-serif;
border: 1px solid #d8d8d8;
border-collapse: collapse;
}
table.convey th, table.convey td {
border: 1px solid #d8d8d8;
padding: .5em;
}
table.convey .dark {
background-color: #dedede;
}
table.convey .medium {
background-color: #efefef;
}
table.convey .light {
background-color: #f8f8f8;
}
.floatcenter {
margin-left: auto;
margin-right: auto;
text-align: center;
}
.floatleft {
float: left;
margin: 0 1em 1em 0;
}
.floatright {
float: right;
margin: 0 0 1em 1em;
}
.box {
background-color: #f8f8f8;
border: 1px solid #efefef;
-webkit-border-radius: 4px;
-khtml-border-radius: 4px;
-moz-border-radius: 4px;
border-radius: 4px;
padding: 15px 15px;
margin-bottom: 1em;
}
</style>
<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=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=DlgLTpKwxUYfFzc1IkN_QYgqfrFBBlcgw_IFzQi4VBc&e="><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-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=b9Rz7GWK2n6kaHGHibPZZdqLQFyz9B1cJ31ordUpySg&e=">https://www.icann.org/news/announcement-2017-05-03-en[icann.org]</a></p>
<hr style="margin: 20px 0px 0px 0px;">
<h2 style="clear: left; margin-bottom: 0px;">Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps Now Available for Public Comment</h2>
<p style="margin: 15px 0px 0px 0px;">3 May 2017</p>
<p>LOS ANGELES – 3 May 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today published a paper, "Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps," for public comment.</p>
<p><strong><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_files_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D03may17-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=urgNwSNHFAQBnoyOTEe2l6xH_P0UhlZRS9aGhupuvKU&e=">Read
the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps[icann.org]</a></strong> [PDF, 159 KB].</p>
<p>This paper is available for public comment through 12 June 2017. Feedback will be incorporated into a report of public comments and provided to the Generic Names Supporting Organization (GNSO) Council for their review and consideration.</p>
<p><strong><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dprivacy-2Dlaw-2D2017-2D05-2D03-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=zQiPCnur0bRGHrkivUNJ6L_6nkigx6yq6xhgoUXRQbc&e=">Comment
on the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law: Assessment and Next Steps[icann.org]</a></strong>.</p>
<p>In accordance with the <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=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=DSWb_J7FskZvxrZFVanpUBKjKPo8AKTMDUZKYtRPwiw&e=">
ICANN Procedure for Handling Whois Conflicts with Privacy Law (Whois Procedure)[icann.org]</a>, this paper opens a review process to gather community input on the effectiveness of the revised Whois Procedure, which was made effective on 18 April 2017. Furthermore,
as requested by the GNSO Council, ICANN is publishing this paper to provide analysis of and solicit community input on the practicality and feasibility of the triggers, as well as suggestions for moving forward with the review. Outputs from this assessment
and comment process are expected to inform the next periodic review of the procedure.</p>
<p>The Whois Procedure has recently been updated, although no ICANN-accredited registrar or registry operator to date has formally invoked the procedure. As a result, this analysis is based solely on community discussions and input received during the
<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=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=hMbLYjXc38c6PSvF8CLR03zUW9HcdkqP5eJsVdMX8hE&e=">
previous review[gnso.icann.org]</a> [PDF, 155 KB], which related to allowing for evaluation of an additional trigger for invoking the procedure. It also draws upon ICANN's experience administering other processes where a contracted party is seeking ICANN's
approval for new services, or waiving certain contractual requirements, as a point of comparison for the implementation of the procedure.</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=Kd8qDJlj6Y97KmseCq8x2N5PWl8IF0jU77SXMYqC_yw&s=VnVOq9oRsaF7sDPnFLjMhT5UeO3CCxxvKfL6huGXE_M&e=">
www.icann.org[icann.org]</a>.</em></p>
</div>
</div>
<br>
<br>
<img src="http://click.icptrack.com/icp/track.php?msgid=1003812&act=CWP8&r=28876652&c=165637" width="1" height="1"></div>
</div>
</span>
</body>
</html>