[gnso-rds-pdp-wg] List discussion topics
Chuck Gomes Consulting
consult at cgomes.com
Thu Jul 27 18:02:21 UTC 2017
Paul,
I am not clear on what you are disagreeing with. Are you arguing that
consent is never a problem for non-registrant contacts. Even in cases 1 &
2, consent might still be an issue although it would presumably be much less
of a problem.
Chuck
From: gnso-rds-pdp-wg-bounces at icann.org
[mailto:gnso-rds-pdp-wg-bounces at icann.org] On Behalf Of Paul Keating
Sent: Thursday, July 27, 2017 5:20 AM
To: Volker Greimann <vgreimann at key-systems.net>; gnso-rds-pdp-wg at icann.org
Subject: Re: [gnso-rds-pdp-wg] List discussion topics
Sorry but I disagree.
A tech or admin contact generally fits into one of the following categories:
1. Agent of the registrant (e.g. Hired or retained to serve).
2. Employee of the registrant
3. A non-individual.
As to #1 and 2, the service in the capacity is part of the responsibilities
of the agent/employee. The contact information is the contact information
used by the agent/employee for commercial purposes. In fact it is generally
either the business email address of the non-individual company or of the
registrant. This is not in fact personal information any more than my email
address for my law firm is personal information. If it were otherwise the
world would grind to a halt because no one could use or publish even an
email issued by the agent/employee on behalf of and in his/her capacity as
an agent/employee.
As for #3, non-individual information is not covered by any of the relevant
data protection laws.
Again, lets focus on the data sets and not incorporate )(at this stage)
issues of what level of access should be granted to those sets.
Paul
From: <gnso-rds-pdp-wg-bounces at icann.org
<mailto:gnso-rds-pdp-wg-bounces at icann.org> > on behalf of Volker Greimann
<vgreimann at key-systems.net <mailto:vgreimann at key-systems.net> >
Date: Thursday, July 27, 2017 at 11:51 AM
To: <gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org> >
Subject: Re: [gnso-rds-pdp-wg] List discussion topics
I think consent is one of the most basic problems for the non-registrant
contacts, e.g. tech, admin (and billing in some cases). As the registrar is
(at best) only interacting directly with the registrant, and the other
contacts are not subject to any agreement and/or policy directly, we had to
trust that the registrant (or his agent) had obtained the appropriate
content from the entities listed for those roles.
Clearly, this is no longer sufficient under the new data privacy regime
where consent bust be explicitly given by the data subject.
Abuse would be a new role to consider, however the same basically applies.
I think the descriptions from the EWG are good and sufficient.
Best,
Volker
Am 26.07.2017 um 22:21 schrieb Chuck Gomes Consulting:
In addition to discussion about the topics in this week’s poll, members are
encouraged to also discuss the following on the WG list between now and our
meeting next week:
For admin, technical, abuse, and privacy/proxy roles, all WG members
encouraged to discuss on-list the following questions:
* Are these roles needed?
* How do they differ from each other?
* How might they differ from the registrant?
The following description of these roles, excerpted from the EWG report, may
be helpful in kicking off discussion:
Note: The above contact types (roles) are being discussed first because they
received broad support in our 28 June call poll. The EWG Report defined two
additional contact types (roles) which received less support in our 28 June
call poll; to enable focus on possible common ground, additional contact
types will be discussed separately.
Chuck
_______________________________________________
gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg at icann.org <mailto: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 <mailto:vgreimann at 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
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann at key-systems.net <mailto:vgreimann at 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.
_______________________________________________ gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg at icann.org <mailto:gnso-rds-pdp-wg at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170727/d1f52bf7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 305931 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170727/d1f52bf7/image001-0001.jpg>
More information about the gnso-rds-pdp-wg
mailing list