<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Because we can then have additional use cases. This is a stop-gap
to comply with legal requirements and also address certain
concerns. There may be other solutions, better solutions. Our job
is to develop these. If we fail, this is what we will end up with
in the long run rather than as a termporary solution.</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 24.10.2017 um 13:11 schrieb John
Bambenek:<br>
</div>
<blockquote type="cite"
cite="mid:15DBB930-2DEE-4801-B563-93ECE8796302@bambenekconsulting.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
So your solution is no one but law enforcement gets whois on
anyone? Because that appears to be the case for .frl and
.amsterdam. Why even bother talking about RDS then?<br>
<br>
<div id="AppleMailSignature">--
<div>John Bambenek</div>
</div>
<div><br>
On Oct 24, 2017, at 13:00, Volker Greimann <<a
href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">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>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>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 24.10.2017 um 12:42 schrieb
John Bambenek:<br>
</div>
<blockquote type="cite"
cite="mid:83AA58ED-4B03-4DDA-8DB8-02C8D023BE01@bambenekconsulting.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
Every action has an equal and opposite reaction. <br>
<br>
<div id="AppleMailSignature">--
<div>John Bambenek</div>
</div>
<div><br>
On Oct 24, 2017, at 11:48, Volker Greimann <<a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">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>Fighting the good fight.<br>
</p>
<br>
<div class="moz-cite-prefix">Am 24.10.2017 um 11:32
schrieb Kris Seeburn:<br>
</div>
<blockquote type="cite"
cite="mid:2881CADA-0F14-4D72-9762-FC129D1849F7@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
This might be interesting news….
<div class=""><br class="">
</div>
<div class=""><a
href="http://domainincite.com/22218-amsterdam-refuses-to-publish-whois-records-as-gdpr-row-escalates"
class="" moz-do-not-send="true">http://domainincite.com/22218-amsterdam-refuses-to-publish-whois-records-as-gdpr-row-escalates</a></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Oct 24, 2017, at 07:59,
jonathan matkowsky <<a
href="mailto:jonathan.matkowsky@riskiq.net"
class="" moz-do-not-send="true">jonathan.matkowsky@riskiq.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<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; -webkit-text-stroke-width: 0px;"
class="">
<div dir="auto" class="">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" class=""><br class="">
</div>
<div dir="auto" class="">Thanks </div>
<div dir="auto" class="">Jonathan </div>
<br class="">
<div class="gmail_quote">
<div class="">On Fri, Oct 20, 2017 at 2:46
AM jonathan matkowsky <<a
href="mailto:jonathan.matkowsky@riskiq.net"
class="" moz-do-not-send="true">jonathan.matkowsky@riskiq.net</a>>
wrote:<br class="">
</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 class="">
<div dir="auto" class="">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" class=""><br class="">
</div>
<div dir="auto" class="">The memo
says:</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">
<div dir="auto" class="">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" class=""><br
class="">
</div>
<div dir="auto" class="">This is
exactly what I was asking to
understand.</div>
<div dir="auto" class=""><br
class="">
</div>
<div dir="auto" class="">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" class=""><br
class="">
</div>
<div dir="auto" class="">Thanks </div>
<div dir="auto" class="">Jonathan </div>
</div>
</div>
<div class=""><br class="">
<div class="gmail_quote">
<div class="">On Thu, Oct 19, 2017
at 9:40 AM Greg Aaron <<a
href="mailto:gca@icginc.com"
target="_blank" class=""
moz-do-not-send="true">gca@icginc.com</a>>
wrote:<br class="">
</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" class=""
lang="EN-US">
<div
class="m_7775193058745579155m_7299029587959283055WordSection1">
<p
class="m_7775193058745579155m_7299029587959283055MsoPlainText"><a
name="m_7775193058745579155_m_7299029587959283055__MailEndCompose"
class=""
moz-do-not-send="true">Dear
Chuck:</a></p>
<p
class="m_7775193058745579155m_7299029587959283055MsoPlainText"><span
class=""> </span></p>
<p
class="m_7775193058745579155m_7299029587959283055MsoPlainText"><span
class="">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_7775193058745579155m_7299029587959283055MsoPlainText"><span
class=""> </span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">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
class=""><span
style="color:
windowtext;" class=""> </span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">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
class=""><span
style="color:
windowtext;" class="">“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
class=""><span
style="color:
windowtext;" class="">Here's
where we need help from
the multistakeholder
community:</span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">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
class=""><span
style="color:
windowtext;" class="">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
class=""><span
style="color:
windowtext;" class=""> </span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">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
class=""><span
style="color:
windowtext;" class=""> </span></span></p>
<p class="MsoNormal"><span
class="">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
class=""> </span></p>
<p class="MsoNormal"><span
class="">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
class=""><span
style="color:
windowtext;" class=""></span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class=""> </span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">All
best,</span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class="">--Greg</span></span></p>
<p class="MsoNormal"><span
class=""><span
style="color:
windowtext;" class=""> </span></span></p>
<span class=""></span>
<div class="">
<div style="border-style:
solid none none;
border-top-width: 1pt;
border-top-color: rgb(225,
225, 225); padding: 3pt
0in 0in;" class="">
<p class="MsoNormal"><b
class=""><span
style="color:
windowtext;"
class="">From:</span></b><span
style="color:
windowtext;" class=""><span
class="Apple-converted-space"> </span><a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
class=""
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a><span
class="Apple-converted-space"> </span>[mailto:<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
class=""
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>]<span
class="Apple-converted-space"> </span><b class="">On Behalf Of<span
class="Apple-converted-space"> </span></b>Stephanie
Perrin<br class="">
<b class="">Sent:</b><span
class="Apple-converted-space"> </span>Thursday, October 19, 2017 11:19
AM<br class="">
<b class="">To:</b><span
class="Apple-converted-space"> </span><a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
class=""
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" class=""
lang="EN-US">
<div
class="m_7775193058745579155m_7299029587959283055WordSection1">
<div class="">
<div style="border-style:
solid none none;
border-top-width: 1pt;
border-top-color: rgb(225,
225, 225); padding: 3pt
0in 0in;" class="">
<p class="MsoNormal"><span
style="color:
windowtext;" class=""><br
class="">
<b class="">Subject:</b><span
class="Apple-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" class=""
lang="EN-US">
<div
class="m_7775193058745579155m_7299029587959283055WordSection1">
<p class="MsoNormal"> </p>
<p class=""><span
style="font-size: 13.5pt;
font-family: "Lucida
Grande", serif;"
class="">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 class=""><span
style="font-size: 13.5pt;
font-family: "Lucida
Grande", serif;"
class="">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 class=""><span
style="font-size: 13.5pt;
font-family: "Lucida
Grande", serif;"
class="">Stephanie Perrin</span></p>
<p class="MsoNormal"> </p>
<div class="">
<p class="MsoNormal">On
2017-10-19 10:43, Chuck
wrote:</p>
</div>
<blockquote style="margin-top:
5pt; margin-bottom: 5pt;"
class="">
<pre class="">Greg,</pre>
<pre class=""> </pre>
<pre class="">Having just finished reading the Hamilton memo, I don't understand why you</pre>
<pre class="">think the WG needs a presentation? What would a presentation from Teresa or</pre>
<pre class="">other ICANN staff person provide us that we couldn't get from the memo</pre>
<pre class="">itself and other sources such as the ICANN Blog, etc.?</pre>
<pre class=""> </pre>
<pre class="">Can you identify any advice from Hamilton that would supplant work we have</pre>
<pre class="">been doing? If so, please identify it.</pre>
<pre class=""> </pre>
<pre class="">In my opinion:</pre>
<pre class="">- The advice of ways forward fits nicely into our policy development</pre>
<pre class="">processes.</pre>
<pre class="">- The Hamilton Memo confirms much of what we already heard from the DP</pre>
<pre class="">experts and Wilson Sonsini so we now have it from three separate sources.</pre>
<pre class="">- You are absolutely that we "need to understand and track the legal</pre>
<pre class="">advice being made" and that it overlaps what we are doing but I think that</pre>
<pre class="">will help us.</pre>
<pre class=""> </pre>
<pre class="">Chuck</pre>
<pre class=""> </pre>
<pre class="">-----Original Message-----</pre>
<pre class="">From: Greg Aaron [<a href="mailto:gca@icginc.com" target="_blank" class="" moz-do-not-send="true">mailto:gca@icginc.com</a>] </pre>
<pre class="">Sent: Thursday, October 19, 2017 7:25 AM</pre>
<pre class="">To: Chuck <a href="mailto:consult@cgomes.com" target="_blank" class="" moz-do-not-send="true"><consult@cgomes.com></a>; 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank" class="" moz-do-not-send="true"><alan.greenberg@mcgill.ca></a>;</pre>
<pre class="">'GNSO RDS PDP' <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre class="">Subject: RE: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre class=""> </pre>
<pre class="">Dear WG leadership:</pre>
<pre class=""> </pre>
<pre class="">As we expected, this ICANN Org effort will have a profound effect on our</pre>
<pre class="">work. We will need to understand and track the legal advice being made,</pre>
<pre class="">which overlaps with and in some places may supplant work we have been doing.</pre>
<pre class="">And the memo's "Finding New Ways Forward" section (3.9) provides advice for</pre>
<pre class="">the policy-making process. Clearly our WG needs (deserves) a presentation</pre>
<pre class="">at Abu Dhabi from Teresa Swinehart, who is heading up this effort. </pre>
<pre class=""> </pre>
<pre class="">Could this be done at the WG meeting on Wednesday 1 November? </pre>
<pre class="">Wednesday will be better attended, both in-person and remotely. (Some</pre>
<pre class="">members may still be in transit during the WG's early Saturday morning</pre>
<pre class="">meeting. And the Saturday meeting is at a challenging time for those</pre>
<pre class="">participating remotely -- ~6:30 a.m. Saturday morning in Europe / 12:30</pre>
<pre class="">a.m. Saturday East Coast USA.)</pre>
<pre class=""> </pre>
<pre class="">As part of the briefing, it would be good to hear about this effort's</pre>
<pre class="">schedule, workplan, and immediate next steps. The memo says: "We intend to</pre>
<pre class="">provide a series of memorandums, which will address different aspects of the</pre>
<pre class="">issue and where the scope and topics of each such memorandum will be</pre>
<pre class="">discussed and agreed with ICANN. We understand that ICANN intends to make</pre>
<pre class="">each memorandum publicly available."</pre>
<pre class=""> </pre>
<pre class="">All best,</pre>
<pre class="">--Greg</pre>
<pre class=""> </pre>
<pre class=""> </pre>
<pre class=""> </pre>
<pre class="">-----Original Message-----</pre>
<pre class="">From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a></pre>
<pre class="">[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" class="" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Chuck</pre>
<pre class="">Sent: Thursday, October 19, 2017 8:51 AM</pre>
<pre class="">To: 'Alan Greenberg' <a href="mailto:alan.greenberg@mcgill.ca" target="_blank" class="" moz-do-not-send="true"><alan.greenberg@mcgill.ca></a>; 'GNSO RDS PDP'</pre>
<pre class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre class="">Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre class=""> </pre>
<pre class="">I want to call attention to the following paragraph:</pre>
<pre class=""> </pre>
<pre class="">"The memo highlights the complexity of these issues in the domain name</pre>
<pre class="">space, and concludes that the current open, publicly available WHOIS</pre>
<pre class="">services cannot remain unchanged. The WHOIS system has to become adaptable</pre>
<pre class="">to address the GDPR from the European perspective, as well as other changing</pre>
<pre class="">regulations around the world."</pre>
<pre class=""> </pre>
<pre class="">After input from Data Protection experts, the Wilson Sonsini memo and now</pre>
<pre class="">this memo, do any in the WG disagree with this statement?</pre>
<pre class=""> </pre>
<pre class="">Chuck</pre>
<pre class=""> </pre>
<pre class=""> </pre>
<pre class=""> </pre>
<pre class="">-----Original Message-----</pre>
<pre class="">From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a></pre>
<pre class="">[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" class="" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Alan Greenberg</pre>
<pre class="">Sent: Thursday, October 19, 2017 5:04 AM</pre>
<pre class="">To: GNSO RDS PDP <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true"><gnso-rds-pdp-wg@icann.org></a></pre>
<pre class="">Subject: Re: [gnso-rds-pdp-wg] ICANN Legal Opinion on GDPR - Part 1</pre>
<pre class=""> </pre>
<pre class="">Full Blog post is at</pre>
<pre class=""><a href="https://www.icann.org/news/blog/data-protection-and-privacy-update" target="_blank" class="" moz-do-not-send="true">https://www.icann.org/news/blog/data-protection-and-privacy-update</a>. Alan</pre>
<pre class=""> </pre>
<pre class="">At 19/10/2017 12:23 AM, Alan Greenberg wrote:</pre>
<blockquote
style="margin-top: 5pt;
margin-bottom: 5pt;"
class="">
<pre class="">Perhaps it has already been posted, but if not, ICANN has received the </pre>
<pre class="">first part of the independent legal analysis of the GDPR in relation to </pre>
<pre class="">WHOIS that had been commissioned.</pre>
<pre class=""> </pre>
<pre class="">It can be found at</pre>
<pre class=""><a href="https://www.icann.org/en/system/files/files/gdpr-memorandum-part1-16oct" target="_blank" class="" moz-do-not-send="true">https://www.icann.org/en/system/files/files/gdpr-memorandum-part1-16oct</a></pre>
<pre class="">17-e</pre>
</blockquote>
<pre class="">n.pdf.</pre>
<blockquote
style="margin-top: 5pt;
margin-bottom: 5pt;"
class="">
<pre class=""> </pre>
<pre class="">Alan</pre>
</blockquote>
<pre class=""> </pre>
<pre class="">_______________________________________________</pre>
<pre class="">gnso-rds-pdp-wg mailing list</pre>
<pre class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" class="" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
<pre class=""> </pre>
<pre class="">_______________________________________________</pre>
<pre class="">gnso-rds-pdp-wg mailing list</pre>
<pre class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" class="" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
<pre class=""> </pre>
<pre class="">_______________________________________________</pre>
<pre class="">gnso-rds-pdp-wg mailing list</pre>
<pre class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" class="" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" class="" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<p class="MsoNormal"> </p>
</div>
</div>
_______________________________________________<br class="">
gnso-rds-pdp-wg mailing list<br
class="">
<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" class=""
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br
class="">
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank"
class="" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</div>
</div>
<div class="">--<span
class="Apple-converted-space"> </span><br
class="">
</div>
<div
class="m_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;
-webkit-text-stroke-width: 0px;" class="">--<span
class="Apple-converted-space"> </span><br
class="">
</div>
<div class="gmail_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; -webkit-text-stroke-width: 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; -webkit-text-stroke-width: 0px;"
class="">
<span style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class="">******************************</span><span
style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class=""><wbr class="">******************************</span><span
style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class=""><wbr class="">*******<br class="">
</span><span style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class="">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; -webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class=""><br
class="webkit-block-placeholder">
</div>
<span style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class="">******************************</span><span
style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class=""><wbr class="">******************************</span><span
style="font-style: normal;
font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; color:
rgb(34, 34, 34); font-family: arial,
sans-serif; font-size: 12.8px;
background-color: rgb(255, 255, 255);"
class=""><wbr class="">*******</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; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">_______________________________________________</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; -webkit-text-stroke-width: 0px;"
class="">
<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; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">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;
-webkit-text-stroke-width: 0px;" class="">
<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; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class=""><a
href="mailto:gnso-rds-pdp-wg@icann.org"
class="" 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; -webkit-text-stroke-width: 0px;"
class="">
<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; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class=""><a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" class=""
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</div>
<br class="">
<div class="">
<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;
orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<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;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<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;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<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;
-webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space;
line-break: after-white-space;" class="">
<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; -webkit-text-stroke-width: 0px;
word-wrap: break-word;
-webkit-nbsp-mode: space; line-break:
after-white-space;" class="">
<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;
-webkit-text-stroke-width: 0px;
word-wrap: break-word;
-webkit-nbsp-mode: space; line-break:
after-white-space;" class="">
<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;
-webkit-text-stroke-width: 0px;"
class=""><br
class="Apple-interchange-newline">
<br class="">
</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;
-webkit-text-stroke-width: 0px;"
class=""><br
class="Apple-interchange-newline">
<br class="">
</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;
-webkit-text-stroke-width: 0px;"
class="">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;
-webkit-text-stroke-width: 0px;"
class=""><a
href="mailto:seeburn.k@gmail.com"
class="" 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;
-webkit-text-stroke-width: 0px;"
class="">
<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);" class="">
<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-position: inherit;
font-variant-caps: inherit;
font-variant-numeric: inherit;
font-variant-alternates:
inherit;
font-variant-east-asian:
inherit; line-height: 1.2em;"
class="">
<dl class="public-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-position:
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-position:
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;"
class=""><a
href="http://www.linkedin.com/in/kseeburn/"
title="View public
profile"
name="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-position:
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;"
class=""
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; orphans: auto;
text-align: start; text-indent: 0px;
text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px;"><span><span><br
class="Apple-interchange-newline">
<span><KeepItOn_Social_animated.gif></span>
</span></span></span></div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gnso-rds-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-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" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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="moz-txt-link-abbreviated" href="http://www.keydrive.lu" 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.
--------------------------------------------
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" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" 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="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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="moz-txt-link-abbreviated" href="http://www.keydrive.lu" 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>_______________________________________________</span><br>
<span>gnso-rds-pdp-wg mailing list</span><br>
<span><a href="mailto:gnso-rds-pdp-wg@icann.org"
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"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</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" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" moz-do-not-send="true">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" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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="moz-txt-link-abbreviated" href="http://www.keydrive.lu" 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.
--------------------------------------------
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" moz-do-not-send="true">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net" moz-do-not-send="true">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com" 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="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" 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="moz-txt-link-abbreviated" href="http://www.keydrive.lu" 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>
<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>