<HTML xmlns:o><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 14 (filtered medium)">
<STYLE><!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@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: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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        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.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        color:black;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Arial","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;}
span.EmailStyle23
        {mso-style-type:personal-reply;
        font-family:"Arial","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:143476346;
        mso-list-template-ids:201229092;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:\F0A7;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></STYLE>
</HEAD>
<BODY lang=EN-US dir=ltr link=blue bgColor=white vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I disagree. The UDRP is designed to correct misbehavior of a valid
domain name owner relating to that owner’s use of a domain name, namely that the
use of a domain infringes the rights of a trademark owner. The basis of
the complaint is not that the domain name owner did not validly register the
domain, but rather that the use of the domain is a trademark violation.
The facts and circumstances of the ownership of trademark rights and the
trademark infringement are outside of the knowledge of the registrars and
registries. The UDRP procedures are designed to get the facts in front of
the dispute resolution panel to provide the trademark owner with a remedy to
trademark infringement that may be difficult or impossible to obtain
judicially.</DIV>
<DIV> </DIV>
<DIV>The TDRP is about correcting a bad domain transfer, and the circumstances
of the transfer are mostly known to the registrars and registries, but there
might be some oversight that a registrar or a registrant would want
corrected. I think we should focus on where the TDRP leaves a registrant
or a registrar without a remedy, and only provide more procedures for scenarios
where a remedy is not currently available.</DIV>
<DIV
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">____________________________<BR>Kevin
R Erdman<BR>Reichel IP LLP<BR>212 West 10th Street, Suite D-280<BR>Indianapolis,
IN 46202<BR>voice 317.677.0689<BR>fax 317.454.1349<BR>email
kevin@reichelip.com<BR>skype kevimundo<BR>web
www.reichelip.com<BR>--------------------------------------------------------------------------------<BR></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=kdorrain@adrforum.com
href="mailto:kdorrain@adrforum.com">Dorrain, Kristine</A> </DIV>
<DIV><B>Sent:</B> Tuesday, December 03, 2013 12:43 PM</DIV>
<DIV><B>To:</B> <A title=vgreimann@key-systems.net
href="mailto:vgreimann@key-systems.net">'Volker Greimann'</A> ; <A
title=jbladel@godaddy.com href="mailto:jbladel@godaddy.com">James M. Bladel</A>
; <A title=mike@haven2.com href="mailto:mike@haven2.com">Mike O'Connor</A>
</DIV>
<DIV><B>Cc:</B> <A title=gnso-irtpd@icann.org
href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</A> </DIV>
<DIV><B>Subject:</B> RE: [gnso-irtpd] here's the little summary of that sequence
of events i rattled off on the call just now -- registrant role in
TDRP</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'>I
agree.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'><o:p></o:p></SPAN> </P>
<DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>From:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>
Volker Greimann [mailto:vgreimann@key-systems.net] <BR><B>Sent:</B> Tuesday,
December 03, 2013 11:41 AM<BR><B>To:</B> Dorrain, Kristine; James M. Bladel;
Mike O'Connor<BR><B>Cc:</B> gnso-irtpd@icann.org<BR><B>Subject:</B> Re:
[gnso-irtpd] here's the little summary of that sequence of events i rattled off
on the call just now -- registrant role in
TDRP<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p></o:p> </P>
<DIV>
<P class=MsoNormal>The issue of Trademark aside, I see many more similarities
between the UDRP and the issue of legitimate ownership of a domain than between
that issue and the TDRP. After all, both are disputes between parties about who
should be the legitimate owner of a domain name. <BR><BR>So while we may not
want to open the UDRP to new complaints, we may want to look at creating a UDRP2
that is designed for exactly these issues. <BR><BR>In both cases the registrar
is asked to do certain things in preparation for the dispute and as its result,
in both parts the question of the ultimate ownership of a domain name is decided
by an independant panel.<BR><BR>Volker<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'>Just
for the record, I think adding a Registrants option to the UDRP would be just
as mucked up as adding it here. In my humble opinion this warrants an
entirely new policy or none at all. We don’t need to reinvent the
Rules….UDRPs Rules are great. Just create the Policy itself, which is
entirely TM focused and would be a beast to open up to non-TM holders.
</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: wingdings; COLOR: windowtext">J</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'> </SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'>Kristine</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Arial","sans-serif"; COLOR: windowtext'> </SPAN><o:p></o:p></P>
<DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>From:</SPAN></B><SPAN
style='FONT-SIZE: 10pt; FONT-FAMILY: "Tahoma","sans-serif"; COLOR: windowtext'>
<A href="mailto:owner-gnso-irtpd@icann.org">owner-gnso-irtpd@icann.org</A> [<A
href="mailto:owner-gnso-irtpd@icann.org">mailto:owner-gnso-irtpd@icann.org</A>]
<B>On Behalf Of </B>Volker Greimann<BR><B>Sent:</B> Tuesday, December 03, 2013
11:09 AM<BR><B>To:</B> James M. Bladel; Mike O'Connor<BR><B>Cc:</B> <A
href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</A><BR><B>Subject:</B>
Re: [gnso-irtpd] here's the little summary of that sequence of events i
rattled off on the call just now -- registrant role in
TDRP</SPAN><o:p></o:p></P></DIV></DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Hi James,<BR><BR>excellent
points there. I think the case with your example is that this is not actually
a case where a registrar is a party to the dispute. Maybe it is a star witness
required to provide the information only it can provide, but not a party.
Those roles are better left to prior and current registrant. <BR><BR>This
however begs the question if ICANN should implement another process for
registrants to solve their disputes, or if this may not be better relegated to
a future re-design of the UDRP? We could for example make a recommendation
that the UDRP be expanded to cover also domain ownership issues in any future
revision of that
policy.<BR><BR>Best,<BR><BR>Volker<BR><BR><BR><o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<DIV>
<P class=MsoNormal>Good thoughts everyone. I think perhaps we should
try to capture the various scenarios in the “Reasons for Denial” area, where
a registrar can legitimately deny a registrant’s request to initiate a
TDRP.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>For example: if the Registrant believes that the identity
of the registrant is in question, or that they cannot substantiate that they
were ever the legitimate registrant (or Transfer Contact) for the name
pre-transfer. If its a scenario in which the registrar has violated
the IRTP, (or even the shiny new TDRP we’re developing), then that is a
matter for Compliance and the registrar's accreditation could be
at-risk. But we should avoid any process where a registrar is
compelled to initiate a TDRP that they believe is without merit, -and- be
forced to pay for the proceedings.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>Thanks—<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>J.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>From:
</SPAN></B><SPAN
style='FONT-SIZE: 11pt; FONT-FAMILY: "Calibri","sans-serif"'>Mike O'Connor
<<A href="mailto:mike@haven2.com">mike@haven2.com</A>><BR><B>Date:
</B>Tuesday, December 3, 2013 at 10:09 <BR><B>To: </B>Volker Greimann <<A
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</A>><BR><B>Cc:
</B>"<A href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</A>" <<A
href="mailto:gnso-irtpd@icann.org">gnso-irtpd@icann.org</A>><BR><B>Subject:
</B>Re: [gnso-irtpd] here's the little summary of that sequence of events i
rattled off on the call just now -- registrant role in
TDRP</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<DIV>
<P class=MsoNormal>hi Volker, <o:p></o:p></P>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>i'm trying to remedy the situation where a registrar is
either in violation of the IRTP themselves (refusing to allow the registrant
to transfer out) or is presumptively denying the registrant due process in a
dispute between registrars. this was recognized as an oversight in the
policy back in the misty past when this series of IRTP PDPs was
launched.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal>i don't care how this happens. registrars are
probably in the best position to figure out the best way to get this done
and i'm happy to leave that discussion up to them. i like James' "put
pressure on Registrars to comply" approach since that seems like a
lighter/simpler one but i can live with anything that fixes that
problem. what i'm not keen on the idea of leaving registrants in their
current situation where these decisions get made "for them" by registrars
with no recourse for trapped registrants except worldwide
courts.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal>On Dec 3, 2013, at 9:51 AM, Volker Greimann <<A
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</A>>
wrote:<o:p></o:p></P></DIV>
<P class=MsoNormal><BR><BR><BR><o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Hi Mike,<BR><BR>you are
assuming that registrants should be beneficiaries of the TDRP. They are not.
Therefore a registrar not initiating a TDRP is not blocking the registrants
access as they do not have such an access in the first place. <BR><BR>If you
want to give the registrant a way to force a registrar to initiate a
proceeding against another registrar, that is another story, but that way
needs to include an obligation of the registrant to pay the costs and a
right of a registrar to charge for this service (to cover the work needed to
handle the process).<BR><BR>Volker<BR><BR><BR><o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<P class=MsoNormal>i think the key distinction i want to draw is with your
sentence "give registrants access to" the TDRP. that's not the
intent. the intent is to ensure that registrants are not blocked
from that process by their registrar. the hope here is to provide an
appeal mechanism in those cases where registrar and registrant disagree on
whether a TDRP is warranted. but i'm fine setting the bar for that
appeal pretty high. <o:p></o:p></P>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal>On Dec 2, 2013, at 11:47 AM, Volker Greimann <<A
href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</A>>
wrote:<o:p></o:p></P></DIV>
<P class=MsoNormal><BR><BR><BR><o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal>I still feel that giving registrants access to the TDRP
process dilutes its purpose as an inter-registrar dispute process designed
to deal with process violations and will turn it into a transfer dispute
process between registrants, dragging registrars and registries into a
civil conflict between two parties. This will result in increased costs
and work for contracted parties.<BR><BR>If a registrar is violating
transfer processes, there will be sufficient incentive for affected
registrars to call them out and if necessary invoke the current
process.<BR><BR>What we need to look at instead is if creating an
alternate process between registrant and former registrant regarding the
ownership of a domain name makes sense. <BR><BR>I am also a big fan of the
line "He who wants to hear the music should pay for the band!", i.e. if a
registrant wants a process to be invoked, he should be prepared to pony up
the fees, just as with the UDRP. Adding a "loser pays" clause makes sense
to me, but in that case it will remain the risk of the complainant that
the respondent cannot pay/is
unreachable/etc...<BR><BR>Volker<o:p></o:p></P></DIV>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt; MARGIN-TOP: 5pt">
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P>Provide the ability for the registrant to trigger the TDRP process in
cases when they disagree with their registrar over an IRTP issue
<o:p></o:p></P>
<P
style="MARGIN-LEFT: 0.5in; TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: symbol"><SPAN
style="mso-list: ignore">·<SPAN
style='FONT: 7pt "Times New Roman"'>
</SPAN></SPAN></SPAN>In general, registrars initiate TDRP when they
can't resolve matters between themselves <o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in">In the case of disagreement between
registrar and registrant as to whether to initiate a TDRP, provide a
path for the registrant to take the issue to Compliance <o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in">Build minimum documentation requirements
for registrants into the policy as a filter to prevent frivolous filings
<o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in">If Compliance agrees with registrant, TDRP
proceeds as normal, with fees paid by registrars, as normal
<o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in">If Compliance disagrees with registrant,
that's it -- it's off to court if the registrant wants to
proceed.<o:p></o:p></P>
<P style="MARGIN-LEFT: 0.5in"> <o:p></o:p></P>
<DIV>
<P class=MsoNormal
style="MARGIN-LEFT: 0.5in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"> <o:p></o:p></P></DIV>
<P class=MsoNormal><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica","sans-serif"'>PHONE:
651-647-6109, FAX: 866-280-2356, WEB: <A
href="http://www.haven2.com/">www.haven2.com</A>, HANDLE: OConnorStP (ID
for Twitter, Facebook, LinkedIn, etc.)</SPAN> <o:p></o:p></P></DIV>
<P class=MsoNormal> <o:p></o:p></P></BLOCKQUOTE>
<P class=MsoNormal><BR><BR><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">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/">www.key-systems.net</A> / <A href="http://www.rrpproxy.net/">www.RRPproxy.net</A><A href="http://www.domaindiscount24.com/">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><A 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 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 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 href="http://www.key-systems.net/">www.key-systems.net</A> / <A href="http://www.rrpproxy.net/">www.RRPproxy.net</A><A href="http://www.domaindiscount24.com/">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><A 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 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></DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P class=MsoNormal><BR><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica","sans-serif"'>PHONE:
651-647-6109, FAX: 866-280-2356, WEB: <A
href="http://www.haven2.com/">www.haven2.com</A>, HANDLE: OConnorStP (ID
for Twitter, Facebook, LinkedIn, etc.)</SPAN> <o:p></o:p></P></DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV></BLOCKQUOTE>
<P class=MsoNormal><BR><BR><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">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/">www.key-systems.net</A> / <A href="http://www.rrpproxy.net/">www.RRPproxy.net</A><A href="http://www.domaindiscount24.com/">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><A 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 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 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 href="http://www.key-systems.net/">www.key-systems.net</A> / <A href="http://www.rrpproxy.net/">www.RRPproxy.net</A><A href="http://www.domaindiscount24.com/">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><A 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 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></DIV>
<P class=MsoNormal> <o:p></o:p></P>
<DIV>
<P class=MsoNormal><BR><SPAN
style='FONT-SIZE: 9pt; FONT-FAMILY: "Helvetica","sans-serif"'>PHONE:
651-647-6109, FAX: 866-280-2356, WEB: <A
href="http://www.haven2.com">www.haven2.com</A>, HANDLE: OConnorStP (ID for
Twitter, Facebook, LinkedIn, etc.)</SPAN><o:p></o:p></P></DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV></DIV></DIV></BLOCKQUOTE>
<P class=MsoNormal><BR><BR><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">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">www.key-systems.net</A> / <A href="http://www.RRPproxy.net">www.RRPproxy.net</A><o:p></o:p></PRE><PRE><A href="http://www.domaindiscount24.com">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><o:p></o:p></PRE><PRE><A 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 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 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 href="http://www.key-systems.net">www.key-systems.net</A> / <A href="http://www.RRPproxy.net">www.RRPproxy.net</A><o:p></o:p></PRE><PRE><A href="http://www.domaindiscount24.com">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><o:p></o:p></PRE><PRE><A 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 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></BLOCKQUOTE>
<P class=MsoNormal><BR><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">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">www.key-systems.net</A> / <A href="http://www.RRPproxy.net">www.RRPproxy.net</A><o:p></o:p></PRE><PRE><A href="http://www.domaindiscount24.com">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><o:p></o:p></PRE><PRE><A 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 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 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 href="http://www.key-systems.net">www.key-systems.net</A> / <A href="http://www.RRPproxy.net">www.RRPproxy.net</A><o:p></o:p></PRE><PRE><A href="http://www.domaindiscount24.com">www.domaindiscount24.com</A> / <A 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 href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</A><o:p></o:p></PRE><PRE><A 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 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></DIV></DIV></DIV></BODY></HTML>