October 2018 - CPWG - lists.icann.org

Fwd: [Policy] Chatham House publish a comment by Emily Taylor on WHOIS and GDPR
by Olivier MJ Crépin-Leblond Oct. 21, 2018

Oct. 21, 2018

FYI - Emily Taylor is a participant in the EPDP. -------- Forwarded Message -------- Subject: [Policy] Chatham House publish a comment by Emily Taylor on WHOIS and GDPR Date: Sat, 20 Oct 2018 09:08:59 +0100 From: Christian de Larrinaga <cdel(a)firsthand.net> Reply-To: cdel(a)firsthand.net To: policy(a)isoc-e.org <policy(a)isoc-e.org> https://www.chathamhouse.org/expert/comment/why-public-directory-domain-nam… -- Christian de Larrinaga _______________________________________________ Policy mailing list Policy(a)lists.isoc-e.org http://lists.isoc-e.org/cgi-bin/mailman/listinfo/policy

4 6

Fwd: [Gnso-epdp-team] Subscribe to EPDP Weekly Update
by Olivier MJ Crépin-Leblond Oct. 18, 2018

Oct. 18, 2018

FYI -------- Forwarded Message -------- Subject: [Gnso-epdp-team] Subscribe to EPDP Weekly Update Date: Tue, 25 Sep 2018 09:20:24 -0400 (EDT) From: Ariel Liang <ariel.liang(a)icann.org> Reply-To: ariel.liang(a)icann.org To: gnso-epdp-team(a)icann.org Don't miss the weekly update in a new format Subscribe to EPDP Weekly Update Dear all: Staff is pleased to inform you that you can now receive a weekly update on the GNSO Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. This is the same weekly update that Rafik Dammak, the GNSO Council Liaison to the EPDP team, provides to the GNSO Council. The EPDP Council weekly update is available through subscription in a newsletter format. If you would like to receive this weekly update, please click the link below to subscribe. If you choose to subscribe, this will give ICANN org permission to send the weekly update to your email address. It also provides ICANN org with an accurate list of subscribers to this newsletter. If you choose to subscribe, you agree to the following statement: "By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…>, and agree to abide by the website Terms of Service <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…>." We please ask that you subscribe by 08 October 2018to begin receiving the updates right away. If you do not wish to receive a weekly update about the EPDP Team, no action from you is needed. All editions of the EPDP weekly update will continue being archived on the wiki <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…>and website <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…>. Click Here to Subscribe to EPDP Weekly Update <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…> If you cannot access the subscription form, please contact ariel.liang(a)icann.org <mailto:ariel.liang@icann.org>to request assistance. We are always exploring ways to improve and make it easier for our community to remain informed. Best Regards, ICANN Policy Staff Follow the GNSO on Twitter Twitter ‌ <http://r20.rs6.net/tn.jsp?f=001ExJbwcyLM3hWsShIDtcPYT_cB523jzwDDUz7jt_J8tJi…> ICANN| 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe gnso-epdp-team(a)icann.org <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> | About our service provider <http://www.constantcontact.com/legal/service-provider?cc=about-service-prov…> Sent by ariel.liang(a)icann.org <mailto:ariel.liang@icann.org> in collaboration with Trusted Email from Constant Contact - Try it FREE today. <http://www.constantcontact.com/index.jsp?cc=nge> Try it free today <http://www.constantcontact.com/index.jsp?cc=nge>

2 1

Fwd: Read the EPDP Update - Week of 8 October
by Marita Moll Oct. 18, 2018

Oct. 18, 2018

Forwarding from the NCUC list. More info on EPDP meetings. I am not sure why such updates aren't coming through At-large lists. Marita Begin forwarded message: > > *From: *ICANN Policy Staff <policy-staff(a)icann.org > <mailto:policy-staff@icann.org>> > *Subject: **Read the EPDP Update - Week of 8 October* > *Date: *16 October 2018 at 22:02:21 GMT+2 > *To: *farell(a)benin2point0.org <mailto:farell@benin2point0.org> > *Reply-To: *policy-staff(a)icann.org <mailto:policy-staff@icann.org> > > EPDP on the Temporary Specification for > gTLD Registration Data > Update for Week of 8 October 2018 > > > > > WHAT HAPPENED THIS WEEK? > > Overview > > * The Team continued working through thedata elements workbooks > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…>; > this week, we focused on: > * Purpose A: Establish the rights of a Registered Name Holder in a > Registered Name and ensuring that the Registered Name Holder may > exercise its rights in respect of the Registered Name; and > * Purpose B: Facilitate lawful access for legitimate 3rd party > interests to data that is already collected and identified herein. > * During the course of the discussion on the transfer of data from > registrar to registry, the Team noted the Purpose A language > required more clarity; specifically, what rights does a registrant > have in a name? To facilitate further discussion on this question, > a small group of volunteers worked together on updated draft text > for Purpose A. > * During the course of the discussion on Purpose B, the Team > identified a disconnect between the processing activity and the > purpose. A small group of volunteers led by Benedict Addis > volunteered to propose new language in response to the issues > identified by the Team. > * To continue the progress form the Team’s F2F meeting, the Team > agreed to work in small groups to cover additional topics/charter > questions that needed to be addressed prior to Barcelona. > > Charter Questions > > * The EPDP Team specifically proposed to address the transfer of > registration data from registrars to registries in an effort to > answer the following Charter questions: > * c1) What data should registrars be required to transfer to the > registry? > * c2) What data is required to fulfill the purpose of a registry > registering and resolving a domain name? > * c3) What data is transferred to the registry because it is > necessary to deliver the service of fulfilling a domain > registration versus other legitimate purposes as outlined in part > (a) above? > * c4) Is there a legal reason why registrars should not be required > to transfer data to the registries, in accordance with previous > consensus policy on this point? > * c5) Should registries have the option to require contact data or not? > * c6) Is there a valid purpose for the registrant contact data to be > transferred to the registry, or should it continue to reside at > the registrar? > > > * Subteam 1 met again to discuss the following Charter questions: > * h) Applicability of Data Processing Requirements > * h3) Should Contracted Parties be allowed or required to treat > legal and natural persons differently, and what mechanism is > needed to ensure reliable determination of status? > * h4) Is there a legal basis for Contracted Parties to treat legal > and natural persons differently? > * h5) What are the risks associated with differentiation of > registrant status as legal or natural persons across multiple > jurisdictions? (See EDPB letter of 5 July 2018). > > > * Subteam 3 met to discuss the following Charter questions: > * j) Temporary Specification and Reasonable Access > * j1) Should existing requirements in the Temporary Specification > remain in place until a model for access is finalized? > * j2) Can the obligation to provide “reasonable access” be further > clarified and/or better defined through the implementation of a > community-wide model for access or similar framework which takes > into account at least the following elements: > * What outside parties / classes of outside parties, and types of > uses of non-public Registration Data by such parties, fall within > legitimate purposes and legal basis for such use? > * Should such outside parties / classes of outside parties be vetted > by ICANN in some manner and if so, how? > * If the parties should not be vetted by ICANN, who should vet such > parties? > * f) Publication of data by registrar/registry: > * f2) Should standardized requirements on registrant contact > mechanism be developed? > * f3) Under what circumstances should third parties be permitted to > contact the registrant, and how should contact be facilitated in > those circumstances? > > Risk > > The EPDP team is going to continue its work on the data elements > workbooks, outstanding items and responses to charter questions in > Barcelona for the F2F meeting. The progress to be made during ICANN63 > will impact the timeline for initial report drafting and delivery for > public comments. The EPDP leadership team is working for the plan > toward the delivery of initial report and afterwards. > > > > > WHAT IS ON NEXT WEEK'S AGENDA? > > The Team will prepare for its meetings at ICANN63. The EPDP Team is > organizing four face-to-face meetings at ICANN63: > (1) 08:30 – 18:30 local time on Saturday, 20 October 2018; > (2) 17:00 – 18:30 local time on Sunday, 21 October 2018; > (3) 17:00-18:30 local time on Wednesday, 24 October 2018; and > (4) 08:30-10:15 local time on Thursday, 25 October. > > Additionally, there is an EPDP high interest topic meeting from > 15:15-16:45 local time on Monday, 22 October 2018. The EPDP Team plans > to provide an update on the Initial Report and preview proposed > recommendations with the community. The Initial Report is expected to > be published after ICANN63. > > > > > STATUS REPORT > > RED > Serious Delay/Issues > > > AMBER > Manageable Delay/Issues > > > GREEN > No Delay/Issues > > Meeting # > & Date > > > Topic 1 > > > Topic 2 > > > Planned Deliverable(s) > > > Status > > (#1) 1-Aug > > > Orientation, Background, Operating Mode > > > ‌ > > > ‌ > > > COMPLETE > > (#2) 7-Aug > > > Temp Sepc Triage - Part 1 > > > ‌ > > > ‌ > > > COMPLETE > > (#3) 9-Aug > > > Temp Sepc Triage - Part 1 > > > ‌ > > > ‌ > > > COMPLETE > > (#4) 14-Aug > > > Temp Sepc Triage - Part 2 > > > ‌ > > > ‌ > > > COMPLETE > > (#5) 16-Aug > > > Temp Sepc Triage - Part 3 > > > ‌ > > > ‌ > > > COMPLETE > > (#6) 21-Aug > > > Temp Sepc Triage - Part 4 > > > ‌ > > > ‌ > > > COMPLETE > > (#7) 28-Aug > > > Proposed Approach to Deliberations > > > ‌ > > > ‌ > > > COMPLETE > > (#8) 28-Aug > > > Section 4.4 - Purposes for processing > > > Triage report*; Appendix D, E, G - URS, UDRP, Transfers* > > > ‌ > > > COMPLETE > > (#9) 30-Aug > > > Section 4.4 - Purposes for processing > > > Appendix C - Data Processing Requirements - Activity & Role Chart > > > ‌ > > > COMPLETE > > (#10) 4-Sep > > > Section 4.4 - Purposes for processing > > > Appendix C - Data Processing Requirements - Activity & Role Chart > > > Triage Report > *submitted to the Council on 13 Sep > > > COMPLETE > > (#11) 6-Sep > > > Appendix C.3 - Processor Requirements > > > Appendix C - Data Processing Requirements - Activity & Role Chart > > > ‌ > > > COMPLETE > > (#12) 11-Sep > > > Appendix C.3 - Processor Requirements > > > Appendix A 2.1 & 3.0 - European Economic Area > > > Redline 4.4 -deliverable terminated > > > COMPLETE > > (#13) 13-Sep > > > Appendix A 2.2-2.4 - Redacted data set* > > > Appendix A 2.1 & 3.0 - European Economic Area > > > Data Elements Survey to be used during F2F meeting -deliverable terminated > > > COMPLETE > > (#14) 18-Sep > > > Appendix A 2.2-2.4 - Redacted data set* > > > Sections 5,6,7 Registry / Registrar Requirements > > > Redline Appendix C- deliverable terminated > > > COMPLETE > > (#15) 20-Sep > > > Section 7.2 Consent > > > Sections 5,6,7 Registry / Registrar Requirements > > > Redline Appendix A 2.1, 2.2-2.4, 3.0 -deliverable terminated > > > COMPLETE > > (#16) 24-Sep > > > LA - Roadmap, Purposes, Data Elements for Processing > > > ‌ > > > ‌ > > > COMPLETE > > (#17) 25-Sep > > > LA - Roadmap, Purposes, Data Elements for Processing > > > ‌ > > > Short list of ICANN purposes > > > COMPLETE > > (#18) 26-Sep > > > LA - Roadmap, Purposes, Data Elements for Processing > > > ‌ > > > Data elements matrix per discussed ICANN purposes > > > COMPLETE > > (#19) 2-Oct > > > Legal Basis for Purposes and related processing activities > > > Review Data Elements Workbook C > > > Next version of Workbook C > > > COMPLETE > > (#20) 4-Oct > > > Review Data Elements Workbook F - Compliance > > > Review Data Elements Workbook N - Ry Eligibility Requirements > > > Next versions of Workbooks F, N > > > COMPLETE > > (#21) 9-Oct > > > Review Data Elements Workbook A - Rt Rights > > > Review Data Elements Workbook M & N > > > Next versions of Workbooks A, M, N > > > COMPLETE > > (#22) 11-Oct > > > Review Data Elements Workbook B - lawful disclosure > > > Prepare for ICANN meeting > > > Next versions of Workbook B > > > COMPLETE > > (#23) 16-Oct > > > Prepare for ICANN meeting > > > ‌ > > > - ICANN63 meeting materials > - ICANN Purposes and lawful basis > - Data Elements Workbooks > > > ‌ > > (#24) 20-Oct > > > ICANN63 Barcelona - EPDP Team > > > ‌ > > > ‌ > > > ‌ > > (#25) 21-Oct > > > ICANN63 Barcelona - HIT > > > ‌ > > > ‌ > > > ‌ > > (#26) 24-Oct > > > ICANN63 Barcelona - EPDP Team > > > ‌ > > > ‌ > > > ‌ > > (#27) 25-Oct > > > ICANN63 Barcelona - EPDP Team > > > ‌ > > > TBD > > > ‌ > > (#28) 1-Nov > > > TBD > > > ‌ > > > TBD > > > ‌ > > (--) 5-Nov > > > Publish Initial Report & Public Comment > > > ‌ > > > Initial Report > > > ‌ > > (--) 5-Nov > > > Publish Initial Report > > > ‌ > > > ‌ > > > ‌ > > (--) 17-Dec > > > Public comment forum on the Initial Report > > > ‌ > > > Public Comment Period launch > > > ‌ > > > > > BUDGET FACT SHEET > > The Budget Fact Sheet is a summary document of the EPDP that > highlights meeting activity, status, milestone achievement, and most > importantly financial resources. Unique to the Fact Sheet are details > of available budget versus actual spend. The Fact Sheet will be > published shortly after the close of the prior month. Read the Budget > Fact Sheethere > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…>. > > > > More Information > > * Workspace Wiki > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…> > * Charter > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…> > * Timeline/Work Plan/Project Plan/Budget Fact Sheet > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…> > * GNSO Website > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…> > > > If you would like to follow this effort as an observer, please email > theGNSO Secretariat <mailto:gnso-secs@icann.org> > > Follow the GNSO on Twitter > > Twitter‌ > <http://r20.rs6.net/tn.jsp?f=0017fmDtgLzrOhw-qOnvSMiIT587krsbjdaUrx10NOAy5v8…> > > > ICANN|12025 Waterfront Drive,Suite 300,Los Angeles, CA 90094-2536 > Unsubscribe farell(a)benin2point0.org > <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> > > Update Profile > <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…>|About > our service provider > <http://www.constantcontact.com/legal/service-provider?cc=about-service-prov…> > > Sent bypolicy-staff(a)icann.org <mailto:policy-staff@icann.org>in > collaboration with > > Trusted Email from Constant Contact - Try it FREE today. > <http://www.constantcontact.com/index.jsp?cc=nge> > Try it free today <http://www.constantcontact.com/index.jsp?cc=nge> >

4 3

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 17 October 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Oct. 18, 2018

Oct. 18, 2018

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number. Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 17 October 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/y7l65hjg The agenda and call details can be found at: https://community.icann.org/x/Nw28BQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: http://adigo.com/icann/ At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

3 2

Re: [CPWG] [registration-issues-wg] [GTLD-WG] Urgent EPDP question
by Alan Greenberg Oct. 15, 2018

Oct. 15, 2018

Greg did not say that ALL 3rd part access benefits users. He said that all users benefit from (some) 3rd party access (A implies B does is not cummutative!). Those who fight spam, malware, phishing and develop reputation services use WHOIS, and that help virtually all users (except those doing the naughty things). Alan At 15/10/2018 02:31 PM, Seun Ojedeji wrote: >Hmm... third party access does not always benefit the end user in reality. > >Cheers! > >Sent from my mobile >Kindly excuse brevity and typos > >On Mon, 15 Oct 2018, 19:15 Greg Shatan, ><<mailto:greg@isoc-ny.org>greg(a)isoc-ny.org> wrote: >I think the proper question to ask is âHow >many end users actually benefited from third parties checking WHOIS dataâ? > >The answer might well be âAll of them.â > >Best regards, > >Greg >On Mon, Oct 15, 2018 at 11:47 AM Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Michele you are correct. I considered putting >that level of detail in, but decided that it >overly complicated a message that was solely >asking about legal vs natural persons. Note that >your comment would have made the parenthetical >twice as long as the rest of the sentence. > >Alan > >At 15/10/2018 05:15 AM, Michele Neylon - Blacknight wrote: > >Alan > > > > > GDPR requires the information related to Natural Persons be protected > > > (for those resident in Europe) be protected. GDPR does not apply to > > > Legal Persons (ie companies). > > > > > >That isn't what GDPR states. > >By presenting it as applying to "natural > >persons" vs "legal persons" you are over > simplifying GDPR and its application. > >GDPR applies to personal data. > >It applies to data subjects. > >It also applies to data processing in the EU > >regardless of where the data subject is. So as > >an Irish company we have to treat our Canadian > >clients' data under GDPR as we are processing it in the EU. > > > > > >Regards > > > >Michele > > > >-- > >Mr Michele Neylon > >Blacknight Solutions > >Hosting, Colocation & Domains > ><https://www.blacknight.com/>https://www.blacknight.com/ > >https://blacknight.blog/ > >Intl. +353 (0) 59 9183072 > >Direct Dial: +353 (0)59 9183090 > >Personal blog: <https://michele.blog/>https://michele.blog/ > >Some thoughts: <https://ceo.hosting/>https://ceo.hosting/ > >------------------------------- > >Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty > >Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 > > > >Ã¯Â»Â¿ > >_______________________________________________ >CPWG mailing list ><mailto:CPWG@icann.org>CPWG(a)icann.org >https://mm.icann.org/mailman/listinfo/cpwg >_______________________________________________ >GTLD-WG mailing list ><mailto:GTLD-WG@atlarge-lists.icann.org>GTLD-WG(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg > >Working Group direct URL: ><https://community.icann.org/display/atlarge/New+GTLDs>https://community.icann.org/display/atlarge/New+GTLDs > >_______________________________________________ >CPWG mailing list ><mailto:CPWG@icann.org>CPWG(a)icann.org >https://mm.icann.org/mailman/listinfo/cpwg >_______________________________________________ >registration-issues-wg mailing list ><mailto:registration-issues-wg@atlarge-lists.icann.org>registration-issues-wg(a)atlarge-lists.icann.org >https://mm.icann.org/mailman/listinfo/registration-issues-wg

3 2

Re: [CPWG] [registration-issues-wg] Urgent EPDP question
by Alan Greenberg Oct. 15, 2018

Oct. 15, 2018

Thanks for the quick replies. I agree that the issue that a legal person may have some "natural person" information associated with it. But there is no way that a registrar can reasonable parse that, so it is up to the registrant to rid their entries of natural person information if they choose to include it. And yes, "Alan Greenberg Inc" had personal information in it. As does alangreenberg.org. But no one forces me to have a domain name. I find particularly amusing the issue of a Legal Person including name-identifying e-mails. Clearly that is a choice which they may know about, but the registrar, registry or ICANN cannot. If you wish to be suitable amused, consider that there are several families in the US with a surname of "Contact". Abuse.Contact(a)gmail.com is potentially a protected address! Certainly registrars and registries would like to simplify their life. And adding a Natural/Legal flag will not be a trivial activity. But that does not imply it is not the right way to go. Alan At 14/10/2018 11:42 PM, you wrote: >In agreement of contractual parties of having 2 systems, one to >protect the "natural person" privacy information for every one >globally and not only those from Europe. >The second is for the "legal persons" and because they're under >licence agreements in the legal system of their respective >countries. Hence moving to a two registered system has to have a >limited and derminate timeframe to move towards the dual registrant >system. I don't think their concerns about changing the system, but >it seems it goes beyond that. > >If there are concerns about the micro commercial business for >individual who function without any registration in their countries, >it would be their individual problem in how to be accountable to >their countries requirements. > >Nadira > > > >On Mon, Oct 15, 2018, 05:01 Holly Raiche ><<mailto:h.raiche@internode.on.net>h.raiche(a)internode.on.net> wrote: >Folks >An argument against differentiation is that the contracted parties >want to be able, as much as possible, to implement one system for >managing information rather than having to differentiate between the >license of a name being a natural person and the licensee of a name >being a corporate person. >Another is says that there are circumstances where information about >legal entities may amount to personal information - for example, >when a small business (usually a legal person) has used the actual >name of the person as the business name, or where, in the case of a >legal person, the contact details provided are for a named >individual - thus GDPR protections should apply uniformly. >My personal view is that, from the perspective of users, the >protections of GDPR really need only apply to natural persons. >That means that companies will need to be careful not to provide >personal contact information for the RAA/Registry agreements. And >from an end user point of view, the management of systems to >differentiate legal from natural persons is not our concern. > >Holly > > > On Oct 15, 2018, at 12:12 PM, Alan Greenberg > <<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: > > > > Here is a question that we need an answer on no later than > Tuesday morning. > > > > GDPR requires the information related to Natural Persons be > protected (for those resident in Europe) be protected. GDPR does > not apply to Legal Persons (ie companies). > > > > ICANN's Temporary Spec allows contracted parties to treat all > registrant alike and subject to GDPR. > > > > The EPDP Charter includes questions about whether contracted > parties may or must treat Legal Persons differently from Natural Persons. > > > > The GAC, BC and IPC have made strong statements about the need to > restrict GDPS to Natural Persons. The contracted parties are > pushing back - strongly. The words vary, but in essence what they > are saying ranges from there should be no constraint on them to > yes, they may differentiate but with an unspecified > time-frame. (As you may note if you looked at the RDS-WHOIS2 > report, registrars under the 2013 RAA must do some validation of > contact information for new an transfered domains, but none to > simple renewal. so there are currently 140,000,000 domains without > verified information (5 years after the 2013 RAA came into force) > and there is no requirement to ever validate their information - so > unspecified time frames can last a LONG time.) > > > > I personally feel that it is essential that we should > differentiate between legal persons and natural persons, just as > GDPR and other privacy legislation does. > > > > Comments? > > > > Alan > > > > _______________________________________________ > > CPWG mailing list > > <mailto:CPWG@icann.org>CPWG(a)icann.org > > https://mm.icann.org/mailman/listinfo/cpwg > > _______________________________________________ > > registration-issues-wg mailing list > > > <mailto:registration-issues-wg@atlarge-lists.icann.org>registration-issues-wg(a)atlarge-lists.icann.org > > > https://mm.icann.org/mailman/listinfo/registration-issues-wg >_______________________________________________ >CPWG mailing list ><mailto:CPWG@icann.org>CPWG(a)icann.org >https://mm.icann.org/mailman/listinfo/cpwg

3 2

A study on geoTLDs and GDPR/ says no evidence-based need for universal access model
by Marita Moll Oct. 15, 2018

Oct. 15, 2018

A bit more info on the potential need for UAM released through a study on geoTLD GDPR survey 2018. Survey findings state: Overall, our findings are that while EU-based geo TLD registries take GDPR seriously and have enacted measures to protect citizens’ personal data, the number of requests to access the data is vanishingly small, and these requests are being dealt with efficiently. This study of the geoTLD registries shows there is*no evidence-based need for a universal access model*, based on how GDPR is working in practice. Full study here: http://geotld.group/2018/10/12/the-geotld-gdpr-survey-2018/ CircleID article: http://www.circleid.com/posts/20181012_the_geotld_gdpr_survey_2018/ Marita

1 0

Urgent EPDP question
by Alan Greenberg Oct. 15, 2018

Oct. 15, 2018

Here is a question that we need an answer on no later than Tuesday morning. GDPR requires the information related to Natural Persons be protected (for those resident in Europe) be protected. GDPR does not apply to Legal Persons (ie companies). ICANN's Temporary Spec allows contracted parties to treat all registrant alike and subject to GDPR. The EPDP Charter includes questions about whether contracted parties may or must treat Legal Persons differently from Natural Persons. The GAC, BC and IPC have made strong statements about the need to restrict GDPS to Natural Persons. The contracted parties are pushing back - strongly. The words vary, but in essence what they are saying ranges from there should be no constraint on them to yes, they may differentiate but with an unspecified time-frame. (As you may note if you looked at the RDS-WHOIS2 report, registrars under the 2013 RAA must do some validation of contact information for new an transfered domains, but none to simple renewal. so there are currently 140,000,000 domains without verified information (5 years after the 2013 RAA came into force) and there is no requirement to ever validate their information - so unspecified time frames can last a LONG time.) I personally feel that it is essential that we should differentiate between legal persons and natural persons, just as GDPR and other privacy legislation does. Comments? Alan

17 19

Meeting Invitation: Consolidated Policy Working Group (CPWG) Call on Wednesday, 17 October 2018 at 13:00 UTC for 90mins
by ICANN At-Large Staff Oct. 14, 2018

Oct. 14, 2018

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 17 October 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/y7l65hjg The agenda (to be updated) and call details can be found at: https://community.icann.org/x/Nw28BQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 3535 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: http://adigo.com/icann/ At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

4 3

EPDP Alternate
by Alan Greenberg Oct. 11, 2018

Oct. 11, 2018

I note that I will be in transit to Barcelona during the EPDP meeting of 16 October and I have submitted the request to have Seun replace met that day. I will be back on the ground the morning of the 17th. Alan

1 0