<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Greg,</p>
<p>I wish it were so, but at ICANN, both are the same. Incorrectly
formatted whois is incorrect whois in the books of ICANN
compliance.</p>
<p>And yes, I agree, that the terminology should be changed and used
as a basis for our discussions.</p>
<p>Best,</p>
<p>Volker</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 10.10.2016 um 18:51 schrieb Greg
Aaron:<br>
</div>
<blockquote
cite="mid:BN6PR13MB1843278000F75A5A950FA18ED9DB0@BN6PR13MB1843.namprd13.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
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:Courier;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.m2007596586480275167m-2640664371089058745m-3041100436472200702m-8681382493968748554apple-converted-space
{mso-style-name:m_2007596586480275167m-2640664371089058745m-3041100436472200702m-8681382493968748554apple-converted-space;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:1.0in 1.0in 1.0in 1.0in;}
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"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">In
the post below, Volker is talking about data FORMATTING,
not ACCURACY. Formatting and accuracy are distinct
concepts. They can have a relationship, but they are not
one and the same. It is very important to understand the
difference.<o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Formatting
is the way in which something is arranged or set out. For
example, do you format country name in the written-out
form ("Canada"), or do you use the two-letter abbreviation
("CA")? Either way the data is accurate; you know the
contact is in Canada.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
formatting of many registration data fields is specified
in the EPP RFCs, which registries and registrars have been
required to follow for years. For example, RFC5733 says
registries and registrars must use certain standard
conventions for timestamps, use email address syntax as
per RFC5322, use two-character country codes per ISO
standards, and must format contact telephone numbers a
certain way derived from international standards. <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
benefits of standardized data formatting are obvious, and
RFCs are designed to bring those benefits to the
Internet. In the case of EPP, registries and registrars
can store and trade data easily and accurately. As the
SSAC has noted, these standards make it easier for people
and applications to understand and use registration data
(SAC051).
<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">The
2013 RAA requires that registrars validate that certain
data fields are FORMATTED CORRECTLY as per the standards.
In SAC058, the SSAC described it this way: "Syntactic
Validation refers to the assessment of data with the
intent to ensure that they satisfy specified syntactic
constraints, conform to specified data standards, and are
transformed and formatted properly for their intended
use."<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Validating
that the data is ACCURATE -- that it's truthful, or that
an address is deliverable, or is suitable for operational
purposes, or however you want to say it -- is a different
concept. Validation of accuracy has different procedures
and can have different standards. For more about that,
please see the sections about Operational Validation and
Identity Validation in SAC058.
</span></span><a moz-do-not-send="true"
href="https://www.icann.org/en/system/files/files/sac-058-en.pdf"><span
style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">https://www.icann.org/en/system/files/files/sac-058-en.pdf</span></span><span
style="mso-bookmark:_MailEndCompose"></span></a><span
style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">
The 2013 contains an operational validation requirement.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Recommendation
1 from SAC058 was: “The SSAC recommends that the ICANN
community should consider adopting the terminology
outlined in this report in documents and discussions.”
The RDS WG should discuss that.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">We
have protocol standards so that things will work, and RFCs
should be adhered to. Hopefully that is uncontroversial.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">With
best wishes,<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">--Greg<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
<a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">gnso-rds-pdp-wg-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-rds-pdp-wg-bounces@icann.org">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Volker Greimann<br>
<b>Sent:</b> Monday, October 10, 2016 4:42 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<b>Subject:</b> Re: [gnso-rds-pdp-wg] For your review -
updated RDS Statement of Purpose<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>I still do not agree: A phone n umber may be technically
incorrect but still functional.<o:p></o:p></p>
<p>Consider these examples:<o:p></o:p></p>
<p>0049-1234-56789<br>
+49-123456789<br>
+49.0123456789<br>
0049(0)123456789<o:p></o:p></p>
<p>and variations thereof.<o:p></o:p></p>
<p>All of these numbers will be readily usabla for anyone with
half a brain cell, yet each and every one of these numbers is
inaccurate under wcurrent whois policies.<br>
For reference, this would be the "correct" number:<o:p></o:p></p>
<p>+49.123456789<o:p></o:p></p>
<p>So what does this tell us? It tells me that on the march to
accuracy, we will create more issues than we will solve.<o:p></o:p></p>
<p>I have seen mail delivered to horribly spelled addresses, yet
otoh, I have also seen time and again that mail sent to
perfectly correct addresses was not delivered, because the
postman could not find it (for example because the entrance to
a building in one street actually was located around the
corner in another street) and the mail was returned
undelivered.<o:p></o:p></p>
<p>Best,<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 09.10.2016 um 19:09 schrieb Richard
Leaning:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Michele,<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">I don't disagree with you. There will
always be scenarios where common sense prevails.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">But if you want to phone me you will
need the accurate number - not something that looks like
my number.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">If you want to respond to me about
these comments, you will need the accurate email address
not something that is sort of my email address. <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">All am saying is we should strive for
accuracy knowing that we may not achieve it but at least
let's try. <o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Cheers<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Dick <br>
<br>
Richard Leaning <o:p></o:p></p>
<div>
<p class="MsoNormal">RIPE NCC<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">External Relations<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(Sent by iPhone)<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On 9 Oct 2016, at 13:41, Michele Neylon - Blacknight <<a
moz-do-not-send="true"
href="mailto:michele@blacknight.com">michele@blacknight.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Dick</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Sorry,
but that’s absolutely untrue. So I agree with Greg.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">I
have been getting postal mail for more than 30 years
and over that period my name, my gender and my address
have been listed inaccurately hundreds of times.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Yet
the postal services in the various countries that I’ve
lived in have been able to get the mail to me.</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">There
is a very big difference between “functional” and
“accurate”.
</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">As
others have pointed out, it’s often impossible to
provide 100% accurate addresses on web forms etc., Try
updating your ESTA for a visit to the US and you’ll
find 9 times out of 10 that the address form doesn’t
allow enough space for the hotel name and address. But
if you provide the hotel name the authorities will
know exactly where you are without the full address.
</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Our
office address, for example, lists us as being in
Carlow. If you actually looked at a map you’d see that
we aren’t in Carlow, but in Laois.
</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Regards</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Michele</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">--</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Mr
Michele Neylon</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Blacknight
Solutions</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hosting,
Colocation & Domains</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><a
moz-do-not-send="true"
href="http://www.blacknight.host/"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://www.blacknight.host/</span></a><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><a
moz-do-not-send="true"
href="http://blacknight.blog/"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://blacknight.blog/</span></a><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><a
moz-do-not-send="true" href="http://ceo.hosting/"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">http://ceo.hosting/</span></a><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Intl.
+353 (0) 59 9183072</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Direct
Dial: +353 (0)59 9183090</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">-------------------------------</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Blacknight
Internet Solutions Ltd, Unit 12A,Barrowside Business
Park,Sleaty</span><o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Road,Graiguecullen,Carlow,R93
X265,</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">Ireland
Company No.: 370845</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-family:"Calibri",sans-serif">From:
</span>
</b><span
style="font-family:"Calibri",sans-serif"><</span><a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"><span
style="font-family:"Calibri",sans-serif">gnso-rds-pdp-wg-bounces@icann.org</span></a><span
style="font-family:"Calibri",sans-serif">>
on behalf of Richard Leaning <</span><a
moz-do-not-send="true"
href="mailto:rleaning@ripe.net"><span
style="font-family:"Calibri",sans-serif">rleaning@ripe.net</span></a><span
style="font-family:"Calibri",sans-serif">><br>
<b>Date: </b>Friday 7 October 2016 at 19:20<br>
<b>To: </b>Greg Shatan <</span><a
moz-do-not-send="true"
href="mailto:gregshatanipc@gmail.com"><span
style="font-family:"Calibri",sans-serif">gregshatanipc@gmail.com</span></a><span
style="font-family:"Calibri",sans-serif">><br>
<b>Cc: </b>gnso-rds-pdp-wg <</span><a
moz-do-not-send="true"
href="mailto:gnso-rds-pdp-wg@icann.org"><span
style="font-family:"Calibri",sans-serif">gnso-rds-pdp-wg@icann.org</span></a><span
style="font-family:"Calibri",sans-serif">><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] For your
review - updated RDS Statement of Purpose</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Thats Greg for articulating it so
well. <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">all i was going to say was - <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">'You can’t contact someone if the
contact information is inaccurate’<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">So i can’t see how you can split
the two.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Richard Leaning<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">External Relations<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">RIPE NCC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</blockquote>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</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 moz-do-not-send="true" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a moz-do-not-send="true" href="http://www.key-systems.net">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.BrandShelter.com">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 moz-do-not-send="true" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.twitter.com/key_systems">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 moz-do-not-send="true" href="http://www.keydrive.lu">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 moz-do-not-send="true" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a moz-do-not-send="true" href="http://www.key-systems.net">www.key-systems.net</a> / <a moz-do-not-send="true" href="http://www.RRPproxy.net">www.RRPproxy.net</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a moz-do-not-send="true" href="http://www.BrandShelter.com">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 moz-do-not-send="true" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.twitter.com/key_systems">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 moz-do-not-send="true" href="http://www.keydrive.lu">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>
</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>