Dear Team, I am all set for the meeting today. To start the discussion I will reference to the case that was posted on the main mailing listby Ayden "Point in fact, I want to emphasize the key phrase here and the problem, “They were not aware that this data was public.” It isn’t a problem that whois is public, its a problem that the registries spend no effort to educate their consumers about what is done with their data and how to make informed decisions. As someone adequately put it a few weeks ago “we don’t think that’s our job”. The problem here is corporate responsibility. She got a barrage of harassing tweets. Well, Twitter in general doesn’t think civility is their job either so misuse of that service probably wasn’t addressed. The entire internet is made up of layers of providers who believe in some measure that security, anti-abuse, consumer safety et al is not their job. They have outsourced that to people like me and others on this list who largely do it for free when the reality is the “not my job” attitude prevents these problems from being addressed at the most logical layer. Instead it has to be done by me. The problem is and always has been corporate responsibility. And if you think this exact same thing won’t happen in any gated whois model, you are grossly naive. " The Information that is exposed in the whois can cause subsequent damage to the registrant. This takes me to the statement The purpose in this case is that there should be an agreement between the registrant and data handler on which information should be shared during Domain Name registration. Upon successful registration, the information provided should be subjected to authentication from the consumers in this case the Domain owners. The gTLD registration data often involved in this purpose – i.e contact data, I suggest that the specific identity of the data subject (e.g., registrant, tech contact, registrar, etc.) and data element(s) as applicable be subject to authentication before being listed. Whose role is it to educate consumers and are they liable for the listing of the data in the whois? Definitely since they are the owners, I suggest that consent should added on which the registrants agree to the data to be listed publicly. Daniel ᐧ Daniel Nanghaka ALAC Sub-Committee on Outreach and Engagement – Co-chair from AFRALO ISOC Uganda Chapter Tel: +256 772 898298 On 16 October 2017 at 19:18, Susan Kawaguchi <susankpolicy@gmail.com> wrote:
Thanks for responding Volker, really appreciate it. I know this was not the best timing but due to our hard deadline of ICANN 60 we are doing the best we can.
Your advice has been noted.
Susan
On Mon, Oct 16, 2017 at 2:14 AM, Volker Greimann < vgreimann@key-systems.net> wrote:
Hi Susan,
it may be helpful for ensuring timely responses not to send requests for feedback with such tight deadlines after the end of the business day on a Friday for some of the participants.
I have filled in the poll now that I have seen your mail.
Best,
Volker
Am 14.10.2017 um 19:09 schrieb Susan Kawaguchi:
Hello All,
Resending in the hope that all members of this sub team will fill out the doodle poll by the end of today.
Thank you to Andrew and Daniel for completing the doodle poll.
Please also take a look at the template and start brainstorming. Looking forward to finding a time for our first meeting.
Susan ---------- Forwarded message ---------- From: Susan Kawaguchi <susankpolicy@gmail.com> Date: Fri, Oct 13, 2017 at 9:15 AM Subject: Drafting Team #2 – Domain Name Control -and- Individual Internet Use To: gnso-rds-pdp-2@icann.org
Hello All,
Welcome! You have been selected by the RDS leadership team to serve on a drafting team to define the RDS purposes named in the subject line above. Thank you very much for volunteering to participate in this effort.
Here is the list of the team members:
Coordinated by: Susan Kawaguchi
Members: Maxim Alzoba, Volker Greimann, Brian Winterfeldt, Tapani Tarvainen, Alan Greenberg, Daniel Nanghaka, Andrew Sullivan
As you can see, this message is being sent via a dedicated mailing list that has been set up to facilitate email communications over the next two to two and half weeks. Please use the list for all of our electronic team communications. Note that this list is publicly archived. Here are the list details.
Mailing list address: gnso-rds-pdp-2@icann.org Mailing list archive: http://mm.icann.org/pipermail/gnso-rds-pdp-2
Attached you will find a template that outlines our tasks and provides a timeline. Please review it right away so that we can start discussions as soon as possible.
We plan to have at least two teleconference calls over the next two weeks, but additional ones may be scheduled as needed. At the same time, mailing list discussion is encouraged. The first call will be scheduled on Tuesday or Wednesday, October 17 or 18. Please complete the Doodle poll linked below not later than end of day on Saturday, October 14 so that a time can be identified that best meets team member availability.
https://icannorg.doodle.com/poll/ehvh66vvutp83yiu
Teams were formed using results from this week’s poll which can be found on the WG wiki. Every team includes:
· At least one person from each of the perspectives named in the poll wherever possible, but without assigning members to more than one team.
· A mix of members who have direct experience regarding the proposed purpose and those who have little or no experience about the proposed purpose.
Remember that the purpose of this work is not to make decisions but rather to facilitate communication and understanding. The team is expected to deliver a one to two-page document to the full WG that will be used in our face to face meeting on Saturday, October 28 to help all WG members understand the applicable purpose.
If you have any questions, please feel free to ask them on this list.
Thanks in advance for completing the Doodle Poll promptly and for participating in our discussions starting today and in the days ahead.
Susan Kawaguchi Drafting Team Coordinator
_______________________________________________ Gnso-rds-pdp-2 mailing listGnso-rds-pdp-2@icann.orghttps://mm.icann.org/mailman/listinfo/gnso-rds-pdp-2
-- 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 <+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851 <+49%206894%209396851> Email: vgreimann@key-systems.net
Web: www.key-systems.net / www.RRPproxy.netwww.domaindiscount24.com / www.BrandShelter.com
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:www.facebook.com/KeySystemswww.twitter.com/key_systems
Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUPwww.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 <+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851 <+49%206894%209396851> Email: vgreimann@key-systems.net
Web: www.key-systems.net / www.RRPproxy.netwww.domaindiscount24.com / www.BrandShelter.com
Follow us on Twitter or join our fan community on Facebook and stay updated:www.facebook.com/KeySystemswww.twitter.com/key_systems
CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUPwww.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-2 mailing list Gnso-rds-pdp-2@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-2
_______________________________________________ Gnso-rds-pdp-2 mailing list Gnso-rds-pdp-2@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-2