<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<pre>Hi Jonathan,
the domain object ID is indeed part of the whois:
>From the Whois of a .org domain -> Registry Domain ID: D104189961-LROR
>From the Whois of a .com domain -> Registry Domain ID: 4065057_DOMAIN_COM-VRSN
>From the Whois of a .Saarland domain -> Registry Domain ID: 8932212620_DOMAIN-SAAR
It is a unique identifier for a registration.
Best,
Volker
</pre>
<br>
<div class="moz-cite-prefix">Am 10.10.2017 um 05:18 schrieb jonathan
matkowsky:<br>
</div>
<blockquote type="cite"
cite="mid:CALsyHBnanBEt+B8AVf3BxTBcyaZWgKNHK67UZriS5+Yj-7k_cg@mail.gmail.com">
<div>
<div dir="auto">Is the Domain Object ID displayed?</div>
<br>
<div class="gmail_quote">
<div>On Mon, Oct 9, 2017 at 3:34 PM Sara Bockey <<a
href="mailto:sbockey@godaddy.com" moz-do-not-send="true">sbockey@godaddy.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div class="m_-1679161643134154073WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light"">I agree with Volker.</span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light""> </span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light"">Sara
</span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light""> </span></p>
<div>
<p class="MsoNormal" style="margin-bottom:1.0pt"><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:#02c54c">sara bockey</span></b><span
style="font-size:12.0pt;color:black"></span></p>
<p class="MsoNormal" style="margin-bottom:1.0pt"><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:#111111">sr. policy manager |
</span></b><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:#02c54c">Go</span></b><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:black">Daddy<sup>™</sup></span></b><span
style="font-size:12.0pt;color:black"></span></p>
<p class="MsoNormal" style="margin-bottom:1.0pt"><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:#111111"><a
href="mailto:sbockey@godaddy.com"
target="_blank" moz-do-not-send="true">sbockey@godaddy.com</a>
480-366-3616</span></b><span
style="font-size:12.0pt;color:black"></span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"GD
Boing";color:#111111">skype: sbockey</span></b><span
style="font-size:10.5pt;font-family:"GT
Walsheim Light";color:black"></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"GT
Walsheim Light";color:black"> </span></p>
</div>
<p class="MsoNormal"><i><span
style="font-size:10.0pt;color:black;background:white">This
email message and any attachments hereto is
intended for use only by the addressee(s) named
herein and may contain confidential information.
If you have received this email in error, please
immediately notify the sender and permanently
delete the original and any copy of this message
and its attachments.</span></i><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light""></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"GT
Walsheim Light""> </span></p>
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:12.0pt;color:black">From: </span></b><span
style="font-size:12.0pt;color:black"><<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>>
on behalf of Volker Greimann <<a
href="mailto:vgreimann@key-systems.net"
target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a>><br>
<b>Date: </b>Monday, October 9, 2017 at 1:13 AM<br>
<b>To: </b>"<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>"
<<a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>></span></p>
</div>
</div>
</div>
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div class="m_-1679161643134154073WordSection1">
<div style="border:none;border-top:solid #b5c4df
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><span
style="font-size:12.0pt;color:black"><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] Proposed
Agreement for Original Registration Date</span></p>
</div>
</div>
</div>
<div bgcolor="white" link="blue" vlink="purple" lang="EN-US">
<div class="m_-1679161643134154073WordSection1">
<div>
<p class="MsoNormal"> </p>
</div>
<p>I still think that the only date that should be
included is the creation date of a domain name as all
potential previous registrations of the same string
refer to a different domain object.
</p>
<p>A domain that once existed and has been permanently
deleted at the registry level is not the same as a
domain registered when the string became available
again, and we should not try to conflate both into one
object.
</p>
<p>Best,</p>
<p>Volker</p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Am 02.10.2017 um 05:28 schrieb
jonathan matkowsky:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">The point is that without it,
you run the risk of misunderstandings of what
the creation date implies for starters. While
that could be mitigated arguably with
disclaimers, there’s no personal information in
indicating whether there are known prior
registration dates and the expert working group
recommended that original registration date be
included. This is just more accurate. Plus the
Whois is the most direct evidence without
necessarily having to ask for documents that
would include personal information. So this
potentially reduces the need for personal
information disclosure. If someone wants to get
their domain back that inadvertently lapsed,
there would be an indicator that it was
previously registered without having to
necessarily prove it. Plus records can more
easily be forged. This couldn’t be.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Sat, Sep 30, 2017 at
12:30 PM Stephanie Perrin <<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank" moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
wrote:</p>
</div>
<blockquote style="border:none;border-left:solid
#cccccc 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",sans-serif">Surely there are
many other ways an individual could prove
the original registration date of a
domain, other than it being in the WHOIS?</span></p>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",sans-serif">Stephanie Perrin</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On 2017-09-28 18:22,
jonathan matkowsky wrote:</p>
</div>
</div>
<div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">There is a lot going
on in the last week, and I am *still*
playing catch up.
</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<div>
<p class="MsoNormal">I apologize with
the religious high holidays at the
end of last week and my travel right
before that, I dropped the ball, but
I want to emphasize that the poll
that was circulated framing the
issue as to whether there is a
requirement for the Original
Registration Date in the EWG Final
Report is not the issue in my humble
opinion. The issue is whether it was
recommended. And it was. Very
clearly. And for good reasons. Some
of those were specified in the EWG
Final Report on page 132, and
illustrated in the annex thereto. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">There are many
very important reasons why this
recommendation was being made from
my perspective. I'm not going to
re-hash them. I am convinced that
the reasons why the EWG as a whole
made this recommendation would be
best satisfied by the counter and
indicator of unknown or yes status.
To just focus on the technical
reasons why they could have done a
better job defining the Original
Registration Date element as a
justification to dismiss the
*importance* of the element on the
basis it was not required would be
unfortunate.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Domains may be
registered and deleted throughout
the day literally within fifteen
minutes apart. Others who lose their
domain inadvertently and then want
to use that original registration
date as a point of reference in
domain recovery should not lose that
opportunity. On the flip side, to be
fair, someone who is the subject of
a UDRP deserves the opportunity to
point to the original registration
date as evidence the domain was
allowed to lapse. When valuating
domain names for sale, it is
important that there be a public
record that there may be a cloud on
the title. etc.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">The fact that
it's unknown there is a prior
existing registration is important
information. It let's people know
that the creation date does not mean
it is the first time the string has
ever been created while at the same
time letting us know when we know
for sure that there has been such a
prior registration in the future
when deletions are tracked. While
technically that may be obvious to
us here, that is not necessarily
obvious to many who rely on Whois.
So the fact it is set to unknown
serves a very important purpose.
Furthermore, when it is actually
known, that is vital information to
provide (nobody said registry
operators have to gather historical
data that is burdensome or that some
might not even have). I am not
convinced it is too much to ask
registry operators to keep track of
deletions in the future. Doing so
may not be hard to implement and
would meet the recommendations of
the EWG. Part of the work we are
doing here has to have long-term
vision and not just whether it is
helpful in the short term for our
personal or commercial purposes at
hand. A lot of people in future
generations are counting on us.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">The particular
date is not as important to meet the
underlying objectives of the EWG in
coming up with this recommendation.
I would also not dismiss outright
how this counter will eventually
serve an important function as an
indicator of severe abuse that is
taking place behind the scenes that
nobody has easy access to see but
can be in the future would be more
readily apparent from following the
EWG's recommendation in this regard
(albeit, interpreting their
recommendation more liberally to
satisfy the policy considerations
and purposes they identified). </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">All of that said,
I recognize and respect that others
may disagree on this. I would at
least then recommend that we ensure
that the specific ID number that
must be collected anyway from an
engineering perspective is required
to actually be *displayed* to
tenuously meet the objectives of the
EWG indirectly since its being
exposed in a protocol anyway by
definition. While this is a lot more
work and not as helpful to many
Internet users as the compromised
suggestion to meet their
recommendation, at least we have
protection assuming there are
historical records as readily
available as today and that people
can point out the different object
ID numbers for these strings and
explain what that means. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Okay, I'm moving
on unless there is a group that
feels based on what I've said, that
we should at least re-visit briefly.
I recognize that there are *many* on
this string with a lot more
experience than me and knowledge
coming from different vantage
points, but feel it is important to
at least lay this out in case others
agree, as I wasn't on the call and
couldn't chime in, in as a timely
manner for which I express my
regrets.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Cheers,</p>
</div>
<div>
<p class="MsoNormal">Jonathan </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Fri, Sep 22,
2017 at 7:45 AM, Chuck <<a
href="mailto:consult@cgomes.com"
target="_blank"
moz-do-not-send="true">consult@cgomes.com</a>>
wrote:</p>
<blockquote
style="border:none;border-left:solid
#cccccc 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">I want to
request that any members who think
there is value in the 'counter'<br>
data element to please answer
Paul's question: " So the utility
of the<br>
counter seems highly limited.
Does it even<br>
deliver the usefulness that its
proponents want it to?" Please
share what<br>
you think that value is on this
list by Monday of next week.<br>
<br>
Chuck<br>
<br>
-----Original Message-----<br>
From: <a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a><br>
[mailto:<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>]
On Behalf Of Paul Keating<br>
Sent: Thursday, September 21, 2017
8:32 AM<br>
To: Greg Aaron <<a
href="mailto:gca@icginc.com"
target="_blank"
moz-do-not-send="true">gca@icginc.com</a>>;
Andrew Sullivan <<a
href="mailto:ajs@anvilwalrusden.com"
target="_blank"
moz-do-not-send="true">ajs@anvilwalrusden.com</a>>;<br>
<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
Subject: Re: [gnso-rds-pdp-wg]
Proposed Agreement for Original
Registration<br>
Date<br>
<br>
And what is the intended purpose
sought to be achieved?<br>
<br>
On 9/21/17, 5:15 PM, "Greg Aaron"
<<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>
on<br>
behalf of <a
href="mailto:gca@icginc.com"
target="_blank"
moz-do-not-send="true">gca@icginc.com</a>>
wrote:<br>
<br>
>The upshot is that the counter
would probably start at "Unknown"
for<br>
>all existing domains.<br>
>* Once implemented, the
feature has little usefulness
until years in<br>
>the future, when some domains
get re-registered and those
strings<br>
>accumulate some history.<br>
>* But many domains get renewed
year after year. Those wouldn't<br>
>accumulate counter history,
and would be set to Unknown either
forever,<br>
>or for long periods if they
are ever allowed to expire and if
they are<br>
>then re-registered. This is a
significant portion of domains.
For<br>
>example .COM has an renewal
rate of around 72%.<br>
><br>
>So the utility of the counter
seems highly limited. Does it
even<br>
>deliver the usefulness that
its proponents want it to?<br>
><br>
><br>
><br>
>-----Original Message-----<br>
>From: <a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a><br>
>[mailto:<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.org</a>]
On Behalf Of Andrew Sullivan<br>
>Sent: Thursday, September 21,
2017 10:49 AM<br>
>To: <a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
>Subject: Re: [gnso-rds-pdp-wg]
Proposed Agreement for Original<br>
>Registration Date<br>
><br>
>On Thu, Sep 21, 2017 at
02:28:39PM +0000, Greg Aaron
wrote:<br>
>> The alternate proposal is
a simple marker that says whether
there has<br>
>>been a known previous
iteration of the domain string,
having been<br>
>>registered with a
different ROID.<br>
>><br>
><br>
>Or a counter, of course,
rather than just the marker. From
the point<br>
>of view of implementation in a
database, I think these two
options are<br>
>approximately the same, so I
prefer the counter because it
provides an<br>
>additional bit of data (that
is, that the domain is changing --
you can<br>
>watch it happen).<br>
><br>
>> And it still presents the
same operational problem: the
registry has<br>
>>to figure out whether a
string has existed before. That
is something<br>
>>registries are not
designed to do. And they may not
have the<br>
>>necessary historical
records. See the notes below.<br>
>><br>
><br>
>Well, no, that's part of the
point of the new proposal: the
registry<br>
>_doesn't_ have to figure that
out, because the counter can be
set to<br>
>"unknown" (in a SQL database,
you'd probably use NULL). To
support<br>
>this feature, however, the
registry would have to track
deletions of<br>
>domain names in the future.
So it wouldn't be free, but it
also<br>
>wouldn't be hard to
implement. (Any real SQL
database, for instance,<br>
>could do this with an ON
DELETE trigger.)<br>
><br>
>Best regards,<br>
><br>
>A<br>
><br>
>--<br>
>Andrew Sullivan<br>
><a
href="mailto:ajs@anvilwalrusden.com"
target="_blank"
moz-do-not-send="true">ajs@anvilwalrusden.com</a><br>
>_______________________________________________<br>
>gnso-rds-pdp-wg mailing list<br>
><a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
><a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
>_______________________________________________<br>
>gnso-rds-pdp-wg mailing list<br>
><a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
><a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
<br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br>
<br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank"
moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></p>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
<p class="MsoNormal"> </p>
</blockquote>
</div>
<div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">*******************************************************************<br>
This message was sent from RiskIQ, and
is intended only for the designated
recipient(s). It may contain
confidential or proprietary information
and may be subject to confidentiality
protections. If you are not a designated
recipient, you may not review, copy or
distribute this message. If you receive
this in error, please notify the sender
by reply e-mail and delete this message.
Thank
you.*******************************************************************</span>
</p>
</blockquote>
</div>
<div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"> </p>
<pre>_______________________________________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
</div>
<p class="MsoNormal">_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></p>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal">-- </p>
</div>
<div>
<p class="MsoNormal">Jonathan Matkowsky</p>
</div>
<p class="MsoNormal"><br>
<span
style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">*******************************************************************<br>
This message was sent from RiskIQ, and is intended
only for the designated recipient(s). It may
contain confidential or proprietary information
and may be subject to confidentiality protections.
If you are not a designated recipient, you may not
review, copy or distribute this message. If you
receive this in error, please notify the sender by
reply e-mail and delete this message. Thank
you.*******************************************************************</span>
<br>
<br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
</p>
<pre>-- </pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.</pre>
<pre> </pre>
<pre>Mit freundlichen Grüßen,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- Rechtsabteilung -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: +49 (0) 6894 - 9396 901</pre>
<pre>Fax.: +49 (0) 6894 - 9396 851</pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>Geschäftsführer: Alexander Siffrin</pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken </pre>
<pre>Umsatzsteuer ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.</pre>
<pre> </pre>
<pre>--------------------------------------------</pre>
<pre> </pre>
<pre>Should you have any further questions, please do not hesitate to contact us.</pre>
<pre> </pre>
<pre>Best regards,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- legal department -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: +49 (0) 6894 - 9396 901</pre>
<pre>Fax.: +49 (0) 6894 - 9396 851</pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank" moz-do-not-send="true">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank" moz-do-not-send="true">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank" moz-do-not-send="true">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank" moz-do-not-send="true">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank" moz-do-not-send="true">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank" moz-do-not-send="true">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank" moz-do-not-send="true">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>CEO: Alexander Siffrin</pre>
<pre>Registration No.: HR B 18835 - Saarbruecken </pre>
<pre>V.A.T. ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank" moz-do-not-send="true">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.</pre>
<pre> </pre>
<pre> </pre>
<pre> </pre>
</div>
</div>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank"
moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></blockquote>
</div>
</div>
<div dir="ltr">-- <br>
</div>
<div class="gmail_signature" data-smartmail="gmail_signature">Jonathan
Matkowsky</div>
<br>
<span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******<br>
</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">This
message was sent from RiskIQ, and is intended only for the
designated recipient(s). It may contain confidential or
proprietary information and may be subject to confidentiality
protections. If you are not a designated recipient, you may not
review, copy or distribute this message. If you receive this in
error, please notify the sender by reply e-mail and delete this
message. Thank you.</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******</span>
</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>