[gnso-rds-pdp-wg] a suggestion for "purpose in detail"

Thu Mar 23 14:12:37 UTC 2017

Exactly. You offer nothing to this discussion. I have presented whois privacy for free as an option, sourced in a document in the wiki in why that works and soon once my INGO is established I will have the DP authorities tell you directly. 

Sent from my iPhone

> On Mar 23, 2017, at 09:10, Volker Greimann <vgreimann at key-systems.net> wrote:
> 
> Have a read at the supporting documents. You may also want to read the GPDR coming into effect next year and what it has to say about agreement and tying it to the service. I will not restate everything that is already in the basic reading materials.
> 
> 
>> Am 23.03.2017 um 14:40 schrieb John Bambenek via gnso-rds-pdp-wg:
>> And what legal requirements are those?  You're presenting little here.
>> 
>>> On 03/23/2017 04:07 AM, Volker Greimann wrote:
>>> We cannot negotiate on legal requirements. We will not leave the
>>> trenches if doing so will expose us to legal risks. You cannot vote an
>>> illegal practice into legality.
>>> 
>>> Everything else is on the table.
>>> 
>>> 
>>>> Am 22.03.2017 um 17:24 schrieb nathalie coupet via gnso-rds-pdp-wg:
>>>> +1 I must say I'm a bit disillusioned by the entire process. This PDP
>>>> should look like a negotiating table, instead it is more like a War
>>>> of Trenches.
>>>> If stakeholders are not motivated to negotiate, there is no sense of
>>>> urgency and stakes for change are so low, then I wonder what we are
>>>> doing here in the first place.
>>>> Could every stakeholder state what their biggest fear is, and we
>>>> could try to avoid their realization?
>>>> Or maybe, in last resort, we should just vote for the best proposal
>>>> and go home?
>>>> 
>>>> Nathalie
>>>> 
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On Mar 22, 2017, at 12:06 PM, Andrew Sullivan
>>>>> <ajs at anvilwalrusden.com> wrote:
>>>>> 
>>>>>> On Wed, Mar 22, 2017 at 10:19:56AM -0500, John Bambenek wrote:
>>>>>> Yes there is a difference which is why I am using both words. And
>>>>>> that's why I am suggesting we talking about optional and maskable
>>>>>> fields right up front as part of the requirements discussion not
>>>>>> some ancillary discussion that happens later after all the
>>>>>> decisions are already made.
>>>>>> 
>>>>> I thought the WG had already decided on a different (multi-pass)
>>>>> strategy, in which data collection itself was treated first with the
>>>>> principle that, if there were some (legitmate, hand-wave hand-wave)
>>>>> purpose then collection would be considered.  Later, the further
>>>>> question of access to such collected items would be taken up.
>>>>> 
>>>>> I don't really care which way we do this, but it seems to me that we
>>>>> need to stop arguing about the way by which we'll reach a result and
>>>>> start actually doing work in the direction of some result.  The
>>>>> meta-discussions about process are wearing out contributors (well, at
>>>>> least one contributor!) and creating the condition in which those who
>>>>> want no changes at all will get their way by exhaustion.  If ICANN is
>>>>> incapable of coming to terms with the deficiencies of whois (the
>>>>> protocol) after all this time, it will be revealed to be ridiculous.
>>>>> 
>>>>> Best regards,
>>>>> 
>>>>> A
>>>>> 
>>>>> -- 
>>>>> Andrew Sullivan
>>>>> ajs at anvilwalrusden.com
>>>>> _______________________________________________
>>>>> gnso-rds-pdp-wg mailing list
>>>>> gnso-rds-pdp-wg at icann.org
>>>>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>>>> _______________________________________________
>>>> gnso-rds-pdp-wg mailing list
>>>> gnso-rds-pdp-wg at icann.org
>>>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
>> _______________________________________________
>> gnso-rds-pdp-wg mailing list
>> gnso-rds-pdp-wg at icann.org
>> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
> 
> -- 
> 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 at key-systems.net
> 
> 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 at key-systems.net
> 
> 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.
> 
> 
> 
> _______________________________________________
> gnso-rds-pdp-wg mailing list
> gnso-rds-pdp-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg