<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>It sounds like you want a contract the only gives you benefits and externalizes the risks and harm to everyone else. <br><br>--<div>John Bambenek</div></div><div><br>On Jun 6, 2017, at 12:45, Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Hi Jonathan,</p>
<p>we went through a very extended and painful exercise once before
with regard to obtaining a waiver from a contractual requirement
set by ICANN that conflicted with local law once before. In that
case, the option of such a waiver and the general process had been
included in the process, yet it still proved incredibly difficult
to complete despite ticking all the boxes of the requirements. We
do not care for such an experience ever again. <br>
</p>
<p>Therefore contracted parties have a vested interest in avoiding
such conflicts in the first place with any new policy. If such
conflicts exists, the policy needs to take them into account fully
and the process needs to be turned around. Contracted parties
should not have to obtain a waiver to avoid having to comply with
a contractual requirement but rather the obligation should only
apply if no conflict exists for that party. <br>
</p>
<p>We have learned from painful experiences in the past. <br>
</p>
<p>Best,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 06.06.2017 um 13:38 schrieb jonathan
matkowsky:<br>
</div>
<blockquote type="cite" cite="mid:CALsyHBnwca6xsuodJNy818GbM9whga1qNX2oWVaGV=pKrk+ehg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Volker,
can you please describe this main issue as you see it in more
detail?</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><span style="font-family:arial,sans-serif;font-size:12.8px"><i>"The
main issue is that ICANN has no working process in place
for a contracted party to show it has an issue with local
laws that can be reasonably invoked before getting called
on it by local authorities, e.g. being sued or fined. So
we need the excemptions baked into the policy to be safe
down the road."</i></span><br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div>Jonathan Matkowsky</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Tue, Jun 6, 2017 at 12:10 PM,
Volker Greimann <span dir="ltr"><<a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Am 02.06.2017 um 18:17 schrieb Andrew Sullivan:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Fri, Jun 02, 2017 at 07:00:23PM +0300, jonathan
matkowsky wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
"3.7.2 Registrar shall abide by applicable laws and
governmental<br>
regulations." Applicable laws vary from jurisdiction
to jurisdiction.<br>
We should keep this in mind.<br>
<br>
</blockquote>
Yes. Also, I don't know why we have to have an opinion
on what<br>
registrars or registries must do overall. What we need
to do, as far<br>
as I can tell, is understand what the data is and what
it is collected<br>
for, and then propose a policy that makes it _possible_
for registrars<br>
and registries to conform with their local laws. No?<br>
</blockquote>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
<span style="background-color:rgb(255,255,0)">
The main issue is that ICANN has no working process in
place for a contracted party to show it has an issue
with local laws that can be reasonably invoked before
getting called on it by local authorities, e.g. being
sued or fined. So we need the excemptions baked into the
policy to be safe down the road.</span><br>
<br>
"Just deal with that on your own later!" is not an
acceptable result.<br>
<br>
As a non-European leader recently put it: "No deal is
better than a bad deal!"<br>
<br>
Best,<br>
Volker<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a></blockquote>
</div>
<br>
</div>
</div>
</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>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>gnso-rds-pdp-wg mailing list</span><br><span><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div></blockquote></body></html>