- RDS-WHOIS2-RT - lists.icann.org

RDS-WHOIS2 Review Team Plenary Call #14, 5 January 2018 - 13:30 UTC
by Jean-Baptiste Deroulez Jan. 5, 2018

Jan. 5, 2018

Dear Review Team Members, In preparation for your call #14<https://community.icann.org/display/WHO/Meeting+%2314+-+5+January+2018>, scheduled for tomorrow, Friday 5 January 2018 – 13:30-15:00 UTC, please find below a suggested agenda: 1. Welcome, roll-call, SoI 2. Update on Terms of Reference and Work plan 3. Subgroup status & next steps * Rapporteurs will be asked to address the following: * Status of first pass work plan and target for delivery to full Review Team * How the subgroup will address next steps identified in the work plan * Identify briefings/resources needed * Review, analyze relevant documentation * Conduct investigation of identified objectives * Conduct relevant interviews as appropriate * Draft summary of key findings * Present findings to full Review Team for approval, as input to development of Review Team recommendations 1. Outreach plan 2. GDPR 3. Face-to-Face meeting discussion 4. A.O.B. You should all have received dial-in details to join this call. If not, please contact us off list at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org> and we will make sure to send you a copy. Please feel free to join 20 minutes early to confirm your Adobe Connect and audio connections, if you wish. As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste Deroulez

4 5

RSVP NEEDED + AGENDA: Call #15 - 8 January 2018
by Jean-Baptiste Deroulez Jan. 5, 2018

Jan. 5, 2018

Dear Review Team members, At the leadership request, please advise on your attendance for next Monday’s plenary meeting. Please see below the approved agenda: 1. Welcome, roll-call, SoI 2. Subgroup status & next steps 3. Outreach plan – item 1: “Adopted terms of reference & work plan” 4. GDPR 5. Face-to-Face meeting discussion 6. A.O.B. Rapporteurs will be asked to address the following: 1. Status of first pass work plan and target for delivery to full Review Team 2. How the subgroup will address next steps identified in the work plan * Identify briefings/resources needed * Review, analyze relevant documentation * Conduct investigation of identified objectives * Conduct relevant interviews as appropriate * Draft summary of key findings * Present findings to full Review Team for approval, as input to development of Review Team recommendations Rapporteur are kindly asked to appoint a deputy if unable to join a call. Kind regards, Jean-Baptiste

1 0

Apologies
by Carlton Samuels Jan. 5, 2018

Jan. 5, 2018

Dear All: Please accept my apologies for today's call. I have a 8a doctor's appointment and so will be unavoidably absent. Best, -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* =============================

1 0

Plenary call
by Walden, Thomas L. Jan. 5, 2018

Jan. 5, 2018

I’ve had a family emergency and will be flying to Los Angeles on Friday. Therefore, unfortunately, I will be unable to call in on the teleconference. I apologize for any inconvenience. Sent from my iPhone

1 0

RDS-WHOIS2 Review Team Terms of Reference
by Alan Greenberg Jan. 3, 2018

Jan. 3, 2018

Hi Katrina, Best wishes for the New Year to you. The RDS-WHOIS2-RT Terms of Reference including its scope has been approved by the Review Team and is being considered by the Board Caucus Group supporting the review and presuming no issues raised, it will be forwarded to the Board. The ToR can be found at https://community.icann.org/download/attachments/64084100/Draft%20ToR%20RDS…. Regards, Alan

1 0

REMINDER: January 2, 2018 - Deadline to submit subgroup first pass planning document
by Jean-Baptiste Deroulez Jan. 3, 2018

Jan. 3, 2018

Dear Review Team Members, We would like to kindly remind you that today is the deadline to submit your subgroup first pass planning document (see here<https://community.icann.org/display/WHO/Subgroups?preview=/71604697/7458251…>), as previously agreed on Plenary Meeting #13<https://community.icann.org/display/WHO/Meeting+%252313+-+8+December+2017>. Thank you for completing and returning the final version on your dedicated sub-team list. Many thanks in advance, and best wishes for 2018. Kind regards, Jean-Baptiste PS: See below the list of subgroups, its wiki pages, identified leader/rapporteur (highlighted in bold) and email addresses. Subgroup 1 – WHOIS RT1 Recommendations * Rec #1: Strategic Priority: https://community.icann.org/x/3plEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Carlton, Cathrin, Volker * Email address: rds-whois2-stratpriority(a)icann.org<mailto:rds-whois2-stratpriority@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-stratpriority/ * Rec #2: Single WHOIS Policy: https://community.icann.org/x/4ZlEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Carlton, Cathrin, Thomas * Email address: rds-whois2-whoispolicy(a)icann.org<mailto:rds-whois2-whoispolicy@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-whoispolicy/ * Rec #3: Outreach: https://community.icann.org/x/5JlEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Carlton, Erika * Email address: rds-whois2-outreach(a)icann.org<mailto:rds-whois2-outreach@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-outreach/ * Rec #4: Compliance: https://community.icann.org/x/55lEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Erika, Susan, Thomas * Email address: rds-whois2-rec4-compliance(a)icann.org<mailto:rds-whois2-rec4-compliance@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/ * Rec #5-9: Data Accuracy: https://community.icann.org/x/6plEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Cathrin, Dmitry, Lili * Email address: rds-whois2-dataaccuracy(a)icann.org<mailto:rds-whois2-dataaccuracy@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-dataaccuracy/ * Rec #10: Privacy/Proxy Services: https://community.icann.org/x/7ZlEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Cathrin, Stephanie, Susan, Volker. * Email address: rds-whois2-privacy-proxy(a)icann.org<mailto:rds-whois2-privacy-proxy@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-privacy-proxy/ * Rec #11: Common Interface: https://community.icann.org/x/8JlEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Susan, Volker * Email address: rds-whois2-comminterface(a)icann.org<mailto:rds-whois2-comminterface@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-comminterface/ * Rec #12-14: IDNs: https://community.icann.org/x/85lEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Dmitry, Lili * Email address: rds-whois2-idns(a)icann.org<mailto:rds-whois2-idns@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-idns/ * Rec #15-16: Plan & Annual Reports: https://community.icann.org/x/9plEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Chris, Lili * Email address: rds-whois2-reports(a)icann.org<mailto:rds-whois2-reports@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-reports/ Subgroup 2 – Anything New: https://community.icann.org/x/_5lEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Stephanie, Susan * Email address: rds-whois2-anythingnew(a)icann.org<mailto:rds-whois2-anythingnew@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-anythingnew/ Subgroup 3 – Law Enforcement Needs: https://community.icann.org/x/-plEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Cathrin, Chris, Thomas * Email address: rds-whois2-lawenforcement(a)icann.org<mailto:rds-whois2-lawenforcement@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-lawenforcement/ Subgroup 4 – Consumer Trust: https://community.icann.org/x/AZpEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Dmitry, Erika, Stephanie, Susan * Email address: rds-whois2-consumertrust(a)icann.org<mailto:rds-whois2-consumertrust@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-consumertrust/ Subgroup 5 – Safeguard Registrant Data: https://community.icann.org/x/BJpEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Alan, Dmitry, Stephanie, Volker * Email address: rds-whois2-safeguard(a)icann.org<mailto:rds-whois2-safeguard@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-safeguard/ Subgroup 6 – Compliance: https://community.icann.org/x/B5pEB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> * Members: Carlton, Chris, Erika, Susan * Email address: rds-whois2-compliance(a)icann.org<mailto:rds-whois2-compliance@icann.org> * Email archive: http://mm.icann.org/pipermail/rds-whois2-compliance/

4 7

Inventory of New and Changes Made to WHOIS Policies and Procedures Since the First WHOIS Review Team Completed Its Work in 2012
by Jean-Baptiste Deroulez Dec. 19, 2017

Dec. 19, 2017

Dear Review Team members, As per action item identified on plenary call #10<https://community.icann.org/display/WHO/Meeting+%2310+-+12+October+2017>, the Review Team had asked ICANN org to provide an inventory of new and changes made to WHOIS policies and procedures since the first WHOIS Review Team completed its work in 2012. Per your request, please find the inventory in the document attached. Thank you for letting us know any questions or comments you may have. Kind regards, Jean-Baptiste

1 0

Consensus Call: Terms of Reference and Work Plan
by Alan Greenberg Dec. 12, 2017

Dec. 12, 2017

The Terms of Reference (ToR) and Work Plan were scheduled to be approved at the plenary meeting scheduled for 27 November 2017. Since that meeting was cancelled due to the number of RT Members who could not attend, the approval was deferred until the meeting scheduled for next Monday. As there are no other items for that meeting's agenda, the approval will be done via e-mail. The current version of the Terms of Reference are attached to this message, and the current Work Plan can be found at https://community.icann.org/display/WHO/Work+Plan. With this message I am initiating a Consensus Call to approve the Terms of Reference and Work Plan, subject to final cosmetic editing and revision to account for the schedule changes made during the meeting today (approval of these documents and completion of templates). This Consensus Call will end at 23:59 UTC on Tuesday, 12 December 2017. If there are non-substantive errors please identify them and they will be corrected. If you do not believe that the documents should not be approved due to the need for a substantive error, please identify the issue and if necessary, the document will be revised and this Consensus Call restarted. Although messages indicating support are welcome, they are not necessary. This Consensus Call will be deemed to have succeeded in the absence of significant opposition (greater than 20% as specified by Section IV of the ToR). Alan

4 4

RDS-WHOIS2 Review Team Plenary Call #13 8 December 2017 - 13:30 UTC
by Jean-Baptiste Deroulez Dec. 8, 2017

Dec. 8, 2017

Dear Review Team Members, In preparation for your call #13<https://community.icann.org/display/WHO/Meeting+%2313+-+8+December+2017>, scheduled for today, Friday 8 December – 13:30-15:00 UTC, please find below a suggested agenda: 1. Welcome, roll-call, SoI updates 2. Terms of Reference and work plan 3. Subgroup kick-off & next steps 4. ICANN61 Scheduling 5. A.O.B. Regarding item 4. ICANN61 Scheduling, RDS-WHOIS2 leaders would like to invite you to have a look at your agendas prior to the call and confirm whether you would be available for a face-to-face meeting at the following dates: * March 8 & 9 2018 (Wednesday, Thursday) * March 16 & 17 2018 (Friday, Saturday) You should all have received dial-in details to join this call. If not, please contact us off list at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org> and we will make sure to send you a copy. Please feel free to join 20 minutes early to confirm your Adobe Connect and audio connections, if you wish. As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste Deroulez

1 1

(no subject)
by Cathrin.BAUER-BULST＠ec.europa.eu Dec. 8, 2017

Dec. 8, 2017

Here is the proposed ECO data flows model. Von: Lars Steffen <lars.steffen(a)eco.de<mailto:lars.steffen@eco.de>> Betreff: Register now for 11 Dec 2017, Bruxelles ??? GDPR Domain Industry Playbook ??? Public Consultation Datum: 24. November 2017 um 10:49:49 MEZ An: "domains(a)lists.eco.de<mailto:domains@lists.eco.de>" <domains(a)lists.eco.de<mailto:domains@lists.eco.de>> Register now! GDPR Domain Industry Playbook - Public Consultation Date: December 11, 2017, 10.00 - 17.00 Brussels time (9.00 - 16.00 UTC) Venue: Representation of Lower Saxony to the European Union, Rue Montoyer 61, B-1000 Bruxelles Remote participation will be offered upon request. Please send an email to: lars.steffen(a)eco.de<mailto:lars.steffen@eco.de> Registration: https://web.eco.de/event/gdpr-domain-industry-playbook-public-consultation/ Eco Association of the Internet Industry invites interested parties to a public consultation on the GDPR Domain Industry Playbook. Dear all, As announced at ICANN60 in Abu Dhabi, eco has commissioned Fieldfisher (Germany) LLP, Hamburg, and Rickert Rechtsanwaltsgesellschaft mbH, Bonn, to work on a data model for the domain industry for generic domain names. The paper is currently being written based on consultations with contracted parties, legal assessments, policy work conducted by the ICANN community and the use case matrix published by ICANN based on a public consultation (see https://www.icann.org/news/blog/data-protection-and-privacy-progress-update…) The proposed data model takes a holistic view at all data elements that contracted parties, i.e. registries and registrars are required to process based on ICANN???s contracts and policies. Further, it covers what data may be collected, transferred or otherwise processed and how data can be disclosed to requesting parties. Thus, it does not only speak to the ???Whois??? issue, but to data processing as such. eco plans to publish the paper for review approximately 5 days before the consultation takes place. The paper will be presented by Attorneys at Law Oliver S??me and Thomas Rickert and then the participants will be invited to comment and discuss the proposal. Subsequently, the paper shall be finalized based on the comment received and it shall serve as a proposal to be presented to ICANN so that contracted parties implementing the model will not be sanctioned by ICANN for noncompliance with the existing contracts, seehttps://www.icann.org/resources/pages/contractual-compliance-statement-2…. We are looking forward to seeing you in Brussels! Kind regards, Thomas & Lars From: RDS-WHOIS2-RT [mailto:rds-whois2-rt-bounces@icann.org] On Behalf Of Erika Mann Sent: Thursday, December 07, 2017 12:58 PM To: Volker Greimann Cc: RDS WHOIS2-RT List Subject: Re: [RDS-WHOIS2-RT] Public WHOIS After May 2018 Indeed, nothing new is mentioned in the letter, we discussed these points few years ago already when I was a member the board. Unfortunately nothing happened then. I'm not getting involved in the legal aspects mentioned in the letter because it's simply too late to quarrel with the Art 29 WP and since this debate is already a public one, one has to live unfortunately with certain consequences. I will send you nonetheless an overview I prepared for larger corporations from a major third country. Kind regards, Erika On Thu, Dec 7, 2017 at 10:06 AM, Volker Greimann <vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>> wrote: This just came in: https://www.icann.org/en/system/files/correspondence/falque-pierrotin-to-ch… The Article 29 WP wrote ICANN again, reiterating their position against public whois very clearly. As the WP is made up of the DPAs that would actually enforce the GDPR, the letter cannot be understood in any other way as than a warning to ICANN and by extention its contracted parties to make sure everything is compliant by May 25 next year. They also go out of their way to clarify why they do not agree with any of the many reasons usually given how public whois could be legal processing after all. Even though the letter does not contain anything new to those that have paid any attention in the past ten years, it it unprecedented in its clarity. Best, Volker Am 06.12.2017 um 11:28 schrieb Erika Mann: Volker, hi - yes, that's correct. A given consent can be withdrawn. Nonetheless the legitimate interest based clauses remain (processing data lawfully) remain intact, in particular in relation to data between business entities. I spoke few days ago to Butterelli who's the head of the European Data Protection Supervisor and he said that he's expecting that remaining guidelines from the entity he's overseeing will be issued in February 2018. Many things will become clearer then. Keep in mind the GDPR is a messy law, insofar as many legal interpretations were not included in the law but need further explanations (guidelines). One needs to keep in mind as well that the ECJ will allow national interpretations that go beyond the GDPR, in particular in consumer right areas. It's a messy process. I'm finalizing by the end of next week a short overview about all the aspects one needs to consider. Happy to share this with this group. This overview is done for companies based outside the EU in a major third country. Cheers, Erika On Wed, Dec 6, 2017 at 11:12 AM, Volker Greimann <vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net>> wrote: Hi Erika, interesting, but I do not see how to construct voluntary, freely given consentin this context. Sure, we can ask registrants to give consent, but they must be free to refuse it or withdraw it at a later time without consequence to their registration request. Best, Volker Am 06.12.2017 um 11:10 schrieb Erika Mann: Not even fully accurate. One can continue to publish core data based on legitimate interest grounds and with an explicit consent declaration. I think people are not really understanding the GDPR well. Erika On Tue, Dec 5, 2017 at 6:59 PM, Carlton Samuels <carlton.samuels(a)gmail.com<mailto:carlton.samuels@gmail.com>> wrote: ..this fella says he's only reporting what TUCOWS say a public whois record would resemble come GDPR implementation next year. https://domainnamewire.com/2017/12/05/wow-public-whois-look-like-2018/ -Carlton ============================== Carlton A Samuels Mobile: 876-818-1799<tel:%28876%29%20818-1799> Strategy, Planning, Governance, Assessment & Turnaround ============================= _______________________________________________ RDS-WHOIS2-RT mailing list RDS-WHOIS2-RT(a)icann.org<mailto:RDS-WHOIS2-RT@icann.org> https://mm.icann.org/mailman/listinfo/rds-whois2-rt _______________________________________________ RDS-WHOIS2-RT mailing list RDS-WHOIS2-RT(a)icann.org<mailto:RDS-WHOIS2-RT@icann.org> https://mm.icann.org/mailman/listinfo/rds-whois2-rt -- 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<tel:+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851<tel:+49%206894%209396851> Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> 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<tel:+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851<tel:+49%206894%209396851> Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> 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. _______________________________________________ RDS-WHOIS2-RT mailing list RDS-WHOIS2-RT(a)icann.org<mailto:RDS-WHOIS2-RT@icann.org> https://mm.icann.org/mailman/listinfo/rds-whois2-rt -- 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<tel:+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851<tel:+49%206894%209396851> Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> 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<tel:+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851<tel:+49%206894%209396851> Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> 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.

2 1