Re: [gnso-thickwhoispdp-wg] new pictures

[Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>]

I think by hacking we should rather focus on the potential for 
unauthorized modifications of the registration database then on 
unauthorized access. I am not worried about the access part unless whois 
becomes less public in the future.
Volker

> Don,
>
> > 1) data loss through hack or inadvertent disclosure
>
> Could you define "inadvertent disclosure" when the data is *always* 
> available globally via :43 and :80 not to mention in bulk?
> I have a difficultly understanding how this data is "hackable" when 
> its freely available. Finally, how could "data loss" be a factor as 
> the data effectively is published. How could it possibly become lost 
> or hacked. I can't seem to think of an example of either, could you 
> provide one of each?
> thanks,
>
> -rick
>
>
> On Sun, Feb 10, 2013 at 6:22 PM, Don Blumenthal <dblumenthal@xxxxxxx 
> <mailto:dblumenthal@xxxxxxx>> wrote:
>     Rick,
>
>     I don't agree that we can ignore a discussion of the possibility
>     of data
>     losses, although we don't need to go into depth on analyzing security
>     measures.
>
>     The legal details are TBD as the data protection group gets to work.
>
>     Don
>
>     On 2/10/13 9:10 PM, "Rick Wesson" <rick@xxxxxxxxxxxxxxxxxxxxxxxx
>     <mailto:rick@xxxxxxxxxxxxxxxxxxxxxxxx>> wrote:
>
>     >Don,
>     >
>     >
>     >> The question for me basically is:
>     >>
>     >> Does requiring a move from a thin to a thick registry raise issues
>     >>concerning 1) data loss through hack or inadvertent disclosure or 2)
>     >>clashes with data protection laws? Both questions need to be
>     considered
>     >>during transfer and when the data is in the registry's Whois.
>     >
>     >In the hopes of keeping this all on track could you enumerate how
>     >these relate to the charter? data -loss though hacking does not
>     appear
>     >to be within our remit. Data protection lwas is as broad as there are
>     >geo-political regions. could you tighten up your constraints and
>     >provide concrete examples of both the laws, country of origin,
>     >implications, and matrix that into a graphic our chair might grok.
>     >
>     >starting timer....
>     >
>     >thanks,
>     >
>     >-rick

--
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.