<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Actually, accreditation is what you (as the accrediting body)
make of it: <br>
</p>
<p>In case of ICANN it also means to subject the accredited entities
to certain rules, codes and policies that you have to follow,
certain requirements that have to be met and certain reviews that
can make them undergo. Accreditation as an ICANN registrar is much
more than a mere rubber stamp. There is a review upon application
and constant reviews after that. That is how contracted parties
are being held accountable. <br>
</p>
<p>Volker<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 07.06.2017 um 18:00 schrieb John
Bambenek:<br>
</div>
<blockquote type="cite"
cite="mid:25D4C385-6F46-4D87-8F39-5C5C4B78EABE@bambenekconsulting.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>Of course "official cybercrime investigators" are accredited
by their government. That's literally the definition of official
and it is not what we are talking about here. </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Given enough money I can call myself
a registrar and still be a criminal. Given even more money, I
can apply and be the registry of .kkk. Which is basically my
point, accreditation is a money laundering scheme that serves
little purpose beyond enriching the accreditors. It is and never
will be a guarantee of anything except "you paid your dues" and
"you checked all the right boxes". </div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">That said, no where near a majority
of registrars or registries are criminal or what I would label
"a problem". <br>
<br>
--
<div>John Bambenek</div>
</div>
<div><br>
On Jun 7, 2017, at 16:23, 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>I have no doubt that all those cybercrime investigators
participating here being honorable and well-intentioned but
the reality is that anyone can call him- or herself a
cybercrime investigator and start publishing reports on
whatever their agenda may be. <br>
</p>
<p>Ultimately, all official cybercrime investigators are
accredited by their respective governments: They are then
called law enforcement. The other category of semi-official
investogators would be private authorities that have been
granted certain powers by law or statute, such as <a
href="http://Jugendschutz.net" moz-do-not-send="true">Jugendschutz.net</a>
(in Germany) or LegitScript (in Japan only?).<br>
</p>
<p>Everyone else is merely attaching a label to themselves
that may or may not be accurate. Heck, even a spammer might
call itself a cybercrime investigator to gain access to
information and circles he would otherwise have no access
to.</p>
<p>Again, kudos to all those who invest their own time and
lifeblood to reducing crime on the internet, be it for free
or as their day job.</p>
<p>Best regards,</p>
<p>Volker<br>
</p>
<br>
<div class="moz-cite-prefix">Am 07.06.2017 um 17:13 schrieb
John Bambenek via gnso-rds-pdp-wg:<br>
</div>
<blockquote type="cite"
cite="mid:13F3815F-1BF2-4BAD-915D-1F4028D80BE4@bambenekconsulting.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<div>There is no sound global accreditation model that isn't
organized and legitimized money laundering at best. Merely
credentials for credentials sake.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">We can be trusted in the sense
that if we weren't we get prosecuted.</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">And atypically most of the good
security investigators are not being paid for their work.
Accreditation prices them right out. Just like ICANN which
doesn't charge membership fees to participate here. <br>
<br>
--
<div>John Bambenek</div>
</div>
<div><br>
On Jun 7, 2017, at 15:55, Stephanie Perrin <<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p><font size="+1"><font face="Lucida Grande">These are
excellent questions. I would add an additional
one: why are private cybercrime investigators not
accredited? How can the global public trust them,
or perhaps why?</font></font></p>
<p><font size="+1"><font face="Lucida Grande">Stephanie
Perrin</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-06-07 10:49, Volker
Greimann wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f75f8fa5-2638-b2b3-a577-01e05adbb0f9@key-systems.net">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p>All good questions that we will no doubt come to
later. <br>
</p>
<br>
<div class="moz-cite-prefix">Am 07.06.2017 um 16:47
schrieb John Bambenek via gnso-rds-pdp-wg:<br>
</div>
<blockquote type="cite"
cite="mid:B52ABF7E-09B4-4C3B-9A8D-444C7F904C31@bambenekconsulting.com">
<div>I want to add. Requiring authentication means
that you will be creating a database (potentially
many of them) that will contain private data
(usernames, emails, passwords, and api keys
combined is some of the most sensitive private
data there is) to access public data. You will be
creating logs of what we search and why (what's
the point of requiring purpose be disclosed if not
to store it. For a subset of us that exposes our
customer lists that could be easily derived. </div>
<div><br>
</div>
<div>The first problem is, who has access to this
data and under what conditions? Will every domain
owner see who queries their domains? That
inherently means targets of our investigations are
not only tipped off that there is an
investigation, but can expose specifically WHO is
investigating. You are increasing the direct
PERSONAL risk investigators take to solve the
problems you have raised with anti-abuse. </div>
<div><br>
</div>
<div>Further, you are inherently creating a database
of high profile targets for intelligence agencies.
System admins, network admins and investigators
are targets of intelligence agencies because they
have privileged access if not the full "keys to
the kingdom". (See: <a
href="https://www.usenix.org/conference/enigma2016/conference-program/presentation/joyce"
moz-do-not-send="true">https://www.usenix.org/conference/enigma2016/conference-program/presentation/joyce</a> short
version, the NSA says these are the exact people
they try to compromise). This system almost
exclusively has those people in it. If LE has
access to the logs and this database, it is hard
to see how intelligence agencies can't get it. Do
you want the NSA knowing what domains you are
looking at knowing its a mere NSL away? </div>
<div><br>
</div>
<div>Further, creating this pool of high-profile
targets also makes the RDS a major target of
attack. By literally everyone. Considering the
problem of password reuse, if this database were
ever compromised, a huge number of organizations
would face very immediate existential threats. Who
is going to pay for the security of RDS? Who is
going to accept the liability when its breached?</div>
<div><br>
</div>
<div>Putting public info behind a gate creates huge
liabilities, assumes great cost, and delivers no
real anti-abuse features because domain status
alone is not weaponizable via phishing (you need
contact info, and if that's behind the gate or a
proxy registration, lets just assume the spammer
can't get to it; also a bad assumption). </div>
<div><br>
</div>
<div>So the basic question for you guys even if you
set the value of MY risk at 0 and completely
irrelevant, what is the return on this massive
investment and who's going to pay that bill? It
won't be me. </div>
<div><br>
</div>
<div>The last point, and I will be very direct about
this. Some of you on this list made a startling
bald statement that you ignore your contractual
OBLIGATIONS as they exist today regarding
registrant accuracy because you "don't like them"
in such a way that at least one investigation was
already opened. For those of you who openly
admitted that you ignore ICANN contractual
requirements for a contract you signed, how can we
(who will bear the personal risks) trust any
assurances you will give that you simply won't
give this data to criminals despite any policy we
create here?</div>
<div><br>
<div>--
<div>John Bambenek</div>
</div>
</div>
<div><br>
On Jun 7, 2017, at 15:20, Michael Peddemors <<a
href="mailto:michael@linuxmagic.com"
moz-do-not-send="true">michael@linuxmagic.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Hi Volker,</span><br>
<span></span><br>
<span>Maybe we are getting to the root of your
position, too much spam ;)</span><br>
<span>Maybe a better spam filter would be the
solution? ;)</span><br>
<span></span><br>
<span>But in all seriousness, what you are
discussing are problems that really should NOT
be part of this discussion. Just because cars
are a target for theft, we should not prevent
owners from parking on the street.</span><br>
<span></span><br>
<span>What you are discussing are criminal
activities, for which other resources are
available to address that problem. But a
gated solution would inherently add to the
problem. First of all, most spam of that type
are already addressed by good filters, and
domains involved in such activity usually end
up on blacklists etc quite quickly, but a
gated approach would prevent some of the
ability to identify those actors, and
report/stop them.</span><br>
<span></span><br>
<span>Some of these tests are automated, eg
right in software policies, and need to have
access to that data on the fly, and that type
of automated detection tool cannot work
properly, or will be very inhibited with any
form of gated access.</span><br>
<span></span><br>
<span>And to argue that in the case of
unfettered access can be used by both the bad
players and the good, do remember that the
'bad actors' have a commercial interest in
gaining that data, and will be the first
people to automate work arounds.. (eg when SPF
came out, surprised how many spammers were
early adopters)</span><br>
<span></span><br>
<span>Every email operator should be able to
have access to that data, eg domain creation
date, expiry date, and that data cannot be
restricted by bulk (have you seen the volume
of senders?) and distributed protection
software should not require the end user to
'register' for access to this data to have
their protections work.</span><br>
<span></span><br>
<span>Gated Access:</span><br>
<span></span><br>
<span>* Inhibits the ability to create systems
that protect privacy</span><br>
<span>* Adds a commercial burden (extra systems)
to those with legitimate requirements</span><br>
<span>* Requires an authentication mechanism
which can create privacy concerns</span><br>
<span>* requires an authentication mechanism
which may not be usable or desired by all
parties</span><br>
<span>* Raises the bar on who can develop
protections and legitimate systems</span><br>
<span>* Provides protection for the very actors
you are worried about.</span><br>
<span>* Adds unnecessary burdens/costs on ICANN
and registrars as well</span><br>
<span>* Adds a point of failure</span><br>
<span>* Research and innovation will be
inhibited</span><br>
<span></span><br>
<span>IMHO, you had better have a STRONG reason
to put a gate up..</span><br>
<span>Let's not mix the problems of certain
criminal elements getting access to this data,
that is a separate issue, and we can't cut off
our nose to spite our face..</span><br>
<span></span><br>
<span>I might suggest that rather than promoting
'gated' access, which those elements would be
the first to sign up for, is spend the same
amount of time working on getting internet
providers to prevent that activity from
occurring in the first place, and doing
anything you can to help those who are trying
to stop such activity, including ensuring that
they (the good guys) have unfettered access.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>On 17-06-07 01:54 AM, Volker Greimann
wrote:</span><br>
<blockquote type="cite"><span>It is remarkable
how much of the spam that we see on a
regular basis</span><br>
</blockquote>
<blockquote type="cite"><span>that is tied to
the domain lifecycle. Fake renewal notices,
SEO offers,</span><br>
</blockquote>
<blockquote type="cite"><span>the lot.</span><br>
</blockquote>
<blockquote type="cite"><span>Anything that
would reduce this is a basis for restricting
access</span><br>
</blockquote>
<blockquote type="cite"><span>somewhat. I do not
really see any harm in such restrictions
either.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Best,</span><br>
</blockquote>
<blockquote type="cite"><span>Volker</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Am 07.06.2017 um
10:27 schrieb jonathan matkowsky:</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>There is no
basis for restricting ungated access any
more so than the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>domain's
existence or the string of characters
registered.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>On Wed, 7 Jun
2017 at 11:22 Volker Greimann <<a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">vgreimann@key-systems.net</a></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span><<a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">mailto:vgreimann@key-systems.net</a>>>
wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> I have no
objections against having this data
available and</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> accessible.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> The question
is whether it should be as accessible as
it is now or</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> whether
there could be certain restrictions. A
tiered access system as</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> has been
proposed would solve this beautifully.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> In this
case, the dates would be on the second
tier (the first tier</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> being full
unhindered access), which would entail
some form of</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
authentification and bulk access
restrictions. Every single one of the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> uses Andrew
desribes would remain possible and
unproblematic, but the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> data would
no longer be in as much danger of being
abused as it is</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> today.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Best,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Volker</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Am
06.06.2017 um 22:07 schrieb Michael
Peddemors:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > +1 as
well..</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > .. but
with so many +1's on having that data
publicly accessible, it</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > would
be interesting to take a straw poll, to a
wider audience</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> on that</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > simple
question..</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > It
would be also nice to see what category
the parties in each camp</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > lie? We
know that everyone involved in making the
internet a</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> safer and</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > better
place (security companies, law enforcement
et al) want it</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >
available, and to define 'thin data' as
wide as possible, and I can</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >
understand that some consideration to
privacy be considered so</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> that it</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > doesn't
go too wide, but not really certain I
understand the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> position</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > of
those that want it as 'thin' as possible,
or non-existant, and/or</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > the
parties behind that position and their
numbers.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > And of
course the ever present question for both
camps, is the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> opinion</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > coming
from a place where there are financial
motivations (not that</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >
necessarily there is anything wrong with
that <sic>) that have</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> formed</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > the
basis of that opinion. (eg, if the money
equation was removed,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > would
you still have that opinion, or even be in
the conversation?)</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > For all
we know, the privacy camp are in very
small numbers in this</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >
conversation, and while they might hold
legitimate positions,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> maybe it</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > isn't
enough to affect the directions/positions
of ICANN as a group</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > going
forward.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > And
IMHO, even if it was 50/50 split, if it
came down to two</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> camps, eg</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > 'the
ones keeping us safe' and 'it
affects/risks our pocketbooks', I</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > would
err on policies that would aid the
former..</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > Don't
want 'politics' to affect such important
decisions..</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> > On
17-06-06 11:22 AM, Andrew Sullivan wrote:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> Hi,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> On
the call today there were arguments being
made about why certain</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
fields should not be publicly accessible.
In effect, what we</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> are now</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
arguing about, in talking about what
should be considered "thin</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> data",</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> is
the definition of the set of data to which
unauthenticated</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> access</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
should be permitted. (Let us please not
get distracted by what is</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
actually required by the RAA or anything
like that just now,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> since the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
outcome of this policy discussion might
change that.)</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
There were several arguments put forth
about whether the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> created on,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
updated on, and expiry dates should be
included. Similarly, people</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
discussed whether the domain status values
should be included. I</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
believe they must be.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> The
Internet is unlike many other technologies
because of its</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> radical</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
decentralization. That is not some sort
of political choice, but</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
instead a fundamental part of the design
of the Internet: it's a</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
network of networks (of networks…) formed
by voluntary</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
interoperation</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
among the participants. Participants in
the Internet interoperate</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
without setting up formal contractual
arrangements between all the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
participating parties. This feature is
part of what has made the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
Internet so successful compared to other
telecommunications</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> systems,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
because the barrier to entry is really
low. But that design</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> comes at</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> a
cost.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> The
cost is that there's not always a party to
speak to, with</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> whom one</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> has
a pre-existing relationship. If
communications break down</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> between</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> two
telephone customers, they know whom to
call: the phone company.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> The
phone company also has contractual (or
sometimes treaty)</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
relationships to other phone companies.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> The
Internet doesn't work that way. If you
and I are communicating</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
over the Internet, there is no guarantee
of direct contractual</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
relationships all the way along the
transit path: that's what open</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
peering policies ensure. The way we make
this work in fact is by</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
placing the responsibility for
troubleshooting out at the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> edges. And</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
because of that, when I need to
troubleshoot my site I need to have</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
tools with which to do that.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> In
domain-based communications (such as
email, IP telephony,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> websites,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
money transfer, and thousands of other
applications), when I</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> encounter</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> a
problem with the communication I need to
answer whether the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> problem</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> is
in _my_ network operation, or in the other
end. Important</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> data to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
rule out "the other end" is in the thin
RDS data.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
Obviously, the nameserver and DNSSEC
information in the RDS</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> will allow</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> me
to tell whether what is in the global DNS
is what ought to be</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
there. For instance, if the RDS has one
value for the name</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> servers,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> but
the DNS returns something else, there is a
problem.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
Less obvious but just as important are the
status values. If a</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> name</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> is
on Hold or is pendingTransfer or something
like that, it can</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> tell</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> me
that something is up. A name that doesn't
appear in the DNS but</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> has
a full complement of name servers in the
RDS, for example,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> might</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> be
on hold; and I can't tell that without
seeing the status values.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> In
the same way, the dates in the RDS allow a
troubleshooter to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
understand what might be wrong when things
are broken. If a</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> name is</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> set
to expire in a day and you're getting a
parking page on the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
website, you have a clue about what is
going on. Most of the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> examples</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
cited in</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="https://whoapi.com/blog/1582/5-all-time-domain-expirations-in-internets-history/"
moz-do-not-send="true">https://whoapi.com/blog/1582/5-all-time-domain-expirations-in-internets-history/</a></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
were trivial to understand for help desks
that could see that a</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> name</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
that should have existed for some time was
just hours old,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> because the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
created_on date was available. And if you
start having trouble and</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> see
a domain was updated about the same time
the trouble</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> started, you</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
have a pretty good clue that the problem
is most likely at the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> target</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
domain, and not in your own network.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> As
for the question of why the global
Internet infrastructure</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> needs to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
help with this, the answer is that _that's
what the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
infrastructure is</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
for_. We have registrars and registries
in order to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> co-ordinate
these</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
assignments and make those assignments
available, in support of the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
distributed administration and operation
of the Internet. If the</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
infrastructure isn't providing this kind
of information in order to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
help administrators of various Internet
administrators, then it</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> isn't</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
doing its job.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> The
Internet is a distributed system. If you
want to make</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> distributed</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
systems work, you have to allow the
operators to have enough</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
information to do their jobs independently
of one another. So,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
regardless of where one lands on whether
any of this data is</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> personal</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
data, it makes no difference. If you want
the domain name</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> system to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
continue to work reliably, you have to
publish this data.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
Centralization and locking the data up for
just registrars simply</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
won't scale.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >>
Best regards,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >> A</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> >></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> ></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> --</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Bei weiteren
Fragen stehen wir Ihnen gerne zur
Verfügung.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Mit
freundlichen Grüßen,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Volker A.
Greimann</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> -
Rechtsabteilung -</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Key-Systems
GmbH</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Im Oberen
Werk 1</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> 66386 St.
Ingbert</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Tel.: +49
(0) 6894 - 9396 901</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Fax.: +49
(0) 6894 - 9396 851</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Email: <a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">vgreimann@key-systems.net</a>
<<a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">mailto:vgreimann@key-systems.net</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Web: <a
href="http://www.key-systems.net"
moz-do-not-send="true">www.key-systems.net</a>
<<a href="http://www.key-systems.net"
moz-do-not-send="true">http://www.key-systems.net</a>>
/</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.RRPproxy.net"
moz-do-not-send="true">www.RRPproxy.net</a>
<<a href="http://www.RRPproxy.net"
moz-do-not-send="true">http://www.RRPproxy.net</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">www.domaindiscount24.com</a>
<<a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">http://www.domaindiscount24.com</a>>
/</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.BrandShelter.com"
moz-do-not-send="true">www.BrandShelter.com</a>
<<a href="http://www.BrandShelter.com"
moz-do-not-send="true">http://www.BrandShelter.com</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Folgen Sie
uns bei Twitter oder werden Sie unser Fan
bei Facebook:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">www.facebook.com/KeySystems</a>
<<a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">http://www.facebook.com/KeySystems</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">www.twitter.com/key_systems</a>
<<a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">http://www.twitter.com/key_systems</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
Geschäftsführer: Alexander Siffrin</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
Handelsregister Nr.: HR B 18835 -
Saarbruecken</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Umsatzsteuer
ID.: DE211006534</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Member of
the KEYDRIVE GROUP</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.keydrive.lu"
moz-do-not-send="true">www.keydrive.lu</a>
<<a href="http://www.keydrive.lu"
moz-do-not-send="true">http://www.keydrive.lu</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Der Inhalt
dieser Nachricht ist vertraulich und nur
für den</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> angegebenen
Empfänger bestimmt. Jede Form der
Kenntnisgabe,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
Veröffentlichung oder Weitergabe an
Dritte durch den Empfänger ist</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> unzulässig.
Sollte diese Nachricht nicht für Sie
bestimmt sein, so</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> bitten wir
Sie, sich mit uns per E-Mail oder
telefonisch in</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Verbindung
zu setzen.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
--------------------------------------------</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Should you
have any further questions, please do not
hesitate to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> contact us.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Best
regards,</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Volker A.
Greimann</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> - legal
department -</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Key-Systems
GmbH</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Im Oberen
Werk 1</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> 66386 St.
Ingbert</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Tel.: +49
(0) 6894 - 9396 901</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Fax.: +49
(0) 6894 - 9396 851</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Email: <a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">vgreimann@key-systems.net</a>
<<a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">mailto:vgreimann@key-systems.net</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Web: <a
href="http://www.key-systems.net"
moz-do-not-send="true">www.key-systems.net</a>
<<a href="http://www.key-systems.net"
moz-do-not-send="true">http://www.key-systems.net</a>>
/</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.RRPproxy.net"
moz-do-not-send="true">www.RRPproxy.net</a>
<<a href="http://www.RRPproxy.net"
moz-do-not-send="true">http://www.RRPproxy.net</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">www.domaindiscount24.com</a>
<<a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">http://www.domaindiscount24.com</a>>
/</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.BrandShelter.com"
moz-do-not-send="true">www.BrandShelter.com</a>
<<a href="http://www.BrandShelter.com"
moz-do-not-send="true">http://www.BrandShelter.com</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Follow us on
Twitter or join our fan community on
Facebook and</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> stay
updated:</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">www.facebook.com/KeySystems</a>
<<a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">http://www.facebook.com/KeySystems</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">www.twitter.com/key_systems</a>
<<a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">http://www.twitter.com/key_systems</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> CEO:
Alexander Siffrin</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Registration
No.: HR B 18835 - Saarbruecken</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> V.A.T. ID.:
DE211006534</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> Member of
the KEYDRIVE GROUP</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="http://www.keydrive.lu"
moz-do-not-send="true">www.keydrive.lu</a>
<<a href="http://www.keydrive.lu"
moz-do-not-send="true">http://www.keydrive.lu</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> This e-mail
and its attachments is intended only for
the person to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> whom it is
addressed. Furthermore it is not permitted
to publish</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> any content
of this email. You must not use, disclose,
copy, print</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> or rely on
this e-mail. If an addressing or
transmission error has</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> misdirected
this e-mail, kindly notify the author by
replying to</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> this e-mail
or contacting us by telephone.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
_______________________________________________</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>
gnso-rds-pdp-wg mailing list</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span> <a
href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>
<<a
href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">mailto:gnso-rds-pdp-wg@icann.org</a>></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><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><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>--</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>jonathan
matkowsky, vp - ip & head of global
brand threat mitigation</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>--</span><br>
</blockquote>
<blockquote type="cite"><span>Bei weiteren
Fragen stehen wir Ihnen gerne zur Verfügung.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Mit freundlichen
Grüßen,</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Volker A. Greimann</span><br>
</blockquote>
<blockquote type="cite"><span>- Rechtsabteilung
-</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Key-Systems GmbH</span><br>
</blockquote>
<blockquote type="cite"><span>Im Oberen Werk 1</span><br>
</blockquote>
<blockquote type="cite"><span>66386 St. Ingbert</span><br>
</blockquote>
<blockquote type="cite"><span>Tel.: +49 (0) 6894
- 9396 901</span><br>
</blockquote>
<blockquote type="cite"><span>Fax.: +49 (0) 6894
- 9396 851</span><br>
</blockquote>
<blockquote type="cite"><span>Email: <a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">vgreimann@key-systems.net</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Web: <a
href="http://www.key-systems.net"
moz-do-not-send="true">www.key-systems.net</a>
/ <a href="http://www.RRPproxy.net"
moz-do-not-send="true">www.RRPproxy.net</a></span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">www.domaindiscount24.com</a>
/ <a href="http://www.BrandShelter.com"
moz-do-not-send="true">www.BrandShelter.com</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Folgen Sie uns bei
Twitter oder werden Sie unser Fan bei
Facebook:</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">www.facebook.com/KeySystems</a></span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">www.twitter.com/key_systems</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Geschäftsführer:
Alexander Siffrin</span><br>
</blockquote>
<blockquote type="cite"><span>Handelsregister
Nr.: HR B 18835 - Saarbruecken</span><br>
</blockquote>
<blockquote type="cite"><span>Umsatzsteuer ID.:
DE211006534</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Member of the
KEYDRIVE GROUP</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.keydrive.lu"
moz-do-not-send="true">www.keydrive.lu</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>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.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>--------------------------------------------</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Should you have
any further questions, please do not
hesitate to contact us.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Best regards,</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Volker A. Greimann</span><br>
</blockquote>
<blockquote type="cite"><span>- legal department
-</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Key-Systems GmbH</span><br>
</blockquote>
<blockquote type="cite"><span>Im Oberen Werk 1</span><br>
</blockquote>
<blockquote type="cite"><span>66386 St. Ingbert</span><br>
</blockquote>
<blockquote type="cite"><span>Tel.: +49 (0) 6894
- 9396 901</span><br>
</blockquote>
<blockquote type="cite"><span>Fax.: +49 (0) 6894
- 9396 851</span><br>
</blockquote>
<blockquote type="cite"><span>Email: <a
href="mailto:vgreimann@key-systems.net"
moz-do-not-send="true">vgreimann@key-systems.net</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Web: <a
href="http://www.key-systems.net"
moz-do-not-send="true">www.key-systems.net</a>
/ <a href="http://www.RRPproxy.net"
moz-do-not-send="true">www.RRPproxy.net</a></span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.domaindiscount24.com"
moz-do-not-send="true">www.domaindiscount24.com</a>
/ <a href="http://www.BrandShelter.com"
moz-do-not-send="true">www.BrandShelter.com</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Follow us on
Twitter or join our fan community on
Facebook and stay updated:</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.facebook.com/KeySystems"
moz-do-not-send="true">www.facebook.com/KeySystems</a></span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.twitter.com/key_systems"
moz-do-not-send="true">www.twitter.com/key_systems</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>CEO: Alexander
Siffrin</span><br>
</blockquote>
<blockquote type="cite"><span>Registration No.:
HR B 18835 - Saarbruecken</span><br>
</blockquote>
<blockquote type="cite"><span>V.A.T. ID.:
DE211006534</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Member of the
KEYDRIVE GROUP</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="http://www.keydrive.lu"
moz-do-not-send="true">www.keydrive.lu</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>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.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>gnso-rds-pdp-wg
mailing list</span><br>
</blockquote>
<blockquote type="cite"><span><a
href="mailto:gnso-rds-pdp-wg@icann.org"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></span><br>
</blockquote>
<blockquote type="cite"><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><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<span></span><br>
<span></span><br>
<span></span><br>
<span>-- </span><br>
<span>"Catch the Magic of Linux..."</span><br>
<span>------------------------------------------------------------------------</span><br>
<span>Michael Peddemors, President/CEO
LinuxMagic Inc.</span><br>
<span>Visit us at <a
href="http://www.linuxmagic.com"
moz-do-not-send="true">http://www.linuxmagic.com</a>
@linuxmagic</span><br>
<span>------------------------------------------------------------------------</span><br>
<span>A Wizard IT Company - For More Info <a
href="http://www.wizard.ca"
moz-do-not-send="true">http://www.wizard.ca</a></span><br>
<span>"LinuxMagic" a Registered TradeMark of
Wizard Tower TechnoServices Ltd.</span><br>
<span>------------------------------------------------------------------------</span><br>
<span>604-682-0300 Beautiful British Columbia,
Canada</span><br>
<span></span><br>
<span>This email and any electronic data
contained are confidential and intended</span><br>
<span>solely for the use of the individual or
entity to which they are addressed.</span><br>
<span>Please note that any views or opinions
presented in this email are solely</span><br>
<span>those of the author and are not intended
to represent those of the company.</span><br>
<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><br>
</div>
</blockquote>
<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>
<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>
</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>
<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">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>