<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-thickwhoispdp-wg] Revised language for review
- To: Marika Konings <marika.konings@xxxxxxxxx>, "gnso-thickwhoispdp-wg@xxxxxxxxx" <gnso-thickwhoispdp-wg@xxxxxxxxx>
- Subject: Re: [gnso-thickwhoispdp-wg] Revised language for review
- From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Date: Wed, 16 Oct 2013 15:19:20 +0200
I can live with this draft as well.
Volker
Dear All,
Based on our discussions today, please find below the proposed
language for inclusion in the Final Report which includes the edits
proposed in the chat (in bold) in relation to the legal review. Please
share your support/non-support and/or proposed edits with the mailing
list.
Thanks,
Marika
/The WG recommends that as part of the implementation process *a legal
review of law applicable to the transition of data from a thin to
thick model that has not already been considered in the EWG memo is
undertaken and* due consideration is given to potential privacy issues
that may arise from the discussions on the transition from thin to
thick Whois, including, for example, guidance on how the long-standing
contractual requirement that registrars give notice to, and obtain
consent, from each registrant for uses of any personally identifiable
data submitted by the registrant should apply to registrations
involved in the transition. //Should any privacy issues emerge from
these transition discussions that were not anticipated by the WG and
which would require additional policy consideration, the
Implementation Review Team is expected to notify the GNSO Council of
these so that appropriate action can be taken. /
/The WG recommends that following the adoption of this report and
recommendations by the GNSO Council, the subsequent public comment
forum (prior to Board consideration) as well as the notification by
the ICANN Board to the GAC, specifically request input on any
considerations related to the transition from thin to thick Whois that
would need to be taken into account as part of the implementation
process. /
--
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
Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.facebook.com/KeySystems
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
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
Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.facebook.com/KeySystems
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
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.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|