ICANN ICANN Email List Archives

[gnso-thickwhoispdp-wg]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-thickwhoispdp-wg] Recommendations for a Thick WHOIS new recommendation

  • To: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
  • Subject: Re: [gnso-thickwhoispdp-wg] Recommendations for a Thick WHOIS new recommendation
  • From: Carlton Samuels <carlton.samuels@xxxxxxxxx>
  • Date: Tue, 3 Sep 2013 13:08:52 -0500

FWIW, there is a consistent thread in current EWG discussions that says
ICANN cannot escape developing a privacy policy within the framework of a
set of binding corporate rules.

-Carlton


==============================
Carlton A Samuels
Mobile: 876-818-1799
*Strategy, Planning, Governance, Assessment & Turnaround*
=============================


On Tue, Sep 3, 2013 at 9:00 AM, Volker Greimann
<vgreimann@xxxxxxxxxxxxxxx>wrote:

>
> Hi Avri,
>
> while I agree with the sentiment, I think by including a catch-all such as
> "and other GNSO policies" we would be casting to broad a net. To be more
> effective and specific to the issues at hand, any issues report requested
> by this WG should be narrowly tailored to the issue of potential privacy
> issues with regard to collection, distribution and publication of private
> data for/in the whois.
>
> Volker
>
>
>>
>>
>>
>> Hi,
>>
>> We have moved a lot of privacy issues into a heap called - 'to be worked
>> on later'
>>
>> I recommend that we include the following recommendation to deal with
>> this myriad  of issues:
>>
>> We recommend that the ICANN Board request a GNSO issues report to cover
>> the issue of Privacy as related to WHOIS and other GNSO policies.
>>
>> This recommendation would probably require some glue language in a few
>> other spots in the final report.
>>
>> The reason for requesting that the Board, as opposed to the GNSO, is the
>> number of ICANN staff organizations, such as legal, that need to be folded
>> into any such effort.  It would also give evidence of ICANN's concern about
>> such issues in this time of great privacy anxiety.
>>
>> thanks
>>
>>
>> Avri Doria
>>
>
>
> --
> 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 >>>

Privacy Policy | Terms of Service | Cookies Policy