<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">The problem with is that we are unable to make progress if we keep having to re-define the terms subject to discussion upon which such progress is predicated. For example, we spent time talking about the ins and outs of privacy in relation to thin data--the overwhelming majority agreed there were no privacy concerns in relation thereto--and then we went ahead and said let's now start re-defining what thin data is. Now we are talking about re-defining authentication. I would say that user authentication is a fairly basic universal concept of validation that a person has been provided with access to a resource. That concept by definition requires knowing something about them. It's basically a form of identity management. </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">We need to keep in mind that when domains expire is critical title information for the public. Unlike land which generally doesn't expire, domain names exist only from when they are created to when they expire. This is the most basic property identification possible.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">When domains were created and when they are set to expire is the most basic information for the public to have the ability to engage with the Internet to make informed choices about information held by the registrars. The accuracy of title to a domain is determined by when it is set to expire and when it was created. If the public is to have confidence in their investments in the Internet, this basic information is important considerations when undertaking any kind of transaction online. The ability to acquire and disseminate information and to control its flow is a source of institutional power that is also potentially abused.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div>Transparency and accessibility<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> </div>are<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> </div>principles of good governance<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> </div>that<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> </div>help<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> the public</div> become and<br>remain engaged with <div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">the Internet</div> and remain aware of how <div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">it</div> functions<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">.</div><div><font face="tahoma, sans-serif"><br></font></div><div>Accessibility to <div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">title</div> information<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> over the Internet</div> is in the public interest because it promotes equality<div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"> </div>. Accessibility to <div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">this information is a necessary condition for transparency to exist. Authentication is by definition, a barrier to access. Certain court documents are in the open because it's in the public interest to remain effectively engaged in, and with, the legal system while holding it to public account. The same is true for the existence of locations where people travel online or visit. Access prevents misconduct and exposes deficiencies to careful public scrutiny. Authentication should not be used just for the sake of practical obscurity, which is a principle that information in public records is effectively protected from disclosure as the result of practical barriers to access.</div></div><div><font face="tahoma, sans-serif"><br></font></div><div><div class="gmail_default" style="font-size:small;display:inline">The arguments I am hearing that records will still be available even if authentication is required does not mean there is no practical obscurity if the public's ability to access them </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline">is limited by practical constraints that come from authentication. The authentication may very well translate into barriers that prevent records from being readily accessible on a large scale. </div></div><div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">The existence of domain names (defined by their creation and expiry dates) is reliable information related to locations on the public Internet, which creates for a stable atmosphere for ownership and transfer of places on the Internet, as well as for visiting or doing business at these places online. The public has the right to know without any barriers to entry the most basic facts about places online, like when they were created and when they won't exist unless renewed according to the authoritative data. It also gives property holders the most basic information about their title and some insurance if they suffer a loss due to a lack of care by the registrar of the record. This is also important for investor confidence for the public doing business online. It is the most very basic of identifying information about the public property--when it was created and when it will cease to exist, as well as when it was last updated. This basic information should never have a barrier to entry in order to promote the transparent and accessible handling of such information.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Expectations of privacy must be balanced with freedom of access to the public Internet. There is no guaranteed right to anonymity or complete privacy online. No government can possibly guarantee that to their citizens, and it's not an unalienable right. The efficient availability of this information is the PRIMARY goal even if we build certain safeguards for personal privacy as long as we are not placing unnecessary barriers to access at the registry or registrar levels in the process of information dissemination.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">You can see an <a href="http://dspace.library.uvic.ca:8080/bitstream/handle/1828/6159/Johnson_Taylor_MPA_2015.pdf?sequence=1&isAllowed=y">example</a> discussed of how this balance has worked for land titles. But domains are a bit different since they cease to exist if not renewed on certain dates. Hence, it's even more important to have public access.</div><br></div><div><div style="left: 120.04px; top: 360.013px; transform: scaleX(0.857885);"><br></div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div>Jonathan Matkowsky,<br>VP – IP & Brand Security<br>USA:: 1.347.467.1193 | Office:: +972-(0)8-926-2766<br>Emergency mobile:: +972-(0)54-924-0831<br>Company Reg. No. 514805332 <br>11/1 Nachal Chever, Modiin Israel<br><a href="http://www.riskiq.co.il" target="_blank">Website</a><br>RiskIQ Technologies Ltd. (wholly-owned by RiskIQ, Inc.)</div></div></div></div>
<br><div class="gmail_quote">On Wed, Jun 7, 2017 at 2:13 PM, Volker Greimann <span dir="ltr"><<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>I think you are getting a step ahead of our target. As we have
not yet defined how authentification would look like, you are
making a presumption that may not be correct. We have not yet
determined that authentification needs to be personal. If may very
well be, but lets look at our verification and authntification
options when we get to that point. <br>
</p>
<p>Volker<br>
</p>
<br>
<div class="gmail-m_7407384160580817143moz-cite-prefix">Am 07.06.2017 um 13:04 schrieb jonathan
matkowsky:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-family:tahoma,sans-serif;font-size:small">Volker,
I am sorry but for privacy reasons, I am advocating that there
has to be a basis for authentication. Once you authenticate,
you are requiring personal information to be disclosed. If
there is no personal information to protect in doing so, than
you would be encroaching on privacy for no legitimate
reason--thereby violating the proportionality principle.</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail-m_7407384160580817143gmail_signature">
<div dir="ltr">
<div>Jonathan Matkowsky,<br>
VP – IP & Brand Security<br>
USA:: <a href="tel:(347)%20467-1193" value="+13474671193" target="_blank">1.347.467.1193</a> | Office:: <a href="tel:+972%208-926-2766" value="+97289262766" target="_blank">+972-(0)8-926-2766</a><br>
Emergency mobile:: <a href="tel:+972%2054-924-0831" value="+972549240831" target="_blank">+972-(0)54-924-0831</a><br>
Company Reg. No. 514805332 <br>
11/1 Nachal Chever, Modiin Israel<br>
<a href="http://www.riskiq.co.il" target="_blank">Website</a><br>
RiskIQ Technologies Ltd. (wholly-owned by RiskIQ, Inc.)</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, Jun 7, 2017 at 1:05 PM, Paul
Keating <span dir="ltr"><<a href="mailto:paul@law.es" target="_blank">paul@law.es</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div>Sorry but your position keeps changing. You clearly
favor restrictions on access. You appear to have
abandoned the privacy angle as justification and are now
relying upon an anti-abuse rationale. This last
position is rather useless. We all know that captcha
and other gates easily overcome. Thus the abuse you
note will continue. Unless you are going to impose
downstream use restrictions - which will largely if not
entirely be unenforceable from a practical standpoint -
there would be nothing to prevent a spammer to
authenticate him/her self using any number of fake
entities and thereafter publish the same data freely to
others.</div>
<div id="gmail-m_7407384160580817143m_-2689582086140126072AppleMailSignature"><br>
</div>
<div id="gmail-m_7407384160580817143m_-2689582086140126072AppleMailSignature">I am
left to conclude that what you really want is to
preclude harvesting of data so that it can be controlled
at the registry/registrar level. <br>
<br>
Sent from my iPad</div>
<div><br>
On 7 Jun 2017, at 10:31, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p>Hi Jonathan,</p>
<p>and I have no issue with the public being able to
get that information. Still, there is no reason why
the requester should not authenticate himself when
making that inquiry. Remember the access levels do
not block access, they just require further
authentification. So the public would be able to
find out when a domain is expected to become
available. This is no argument against gated access.</p>
<p>Best,</p>
<p>Volker</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="gmail-m_7407384160580817143m_-2689582086140126072moz-cite-prefix">Am
07.06.2017 um 11:23 schrieb jonathan matkowsky:<br>
</div>
<blockquote type="cite">
<div>The public has the right to know when a domain
is expected to become available. They might need
to place a backorder. All UDRPs require the
provider to check whether the domain is set to
expire during the proceeding. The fake renewal
notices and SEO scams will continue based on the
existence of the domain. I have seen countless
such scams where the domain is not set to expire
for years, and where it wasn't even recently
created--which supports keeping the creation and
expiration dates ungated so that companies can
verify that the scams are not bona fide.</div>
<div><br>
<div class="gmail_quote">
<div>On Wed, 7 Jun 2017 at 11:54 Volker Greimann
<<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"> It is
remarkable how much of the spam that we see
on a regular basis that is tied to the
domain lifecycle. Fake renewal notices, SEO
offers, the lot. <br>
Anything that would reduce this is a basis
for restricting access somewhat. I do not
really see any harm in such restrictions
either.<br>
<br>
Best,<br>
Volker</div>
<div bgcolor="#FFFFFF"><br>
<br>
<div class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-cite-prefix">Am
07.06.2017 um 10:27 schrieb jonathan
matkowsky:<br>
</div>
<blockquote type="cite">
<div>There is no basis for restricting
ungated access any more so than the
domain's existence or the string of
characters registered.</div>
<div><br>
<div class="gmail_quote">
<div>On Wed, 7 Jun 2017 at 11:22
Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have no
objections against having this data
available and accessible.<br>
The question is whether it should be
as accessible as it is now or<br>
whether there could be certain
restrictions. A tiered access system
as<br>
has been proposed would solve this
beautifully.<br>
<br>
In this case, the dates would be on
the second tier (the first tier<br>
being full unhindered access), which
would entail some form of<br>
authentification and bulk access
restrictions. Every single one of
the<br>
uses Andrew desribes would remain
possible and unproblematic, but the<br>
data would no longer be in as much
danger of being abused as it is
today.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
<br>
Am 06.06.2017 um 22:07 schrieb
Michael Peddemors:<br>
> +1 as well..<br>
><br>
> .. but with so many +1's on
having that data publicly
accessible, it<br>
> would be interesting to take a
straw poll, to a wider audience on
that<br>
> simple question..<br>
><br>
> It would be also nice to see
what category the parties in each
camp<br>
> lie? We know that everyone
involved in making the internet a
safer and<br>
> better place (security
companies, law enforcement et al)
want it<br>
> available, and to define 'thin
data' as wide as possible, and I can<br>
> understand that some
consideration to privacy be
considered so that it<br>
> doesn't go too wide, but not
really certain I understand the
position<br>
> of those that want it as 'thin'
as possible, or non-existant, and/or<br>
> the parties behind that
position and their numbers.<br>
><br>
> And of course the ever present
question for both camps, is the
opinion<br>
> coming from a place where there
are financial motivations (not that<br>
> necessarily there is anything
wrong with that <sic>) that
have formed<br>
> the basis of that opinion. (eg,
if the money equation was removed,<br>
> would you still have that
opinion, or even be in the
conversation?)<br>
><br>
> For all we know, the privacy
camp are in very small numbers in
this<br>
> conversation, and while they
might hold legitimate positions,
maybe it<br>
> isn't enough to affect the
directions/positions of ICANN as a
group<br>
> going forward.<br>
><br>
> And IMHO, even if it was 50/50
split, if it came down to two camps,
eg<br>
> 'the ones keeping us safe' and
'it affects/risks our pocketbooks',
I<br>
> would err on policies that
would aid the former..<br>
><br>
> Don't want 'politics' to affect
such important decisions..<br>
><br>
><br>
><br>
> On 17-06-06 11:22 AM, Andrew
Sullivan wrote:<br>
>> Hi,<br>
>><br>
>> On the call today there
were arguments being made about why
certain<br>
>> fields should not be
publicly accessible. In effect,
what we are now<br>
>> arguing about, in talking
about what should be considered
"thin data",<br>
>> is the definition of the
set of data to which unauthenticated
access<br>
>> should be permitted. (Let
us please not get distracted by what
is<br>
>> actually required by the
RAA or anything like that just now,
since the<br>
>> outcome of this policy
discussion might change that.)<br>
>><br>
>> There were several
arguments put forth about whether
the created on,<br>
>> updated on, and expiry
dates should be included.
Similarly, people<br>
>> discussed whether the
domain status values should be
included. I<br>
>> believe they must be.<br>
>><br>
>> The Internet is unlike many
other technologies because of its
radical<br>
>> decentralization. That is
not some sort of political choice,
but<br>
>> instead a fundamental part
of the design of the Internet: it's
a<br>
>> network of networks (of
networks…) formed by voluntary
interoperation<br>
>> among the participants.
Participants in the Internet
interoperate<br>
>> without setting up formal
contractual arrangements between all
the<br>
>> participating parties.
This feature is part of what has
made the<br>
>> Internet so successful
compared to other telecommunications
systems,<br>
>> because the barrier to
entry is really low. But that
design comes at<br>
>> a cost.<br>
>><br>
>> The cost is that there's
not always a party to speak to, with
whom one<br>
>> has a pre-existing
relationship. If communications
break down between<br>
>> two telephone customers,
they know whom to call: the phone
company.<br>
>> The phone company also has
contractual (or sometimes treaty)<br>
>> relationships to other
phone companies.<br>
>><br>
>> The Internet doesn't work
that way. If you and I are
communicating<br>
>> over the Internet, there is
no guarantee of direct contractual<br>
>> relationships all the way
along the transit path: that's what
open<br>
>> peering policies ensure.
The way we make this work in fact is
by<br>
>> placing the responsibility
for troubleshooting out at the
edges. And<br>
>> because of that, when I
need to troubleshoot my site I need
to have<br>
>> tools with which to do
that.<br>
>><br>
>> In domain-based
communications (such as email, IP
telephony, websites,<br>
>> money transfer, and
thousands of other applications),
when I encounter<br>
>> a problem with the
communication I need to answer
whether the problem<br>
>> is in _my_ network
operation, or in the other end.
Important data to<br>
>> rule out "the other end" is
in the thin RDS data.<br>
>><br>
>> Obviously, the nameserver
and DNSSEC information in the RDS
will allow<br>
>> me to tell whether what is
in the global DNS is what ought to
be<br>
>> there. For instance, if
the RDS has one value for the name
servers,<br>
>> but the DNS returns
something else, there is a problem.<br>
>><br>
>> Less obvious but just as
important are the status values. If
a name<br>
>> is on Hold or is
pendingTransfer or something like
that, it can tell<br>
>> me that something is up. A
name that doesn't appear in the DNS
but<br>
>> has a full complement of
name servers in the RDS, for
example, might<br>
>> be on hold; and I can't
tell that without seeing the status
values.<br>
>><br>
>> In the same way, the dates
in the RDS allow a troubleshooter to<br>
>> understand what might be
wrong when things are broken. If a
name is<br>
>> set to expire in a day and
you're getting a parking page on the<br>
>> website, you have a clue
about what is going on. Most of the
examples<br>
>> cited in<br>
>> <a href="https://whoapi.com/blog/1582/5-all-time-domain-expirations-in-internets-history/" rel="noreferrer" target="_blank">https://whoapi.com/blog/1582/5<wbr>-all-time-domain-expirations-i<wbr>n-internets-history/</a><br>
>><br>
>> were trivial to understand
for help desks that could see that a
name<br>
>> that should have existed
for some time was just hours old,
because the<br>
>> created_on date was
available. And if you start having
trouble and<br>
>> see a domain was updated
about the same time the trouble
started, you<br>
>> have a pretty good clue
that the problem is most likely at
the target<br>
>> domain, and not in your own
network.<br>
>><br>
>> As for the question of why
the global Internet infrastructure
needs to<br>
>> help with this, the answer
is that _that's what the
infrastructure is<br>
>> for_. We have registrars
and registries in order to
co-ordinate these<br>
>> assignments and make those
assignments available, in support of
the<br>
>> distributed administration
and operation of the Internet. If
the<br>
>> infrastructure isn't
providing this kind of information
in order to<br>
>> help administrators of
various Internet administrators,
then it isn't<br>
>> doing its job.<br>
>><br>
>> The Internet is a
distributed system. If you want to
make distributed<br>
>> systems work, you have to
allow the operators to have enough<br>
>> information to do their
jobs independently of one another.
So,<br>
>> regardless of where one
lands on whether any of this data is
personal<br>
>> data, it makes no
difference. If you want the domain
name system to<br>
>> continue to work reliably,
you have to publish this data.<br>
>> Centralization and locking
the data up for just registrars
simply<br>
>> won't scale.<br>
>><br>
>> Best regards,<br>
>><br>
>> A<br>
>><br>
><br>
><br>
><br>
<br>
--<br>
Bei weiteren Fragen stehen wir Ihnen
gerne zur Verfügung.<br>
<br>
Mit freundlichen Grüßen,<br>
<br>
Volker A. Greimann<br>
- Rechtsabteilung -<br>
<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0)
6894 - 9396 901</a><br>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0)
6894 - 9396 851</a><br>
Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><br>
<br>
Web: <a href="http://www.key-systems.net" rel="noreferrer" target="_blank">www.key-systems.net</a>
/ <a href="http://www.RRPproxy.net" rel="noreferrer" target="_blank">www.RRPproxy.net</a><br>
<a href="http://www.domaindiscount24.com" rel="noreferrer" target="_blank">www.domaindiscount24.com</a>
/ <a href="http://www.BrandShelter.com" rel="noreferrer" target="_blank">www.BrandShelter.com</a><br>
<br>
Folgen Sie uns bei Twitter oder
werden Sie unser Fan bei Facebook:<br>
<a href="http://www.facebook.com/KeySystems" rel="noreferrer" target="_blank">www.facebook.com/KeySystems</a><br>
<a href="http://www.twitter.com/key_systems" rel="noreferrer" target="_blank">www.twitter.com/key_systems</a><br>
<br>
Geschäftsführer: Alexander Siffrin<br>
Handelsregister Nr.: HR B 18835 -
Saarbruecken<br>
Umsatzsteuer ID.: DE211006534<br>
<br>
Member of the KEYDRIVE GROUP<br>
<a href="http://www.keydrive.lu" rel="noreferrer" target="_blank">www.keydrive.lu</a><br>
<br>
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.<br>
<br>
------------------------------<wbr>--------------<br>
<br>
Should you have any further
questions, please do not hesitate to
contact us.<br>
<br>
Best regards,<br>
<br>
Volker A. Greimann<br>
- legal department -<br>
<br>
Key-Systems GmbH<br>
Im Oberen Werk 1<br>
66386 St. Ingbert<br>
Tel.: <a href="tel:+49%206894%209396901" value="+4968949396901" target="_blank">+49 (0)
6894 - 9396 901</a><br>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0)
6894 - 9396 851</a><br>
Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><br>
<br>
Web: <a href="http://www.key-systems.net" rel="noreferrer" target="_blank">www.key-systems.net</a>
/ <a href="http://www.RRPproxy.net" rel="noreferrer" target="_blank">www.RRPproxy.net</a><br>
<a href="http://www.domaindiscount24.com" rel="noreferrer" target="_blank">www.domaindiscount24.com</a>
/ <a href="http://www.BrandShelter.com" rel="noreferrer" target="_blank">www.BrandShelter.com</a><br>
<br>
Follow us on Twitter or join our fan
community on Facebook and stay
updated:<br>
<a href="http://www.facebook.com/KeySystems" rel="noreferrer" target="_blank">www.facebook.com/KeySystems</a><br>
<a href="http://www.twitter.com/key_systems" rel="noreferrer" target="_blank">www.twitter.com/key_systems</a><br>
<br>
CEO: Alexander Siffrin<br>
Registration No.: HR B 18835 -
Saarbruecken<br>
V.A.T. ID.: DE211006534<br>
<br>
Member of the KEYDRIVE GROUP<br>
<a href="http://www.keydrive.lu" rel="noreferrer" target="_blank">www.keydrive.lu</a><br>
<br>
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.<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a></blockquote>
</div>
</div>
<div>-- <br>
</div>
<div>jonathan
matkowsky, vp - ip & head of global
brand threat mitigation</div>
</blockquote>
<br>
<pre class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143m_-2689582086140126072m_1381224760868507598moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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>
</div>
</div>
<div dir="ltr">-- <br>
</div>
<div>jonathan
matkowsky, vp - ip & head of global brand
threat mitigation</div>
</blockquote>
<br>
<pre class="gmail-m_7407384160580817143m_-2689582086140126072moz-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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143m_-2689582086140126072moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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">gnso-rds-pdp-wg@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/gnso-rds-pdp-wg</a></span></div>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="gmail-m_7407384160580817143moz-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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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">+49 (0) 6894 - 9396 901</a>
Fax.: <a href="tel:+49%206894%209396851" value="+4968949396851" target="_blank">+49 (0) 6894 - 9396 851</a>
Email: <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a>
Web: <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a>
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a>
<a class="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems" target="_blank">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="gmail-m_7407384160580817143moz-txt-link-abbreviated" href="http://www.keydrive.lu" target="_blank">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></div><br></div></div></div>