<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi paul,<br>
<br>
in fact we are doing the opposite, i.e. defining when something the
registrant already has can/most/should be taken away and we are
making certain that any such removal of a position the registrant is
in tune with his rights. <br>
<br>
The current status quo is that the registrant has privacy. <br>
<br>
The question now is: When can this be taken away and for what
reasons and what protections are needed to ensure that this
violation can not occur when it would violate the rights of the
registrant.<br>
<br>
As to your comments, there already are quasi supranational privacy
laws:<br>
<br>
no matter where you are located as a service provider, if you serve
customers from the EU, EU data privacy laws applies to your handling
of that customers data. So under current EU law, you will have to
protect the privacy rights of European customers. Now enforcement of
that may be another issue, but the legal basis is as above.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
<br>
<div class="moz-cite-prefix">Am 07.04.2015 um 15:26 schrieb McGrady,
Paul D.:<br>
</div>
<blockquote
cite="mid:75341379935C8848A681B6FBC94797F382CB6627@WSWMXDB02.winston.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Times New Roman","serif";
color:black;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1230843550;
mso-list-template-ids:1092899780;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1655177674;
mso-list-template-ids:2142924864;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 class="WordSection1">
<p class="MsoNormal"><span style="color:black">I’m becoming very
concerned that we are getting way off track here by
attempting to create supranational privacy rights and then
put the burden of interpretation of such supranational
privacy rights on providers and the enforcement of whether
or not the providers got it right onto ICANN. Before we go
further, I would really like for someone to point out where
we think we get this scope, because I’m not at all sure that
ICANN has the remit to create and enforce supranational
privacy rights (so I think it is very likely that we don’t
either). Can someone point me to the appropriate document?
Absent a pre-existing supranational privacy right, it seems
to me that the “process” for any violation of national
privacy rights would be for the abused party to take action
in the courts if a cause of action exists. I don’t see how
in the world we are going annex 200+ countries privacy laws…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Kathy Kleiman<br>
<b>Sent:</b> Tuesday, April 07, 2015 8:08 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] Missing Annex<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Steve and All,<br>
I think we need to add a missing Annex - one to cover the
process that should take place when a Requester or the
Trademark/Copyright Owner to which it is reporting disclose
the Revealed Data in way that is not consistent with the
limitations agreed to in the disclosure -- e.g., publishes
the data or passes it on to other third parties (who
presumably misuse it- which is how the Provider might learn
of the misuse). This action could, of course, compromise
the safety and security of individuals and organizations.<br>
<br>
I volunteer to work with others to write such an Annex by
next week... <br>
<br>
Best,<br>
Kathy<br>
<br>
:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in">Just a brief
note that could facilitate our discussion tomorrow with
regard to the “Annex” to the draft disclosure framework.
(Thanks Mary for recirculating this text.)
<o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in">As the title
spells out, the document sets forth “Some options for
resolving disputes arising from alleged false statements
leading to improper disclosures<b>.”
</b>The Annex is not intended to address any appeal
mechanism regarding a disclosure request, but only the
consequences of a request wrongfully granted because based
on false pretenses.
<o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in">In this
document, “some” options basically boils down to two
options. Under the first option, a requestor would agree to
submit such disputes to an arbitrator. (The other party to
the dispute, the privacy/proxy service provider, would
presumably agree to this method as well, as part of its
accreditation process.) The document provides some more
detail about the arbitration process, though certainly much
more work would need to be done to implement it.<o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in">Under the
second option, the requestor would agree, for purposes of
such wrongful disclosure disputes, to submit to the
jurisdiction of the courts in the territory where the
service provider is located. <o:p></o:p></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in">Our
discussions over the past few weeks may have made the last
paragraph of the Annex document less relevant. It is based
on the assumption that, under either option, not all
requestors would necessarily be required to agree. As
specified in section I.b.iv of the overall document, a
service provider could, if it chose, institute a “trusted
requestor” program to facilitate processing of requests from
reliable sources. The last paragraph of the Annex says that
a service provider could, if it chose, make such an
agreement a condition of entry into a “trusted requestor”
program, if it had one. This last paragraph may be
irrelevant if the group decides that
<u>some</u> dispute resolution process should be available <u>whenever</u>
the service provider believes it has wrongfully disclosed
based on false pretenses. But ultimately the group still
needs to decide whether there will be such a mandatory
dispute resolution process, and if so, which process it will
be (arbitration, or litigation in the service provider’s
home court).
<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
Looking forward to our discussion tomorrow.
</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Steve
Metalitz</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Mary Wong<br>
<b>Sent:</b> Monday, April 06, 2015 10:05 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] Agenda and
documents for WG call on 7 April 2014</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Dear
WG members,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The
proposed agenda for the next WG call on 7 April 2014
is as follows:</span><o:p></o:p></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo3">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Roll
call/updates to SOI</span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo3">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Continue
deliberations on Category F, specifically: (a)
attestation/signatory for Requests; (b) Section
III.C(5); (c) non-use of high-volume automated
processes; and (d) the Annex.</span><o:p></o:p></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo3">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Next
steps/next meeting</span><o:p></o:p></li>
</ol>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Please
also find attached an updated version of the draft
disclosure framework for agenda item #2. This
version accepts all the changes up to last week
(excluding prior suggested changes to the type of
information required on a Requestor), and adds the
recent language suggested by Val on attestation,
Todd and Volker on III.C(5) (in square brackets as
two alternate versions), and a final
paragraph/sentence on the automation issue, based on
language previously suggested by Todd and a
suggestion by James to look at the specific language
in the 2013 RAA applicable to this type of activity.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The
draft Annex 1 is also attached – it preserves the
original text that was presented to the WG several
weeks ago, since the WG chairs thought it would be
easier to review that way in order to ensure that
everyone is clear about the options being offered.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks
and cheers</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Mary
Wong</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Senior
Policy Director</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Internet
Corporation for Assigned Names & Numbers
(ICANN)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Telephone:
+1 603 574 4892</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Email:
<a moz-do-not-send="true"
href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
The contents of this message may be privileged and confidential.
Therefore, if this message has been received in error, please
delete it without reading it. Your receipt of this message is not
intended to waive any applicable privilege. Please do not
disseminate this message without the permission of the author.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>