<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>With all due respect, I utterly reject this recommendation. If
contracted parties had to undergo a full audit for every ARS
complaint, we would get nothing else done. This suggested
recommendation is so far beyond the pale, it defies any common
sense. <br>
</p>
<p>As I explained before, receipt of a whois inaccuracy complaint or
an ARS ticket does not indicate the registrar is not complying
with its contractual or policy obligations. It merely means some
data is incorrect. This can have many reasons outside the
registrar not doing his job. <br>
</p>
<p>I object to any attempt to include this or a similar
recommendation in the report. There is simply no need for such a
recommendation. Further, this recommendation is not based on any
facts or findings of patters where these obligations are regularly
violated. It is entirely based on a ficticious assumption that has
no basis in reality - that the occurance of whois inaccuracies
mean that someone is violating their obligations. </p>
<p>I also want to point out that compliance does inquire about
validation and verification methods being correctly implemented in
case there are indications of misconduct and registrars that
receive greater than average numbers of complaints are already
targeted more often in the scheduled audit runs. <br>
</p>
<p>Volker<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Am 03.06.2018 um 11:54 schrieb SUN
Lili:<br>
</div>
<blockquote type="cite"
cite="mid:c71f512688d8416db82e61cd33c91986@MBX21.interpol.int">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Dear
all,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">For
the proposed recommendations, I’d suggest to merge #1 and #7
into one, #2 and #6 into one. I support that “all domain
name registrations adhere to the WHOIS requirements in the
2013 Registrar Accreditation Agreement”, but I’m cautious
about the necessity of a new policy to be developed (maybe
it’s a routine within ICANN?). My impression is that there
are too many policies in the realm of Whois rather than not
enough. By the end of this year, all registrars will shift
to 2013 RAA, it’s time to endorse a standardized requirement
for all gTLDs.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’d
like to propose a new recommendation as below:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Recommendation:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Following
a valid WHOIS ARS ticket, or Whois inaccuracy complaint, an
full audit targeting the relating registrar should be
initiated, to check if the registrar follows the contractual
obligations, the consensus policies, etc. Sanctions should
be applied if deficiencies identified.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Findings:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">All
current compliance activities are separate and conducted
individually. WHOIS ARS sampled Whois records to do accuracy
test, the Audit programme sampled registrars to conduct
audit, no synergies have been gained through different
action tracks.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Rationale:
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If
a Whois record is not accurate due to registrar didn’t
conduct validation and verification, it shouldn’t be a
standalone case. A follow up audit will help to mitigate all
issues regarding the outstanding registrar.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Impact
of Recommendation:<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Only
related registrars will be impacted by this recommendation
along with the compliance team.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US">Feasibility of Recommendation:
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US">This recommendation will make the Audit program
more targeted. The compliance team may need further
assessment of resources to implement this recommendation.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US">Lili<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US"> RDS-WHOIS2-RT
[<a class="moz-txt-link-freetext" href="mailto:rds-whois2-rt-bounces@icann.org">mailto:rds-whois2-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Volker Greimann<br>
<b>Sent:</b> Saturday, 26 May, 2018 12:02 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:rds-whois2-rt@icann.org">rds-whois2-rt@icann.org</a><br>
<b>Subject:</b> Re: [RDS-WHOIS2-RT] Compliance subgroup
draft report<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Susan,<o:p></o:p></p>
<p>regarding the analysis section, one brief point:<o:p></o:p></p>
<p>The cancellation or suspension of the registration does not
necessarily mean that the data was incorrect. In many cases,
the registrant simply ignored the message, saw it too late,
did not have it forwarded by a reseller, etc and therefore did
not respond by the time the registrar is obliged to take
action. So if you take a nice three week hiking tour, that is
the best time for anyone who wants to take down your domain
name. Let's be careful with drawing conclusions from data that
can be interpreted in many ways.<o:p></o:p></p>
<p>To the next paragraph, ICANN actually monitors suspended
domains and reaches out to registrars when such domains are
unsuspended.<o:p></o:p></p>
<p>I disagree with the conclusion that a suspended domain should
not be unsuspended without verification as the suspension can
have occurred for a multitude of reasons that have nothing to
do with the registration data. (Most common on our registrar:
Hacked wordpress blogs with subsites that lead to phishing
sites - usually fixed by removing the subpages and updating
the WordPress by the registrant). As for the recommendation,
that is a significant implementation impact for little to no
benefit. I see no harm in having false data in the whois of a
suspended domain. And I also disagree with the second part of
the recommendation, as detailed above. And to the added
question, yes, suspended domain names can and will be renewed.<o:p></o:p></p>
<p>Re: Grandfathered domains:<o:p></o:p></p>
<p>I have significant concerns about the logistics of this
recommendation. Not having to touch legacy domains and their
owners unless there is active cause to do so has been a
significant part of the agreement between Registrars and ICANN
under the 2013 RAA negotiations. I also note that that usually
older domains are not as much a cause for
<o:p></o:p></p>
<p>Re: Bulk Submission tool:<o:p></o:p></p>
<p>We should add something that submissions remain manageable by
registrars of all sizes, since receiving 300 single tickets or
one ticket with 300 domains can overwhelm the abuse function
of smaller registrars. So complaints using such a tool need to
be for one issue with multiple domains, not various issues
with multiple domains. So if they all use the same incorrect
whois for example, that would be a valid use, but if they all
use different whois data, they should be submitted
individually. Rules for combining UDRP complaints could inform
on what should be applied here to keep this tool relevant.<o:p></o:p></p>
<p>Proactive: The ARS is quite proactive and feeds directly into
compliance. Should ICANN undertake two or more projects with
the same goal at the same time? Also, is there actual value in
improving whois data quality where no other issue exists? We
have many cases where data is outdated because people moved
and forgot to update their whois. When we notice this we ask
them to update, but is this really an issue that needs fixing
by the community? Is Whois accuracy an aboslute goal in and of
itself? I do not support the recommendation that compliance
should be more proactive in monitoring. With Whois ARS and
volunteer community effort, sufficient proactive efforts
exist.<o:p></o:p></p>
<p>Cross validation: Cannot be a compliance issue until it is
agreed between ICANN and registrars. The working group is
still deliberating.
<o:p></o:p></p>
<p>Table on Page 18: The RT1 Recommendation refers to proactive
management and scaling of compliance activities, not proactive
assessment and enforcement. The RT1 Rec means that Compliance
should be proactive with regard to its own ability to perform
its function, not to expand on that function as the comment in
the table suggests.<o:p></o:p></p>
<p>Finally, the document keeps using the term TLDs where domain
names are meant. This should be updated. Example: "legacy
tlds"<o:p></o:p></p>
<p>Recommendations:<o:p></o:p></p>
<p>#1: We should not recommend enforcement of a registry policy
against registrars. If anything, it is a contractual issue
between registries and registrars and thus behind the picket
fence. If anything, it would have to be enforced against
registries not properly implementing it. It therefore cannot
be part of the registrar audit.<o:p></o:p></p>
<p>#2: Strongly disagree with this recommendation, as detailed
above. Highly unfeasible due to requirement to touch hundreds
of thousands of customers to basically ask them to add or
change formatting on certain data. Customer support nightmare
and costs highly outweighing the benefits. Strongly opposed.<o:p></o:p></p>
<p>#3: Opposed, as detailed above.<o:p></o:p></p>
<p>#5: Agreed, provided we include measures to keep such reports
manageable, applying rules similar to the ones for joining
UDPR complaints together. Rationale: See above.<o:p></o:p></p>
<p>#6 Seems to duplicate Rec 2? Strongly opposed as detailed
above. Logistical nightmare.
<o:p></o:p></p>
<p>#7 Opposed: This issue has been addressed by the GNSO, see: <a
href="https://gnso.icann.org/en/group-activities/inactive/2015/dmpm"
moz-do-not-send="true">
https://gnso.icann.org/en/group-activities/inactive/2015/dmpm</a> Let us
not re-open issues that have already been debated at length by
the community. And why only the compliance team?
<o:p></o:p></p>
<p>Volker<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Am 24.05.2018 um 20:54 schrieb Susan
Kawaguchi:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hello All, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please see the attached Compliance
subgroup draft report. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Apologies to the subgroup in not
providing this to you earlier in the week for your
review but thought it best to hit the deadline for the
draft report to the full working group. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This report still needs more work, I
definitely did not organize the information optimally
and will continue to work on that. I intend to use a
table format for some of our analysis as we did for the
RT1 compliance recommendation. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Also there may be duplicative
language as I moved things around I may not have caught
all of the changes. I also intentionally left some
duplicative language to remind me to continue editing. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am hoping the subgroup will meet
next week for additional discussion on the findings and
recommendations. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Susan <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>RDS-WHOIS2-RT mailing list<o:p></o:p></pre>
<pre><a href="mailto:RDS-WHOIS2-RT@icann.org" moz-do-not-send="true">RDS-WHOIS2-RT@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>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><o:p></o:p></pre>
<pre><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><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></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.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" moz-do-not-send="true">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>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><o:p></o:p></pre>
<pre><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><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems" moz-do-not-send="true">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a href="http://www.twitter.com/key_systems" moz-do-not-send="true">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="http://www.keydrive.lu" moz-do-not-send="true">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></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.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</div>
<div>
***************************************************************************************************<br>
This message, and any attachment contained, are confidential and
subject of legal privilege. It may be used solely for the
designated police/justice purpose and by the individual or
entity to whom it is addressed. The information is not to be
disseminated to another agency or third party without the
author’s consent, and must not be retained longer than is
necessary for the fulfilment of the purpose for which the
information is to be used. All practicable steps shall be taken
by the recipients to ensure that information is protected
against unauthorised access or processing. INTERPOL reserves the
right to enquire about the use of the information provided.<br>
If you are not the intended recipient, be advised that you have
received this message in error. In such a case, you should not
print it, copy it, make any use of it or disclose it, but please
notify us immediately and delete the message from any computer.<br>
*************************************************************************************************<br>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
RDS-WHOIS2-RT mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RDS-WHOIS2-RT@icann.org">RDS-WHOIS2-RT@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/rds-whois2-rt">https://mm.icann.org/mailman/listinfo/rds-whois2-rt</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">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>