<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Why should these TLds be put on block lists absent any evidence
of significant abusive use? Purely as a punitive measure for
complying with legal requirements? That is not reasonable.</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 24.10.2017 um 15:24 schrieb Dotzero:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ4XoYcq2+bG_QG1qJD9VB7V6S9nuyjkwsT4A2yuoJxtD9Zzwg@mail.gmail.com">
<div dir="ltr">
<div>
<div>I don't think that is the reaction John was thinking of
Volker. <br>
<br>
One reaction (proposal that has actually been made this
morning) to the going dark steps taken by Mijndomein is to
add FRLregistry and dotAmsterdam to block lists or RPZ. I
don't know whether this proposal will gain traction or not.
Other potential reactions might include blocking domains
registered through particular registrars. There is certainly
a potential for balkanization of the Internet from these
sorts of actions.<br>
<br>
</div>
Personally I'm taking a wait and see approach before deciding
what to propose internally within my organization for traffic
originating from TLDs or registrars who have gone dark. <br>
<br>
</div>
Michael Hammer<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Oct 24, 2017 at 7:00 AM, 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">
<div text="#000000" bgcolor="#FFFFFF">
<p>True. Legal Requirement (Action) -> Compliant
implementation (Reaction)</p>
<p>Seriously though, I see this as a legitimate proposal
for a registry operator to both meet the needs of law
enforcement to access this data and the data protection
requirements in the jurisdictions that affect their
business.</p>
<p>ICANN should not have turned this into a compliance
matter, but now that they did, It is good to see them
stand up and defend their need to remain compliant with
applicable laws. I see this as a model of how all Whois
data for European data subjects will likely look in less
than 6 months. <br>
</p>
<p>Best,</p>
<p>Volker<br>
</p>
<div>
<div class="h5">
<p><br>
</p>
<br>
<div class="m_-59333515633959626moz-cite-prefix">Am
24.10.2017 um 12:42 schrieb John Bambenek:<br>
</div>
<blockquote type="cite"> Every action has an equal and
opposite reaction. <br>
<br>
<div id="m_-59333515633959626AppleMailSignature">--
<div>John Bambenek</div>
</div>
<div><br>
On Oct 24, 2017, at 11:48, Volker Greimann <<a
href="mailto:vgreimann@key-systems.net"
target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p>Fighting the good fight.<br>
</p>
<br>
<div class="m_-59333515633959626moz-cite-prefix">Am
24.10.2017 um 11:32 schrieb Kris Seeburn:<br>
</div>
<blockquote type="cite"> This might be
interesting news….
<div><br>
</div>
<div><a
href="http://domainincite.com/22218-amsterdam-refuses-to-publish-whois-records-as-gdpr-row-escalates"
target="_blank" moz-do-not-send="true">http://domainincite.com/22218-<wbr>amsterdam-refuses-to-publish-<wbr>whois-records-as-gdpr-row-<wbr>escalates</a></div>
<div><br>
</div>
<div><br>
<div><br>
<blockquote type="cite">
<div>On Oct 24, 2017, at 07:59, jonathan
matkowsky <<a
href="mailto:jonathan.matkowsky@riskiq.net"
target="_blank"
moz-do-not-send="true">jonathan.matkowsky@riskiq.net</a><wbr>>
wrote:</div>
<br
class="m_-59333515633959626Apple-interchange-newline">
<div>
<div
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<div dir="auto">Hi, Chuck, Regarding
below, has a decision been made by
leadership whether to invite the
org folks to meet with us in Abu
Dhabi as Greg A. was suggesting?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks </div>
<div dir="auto">Jonathan </div>
<br>
<div class="gmail_quote">
<div>On Fri, Oct 20, 2017 at 2:46
AM jonathan matkowsky <<a
href="mailto:jonathan.matkowsky@riskiq.net"
target="_blank"
moz-do-not-send="true">jonathan.matkowsky@riskiq.net</a><wbr>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>
<div dir="auto">The other week
I was asking this group
about the significance of
the ePrivacy Directive and
asked to get some feedback.</div>
<div dir="auto"><br>
</div>
<div dir="auto">The memo says:</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto">While our
memorandum series will
primarily focus on the
GDPR, we will also address
other relevant pieces of
EU legislation that may
have effect on the
processing of personal
data through the Whois
services, such as but not
limited to the EU ePrivacy
Directive 2002/58/EC and
the proposed new EU
ePrivacy Regulation aimed
to replace the said
directive in May 2018.</div>
<div dir="auto"><br>
</div>
<div dir="auto">This is
exactly what I was asking
to understand.</div>
<div dir="auto"><br>
</div>
<div dir="auto">That said, I
do want to continue our
work, but I also have
limited resources—as do we
all—so the sooner we can
get this information, the
better. It may help us in
deciding the most
efficient way forward, or
at least help confirm we
aren’t wasting our time in
how we move forward here?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thanks </div>
<div dir="auto">Jonathan </div>
</div>
</div>
<div><br>
<div class="gmail_quote">
<div>On Thu, Oct 19, 2017 at
9:40 AM Greg Aaron <<a
href="mailto:gca@icginc.com" target="_blank" moz-do-not-send="true">gca@icginc.com</a>>
wrote:<br>
</div>
<blockquote
class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div bgcolor="white"
link="blue"
vlink="purple"
lang="EN-US">
<div
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055WordSection1">
<p
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055MsoPlainText"><a
name="m_-59333515633959626_m_7775193058745579155_m_7299029587959283055__MailEndCompose"
moz-do-not-send="true">Dear Chuck:</a></p>
<p
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055MsoPlainText"><span> </span></p>
<p
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055MsoPlainText"><span>ICANN
meetings are for
information-sharing.
And since we have
two efforts
working on some of
the exact same
issues, I suggest
that some
info-sharing could
be very helpful to
our volunteers. </span></p>
<p
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055MsoPlainText"><span> </span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">The ICANN Org effort with Hamilton is clearly
going to be more
comprehensive
than the narrow
effort our WG
has received
from Wilson
Sonsini. And as
you know, the
Org effort will
set a precedent
which will be
important for
our WG to
understand. </span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext"> </span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">The new memo, and those to come, are about the
impact of GDPR
on registration
data and WHOIS.
I draw your
attention to the
end of the blog
post:</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">“As a reminder, this legal analysis is intended
to serve as
building block
for community
discussions
about how to
approach GDPR
issues in the
domain name
space. [WHOIS.]</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">Here's where we need help from the
multistakeholder
community:</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">Please review the initial legal analysis and
provide
feedback. This
includes
identifying
possible
questions, and
how best to
interact with
data protection
agencies and
others to get to
the next step of
the analysis.</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">It will be helpful to receive your feedback at
the earliest
opportunity, so
as to inform the
upcoming
discussions at
ICANN60, and to
feed into future
iterations of
the legal
analysis.”</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext"> </span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">The RDS WG is the main place where the
multistakeholder
community is
considering
WHOIS. So one
would think that
ICANN Org would
have already
reached out to
our WG. I am
surprised that
it has not.
So, I think it’s
appropriate for
us to invite the
Org folks in.
The goal is to
understand that
work and ask
questions.
Maybe the RDS WG
could then
formulate some
feedback as
requested
above. After
all, we’ve been
thinking about
this stuff for
almost two years
now..</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext"> </span></span></p>
<p class="MsoNormal"><span>As
part of the
briefing, it would
be good to hear
about this
effort's schedule
and workplan. The
memo says: "We
intend to provide
a series of
memorandums, which
will address
different aspects
of the issue and
where the scope
and topics of each
such memorandum
will be discussed
and agreed with
ICANN. We
understand that
ICANN intends to
make each
memorandum
publicly
available." I do
not see any of
those details in
the memo or blog.
For example, what
topics will be the
subjects of the
forthcoming
memos? There’s
clearly a plan for
that.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>I
have no idea of
any of that will
come out in the
GDPR session on
Thursday, but
since that
consists of panel
presentations, I
am unsure and
would prefer that
our WG definitely
get a briefing and
a chance to ask
questions.</span><span><span
style="color:windowtext"></span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext"> </span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">All best,</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext">--Greg</span></span></p>
<p class="MsoNormal"><span><span
style="color:windowtext"> </span></span></p>
<span></span>
<div>
<div
style="border-style:solid
none
none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt
0in 0in">
<p
class="MsoNormal"><b><span
style="color:windowtext">From:</span></b><span style="color:windowtext"><span
class="m_-59333515633959626Apple-converted-space"> </span><a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@<wbr>icann.org</a><span
class="m_-59333515633959626Apple-converted-space"> </span>[mailto:<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-<wbr>pdp-wg-bounces@icann.org</a>]<span
class="m_-59333515633959626Apple-converted-space"> </span><b>On Behalf
Of<span
class="m_-59333515633959626Apple-converted-space"> </span></b>Stephanie
Perrin<br>
<b>Sent:</b><span
class="m_-59333515633959626Apple-converted-space"> </span>Thursday,
October 19,
2017 11:19 AM<br>
<b>To:</b><span
class="m_-59333515633959626Apple-converted-space"> </span><a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></span></p>
</div>
</div>
</div>
</div>
<div bgcolor="white"
link="blue"
vlink="purple"
lang="EN-US">
<div
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055WordSection1">
<div>
<div
style="border-style:solid
none
none;border-top-width:1pt;border-top-color:rgb(225,225,225);padding:3pt
0in 0in">
<p
class="MsoNormal"><span
style="color:windowtext"><br>
<b>Subject:</b><span
class="m_-59333515633959626Apple-converted-space"> </span>Re:
[gnso-rds-pdp-wg]
ICANN Legal
Opinion on
GDPR - Part 1</span></p>
</div>
</div>
</div>
</div>
<div bgcolor="white"
link="blue"
vlink="purple"
lang="EN-US">
<div
class="m_-59333515633959626m_7775193058745579155m_7299029587959283055WordSection1">
<p class="MsoNormal"> </p>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",serif">I am curious as to how the questions are being
framed. Who is
the client, ICANN
the MS body, ICANN
the CEO and staff
(who have been
found to be a
co-controller and
therefore have an
interest in
avoiding fines) or
ICANN the Board.</span></p>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",serif">There are different interests at stake here, I
think it would be
useful to get a
fuller
understanding of
how Teresa
Swineheart is
handling the
development of
questions.</span></p>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",serif">Stephanie Perrin</span></p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On
2017-10-19 10:43,
Chuck wrote:</p>
</div>
<blockquote
style="margin-top:5pt;margin-bottom:5pt">
<pre>Greg,</pre>
<pre> </pre>
<pre>Having just finished reading the Hamilton memo, I don't understand why you</pre>
<pre>think the WG needs a presentation? What would a presentation from Teresa or</pre>
<pre>other ICANN staff person provide us that we couldn't get from the memo</pre>
<pre>itself and other sources such as the ICANN Blog, etc.?</pre>
<pre> </pre>
<pre>Can you identify any advice from Hamilton that would supplant work we have</pre>
<pre>been doing? If so, please identify it.</pre>
<pre> </pre>
<pre>In my opinion:</pre>
<pre>- The advice of ways forward fits nicely into our policy development</pre>
<pre>processes.</pre>
<pre>- The Hamilton Memo confirms much of what we already heard from the DP</pre>
<pre>experts and Wilson Sonsini so we now have it from three separate sources.</pre>
<pre>- You are absolutely that we "need to understand and track the legal</pre>
<pre>advice being made" and that it overlaps what we are doing but I think that</pre>
<pre>will help us.</pre>
<pre> </pre>
<pre>Chuck</pre>
<pre> </pre>
<pre>-----Original Message-----</pre>
<pre>From: Greg Aaron [<a href="mailto:gca@icginc.com" target="_blank" moz-do-not-send="true">mailto:gca@icginc.com</a>] </pre>
<pre>Sent: Thursday, October 19, 2017 7:25 AM</pre>
<pre>To: Chuck <a href="mailto:consult@cgomes.com" target="_blank" moz-do-not-send="true"><consult@cgomes.com></a>; 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank" moz-do-not-send="true"><alan.greenberg@mcgill.ca></a>;</pre>
<pre>'GNSO RDS PDP' <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre>Subject: RE: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre> </pre>
<pre>Dear WG leadership:</pre>
<pre> </pre>
<pre>As we expected, this ICANN Org effort will have a profound effect on our</pre>
<pre>work. We will need to understand and track the legal advice being made,</pre>
<pre>which overlaps with and in some places may supplant work we have been doing.</pre>
<pre>And the memo's "Finding New Ways Forward" section (3.9) provides advice for</pre>
<pre>the policy-making process. Clearly our WG needs (deserves) a presentation</pre>
<pre>at Abu Dhabi from Teresa Swinehart, who is heading up this effort. </pre>
<pre> </pre>
<pre>Could this be done at the WG meeting on Wednesday 1 November? </pre>
<pre>Wednesday will be better attended, both in-person and remotely. (Some</pre>
<pre>members may still be in transit during the WG's early Saturday morning</pre>
<pre>meeting. And the Saturday meeting is at a challenging time for those</pre>
<pre>participating remotely -- ~6:30 a.m. Saturday morning in Europe / 12:30</pre>
<pre>a.m. Saturday East Coast USA.)</pre>
<pre> </pre>
<pre>As part of the briefing, it would be good to hear about this effort's</pre>
<pre>schedule, workplan, and immediate next steps. The memo says: "We intend to</pre>
<pre>provide a series of memorandums, which will address different aspects of the</pre>
<pre>issue and where the scope and topics of each such memorandum will be</pre>
<pre>discussed and agreed with ICANN. We understand that ICANN intends to make</pre>
<pre>each memorandum publicly available."</pre>
<pre> </pre>
<pre>All best,</pre>
<pre>--Greg</pre>
<pre> </pre>
<pre> </pre>
<pre> </pre>
<pre>-----Original Message-----</pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>] On Behalf Of Chuck</pre>
<pre>Sent: Thursday, October 19, 2017 8:51 AM</pre>
<pre>To: 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank" moz-do-not-send="true"><alan.greenberg@mcgill.ca></a>; 'GNSO RDS PDP'</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre> </pre>
<pre>I want to call attention to the following paragraph:</pre>
<pre> </pre>
<pre>"The memo highlights the complexity of these issues in the domain name</pre>
<pre>space, and concludes that the current open, publicly available WHOIS</pre>
<pre>services cannot remain unchanged. The WHOIS system has to become adaptable</pre>
<pre>to address the GDPR from the European perspective, as well as other changing</pre>
<pre>regulations around the world."</pre>
<pre> </pre>
<pre>After input from Data Protection experts, the Wilson Sonsini memo and now</pre>
<pre>this memo, do any in the WG disagree with this statement?</pre>
<pre> </pre>
<pre>Chuck</pre>
<pre> </pre>
<pre> </pre>
<pre> </pre>
<pre>-----Original Message-----</pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>] On Behalf Of Alan Greenberg</pre>
<pre>Sent: Thursday, October 19, 2017 5:04 AM</pre>
<pre>To: GNSO RDS PDP <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre> </pre>
<pre>Full Blog post is at</pre>
<pre><a href="https://www.icann.org/news/blog/data-protection-and-privacy-update" target="_blank" moz-do-not-send="true">https://www.icann.org/news/<wbr>blog/data-protection-and-<wbr>privacy-update</a>. Alan</pre>
<pre> </pre>
<pre>At 19/10/2017 12:23 AM, Alan Greenberg wrote:</pre>
<blockquote
style="margin-top:5pt;margin-bottom:5pt">
<pre>Perhaps it has already been posted, but if not, ICANN has received the </pre>
<pre>first part of the independent legal analysis of the GDPR in relation to </pre>
<pre>WHOIS that had been commissioned.</pre>
<pre> </pre>
<pre>It can be found at</pre>
<pre><a href="https://www.icann.org/en/system/files/files/gdpr-memorandum-part1-16oct" target="_blank" moz-do-not-send="true">https://www.icann.org/en/<wbr>system/files/files/gdpr-<wbr>memorandum-part1-16oct</a></pre>
<pre>17-e</pre>
</blockquote>
<pre>n.pdf.</pre>
<blockquote
style="margin-top:5pt;margin-bottom:5pt">
<pre> </pre>
<pre>Alan</pre>
</blockquote>
<pre> </pre>
<pre>______________________________<wbr>_________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
<pre> </pre>
<pre>______________________________<wbr>_________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
<pre> </pre>
<pre>______________________________<wbr>_________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<p class="MsoNormal"> </p>
</div>
</div>
______________________________<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/<wbr>listinfo/gnso-rds-pdp-wg</a></blockquote>
</div>
</div>
<div>--<span
class="m_-59333515633959626Apple-converted-space"> </span><br>
</div>
<div
class="m_-59333515633959626m_7775193058745579155gmail_signature"
data-smartmail="gmail_signature">Jonathan Matkowsky</div>
</blockquote>
</div>
</div>
<div dir="ltr"
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">--<span
class="m_-59333515633959626Apple-converted-space"> </span><br>
</div>
<div
class="m_-59333515633959626gmail_signature"
data-smartmail="gmail_signature"
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Jonathan
Matkowsky</div>
<br
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******<br>
</span><span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">This
message was sent from RiskIQ, and is
intended only for the designated
recipient(s). It may contain
confidential or proprietary
information and may be subject to
confidentiality protections. If you
are not a designated recipient, you
may not review, copy or distribute
this message. If you receive this in
error, please notify the sender by
reply e-mail and delete this
message. Thank you.</span>
<div
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><br
class="m_-59333515633959626webkit-block-placeholder">
</div>
<span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******</span><span
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">_______________________<wbr>________________________</span><br
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">gnso-rds-pdp-wg
mailing list</span><br
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a
href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></span><br
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span
style="font-family:Helvetica-Light;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</div>
<br>
<div>
<div dir="auto"
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div dir="auto"
style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div dir="auto"
style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div dir="auto"
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div
style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space">
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br
class="m_-59333515633959626Apple-interchange-newline">
<br>
</div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br
class="m_-59333515633959626Apple-interchange-newline">
<br>
</div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Kris
Seeburn</div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a
href="mailto:seeburn.k@gmail.com" target="_blank" moz-do-not-send="true">seeburn.k@gmail.com</a></div>
<div
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<ul
style="margin:0px;padding:0px
0px
8px;border:0px;outline:0px;font-family:Helvetica,Arial,sans-serif;vertical-align:baseline;list-style:none;line-height:17px;display:table-cell;width:504px;color:rgb(51,51,51)">
<li
style="margin:0px;padding:8px
12px 2px
0px;border:0px;outline:0px;font-style:inherit;font-size:11px;font-family:inherit;vertical-align:baseline;font-variant-ligatures:inherit;font-variant-caps:inherit;font-variant-numeric:inherit;font-variant-alternates:inherit;font-variant-east-asian:inherit;line-height:1.2em">
<dl
class="m_-59333515633959626public-profile"
style="margin:0px;padding:0px;border:0px;outline:0px;font-style:inherit;font-family:inherit;vertical-align:baseline;font-variant-ligatures:inherit;font-variant-caps:inherit;font-variant-numeric:inherit;font-variant-alternates:inherit;font-variant-east-asian:inherit;line-height:inherit;word-wrap:break-word">
<dd
style="margin:0px;padding:2px
9px 1px
0px;border:0px;outline:0px;font-style:inherit;font-family:inherit;vertical-align:top;font-variant-ligatures:inherit;font-variant-caps:inherit;font-variant-numeric:inherit;font-variant-alternates:inherit;font-variant-east-asian:inherit;line-height:inherit;display:inline-block;zoom:1"><a
href="http://www.linkedin.com/in/kseeburn/" title="View public profile"
name="m_-59333515633959626_webProfileURL" style="margin:0px 10px 0px
0px;padding:0px
0px 0px
19px;border:0px;outline:0px;font-style:inherit;font-family:inherit;vertical-align:middle;text-decoration:none;color:rgb(102,102,102);font-variant-ligatures:inherit;font-variant-caps:inherit;font-variant-numeric:inherit;font-variant-alternates:inherit;font-variant-east-asian:inherit;line-height:inherit;display:inline-block;zoom:1;background-image:url(http://s.c.lnkd.licdn.com/scds/common/u/images/apps/profile/sprite/sprite_profile_top_card_v8.png);background-position:0px
-249px;background-repeat:no-repeat no-repeat" target="_blank"
moz-do-not-send="true">www.linkedin.com/in/kseeburn/</a></dd>
</dl>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span
style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span><span><br
class="m_-59333515633959626Apple-interchange-newline">
<span><KeepItOn_Social_animated.gif></span>
</span></span></span></div>
<br>
</div>
<br>
<fieldset
class="m_-59333515633959626mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
<a class="m_-59333515633959626moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="m_-59333515633959626moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">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="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">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.
------------------------------<wbr>--------------
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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">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="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">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>______________________________<wbr>_________________</span><br>
<span>gnso-rds-pdp-wg mailing list</span><br>
<span><a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></span><br>
<span><a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</blockquote>
<br>
<pre class="m_-59333515633959626moz-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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">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="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">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.
------------------------------<wbr>--------------
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.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a>
Email: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">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="m_-59333515633959626moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">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>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org"
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/<wbr>listinfo/gnso-rds-pdp-wg</a><br>
</blockquote>
</div>
<br>
</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>
</body>
</html>