<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] - Preliminary Issue Report - New gTLD Subsequent Procedures
Thanks for the clarification.
So the option that Steve originally presented of publishing on 9/3 rather than
8/31 is not in order?
Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell
Twitter: @VlawDC
"Luck is the residue of design" -- Branch Rickey
From: Volker Greimann [mailto:vgreimann@xxxxxxxxxxxxxxx]
Sent: Tuesday, August 25, 2015 1:11 PM
To: Phil Corwin; Austin, Donna; jrobinson@xxxxxxxxxxxx; 'Steve Chan';
council@xxxxxxxxxxxxxx; bret@xxxxxxxxxxxxxxxx
Subject: Re: [council] - Preliminary Issue Report - New gTLD Subsequent
Procedures
Having looked at the PDP manual
(http://gnso.icann.org/en/council/annex-2-pdp-manual-16dec11-en.pdf), Section
6, I can confirm the below is accurate. There is no deliberation step required
or even forseen for the publication of an issues report.
Best regards,
Volker
Am 25.08.2015 um 19:01 schrieb Volker Greimann:
Hi Phil,
Unless I am mistaken, the publication of an issues report that has already been
requested by the Council by ICANN staff is not subject to a deliberation or
decision by the Council. While we may deliberate, this would not impact the
issues report, therefore it is of no consequence. Only after public comments
have been submitted and reviewed the Council has a role to play again in
deciding whether to initiate a PDP. If the report is ready, it should be
published for public comment.
We can therefore use the allotted time to discuss the published issues report
during our meeting but I see no reason whatsoever for delaying the report for
our benefit as our deliberations will not impact this in any way forseen by the
bylaws.
What we can then debate at our meeting is whether an extention of the standard
40 day public comment period is warranted or even required and I am open for
debate on that.
With respect to your question, a month is not in itself problematic, but a
month here and a month there quickly adds up to another year or two. So I am
very much in favor of streamlining the formal process in favor of having a good
PDP effort that may as well take more time than currently expected.
TL;DR: The report should be published; our discussion item will not be affected
either way due to our defined role in the PDP process not being affected by
publication.
Best regards,
Volker
Am 25.08.2015 um 18:42 schrieb Phil Corwin:
Respectfully disagreeing, it is the position of the BC that the comment period
should be initiated immediately following the Council call of September 3rd,
and that the comment period should be for 60 days.
Publication on August 31st will render null and void this item on the proposed
Council agenda for September 3:
Item 4: COUNCIL DISCUSSION & DECISION - Public Comment Period
for New gTLDs Subsequent Procedures Preliminary Issue Report (15 minutes)
At its July 2015 meeting, the GNSO Council approved the staff
request<http://gnso.icann.org/mailing-lists/archives/council/msg17350.html> for
an extension of the deadline for publication of the Preliminary Issue Report on
New gTLDs Subsequent Procedures. The extension was viewed as necessary given
the number of potential topics that had been identified by the New gTLDs
Subsequent Procedures Discussion Group and the need to develop a proposed
framework for handling those topics in a possible PDP. The Council had also
discussed briefly the possible benefits of having an extended public comment
period in view of the community interest in this matter. Here the Council will
discuss the ramifications of extending the public comment period and decide
whether or not to recommend moving forward with the idea.
4.1 - Update and presentation of possible timelines (Steve Chan)
4.2 - Council discussion
4.3 - Council decision and next steps
Publishing for only 40 days will close out the comment period prior to the
Dublin ICANN meeting, at which the community can be more fully informed about
the Preliminary Issue Report.
Really, with the second round at least several years off, what is the rush when
all we are talking about is a one month delay of Council consideration of the
Final Report, when that approval can still be accomplished this calendar year?
Thank you for your consideration.
Best to all, Philip
Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell
Twitter: @VlawDC
"Luck is the residue of design" -- Branch Rickey
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Austin, Donna
Sent: Tuesday, August 25, 2015 12:25 PM
To: Volker Greimann; jrobinson@xxxxxxxxxxxx<mailto:jrobinson@xxxxxxxxxxxx>;
'Steve Chan'; council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>;
bret@xxxxxxxxxxxxxxxx<mailto:bret@xxxxxxxxxxxxxxxx>
Subject: RE: [council] - Preliminary Issue Report - New gTLD Subsequent
Procedures
I support Volker's position.
I would also add, that given the considerable amount of work that was
undertaken by the Discussion Group which largely scoped and informed the Issues
Report, I do not see any reason to extend the comment period by an extra 20
days.
It would appear from Steve's email that if we delay the posting of the Issue
Report by 3 days to 3 September, it removes the possibility of the Council
considering the Final Report on 19 November.
Thanks
Donna
Donna Austin: Neustar, Inc.
Policy and Industry Affairs Manager
Cell: +1.310.890.9655 Email:
donna.austin@xxxxxxxxxxx<mailto:donna.austin@xxxxxxxxxxx>
________________________________
The information contained in this e-mail message is intended only for the use
of the recipient(s) named above and may contain confidential and/or privileged
information. If you are not the intended recipient you have received this
e-mail message in error and any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify me immediately and delete the original message.
Follow Neustar: [cid:image001.png@01CC3CD3.5F595DC0]
Facebook<http://www.facebook.com/neustarinc>
[cid:image002.png@01CC3CD3.5F595DC0]
LinkedIn<http://www.linkedin.com/company/5349>
[cid:image003.png@01CC3CD3.5F595DC0] Twitter<http://www.twitter.com/neustar>
P Please consider the environment before printing this e-mail.
From: owner-council@xxxxxxxxxxxxxx<mailto:owner-council@xxxxxxxxxxxxxx>
[mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Volker Greimann
Sent: Tuesday, 25 August 2015 1:48 AM
To: jrobinson@xxxxxxxxxxxx<mailto:jrobinson@xxxxxxxxxxxx>; 'Steve Chan'
<steve.chan@xxxxxxxxx<mailto:steve.chan@xxxxxxxxx>>;
council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>;
bret@xxxxxxxxxxxxxxxx<mailto:bret@xxxxxxxxxxxxxxxx>
Subject: Re: [council] - Preliminary Issue Report - New gTLD Subsequent
Procedures
Hi Steve,
thank you indeed for the update.
I see no reason to delay the publication, especially since the delay by a few
days will cause us to lose a full month at least.
Given that we can expect delays down the road as this will be a piece of
substantial work, I would favor publication sooner rather than later, with a
standard 40 day comment period.
Best,
Volker
Am 24.08.2015 um 21:38 schrieb Jonathan Robinson:
Steve and GNSO Councillors,
It seems to me that we need to think about a three points here:
1. Do we publish 31st August i.e. ahead of the forthcoming council meeting
and such that we can deal with this at the 19 November meeting as per option 1
below OR
2. Do we publish 3rd September and, if so, does that necessarily mean we
miss dealing with it on 19 November?
3. Regardless of 31 August or 3rd September, do we think that a public
comment period of more than the now standard 40 day period is necessary?
Note: My personal opinion is that it would be OK to publish with a 40 day
comment period and then extend if that was felt to be important / necessary and
that this will not be confusing.
Thoughts / input will be helpful, especially if we are to publish the report by
31 August.
Thanks,
Jonathan
From: Steve Chan [mailto:steve.chan@xxxxxxxxx]
Sent: 18 August 2015 23:26
To: council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>;
bret@xxxxxxxxxxxxxxxx<mailto:bret@xxxxxxxxxxxxxxxx>
Subject: Re: [council] - Preliminary Issue Report - New gTLD Subsequent
Procedures
Bret,
Thanks, great question and hopefully the information below is beneficial to the
Council's consideration of the 3 day hold, as well as the discussion around the
extended public comment period. Regarding next steps and timing, here is the
relevant language from the PDP Manual:
The Staff Manager is responsible for drafting a summary and analysis of the
public comments received on the Issue Report and producing a Final Issue Report
based upon the comments received. The Staff Manager should forward the Final
Issue Report, along with any summary and analysis of the public comments
received, to the Chair of the GNSO Council for consideration for initiation of
a PDP.
The summary and analysis and the Final Issue Report are expected to be
delivered to the Chair of the GNSO Council within 30 days of the closing of the
public comment forum, though the Staff Manager may request an extension of that
30-day time for delivery.
Without knowledge of the level of public comment that will be received, it is
difficult to estimate how long the summary and analysis and Final Issue Report
will take to prepare. However, assuming 30 days, here are the three timelines
expanded to include the next GNSO Council meeting, as long as the document and
motion deadline is met. I would note, these are are the first, and not only,
opportunities for the Council to consider the initiation of a PDP:
* Publish 31 August -> 40 Day Public Comment -> Close 10 October -> 9
November PC Analysis & Final Report -> 9 November Documents & Motions Deadline
-> 19 November GNSO Council Meeting
* Publish 3 September -> 40 Day Public Comment -> Close 13 October -> 12
November PC Analysis & Final Report -> 7 December Documents & Motions Deadline
-> 17 December GNSO Council Meeting
* Publish 3 September -> 60 Day (for instance) Public Comment -> Close 2
November -> 2 December PC Analysis & Final Report -> 7 December Documents &
Motions Deadline -> 17 December GNSO Council Meeting
These are all estimates of course, and in the case of the first bullet,
dependent on everything executing according to plan to be able to precisely hit
the documents & motions deadline. Substantial public comment and substantive
changes to the Final Report could ultimately derail these timelines.
Apologies for the lengthy response, but I hope this answers your questions.
Best,
Steve
From: Bret Fausett <bret@xxxxxxxxxxxxxxxx<mailto:bret@xxxxxxxxxxxxxxxx>>
Date: Tuesday, August 18, 2015 at 2:22 PM
To: Steve Chan <steve.chan@xxxxxxxxx<mailto:steve.chan@xxxxxxxxx>>,
"council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>"
<council@xxxxxxxxxxxxxx<mailto:council@xxxxxxxxxxxxxx>>
Subject: Re: [council] - Preliminary Issue Report - New gTLD Subsequent
Procedures
Thanks Steve. Great news on the progress.
On the timelines, can you remind me what happens after the close of the comment
deadline? How do we get from the close of the public comment period to Day 1 of
the PDP working group? How many Council meetings/votes between close of comment
period and starting the hard policy work?
Bret
On Aug 18, 2015, at 1:26 PM, Steve Chan
<steve.chan@xxxxxxxxx<mailto:steve.chan@xxxxxxxxx>> wrote:
Dear Councilors,
Staff is on track to be able to deliver the Preliminary Issue Report on New
gTLD Subsequent Procedures for public comment by the end of August, as
discussed on the previous GNSO Council meeting. However, I wanted to note that
during the meeting, the possibility of providing for an extended public comment
period was also discussed, which would keep it open through the ICANN54
meeting. This topic is expected to be on the agenda for the next Council
meeting, scheduled for 03 September and as such, it may make sense to delay the
publication of the report by approximately 3 days to allow for discussion
during the meeting and a decision to be made, to avoid confusion from possibly
amending the comment close date. The impact appears to be minimal:
* Publish 31 August -> 40 Day Public Comment -> Close 10 October (note that
this is a Saturday)
* Publish 3 September -> 40 Day Public Comment -> Close 13 October
* Publish 3 September -> 60 Day (for instance) Public Comment -> Close 2
November
Staff is leaning towards waiting the three days and immediately putting in the
request to publish the Preliminary Issue Report after a decision is made, but
wanted to be sure there were no strong objections to this approach.
Best,
Steven Chan
Sr. Policy Manager
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
steve.chan@xxxxxxxxx
<mailto:steve.chan@xxxxxxxxx>
direct: +1.310.301.3886
mobile: +1.310.339.4410
tel: +1.310.301.5800
fax: +1.310.823.8649
--
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web:
www.key-systems.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=NFTUH2gHAgMZwtwHVYO24OeBmtc9MP5tLRtIWtIodCs&e=>
/
www.RRPproxy.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=v-JDchL89R2vFwAEy5yOnnkjKoHSEPNJnCkJPDfRchc&e=>
www.domaindiscount24.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=qiVsBjOKfvG70kx9l0jxUeb6RAiNc7PGuymC2MWT2Io&e=>
/
www.BrandShelter.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=PJKsGm0dygKOdPw6ogTLmmsqcgH-L10CJgRJjvwf06A&e=>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySystems&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=rDVhKmFKZBimibKpU8BllHfceYKH4fhNHSVMOx9nmFc&e=>
www.twitter.com/key_systems<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsystems&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=T9FB1A4yriMDgABiElEyZ_5g7aIxOQBqbJAlcsn44m8&e=>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=GCu1SDFVe0uItA1DjnkAiQ-g67oUN_xOmpTwcYaMJOg&e=>
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web:
www.key-systems.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=NFTUH2gHAgMZwtwHVYO24OeBmtc9MP5tLRtIWtIodCs&e=>
/
www.RRPproxy.net<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=v-JDchL89R2vFwAEy5yOnnkjKoHSEPNJnCkJPDfRchc&e=>
www.domaindiscount24.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=qiVsBjOKfvG70kx9l0jxUeb6RAiNc7PGuymC2MWT2Io&e=>
/
www.BrandShelter.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=PJKsGm0dygKOdPw6ogTLmmsqcgH-L10CJgRJjvwf06A&e=>
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySystems&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=rDVhKmFKZBimibKpU8BllHfceYKH4fhNHSVMOx9nmFc&e=>
www.twitter.com/key_systems<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsystems&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=T9FB1A4yriMDgABiElEyZ_5g7aIxOQBqbJAlcsn44m8&e=>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=AwMD-g&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=h_tMV3s1ezNblZVKti4mGdM7TnPW6hk3UlRURrzpDVw&s=GCu1SDFVe0uItA1DjnkAiQ-g67oUN_xOmpTwcYaMJOg&e=>
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.
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2015.0.6081 / Virus Database: 4401/10465 - Release Date: 08/19/15
--
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
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.
--
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
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: vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>
Web: www.key-systems.net<http://www.key-systems.net> /
www.RRPproxy.net<http://www.RRPproxy.net>
www.domaindiscount24.com<http://www.domaindiscount24.com> /
www.BrandShelter.com<http://www.BrandShelter.com>
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems<http://www.facebook.com/KeySystems>
www.twitter.com/key_systems<http://www.twitter.com/key_systems>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu<http://www.keydrive.lu>
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.
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2015.0.6081 / Virus Database: 4401/10465 - Release Date: 08/19/15
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|