<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
That sounds reasonable. The notice period could be seen as similar
to the suspension period for registrars currently in place where a
registrar is no langer able to accept new registrations or
transfers, but can still serve its existing customers. <br>
<br>
I support the suggested change of moving the notice out of the
breach notice period.<br>
<br>
Volker<br>
<br>
<br>
<div class="moz-cite-prefix">Am 30.11.2015 um 17:38 schrieb Darcy
Southwell:<br>
</div>
<blockquote
cite="mid:D281AD18.666A1%25darcy.southwell@endurance.com"
type="cite">
<div>All,</div>
<div><br>
</div>
<div>I have some concerns about the language contained in
Principle 1 on page 17. It’s certainly important the WG’s
recommendations focus on minimizing any risks of exposing
private customer data during the de-accreditation process.
However, notifying customers “during the breach notice process
(or its equivalent)” seems problematic. This assumes every P/P
provider that receives a breach notice will end up
de-accredited. That’s clearly not the case in the current
registrar breach process, and it’s unlikely to be case with the
P/P providers. Second, there could be significant negative
impact to businesses that receive just one breach notice even
though the breach ends up cured. The focus of the breach
process should not be to penalize every provider that’s ever
done something in violation of the accreditation contract – and
that’s what this approach implies. </div>
<div><br>
</div>
<div>It seems the better approach would be to notify customers
somewhere between the date of the termination notice and the
effective date of the accreditation termination. If we
consider a 30–day period between the termination notice and
termination effective date, there is ample time to notify
customers. </div>
<div><br>
</div>
<div>Look forward to tomorrow’s meeting.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Darcy</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; BORDER-BOTTOM: medium none;
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT:
0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span
style="font-weight:bold">From: </span> <<a
moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a></a>>
on behalf of "Metalitz, Steven" <<a moz-do-not-send="true"
href="mailto:met@msk.com">met@msk.com</a>><br>
<span style="font-weight:bold">Date: </span> Monday, November
23, 2015 at 1:33 PM<br>
<span style="font-weight:bold">To: </span> 'Mary Wong' <<a
moz-do-not-send="true" href="mailto:mary.wong@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:mary.wong@icann.org">mary.wong@icann.org</a></a>>,
"<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span> Re:
[Gnso-ppsai-pdp-wg] Final Report with updated recommendations,
and next steps<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml"
xmlns="http://www.w3.org/TR/REC-html40">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1057244481;
mso-list-template-ids:143947432;}
@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><!--[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 link="blue" vlink="purple" lang="EN-US">
<div class="WordSection1">
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in"><span
style="color:black;mso-fareast-language:EN-US">Thanks
to Mary and her colleagues for generating this final
report text.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in"><span
style="color:black;mso-fareast-language:EN-US">As
noted on last week’s call, unless it seemed necessary
to hold our usual weekly meeting this week (tomorrow),
we would cancel it, in order to give WG members time
to review this text carefully. The call tomorrow has
now been cancelled, and we urge you to use this week
for this review, and for consultation with the
relevant GNSO stakeholder group/constituency, or with
ALAC groups, as appropriate.
<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in"><span
style="color:black;mso-fareast-language:EN-US">The
goal of the review and consultation is to identify any
mistakes or ambiguities in this text that would
interfere with your ability to respond to the
consensus call. We urge WG members to bring any such
issues up on the WG list as soon as possible, which
will help us in fashioning a productive agenda for the
next WG call on Tuesday December 1. We have allocated
90 minutes for this call (beginning at 1430 UTC) to
provide additional time to discuss and resolve any
errors or ambiguities identified. We anticipate that
this will be the final WG call before the close of the
consensus call on Monday, December 7. All
expressions of support for the recommendations of the
Final Report, as well as any separate statements
regarding recommendations that you cannot support,
will be due at that time. Thanks to all for your
continued efforts as we bring this report across the
finish line!
<o:p></o:p></span></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in"><span
style="color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"
style="margin-bottom:12.0pt;text-indent:.5in"><span
style="color:black;mso-fareast-language:EN-US">Steve
Metalitz and Graeme Bunton
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family: Tahoma, sans-serif;">From:</span></b><span
style="font-size: 10pt; font-family: Tahoma,
sans-serif;"> <a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Mary Wong<br>
<b>Sent:</b> Friday, November 20, 2015 5:39 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] Final Report
with updated recommendations, and next steps<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Dear
WG members,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Please
find attached both a clean and marked-up (red-lined)
version of the updated draft Final Report. As the
marked-up version may be somewhat difficult to read
given the number of paragraphs moved around, added
to or deleted, we hope the clean version will be
helpful in providing a straightforward read of the
proposed final form of the WG recommendations while
the mark-up will show where the changes were made
from the draft report that was circulated on 8
October.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">As
noted in the WG Work Plan, circulation of this
updated document opens the period for the WG’s
consensus call. Following this, in accordance with
the GNSO's WG Guidelines, the WG co-chairs will make
a final evaluation of the consensus support levels
and, if necessary, assign specific designations of
such to each individual WG recommendation. Any
minority statements must therefore also be submitted
by that time. As noted in the WG Work Plan, the
co-chairs plan to close the consensus call period by
<b>Monday 7 December 2015</b>. Unless determined
otherwise as a result of this consensus period, the
recommendations are currently marked as Full
Consensus of the WG.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">For
your convenience, the main changes that were made to
the draft report include the following:<o:p></o:p></span></p>
</div>
<ul type="disc">
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">All the
substantive changes can be seen in the Executive
Summary, which retain the format and numbering of
the recommendations from the earlier draft. Most of
the additional WG conclusions based on discussions
subsequent to 8 October were added to existing
numbered recommendations. The relevant portions of
Section V (WG Deliberations) and VII (WG Final
Recommendations) have also been updated to reflect
the substantive changes to the numbered WG
recommendations in the Executive Summary. Most of
the rest of the report, and much of even Sections
and VII, remain unchanged from both the Initial
Report (May 2015) and the draft Final Report.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">The final version
of the Illustrative Disclosure Framework reflecting
the consensus of Sub Team 3 has been incorporated
into the report as Annex B. P<u>lease note that the
final recommendation includes only one option for
dispute resolution, which is jurisdiction over
arbitration, in language discussed by the WG and
finalized by the Sub Team.</u> There is also a
recommendation for a post-implementation review of
the overall framework, followed by periodic reviews
thereafter.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">On transfers, you
will see from the recommendations that language has
been added, in particular to #8 and #21.
<u>The former makes reference to the effect of
IRTP-C, and the latter – in relation to
de-accreditation – adds a specific recommendation
to the effect that a registrar must lift the
otherwise-required lock under IRTP-C if so
requested by the beneficial user of a proxy
registration</u>. This recommendation is based on
the narrower option presented by the Registrar
Services team to the WG following the WG call
earlier this week. We have also retained the
original WG recommendation that the next review of
the IRTP expressly include consideration of the
effect on P/P registrations.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">On
de-accreditation, we have replaced the original
specific individual recommendations with the new set
of three general principles recently reviewed by the
WG.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">On definitions,
we have included those for a Privacy Service and a
Proxy Service in the list of definitions, and added
the most recent version of the new, supplemental
language about registrars not knowingly accepting
registrations from accredited (versus unaccredited)
P/P service providers, and the consequence that an
unaccredited provider effectively therefore has all
the responsibility of a Registered Name Holder.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">On LEA, we have
added language to reflect the WG’s further agreement
in Dublin about “importing” a few critical elements
from the Illustrative Disclosure Framework into a
suggestion that these be included in any future LEA
request framework that may be developed.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">In the general
recommendation section, we have added
recommendations based on the work of Sub Team 3, as
discussed by the WG in Dublin, for an
educational/outreach program and for the periodic
provision of aggregated statistics to ICANN by
providers.<o:p></o:p></span></li>
<li class="MsoNormal"
style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif;">Elsewhere, we
have added or edited language, again based on the
WG’s discussions in Dublin and subsequently, to
flesh out or clarify existing recommendations. Most
of these are indicated with a comment box explaining
where the change came from.<o:p></o:p></span></li>
</ul>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Thanks
to everyone, especially our co-chairs and the
various Sub-Teams, for facilitating our progress
toward a Final Report!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Cheers<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Mary<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Mary
Wong<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Senior
Policy Director<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Internet
Corporation for Assigned Names & Numbers
(ICANN)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Telephone:
+1 603 574 4889<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;">Email:
<a moz-do-not-send="true"
href="mailto:mary.wong@icann.org">mary.wong@icann.org</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 10.5pt;
font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a moz-do-not-send="true"
href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></span>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</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>