<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
Agreed Michael, <br>
<br>
I can only imagine some sort of access to a database that contains
anonymised data, yet folks who deal with botnets can obtain valuable
info from that database. <br>
What would those data points be for a botnet? <br>
<br>
Thanks, <br>
<br>
Theo <br>
<br>
<div class="moz-cite-prefix">On 28-9-2017 15:58, Dotzero wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ4XoYc9WtFUfmP9GNUVHP1J9M=VnKFUg=1r9XoKNb88ZYQ9TQ@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>Stephanie,<br>
<br>
</div>
Please correct me if I'm wrong, but I don't
believe that any of the data elements being
discussed as possible candidates for inclusion
in RDS would be considered "sensitive personal
data" as defined under GDPR. We aren't asking
for political beliefs, sexual orientation, trade
union membership or any of the other categories
specified.<br>
<br>
</div>
If you had stated "<font size="+1"><font
face="Lucida Grande">Making personal data
public does not, by legal definition, change
its character as personal data."</font></font>
then we could perhaps find agreement and move on
to a discussion as to which data elements are
truly personal data, whether the collection and
publication is justified based on the
purpose/activity and things like proportionality.
<br>
<br>
</div>
My sense is that unless we (collectively) work to
find areas of common understanding, this effort is
doomed to failure.<br>
<br>
</div>
We should be asking ourselves questions like:<br>
<br>
</div>
If this data/information is not available
(publicly/gated), what are potential impacts (positive
or negative) on the security and stability of DNS and
the Internet?" What are the impacts to individuals and
what are the impacts to the ecosystem as a whole? We
cannot answer questions like proportionality without
considering these sorts of questions. <br>
<br>
I would pose this question to the group: If you knew
with some certainty that limiting availability of
information that allows individuals, groups and
organizations to mitigate abuse at scale would wreak
havoc on the stability, security and overall usefulness
of the Internet, would you advocate the limitations
currently being advocated?<br>
<br>
</div>
At the other end of the spectrum I would pose this
question: Recognizing privacy concerns (whether legal or
ethical), what mechanisms might be implemented within the
proposed RDS that would protect individual privacy of
legitimate users but still allow abuse mitigation
techniques based on DNS information of Internet abuse?<br>
<br>
</div>
I think this (to some extent) stakes out the 2 extremes and
asks how to address the key issue(s) presented by proponents
of the other extreme.<br>
<br>
</div>
Let's try thinking outside the box.<br>
<br>
</div>
Michael Hammer<br>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote"><br>
On Thu, Sep 28, 2017 at 9:36 AM, Stephanie
Perrin <span dir="ltr"><<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank" moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</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><font size="+1"><font face="Lucida
Grande">Making sensitive data public
does not, by legal definition,
change its character as personal
data.</font></font></p>
<p><font size="+1"><font face="Lucida
Grande">Stephanie P</font></font><br>
</p>
<div>
<div class="h5"> <br>
<div
class="m_6373870469082176298moz-cite-prefix">On
2017-09-28 09:34, John Bambenek via
gnso-rds-pdp-wg wrote:<br>
</div>
<blockquote type="cite">
<div>Public data cannot, by
definition, be breached. </div>
<div
id="m_6373870469082176298AppleMailSignature"><br>
</div>
<div
id="m_6373870469082176298AppleMailSignature">J<br>
<br>
--
<div>John Bambenek</div>
</div>
<div><br>
On Sep 28, 2017, at 08:29, theo
geurts <<a
href="mailto:gtheo@xs4all.nl"
target="_blank"
moz-do-not-send="true">gtheo@xs4all.nl</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div> Indeed privacy prevents a
lot of consumers being
exploited.<br>
<br>
Privacy by design usually plays
a significant role when setting
up security around databases.
Often, less is more, data that
is not present cannot cause a
data breach. The GDPR had to set
a whole bunch of rules around
data breaches and response times
and accounting. Though given the
number of weekly data breaches,
most likely for the best, yet it
is still a load of rules to deal
with. <br>
<br>
Theo<br>
<br>
<div
class="m_6373870469082176298moz-cite-prefix">On
28-9-2017 15:19, John Bambenek
via gnso-rds-pdp-wg wrote:<br>
</div>
<blockquote type="cite">
<div>Thankfully there are
people who donate their time
and talent tackling the
privacy and security risks
that are seeking to exploit
consumers. ;)<br>
<br>
--
<div>John Bambenek</div>
</div>
<div><br>
On Sep 28, 2017, at 03:08,
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>The role of ICANN to
ensure the stability and
security of the internet
is a technical role, not
one of being an internet
policeman. That role is
already filled by
internet policemen.</p>
<p>Volker<br>
</p>
<br>
<div
class="m_6373870469082176298moz-cite-prefix">Am
27.09.2017 um 20:05
schrieb Chuck:<br>
</div>
<blockquote type="cite">
<div
class="m_6373870469082176298WordSection1">
<p class="MsoNormal"><span
style="color:windowtext">Without at all minimizing ICANN’s role with
regard to security
and stability of
the Internet
because I do
believe that is a
critical role, I
do want to point
out that that also
is a limited
role. Here is a
copy of the first
part of ICANN’s
mission from its
Bylaws:</span></p>
<p class="MsoNormal"><span
style="color:windowtext"> </span></p>
<p class="MsoNormal"><span
style="color:windowtext">“</span><span
style="font-size:12.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">Section
1.1. MISSION</span></p>
<p class="MsoNormal"><span
style="font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">(a) The
mission of the
Internet
Corporation for
Assigned Names and
Numbers ("<b>ICANN</b>")
is to ensure the
stable and secure
operation of the
Internet's unique
identifier systems
as described in
this <u>Section
1.1(a)</u> (the
"<b>Mission</b>").
Specifically,
ICANN:</span></p>
<p class="MsoNormal"><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">(i)
Coordinates the
allocation and
assignment of
names in the root
zone of the Domain
Name System ("<b>DNS</b>")
and coordinates
the development
and implementation
of policies
concerning the
registration of
second-level
domain names in
generic top-level
domains ("<b>gTLDs</b>").
In this role,
ICANN's scope is
to coordinate the
development and
implementation of
policies:</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt"><span
style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span
style="font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">For
which uniform or
coordinated
resolution is
reasonably
necessary to
facilitate the
openness,
interoperability,
resilience,
security and/or
stability of the
DNS including,
with respect to
gTLD registrars
and registries,
policies in the
areas described in
Annex G-1 and
Annex G-2; and</span></p>
<p class="MsoNormal"
style="margin-right:0in;margin-bottom:11.25pt;margin-left:30.0pt"><span
style="font-size:10.0pt;font-family:Symbol"><span>·<span> </span></span></span><span
style="font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">That are
developed through
a bottom-up
consensus-based
multistakeholder
process and
designed to ensure
the stable and
secure operation
of the Internet's
unique names
systems.</span></p>
<p class="MsoNormal"><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">The
issues, policies,
procedures, and
principles
addressed in Annex
G-1 and Annex G-2
with respect to
gTLD registrars
and registries
shall be deemed to
be within ICANN's
Mission.</span></p>
<p class="MsoNormal"><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">. . .</span><span
style="color:windowtext">”</span></p>
<p class="MsoNormal"><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">Note in
(a) and the second
bullet under (i)
that it says “</span><span
style="font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">to
ensure the stable
and secure
operation of the
Internet's unique
identifier systems</span><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">”.
ICANN’s security
and stability role
is limited to its
responsibilities
involving the ‘</span><span
style="font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">Internet's
unique identifier
systems</span><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN">’. I am
pretty sure
everyone
understands that
but wanted to make
sure. For our
purposes in this
WG, ICANN has a
clear mandate to
ensure security
and stability of
the generic domain
names system.</span></p>
<p class="MsoNormal"><span
style="font-size:13.0pt;font-family:"Helvetica",sans-serif;color:#333333"
lang="EN"> Chuck</span></p>
<p class="MsoNormal"><span
style="color:windowtext"> </span></p>
<p class="MsoNormal"><a
name="m_6373870469082176298__MailEndCompose" moz-do-not-send="true"><span
style="color:windowtext"> </span></a></p>
<span></span>
<div>
<div
style="border:none;border-top:solid
#e1e1e1
1.0pt;padding:3.0pt
0in 0in 0in">
<p
class="MsoNormal"><b><span
style="color:windowtext">From:</span></b><span style="color:windowtext">
<a
class="m_6373870469082176298moz-txt-link-abbreviated"
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>
[<a
class="m_6373870469082176298moz-txt-link-freetext"
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>]
<b>On Behalf
Of </b>John
Bambenek via
gnso-rds-pdp-wg<br>
<b>Sent:</b>
Wednesday,
September 27,
2017 9:12 AM<br>
<b>To:</b> <a
class="m_6373870469082176298moz-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><br>
<b>Subject:</b>
Re:
[gnso-rds-pdp-wg]
ICANN
Meetings/Conversations
with Data
Protection and
Privacy
Commissioners</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p>Except that the
domain name system
is not YOUR system,
it is ICANN's who
has a very clear
mandate for the
security and
stability of the
internet.</p>
<p>The purpose is NOT
letting registrants
get domains and
helping registries
get paid. It never
has been.</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On
09/27/2017 09:52
AM, Volker
Greimann wrote:</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Hi Greg,</p>
<p>I think we need
to dig down even
deeper initially.
Instead of RDS,
the core of the
matter is the need
for the data when
defining the
purpose for
collection.</p>
<p>This is very easy
to answer for
registrars: "We
need (certain
elements of) the
data to be able to
properly provide
the business,
invoice the
customer, collect
his payments, send
reminders and
notices, protect
the rights of the
customers in case
of business
failure, comply
with legal
requirements like
record-keeping,
etc.". I am
leaving out any
contractual
requirements, as
they do not matter
for the
registrars' own
purpose. These are
external purposes
that the registrar
would have to
execute without
having an own,
direct need for. </p>
<p>For registries,
it gets fuzzier as
they do not have a
direct connection
to the
registrants. From
a service
provision
perspective,
registries have no
need for the data,
and no right to
it, except maybe
for purposes of
eligibility
verification. </p>
<p>When going beyond
registries to the
general public,
there is no
purpose that
connects to the
provision of the
service to the
registrant
directly. There
also (in most
countries) is no
legal requirement
to collect and
publish this data.
Yet there is still
a need for the
data, as we have
discussed in great
detail. </p>
<p>So our first
question always
must be the
following:</p>
<p>"How do we serve
the needs of the
general public
that has an
interest in the
ability of
obtaining such
data without
violating any
applicable laws or
the rights of the
registrant to the
privacy of his
data?"</p>
<p>This has to be
the basis of any
design decision
and any argument
made in this
group. </p>
<p>Arguing that
certain laws are
unreasonable or
unworkable is a
dangerous question
as it effectively
proposes to ignore
laws that we as a
community do not
like, at the risk
of contracted
parties and to the
detriment of the
beneficiaries of
such laws. just
because there has
not been any
enforcement action
in the past does
not mean we can
ignore the law
applicable to the
individual
contracted
parties. And we
are not talking
about jaywalking
here, some of
these laws have
significant
penalties attached
to them, as we
have also
discussed before.
</p>
<p>I agree with Greg
that the ability
of contracted
parties to be free
to make business
decisions cannot
be absolute. It
has to be bound on
the one side by
ICANN policies and
the other side by
applicable law.
And these two
external pressures
should not be in
conflict with each
other. If we can
achieve that while
answering the
basic question
above, our work is
done. At least for
the time being, as
laws may obviously
change, but that
can be taken into
account as well.
Any discussion
that seeks to
circumvent this
basic question
will ultimately
lead to the
failure of our
work and by
extention to the
end of whois. The
latter due to the
incompatibility of
current whois with
applicable law.</p>
<p>I think with our
initial "purpose
definition"
exercise, we
already went a
great way in
determining what
those needs are
and our current
work to discuss
data points goes
into that question
as well, even
though personally
I feel that by
defining data
points at this
point and going
into the sticks in
some of the
discussions we are
wasting time. The
question should
never be "Do we
need a Facebook
contact in the
RDS?" and always
be "What contacts
are needed as bare
minimum to achieve
needs X, Y, Z,
...". </p>
<p>Best,</p>
<p>Volker</p>
<p class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">Am
27.09.2017 um
16:00 schrieb
Greg Shatan:</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Arial",sans-serif"></span><span
style="font-family:"Verdana",sans-serif">The
"data
controllers"
here do not
exist in a
vacuum. While
registrars and
registries
need to be
free to make
many types of
decisions in
their own
business
judgment, that
cannot be an
absolute
rule. This is
at odds with
the ICANN
model,
consensus
policy, etc.
In this case,
the data
controllers
are part of a
larger
ecosystem, and
the "needs" go
beyond the
individual
business needs
of each data
controller.
(Indeed, the
individual
data
controller has
its own
database of
information
for its
business
needs.)</span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Verdana",sans-serif"> </span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Verdana",sans-serif">As I previously
noted, we are
going back to
first
principles --
which is not
necessarily a
bad thing.
Why does ICANN
(and by
extension, the
Internet) need
WHOIS/RDS?
That is the
question. Not
"why does a
particular
[registrar/registry]
need
WHOIS/RDS?"</span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Verdana",sans-serif"> </span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Verdana",sans-serif">Greg</span><span
style="font-family:"Arial",sans-serif"></span><span
style="font-family:"Verdana",sans-serif"></span></p>
</div>
<div>
<p
class="MsoNormal"><span
style="font-family:"Verdana",sans-serif"> </span></p>
</div>
</div>
<div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
Wed, Sep 27,
2017 at 5:12
AM, Volker
Greimann <<a
href="mailto:vgreimann@key-systems.net" target="_blank"
moz-do-not-send="true">vgreimann@key-systems.net</a>>
wrote:</p>
<blockquote
style="border:none;border-left:solid
#cccccc
1.0pt;padding:0in
0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p>So when
will you start
advocating the
collection and
publication of
WHOIS for
internet
users? Because
they would be
connecting to
your network
all the
time...</p>
<p><span
style="color:#888888">Volker</span></p>
<div>
<div>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">Am
26.09.2017 um
20:48 schrieb
John Bambenek
via
gnso-rds-pdp-wg:</p>
</div>
</div>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p>"<span>As
for privacy
proxy solving
the problem,
it does not.
Over
collection is
not solved by
providing a
proxy in the
third party
disclosure
mechanism. It
is still
over-collection,
disproportionate to needs."</span></p>
<p><span>I
fundamentally
disagree
because the
purpose of
ICANN is not
the mere
facilitation
of domain from
registry to
registrant.
The purpose is
the security
and stability
of the
internet and
that means I
have a need to
verify who is
connecting to
my network and
have a means
of contacting
them. That
point has
never been
made, to my
knowledge, to
them.</span></p>
<p><span>The
point that
removing that
ability of me
being able to
contact domain
owners does
far MORE to
REDUCE the
privacy of the
registrants
than does
publishing
said
information.
We talk often
about
verification
out-of-band
for sensitive
communications. How can I do that without a phone number?</span></p>
<p><span>I
will loudly
and vigorously
argue that the
path advocated
will make the
problem FAR
worse and not
better.
Hopefully we
don't get to
the point
where I have
actual data to
prove that.</span></p>
<p
class="MsoNormal"> </p>
<div>
<p
class="MsoNormal">On
9/26/2017 1:34
PM, Stephanie
Perrin wrote:</p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p
class="MsoNormal"><span>As
for privacy
proxy solving
the problem,
it does not.
Over
collection is
not solved by
providing a
proxy in the
third party
disclosure
mechanism. It
is still
over-collection,
disproportionate to needs.</span></p>
</blockquote>
<p
class="MsoNormal"><br>
<br>
</p>
<pre>-- </pre>
<pre>--</pre>
<pre> </pre>
<pre>John Bambenek</pre>
<p
class="MsoNormal"><br>
<br>
</p>
</div>
</div>
<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>
<div>
<div>
<pre>-- </pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.</pre>
<pre> </pre>
<pre>Mit freundlichen Grüßen,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- Rechtsabteilung -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>Geschäftsführer: Alexander Siffrin</pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken </pre>
<pre>Umsatzsteuer ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>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.</pre>
<pre> </pre>
<pre>------------------------------<wbr>--------------</pre>
<pre> </pre>
<pre>Should you have any further questions, please do not hesitate to contact us.</pre>
<pre> </pre>
<pre>Best regards,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- legal department -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>CEO: Alexander Siffrin</pre>
<pre>Registration No.: HR B 18835 - Saarbruecken </pre>
<pre>V.A.T. ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>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>
<pre> </pre>
<pre> </pre>
<pre> </pre>
</div>
</div>
</div>
<p
class="MsoNormal">______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list <a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a> <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>
</p>
</blockquote>
</div>
</div>
<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>
<pre>-- </pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.</pre>
<pre> </pre>
<pre>Mit freundlichen Grüßen,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- Rechtsabteilung -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>Geschäftsführer: Alexander Siffrin</pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken </pre>
<pre>Umsatzsteuer ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>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.</pre>
<pre> </pre>
<pre>------------------------------<wbr>--------------</pre>
<pre> </pre>
<pre>Should you have any further questions, please do not hesitate to contact us.</pre>
<pre> </pre>
<pre>Best regards,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- legal department -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 901</a></pre>
<pre>Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank" moz-do-not-send="true">+49 (0) 6894 - 9396 851</a></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>CEO: Alexander Siffrin</pre>
<pre>Registration No.: HR B 18835 - Saarbruecken </pre>
<pre>V.A.T. ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>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>
<pre> </pre>
<pre> </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>
</div>
<br>
<fieldset
class="m_6373870469082176298mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_6373870469082176298moz-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_6373870469082176298moz-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_6373870469082176298moz-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_6373870469082176298moz-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_6373870469082176298moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_6373870469082176298moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_6373870469082176298moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_6373870469082176298moz-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_6373870469082176298moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_6373870469082176298moz-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_6373870469082176298moz-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_6373870469082176298moz-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_6373870469082176298moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a class="m_6373870469082176298moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a>
<a class="m_6373870469082176298moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a class="m_6373870469082176298moz-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_6373870469082176298moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a>
<a class="m_6373870469082176298moz-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_6373870469082176298moz-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>
<br>
<fieldset
class="m_6373870469082176298mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_6373870469082176298moz-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_6373870469082176298moz-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>
</div>
</blockquote>
<br>
<fieldset
class="m_6373870469082176298mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
gnso-rds-pdp-wg mailing list
<a class="m_6373870469082176298moz-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_6373870469082176298moz-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>
</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>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</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">gnso-rds-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<br>
</body>
</html>