<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; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div><br>
</div>
<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="http://www.icann.org/"><img alt="ICANN" src="https://www.icann.org/sites/default/files/assets/icann-primary-94x94.jpg" style="border: 0px; width: 94px; height: 94px; float: left; margin-top: 0px; margin-right: 10px;"></a>
<h2>News Alert</h2>
<p style="margin: 0px 0px 10px 0px; font-family: arial; font-size: small;"><a href="https://www.icann.org/news/announcement-2016-07-21-en">https://www.icann.org/news/announcement-2016-07-21-en</a></p>
<hr style="margin: 20px 0px 0px 0px;">
<h2 style="clear: left; margin-bottom: 0px;">Notice of Preliminary Determination To Grant Registrar Data Retention Waiver Request</h2>
<p style="margin: 15px 0px 0px 0px;">21 July 2016</p>
<p>ICANN has made a preliminary determination that it is prepared to grant data retention waiver requests submitted by registrars World4 You Internet Service GmbH and LEDL.NET GmbH (the "Registrar") under the 2013 Registrar Accreditation Agreement (the "2013
RAA"). Section 2 of the Data Retention Specification (the "Specification") of 2013 RAA provides that prior to granting any exemption under the Specification, ICANN will post its determination on the ICANN website for a period of thirty (30) calendar days.</p>
<p>Pursuant to Section 2 of the Specification, Registrar submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of the Registrar's contention that compliance with the data collection and/or retention requirements of the
Specification violates applicable law.</p>
<p>The Waiver Request was originally accompanied by the letter of the Article 29 Working Party dated 6 June 2013 (Statement on the data protection impact of the revision of the ICANN RAA). The Waiver Request was later supplemented by a legal opinion of Austrian
counsel asserting that compliance with the data collection and/or retention requirements of the Specification violates various applicable provisions of Austrian data protection and telecommunications law.</p>
<p>The Waiver Request originally concerned Sections 1.1 and 1.2 of the Specification and sought to exclude any of these data elements from the retention obligation. In subsequent correspondence and good faith discussions it has been acknowledged that legitimate
purposes may exist for the retention of data elements specified in the Specification; provided that ICANN submits a comprehensive list of legitimate purposes and recipients or categories of recipients for which/whom the data elements need to be retained, so
that the Austrian registrars will be able to determine whether the data collection and/or retention requirements of the Specification constitute a so called standard application (Standardanwendung) which does not need to be notified with or authorized by the
Austrian Data Protection Authority (the "Authority"). Should this not be the case, each Austrian registrar will have to notify the Authority on an individual basis of the data collection and/or retention requirements of the Specification based upon the comprehensive
list of legitimate purposes and recipients or categories of recipients to be provided by ICANN or apply for authorization of such data collection and/or retention, where provided for under applicable Austrian law. Irrespective whether the data collection and/or
retention requirements of the Specification constitute a so called standard application or not, the registrars will be required to respect claims of data subjects for deletion or correction, to the extent provided for under applicable Austrian law.</p>
<p>Furthermore, the legal opinion of Austrian counsel accompanying the Waiver Request cited Article 6 para. 1 nos. 2 and 5 of the Austrian Data Protection Act (Datenschutzgesetz 2000). These sections provide as follows (the following is an unofficial translation
from German):</p>
<p>Article 6 para. 1 no. 2<br>
"Data shall only … be collected for the specific, explicit and legitimate purposes and not further processed in a way incompatible with those purposes; …."</p>
<p>Article 6 para. 1 no. 5<br>
"Data shall only … be kept in a form which permits identification of data subjects as long as this is necessary for the purposes for which the data were collected; a longer period of storage may be laid down in specific laws, particularly laws concerning archives."</p>
<p>The Registrar is therefore seeking a waiver with respect to Sections 1.1.1 through 1.1.8 of the Specification that seeks to reduce from two years to one year the period for which these specified data elements must be retained after the Registrar's sponsorship
of the Registration ends.</p>
<p>Against the background of the foregoing issues, ICANN has determined on a preliminary basis that it is prepared to grant the Waiver Request in a limited scope as outlined below. ICANN is posting this preliminary determination for a period of thirty (30)
days to seek feedback and input from the community on the proposed data retention waiver. After the thirty (30) day period following this posting has expired, ICANN will consider all feedback and input received before making a final determination on whether
to grant the Waiver Requests.</p>
<p>The scope of the proposed waiver would be to permit the Registrar to maintain the information specified in Sections 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of one (1) additional year
thereafter rather than two (2) additional years thereafter. The specific change to the Specification would be that, for the duration of the waiver, the retention requirement of Section 1.1 of the Data Retention Specification would be changed from "two additional
years" to "one additional year." </p>
<p>Apart from that, the Registrar shall remain obliged to retain all data elements specified in Sections 1.1 and 1.2 of the Specification for the periods specified therein; provided that ICANN submits a comprehensive list of legitimate purposes and recipients
or categories of recipients for which/whom the data elements need to be retained. ICANN hereby declares the " legitimate purposes for collection / retention and recipients or categories of recipients " contained in the "Description of 2013 RAA Data Retention
Specification - Data Elements, Legitimate Purposes for Collection/Retention and Recipients of Data" (available at
<a href="https://www.icann.org/en/system/files/files/raa-data-retention-elements-10aug15-en.pdf">
https://www.icann.org/en/system/files/files/raa-data-retention-elements-10aug15-en.pdf</a> [PDF, 295 KB]) (the "Description") to constitute such comprehensive list of legitimate purposes and recipients or categories of recipients, subject to further changes.</p>
<p>If additional or other legitimate purposes for collection / retention or recipients or categories of recipients become relevant in the future, ICANN will publicly notify thereof and change the Description accordingly. If changing the purposes or recipients
or categories of recipients requires the (additional) notification of or authorization by the Authority, the Registrar will conduct such notification or apply for such authorization accordingly.</p>
<p>ICANN shall provide reasonable additional information regarding the legitimate purposes or recipients or categories of recipients if and as reasonably requested by the Authority within the scope of such notification or application for authorization.</p>
<p>If and insofar as the Authority rules that the collection / retention of certain data for certain purposes and / or recipients or categories of recipients violate applicable law ICANN and the Registrar will determine in good faith whether and to what extent
the Description can be changed to accommodate the concerns of the Authority. The rules of the Waiver Request procedure described in Sections 2, 3, and 4 of the Specification shall apply accordingly in this case and written notice of the Authority's rejection
decision to ICANN will be deemed to constitute a further Waiver Request.</p>
<p>Furthermore, it is acknowledged that data elements which are subject to claims of data subjects for correction or deletion are excepted from the collection and/or retention requirements of the Specification, if and to the extent they are founded under applicable
Austrian law.</p>
<p>In all other respects the terms of the Specification would remain AS-IS.</p>
<p>If ICANN does make a final determination to grant the Waiver Request sought by the Registrars, the provisions of Section 3 of the Specification would apply to similar waivers requested by other registrars located in the same jurisdiction. Section 3 of the
Specification provides as follows:</p>
<blockquote>
<p>If (i) ICANN has previously waived compliance with the requirements of any requirement of this Data Retention Specification in response to a Waiver Request from a registrar that is located in the same jurisdiction as Registrar and (ii) Registrar is subject
to the same applicable law that gave rise to ICANN's agreement to grant such wavier, Registrar may request that ICANN to grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not
approving such request, in which case Registrar may thereafter make an Wavier Request pursuant to Section 2 of this Data Retention Specification.</p>
</blockquote>
<p>A public comment period will remain open until 23:59 UTC, 22 August, 2016. Public comments will be available for consideration by ICANN staff and the ICANN Board.</p>
<p>The Registrar's Waiver Request and supporting documents are available here: <a href="https://www.icann.org/en/system/files/files/waiver-request-ledlnet-gmbh-21jul16-en.pdf">
https://www.icann.org/en/system/files/files/waiver-request-ledlnet-gmbh-21jul16-en.pdf</a> [PDF, 2.92 MB].</p>
<p>Comments can be posted to: <a href="mailto:comments-ledlnet-gmbh-21jul16@icann.org">
comments-ledlnet-gmbh-21jul16@icann.org</a>.</p>
<p>Comments can be viewed at: <a href="https://forum.icann.org/lists/comments-ledlnet-gmbh-21jul16/">
https://forum.icann.org/lists/comments-ledlnet-gmbh-21jul16/</a>.</p>
</div>
</div>
<br>
<div style="background-color:#FFFFFF"><br>
</div>
<img src="http://click.icptrack.com/icp/track.php?msgid=991375&act=CWP8&r=28876652&c=165637" width="1" height="1"></div>
</div>
</span>
</body>
</html>