September 2018 - Gnso-epdp-team

***REMINDER*** Meeting Invitation / Alternates & Observers / GDPR Q&A session with the EPDP Team / Wednesday, 19 September 2018 at 13:00 UTC
by Julie Bisland 18 Sep '18

18 Sep '18

Dear all, Non-members can follow the GDPR Q&A session with the GNSO Temp Spec gTLD RD EPDP team on Wednesday, 19 September 2018 at 13:00 UTC via the audio cast or view only Adobe Connect room. Please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Julie

1 0

Proposed Agenda - EPDP Team Meeting #14 - 18 September 2018
by Marika Konings 18 Sep '18

18 Sep '18

Dear All, Please find below the proposed agenda for Thursday’s EPDP Team meeting. As a reminder, you can find the action items and their expected delivery date/time here: https://community.icann.org/x/NwSNBQ. Best regards, Caitlin, Berry and Marika ============ EPDP Meeting #14 Agenda Tuesday, 18 September 2018 1. Roll Call & SOI Updates (5 minutes) 2. Welcome and Updates from EPDP Team Chair (5 minutes) * Reminder to complete GDPR Training Course by Tuesday, 18 September * Reminder of GDPR Q&A session with Becky Burr on Wednesday, 19 September * ICANN63 Travel Support * Recap CBI Open House Session * Other updates, if applicable 1. Appendix C (30 minutes) Objective: Reach Preliminary Agreement on how to move forward with Appendix C * Review additional input provided by RySG * Agree on next steps 1. Section 4.4 (80 minutes) Objective of discussion: (1) begin formulating answers to Charter questions<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>: Part 1: Purposes for Processing Registration Data a) Purposes outlined in Sec. 4.4.1-4.4.13 of the Temporary Specification: a1) Are the purposes enumerated in the Temporary Specification valid and legitimate? a2) Do those purposes have a corresponding legal basis? a3) Should any of the purposes be eliminated or adjusted? a4) Should any purposes be added? (2) begin formulating answers to EDPB advice<https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-05jul…> re: ICANN not conflating its own purposes with the interests of third parties. * Review input received on Registrar purposes (see https://docs.google.com/document/d/1IinDj9isH6uU-KYIVPPu2GyT0-Q3urTXXIW1Hhr…) * Agree on next steps * Review input received on overview of purposes (see https://docs.google.com/spreadsheets/d/1RivZFrPQpJ_bgDlOI6yfhhYaSs2oYgS1n4T…) * Agree on next steps 1. Confirm action items and questions for ICANN Org, if any (5 minutes) 2. Wrap and confirm next meeting to be scheduled for Tuesday 18 September at 13.00 UTC.)

1 1

EPDP Team - Los Angeles Face to Face logistics/ 24-26 September
by Terri Agnew 17 Sep '18

17 Sep '18

Hello EPDP Team, Please see attached document with logistics for the EPDP Face-to- Face meeting held 24-26 September 2018 in Los Angeles. Remote participation join information will be sent out shortly. Thank you. With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: terri.agnew(a)icann.org<mailto:terri.agnew@icann.org> Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

1 0

Re: [Gnso-epdp-team] Input on proposals in relation to Appendix C - Input due by Friday 14 September at 19.00 UTC
by Plaut, Diane 17 Sep '18

17 Sep '18

Dear Caitlin, Berry and Marika- Attached please find the IPC input in relation to Appendix C. Sincerely, Diane Diane Plaut General Counsel and Privacy Officer [cid:image001.png@01D3CA70.18FC1D40] Direct +1 917 983 3529 diane.plaut(a)corsearch.com<mailto:diane.plaut@corsearch.com> 220 West 42nd Street, 11th Floor, New York, NY 10036, United States www.corsearch.com<http://www.corsearch.com/> Join Corsearch on Twitter<https://twitter.com/corsearch> Linkedin<https://www.linkedin.com/company/2593860/> Trademarks + Brands<http://trademarksandbrands.corsearch.com/> Customer Service/Platform Support: 1 800 SEARCH1™ (1 800 732 7241) Corsearch.USCustomerService(a)corsearch.com<mailto:Corsearch.USCustomerService@corsearch.com> Confidentiality Notice: This email and its attachments (if any) contain confidential information of the sender. The information is intended only for the use by the direct addressees of the original sender of this email. If you are not an intended recipient of the original sender (or responsible for delivering the message to such person), you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance of the contents of and attachments to this email is strictly prohibited. If you have received this email in error, please immediately notify the sender at the address shown herein and permanently delete any copies of this email (digital or paper) in your possession. From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, September 11, 2018 at 12:47 PM To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Input on proposals in relation to Appendix C - Input due by Friday 14 September at 19.00 UTC Dear All, In relation to Action item #9: Support team to collate RySG proposal and Margie's proposal into one document – note that an updated version of the Discussion Summary Index (DSI) has been posted on the wiki which now includes the early input received in relation to Appendix C as well as the proposals put forward by the RySG and Margie (see https://community.icann.org/x/ExxpBQ<https://community.icann.org/x/ExxpBQ>, page 16 and 17). Per Action Item #10, please provide input on these proposals and/or how these can be reconciled at the latest by Friday 14 September 19.00 UTC. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Recordings, Attendance & AC chat from the Open House Meeting with CBI and EPDP Team held Monday, 17 September 2018
by Andrea Glandon 17 Sep '18

17 Sep '18

Dear all, Please find the attendance and AC chat attached to this email. The MP3 and AC recording below from the Open House Meeting with CBI and EPDP Team call held on Monday, 17 September 2018 at 14:00 UTC. These have also been posted on the agenda wiki page: https://community.icann.org/x/zwGrBQ MP3: https://audio.icann.org/gnso/gnso-open-house-cbi-epdp-17sep18-en.mp3 AC Recording: https://participate.icann.org/p37k3ftlqp7/<https://participate.icann.org/p37k3ftlqp7/?OWASP_CSRFTOKEN=81a39a1ebb180a13…> ** Please let me know if your name has been left off the list ** Mailing list archives of the GNSO Temp Spec gTLD RD EPDP : https://mm.icann.org/pipermail/gnso-epdp-team/ Main wiki page for the working group: https://community.icann.org/x/IYEpBQ Thank you. Kind Regards, Andrea Glandon

1 0

Reminder: please complete required GDPR training by 18 September
by Caitlin Tubergen 17 Sep '18

17 Sep '18

Dear All, As of today’s date, we note that many of you have not completed the required GDPR training. All EPDP Team Members, Alternates and Liaisons should have received an email with your login credentials from noreply(a)grcelearning.com on Monday, 10 September. If you did not receive an email, please contact the ICANN Support Team as soon as possible. Please note that the deadline to complete the GDPR training is Tuesday, 18 September. Thank you. Best regards, Marika, Berry and Caitlin

1 0

EPDP Fact Sheet
by Berry Cobb 17 Sep '18

17 Sep '18

EPDP Members and Alternates, Please find attached the first release of the EPDP Fact Sheet. Purpose: This is a summary document (page 1) of the EPDP that highlights Meeting Activity, Status, Milestone acheivement, and most importantly financial resources. Detailed project planning and status can be found via other work products. Unique to the Fact Sheet are details of available budget versus actual spend. Funding Source & Amount: On 7 August 2018, Cherine Chalaby of the ICANN Board notified <https://gnso.icann.org/sites/default/files/file/field-file-attach/chalaby-t o-gnso-council-07aug18-en.pdf> the GNSO Council of supplemental budget available to execute the EPDP. In short, $590,000 was allotted to this effort to cover expenses related to professional services, telcom services, external experts, face to face travel support, and contingencies. Detailed allotment to budget line items can be found in Cherine's letter, as well as, pages 2 & 3 of the Fact Sheet. Project Cost Support Team (PCST): The concept of the PCST was first used for the CCWG on ICANN's Accountability where funds were allotted to that effort. The effort will be replicated here which is a first for the GNSO. Members of the PCST consist of EDPD leadership, Council leadership, ICANN Finance and ICANN Policy staff support. As noted in Cherine's letter, budget responsibilities lie with David Olive, SVP of Policy Development, who will coordinate with the PCST in review of requests and ultimate approval of expenses. Publication Frequency: The Fact Sheet will be published shortly after the close of the prior month. Also note that ICANN Finance will also provide financial reporting that will compliment the Fact Sheet as actual expenses are entered and reconciled in ICANN's finance system. Key Points to Fact Sheet - version1: . EPDP Status is a high-level summary of % Time Elapsed and not that of milestones achieved. This is a time based statistic because the EPDP and community have until 24 May 2019 to accomplish the task. This section also includes a Budget Spent vs. Committed percentage. Committed means that agreements for spend have set in motion, such as supported travel, telcom services, or contracts signed with vendors. . Section I Meeting Stats is a summary of meeting/conference call hours spent activity. . Section II Financial Resources is a break out of budgeted vs. committed vs. actual expense. It is divided between professional services and travel. This first version is intended to show a baseline of the entrire budget without any expenses. As noted above, the total amount is $590,000. However, given the urgency to prepare for the LA face to face, $87,000 shows as committed. . Section III Milestones is a high-level summary of milestones accomplished by phase including weighting. The EPDP is essentially broken down into three primary deliverables: Triage Report, Initial Report, and Final Report. Note, that this current version omits milestones relating to the issue of access as per the charter, the primary deliverbles must be delivered to meet the 24 May 2019 expiration of the Temporary Specification. . Page 2 is a detailed breakout of budget line items releated to professional services. While there are funds committed to training, telcom, and mediation, the commitments and any actuals will not appear until the September 2018 version of the Fact Sheet. . Page 3 is a detailed breakout of budget line items related to travel support. As noted above, $87K has been committed in support of the LA face to face. Any actuals and the committed funds for Barcelona, ICANN63 will appear in the September version. Stay tuned for the September version as it will contain much more information related to in-flight budget activities. The release should occur by the close of the first week in October. Please let me know if you have any questions. Thank you. B Berry Cobb GNSO Policy Consultant @berrycobb

1 0

Re: [Gnso-epdp-team] Section 4.4.8
by Kavouss Arasteh 17 Sep '18

17 Sep '18

Dear Ayden Sorry if I was not clear . It was a typo changing the sense of my comment I meant that a Recital from the current version of GDPR would NOT be a less relevant source of insight than an Opinion of A29 from 2014 regarding a Directive which has itself been superseded by GDPR..In other words as Mark mentioned ,contrary to the situation existed in the pre -GDPR, as the interests and fundamental rights of the data subject could in particular override the interest of the data controller where personal data are processed in circumstances where data subjects do not reasonably expect further processing. Article 29 is now integrated in GPDR and advice from that has the same weight as the relevant source of insight. Regards On Mon, Sep 17, 2018 at 3:11 PM Ayden Férdeline <icann(a)ferdeline.com> wrote: > Hi Kavouss, > > I’m sorry but I don’t understand this email. Can you please expand on what > you mean in regards to the Article 29 Working Party? Thanks. > > Ayden Férdeline > > > On Mon, Sep 17, 2018 at 15:06, Kavouss Arasteh <kavouss.arasteh(a)gmail.com> > wrote: > > I fully support the view points and arguments submitted by Mark and Hadia > . > I think arguments launched by Ayden are a narrow thinking and soft reading > of the process. > Ar 29 SHALL NOT prevail the basic requirements and mandatory provisions > of GPDR > Regards > Kavouss > > On Mon, Sep 17, 2018 at 9:29 AM Hadia Abdelsalam Mokhtar EL miniawi < > Hadia(a)tra.gov.eg> wrote: > >> Hi Ayden, >> >> >> >> You say in your email below " It is true that the opinions of A29 were >> also non-binding, but their guidance should carry weight and credibility >> with us, because EU Courts have typically taken their opinions into >> consideration, and now that A29 has morphed into the Data Protection Board, >> it has new legal powers and their previous opinions heavily shaped the >> construction of the GDPR" >> >> >> >> Just a quick clarification normally recitals are used by the court of >> justice to establish what any directive means. However you should keep in >> mind that the recitals of the GDPR are not only going to be used by the >> courts of justice but also by the European Data Protection Board (EDPB) >> when carrying its role in ensuring that the regulation is applied. >> >> >> >> Hadia >> >> >> >> *From:* Ayden Férdeline [mailto:icann@ferdeline.com] >> *Sent:* Monday, September 17, 2018 9:12 AM >> *To:* Mark Svancarek >> *Cc:* Hadia Abdelsalam Mokhtar EL miniawi; gnso-epdp-team(a)icann.org >> *Subject:* Re: [Gnso-epdp-team] Section 4.4.8 >> >> >> >> Hi Mark, >> >> >> >> Thanks for your email and for giving me the opportunity to clarify my >> remarks. >> >> >> >> I don’t want to suggest that we should ignore the contents of the >> Recitals — but we should not treat Recitals the same as we treat the >> Articles of the GDPR, because the Recitals have no independent legal value >> and are subordinate to, and cannot contradict, the legislative provisions. >> I did not see that distinction being made in the message that I responded >> to. >> >> >> >> It is true that the opinions of A29 were also non-binding, but their >> guidance should carry weight and credibility with us, because EU Courts >> have typically taken their opinions into consideration, and now that A29 >> has morphed into the Data Protection Board, it has new legal powers and >> their previous opinions heavily shaped the construction of the GDPR >> >> >> >> Best wishes, >> >> >> >> Ayden Férdeline >> >> >> >> P.S. Hopefully my response is received, as I will shortly be losing >> posting rights to this list, as I have appointed an alternate for this >> week’s calls. >> >> >> >> >> >> On 17 Sep 2018, at 01:47, Mark Svancarek (CELA) <marksv(a)microsoft.com> >> wrote: >> >> >> >> Ayden, I don’t understand your logic that a Recital from the current >> version of GDPR would be a less relevant source of insight than an Opinion >> of A29 from 2014 regarding a Directive which has itself been superseded by >> GDPR. >> >> >> >> From Recital 47: "The interests and fundamental rights of the data >> subject could in particular override the interest of the data controller >> where personal data are processed in circumstances where data subjects do >> not reasonably expect further processing" >> >> >> >> In the pre-GDPR world, I think that the data subject **might** have had >> a reason to expect further processing based on preventing fraud in some >> undefined fashion (though **probably not**) and the data subject **would >> not** have had a reason to expect further processing for direct >> marketing purposes. (I use these examples simply because they are mentioned >> in the Recital.) >> >> >> >> In the new policy that we are creating, we should make it very clear to >> the data subject at the time of collection that the data may possibly be >> used for defined anti-fraud purposes. >> >> >> >> /marksv >> >> *From:* Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> *On Behalf >> Of *Ayden Férdeline >> *Sent:* Sunday, September 16, 2018 8:08 AM >> *To:* Hadia Abdelsalam Mokhtar EL miniawi <Hadia(a)tra.gov.eg> >> *Cc:* gnso-epdp-team(a)icann.org >> *Subject:* Re: [Gnso-epdp-team] Section 4.4.8 >> >> >> >> Hi Hadia, >> >> >> >> If we consider Recital 47 in its entirety and thus in its context, I >> don’t think it necessarily means what you say it does. The same goes for >> Recital 49. >> >> >> >> But let’s not get ahead of ourselves. We need to distinguish between a >> Recital of the GDPR and an Article of the GDPR, as they are not the same. *While >> the recitals may inform the interpretation of the GDPR's articles, they are >> not legally binding. Only the GDPR's articles are binding instruments.* >> >> >> >> I would suggest that we should be considering published guidance from the >> Article 29 Working Party on what a legitimate interest is. In Opinion >> 06/2014 >> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fec.europa.e…> on >> the "Notion of Legitimate Interests", they caution that legitimate >> interests "should thus not be considered as 'the weakest link' or an open >> door to legitimise all data processing activities which do not fall under >> any of the other legal grounds" for processing. Rather, it is intended to >> give "necessary flexibility for data controllers for situations where there >> is no undue impact on data subjects." >> >> >> >> That’s the important distinction here. Anyone who intends to use personal >> data must balance its own legitimate interest against the rights of the >> data subject, *and also against the data subject’s interests*, >> irrespective of whether those interests are legitimate or not. See Article >> 6(f) of the GDPR. >> >> >> >> Best wishes, >> >> >> >> Ayden Férdeline >> >> >> >> >> >> >> On 16 Sep 2018, at 16:43, Hadia Abdelsalam Mokhtar EL miniawi < >> Hadia(a)tra.gov.eg > wrote: >> >> >> >> Hi Amr and All, >> >> >> >> I don't think that a final agreement was actually reached on moving items >> 4.4.2, 4.4.8, 4.4.9 and 4.4.10 from under the header "Purposes for >> Processing gTLD Registration Data". >> >> >> >> The whole confusion in my opinion comes from two considerations the first >> is our lack of understanding of the interests which lets us sometimes put >> some interests that are typically ICANN purposes as third party purposes >> and the second is that when we talk about data processing we mix collection >> with disclosure. >> >> >> >> Recital 47 of the GDPR states that " The processing of personal data >> strictly necessary for the purposes of preventing fraud also constitutes a >> legitimate interest of the data controller concerned" Therefore fraud >> prevention constitutes a legitimate interest, and recital 49 of the GDPR >> states that the necessary and proportionate processing for network security >> also constitutes a legitimate interest. So when we speak about the original >> text of 4.4.8 >> >> "Supporting a framework to address issues involving domain name >> registrations, including but not limited to: consumer protection, >> investigation of cybercrime, DNS abuse, and intellectual property >> protection;" First we should not deduce that the text speaks only about >> the access, in order to have a framework through which access can be >> provided you should also have the data itself (that is the collection of >> the data). Second I would argue that the collection of the data for the >> above purpose is not only a third party's purpose but it is also an ICANN >> purpose >> >> >> >> As for the difference between a framework and a model, a framework is a >> guide or some principles that make you implement the model, while the model >> is the tool itself. I would rather see the actual model than just the >> principles. >> >> >> >> >> >> >> >> >> >> >> >> >> >> *From:* Amr Elsadr [mailto:aelsadr@protonmail.ch <aelsadr(a)protonmail.ch> >> ] >> *Sent:* Thursday, September 13, 2018 2:03 PM >> *To:* Arasteh >> *Cc:* Hadia Abdelsalam Mokhtar EL miniawi; gnso-epdp-team(a)icann.org >> *Subject:* Re: [Gnso-epdp-team] Section 4.4.8 >> >> >> >> Hi Hadia and Kavouss, >> >> >> >> The volunteer team working on 4.4.8 did so with the understanding that >> sections 4.4.2, 4.4.8, 4.4.9 and 4.4.10 would be moved out from under the >> header "Purposes for Processing gTLD Registration Data". This was following >> Kurt’s email to the EPDP list on 4 September, titled "Project Plan >> Adjustments and Policy Organization". >> >> >> >> We did consider an earlier suggestion by Mark; to split the processing >> purposes to two lists, one to achieve the purposes of controllers and one >> of third-parties. However, we did not pursue this too aggressively. >> Speaking for myself, I agree that 4.4.8 in both its original and proposed >> altered forms do not describe purposes for processing (for any party). >> >> >> >> I am not sure why a "model" would be preferable to a "framework", so if >> you could elaborate on why you believe it to be more specific, I would be >> grateful. Within NCSG, we have considered both these terms, as well as >> others such as "Methodology" and "Mechanism". We haven’t settled on any >> one, just yet. >> >> >> >> As Alex suggested in his original email, this is still a tentative >> proposal. We like it, or at least prefer it to other alternatives >> previously suggested, but we’re not exactly married to it just yet. :-) >> >> >> >> Thanks. >> >> >> >> Amr >> >> >> >> >> >> On Sep 13, 2018, at 12:49 PM, Arasteh <kavouss.arasteh(a)gmail.com> wrote: >> >> >> >> Dear All >> >> I agree almost with what Hadia said >> >> Kavouss >> >> Sent from my iPhone >> >> >> On 13 Sep 2018, at 10:45, Hadia Abdelsalam Mokhtar EL miniawi < >> Hadia(a)tra.gov.eg > wrote: >> >> Hi All, >> >> >> >> Dear Alex and Amr, >> >> >> >> First off thank you for your effort and time on this proposal. But are >> you saying that among the purposes of the processing of the data is the " >> identification of third-parties with legitimate interests". This is surely >> not one of the purposes for the processing of the data therefore a suggest >> removing it. >> >> >> >> So my suggestion would be. >> >> >> >> 4.4.8 Supporting a Model that provides access to parties with legitimate >> interests grounded in legal bases to Registration Data relevant to >> addressing specific issues involving domain name registrations; such as >> issues related to consumer protection, investigation of cybercrime, DNS >> abuse and intellectual property protection. >> >> >> >> I put model as I think it is more specific but I am fine with using the >> term framework if you see it more appropriate. I also suggest adding "such >> as issues related to" which would serve to provide examples of third >> parties with legitimate interest. >> >> >> >> Kind Regards >> >> Hadia >> >> >> >> >> >> >> >> *From:* Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org >> <gnso-epdp-team-bounces(a)icann.org>] *On Behalf Of *Alex Deacon >> *Sent:* Tuesday, September 11, 2018 10:34 PM >> *To:* gnso-epdp-team(a)icann.org >> *Subject:* [Gnso-epdp-team] Section 4.4.8 >> >> >> >> Hi All, >> >> >> >> As you know a group of us has been working to recommend an update to >> Section 4.4.8 of the temp spec. >> >> >> >> While we haven't come to full agreement on the update, we are pretty >> close and wanted to share the current/tentative output of the volunteer >> team with the broader team. >> >> >> >> 4.4.8 Supporting a framework that enables identification of >> third-parties with legitimate interests grounded in legal bases, and >> providing these third-parties with access to Registration Data relevant to >> addressing specific issues involving domain name registrations *related >> to consumer protection, investigation of cybercrime, DNS abuse and >> intellectual property protection. * >> >> >> >> The non-bold text was suggested by Amr/NCSG and the added bold text was >> an updated suggested by me/IPC and supported by the BC. >> >> >> >> Giving it a re-read again today I think additional word-smithing could be >> warranted, but for now I will resist and step away and let others share >> their thoughts. >> >> >> >> Alex >> >> >> >> >> >> >> -- >> >> ___________ >> >> *Alex Deacon* >> >> Cole Valley Consulting >> >> alex(a)colevalleyconsulting.com >> >> +1.415.488.6009 >> >> >> >> _______________________________________________ >> Gnso-epdp-team mailing list >> Gnso-epdp-team(a)icann.org >> https://mm.icann.org/mailman/listinfo/gnso-epdp-team >> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.o…> >> >> >> _______________________________________________ >> Gnso-epdp-team mailing list >> Gnso-epdp-team(a)icann.org >> https://mm.icann.org/mailman/listinfo/gnso-epdp-team > >

1 0

Fwd: [Ntfy-gnso-epdp-team] Meeting Invitation/ Open house meeting with CBI and the EPDP team / Monday, 17 September 2018 at 14:00 UTC
by Kurt Pritz 17 Sep '18

17 Sep '18

Hi Everyone: See the note from CBI below. Thanks and regards, Kurt > Begin forwarded message: > > From: David Plumb <dplumb(a)cbi.org> > Subject: Re: [Ntfy-gnso-epdp-team] Meeting Invitation/ Open house meeting with CBI and the EPDP team / Monday, 17 September 2018 at 14:00 UTC > Date: September 16, 2018 at 7:40:29 PM PDT > To: Kurt Pritz <kurt(a)kjpritz.com> > Cc: Terri Agnew <terri.agnew(a)icann.org>, "gina(a)cbi.org" <gina(a)cbi.org>, "tberkman(a)cbi.org" <tberkman(a)cbi.org> > > Hi Kurt, > Many thanks for this email. > We’ve created a sign-up sheet for those who would would like to speak with us next week. It’s on this google sheet <https://docs.google.com/spreadsheets/d/17hNfTImZ83bNOd4QAQiu1RuEH5tjtUR7MkB…>. > I’m not sure if I can post to the list, so I’ll kindly as you to circulate. We’d ask that the different stakeholder groups assign one person to speak with us, our they can all join together on a call. > Thanks and speak tomorrow, > David > > (Fyi, the full link, if helpful, is: https://docs.google.com/spreadsheets/d/17hNfTImZ83bNOd4QAQiu1RuEH5tjtUR7MkB… <https://docs.google.com/spreadsheets/d/17hNfTImZ83bNOd4QAQiu1RuEH5tjtUR7MkB…> > > >> On Sep 16, 2018, at 8:07 PM, Kurt Pritz <kurt(a)kjpritz.com <mailto:kurt@kjpritz.com>> wrote: >> >> Hi Everyone: >> >> For the agenda for tomorrow’s / today’s call regarding the introduction of CBI and the use of mediation techniques at the meeting in Los Angeles, I suggest: >> >> 1) Brief introduction by the CBI team; a few minute description of CBI, their expertise, their experience working with ICANN, and the name, rank and role of each of the CBI attendees: David Plumb, Gina Bartlett and Toby Berkman. >> >> 2) Input and information from the team to the CBI. Some of you offered to provide information regarding the conduct of face-to-face meetings. I am a bit sad that the CBI team is a newcomer to our proceedings at this stage but I hope some of you can speak up in a collaborative way to provide what advice you might have for integrating CBI into the team and sharing lessons learned from your previous experience. >> >> 3) CBI to provide information regarding the use of mediation techniques in a multi-stakeholder setting and how they might apply here. We have had two sessions with the CBI team and, as mentioned above, there is some limited experience with ICANN. I think the the EPDP team’s job is to provide your best feedback. >> >> $) An interactive session, questions and answers. CBI can take this information back and adjust their planning for the meeting next week. >> >> Thanks to those of you that attend and participate. >> >> Best regards, >> >> Kurt >> >> >> >> >> >>> On Sep 13, 2018, at 2:58 PM, Terri Agnew <terri.agnew(a)icann.org <mailto:terri.agnew@icann.org>> wrote: >>> >>> Dear all, >>> >>> To facilitate the sharing of ideas and suggestions with the CBI team in relation to the LA F2F meeting, please note that an open house session has been scheduled for Monday 17 September from 14.00 - 15.00 UTC. This is an optional meeting - those interested to connect with CBI and share their ideas for the planning and running of the F2F meeting are encouraged to join. >>> >>> The open house meeting with CBI and the EPDP team is scheduled on Monday, 17 September 2018 at 14:00 UTC for 1hour. >>> 7:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Tuesday)01:00 Melbourne AEST >>> For other times: https://tinyurl.com/y73vko2k <https://tinyurl.com/y73vko2k> >>> >>> Agenda Wiki: https://community.icann.org/x/zwGrBQ <https://community.icann.org/x/zwGrBQ> >>> >>> Please ensure you read the below information: >>> >>> CONFERENCE CALL INFORMATION FOR MEMBERS >>> Adobe Connect room: https://participate.icann.org/gnso-epdp-team <https://participate.icann.org/gnso-epdp-team> >>> If you’re having trouble joining, please check your plug ins: http://tinyurl.com/icannactest <http://tinyurl.com/icannactest> >>> Please allow yourself additional time before start of meeting to log into Adobe Connect. >>> **Important**- Please log into Adobe Connect with your FIRST and LAST NAME-AFFILIATION/INDIVIDUAL >>> Instructions explaining how to connect the audio in the Adobe Connect room are attached. A calendar invitation has equally been sent and an ical (if your inbox doesn’t receive direct calendar invitations) is available here as attachment for you to download to your calendar. >>> >>> ALTERNATES will be assigned by Members in case of Member absence for a determined period of time and will therefore replace the aforementioned Member on the mailing list and on conference calls. In case of absence, members must assign an appointed Alternate via the Alternate Assignment form [goo.gl] <https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_xtfYf9mWF…>. >>> >>> MEETING AUDIO CAST AND VIEW ONLY ADOBE CONNECT (FOR ALTERNATES AND OBSERVERS) >>> To join the event, click on the link: >>> Listen in browser: http://stream.icann.org:8000/stream01 <http://stream.icann.org:8000/stream01> >>> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u <http://stream.icann.org:8000/stream01.m3u> >>> View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers <https://participate.icann.org/gnso-epdp-observers> >>> If you require a dial-out or to send apologies (do not send to full working group) please send an email request with your preferred contact number to gnso-secs(a)icann.org <mailto:gnso-secs@icann.org> >>> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> >>> To join via Verizon Bridge, see dial in numbers and participant passcode below. >>> >>> Kind regards, >>> >>> Terri >>> >>> ___________________________________________________________ >>> >>> To join the audio bridge, call in using the appropriate phone number below and provide the Participant Passcode verbally to the operator. >>> >>> Participant passcode: EPDP >>> Dial in numbers: >>> Country >>> >>> Toll Numbers >>> Freephone/ >>> Toll Free Number >>> ARGENTINA >>> >>> >>> >>> >>> >>> 0800-777-0519 >>> >>> AUSTRALIA >>> >>> ADELAIDE: >>> >>> 61-8-8121-4842 >>> >>> 1-800-657-260 >>> >>> AUSTRALIA >>> >>> BRISBANE: >>> >>> 61-7-3102-0944 >>> >>> 1-800-657-260 >>> >>> AUSTRALIA >>> >>> CANBERRA: >>> >>> 61-2-6100-1944 >>> >>> 1-800-657-260 >>> >>> AUSTRALIA >>> >>> MELBOURNE: >>> >>> 61-3-9010-7713 >>> >>> 1-800-657-260 >>> >>> AUSTRALIA >>> >>> PERTH: >>> >>> 61-8-9467-5223 >>> >>> 1-800-657-260 >>> >>> AUSTRALIA >>> >>> SYDNEY: >>> >>> 61-2-8205-8129 >>> >>> 1-800-657-260 >>> >>> AUSTRIA >>> >>> >>> >>> 43-1-92-81-113 >>> >>> 0800-005-259 >>> >>> BELGIUM >>> >>> >>> >>> 32-2-400-9861 >>> >>> 0800-3-8795 >>> >>> BRAZIL >>> >>> SAO PAULO: >>> >>> 55-11-3958-0779 >>> >>> 0800-7610651 >>> >>> CHILE >>> >>> >>> >>> >>> >>> 1230-020-2863 >>> >>> CHINA >>> >>> CHINA A: >>> >>> 86-400-810-4789 >>> >>> 10800-712-1670 >>> >>> CHINA >>> >>> CHINA B: >>> >>> 86-400-810-4789 >>> >>> 10800-120-1670 >>> >>> COLOMBIA >>> >>> >>> >>> >>> >>> 01800-9-156474 >>> >>> CROATIA >>> >>> >>> >>> >>> >>> 080-08-06-309 >>> >>> CZECH REPUBLIC >>> >>> >>> >>> 420-2-25-98-56-64 >>> >>> 800-700-177 >>> >>> DENMARK >>> >>> >>> >>> 45-7014-0284 >>> >>> 8088-8324 >>> >>> EGYPT >>> >>> >>> >>> >>> >>> 0800000-9029 >>> >>> ESTONIA >>> >>> >>> >>> >>> >>> 800-011-1093 >>> >>> FINLAND >>> >>> >>> >>> 358-9-5424-7162 >>> >>> 0-800-9-14610 >>> >>> FRANCE >>> >>> LYON: >>> >>> 33-4-26-69-12-85 >>> >>> 080-511-1496 >>> >>> FRANCE >>> >>> MARSEILLE: >>> >>> 33-4-86-06-00-85 >>> >>> 080-511-1496 >>> >>> FRANCE >>> >>> PARIS: >>> >>> 33-1-70-70-60-72 >>> >>> 080-511-1496 >>> >>> GERMANY >>> >>> >>> >>> 49-69-2222-20362 >>> >>> 0800-664-4247 >>> >>> GREECE >>> >>> >>> >>> 30-80-1-100-0687 >>> >>> 00800-12-7312 >>> >>> HONG KONG >>> >>> >>> >>> 852-3001-3863 >>> >>> 800-962-856 >>> >>> HUNGARY >>> >>> >>> >>> 36-1-700-8856 >>> >>> 06-800-12755 >>> >>> INDIA >>> >>> INDIA A: >>> >>> >>> >>> 000-800-852-1268 >>> >>> INDIA >>> >>> INDIA B: >>> >>> >>> >>> 000-800-001-6305 >>> >>> INDIA >>> >>> INDIA C: >>> >>> >>> >>> 1800-300-00491 >>> >>> INDONESIA >>> >>> >>> >>> >>> >>> 001-803-011-3982 >>> >>> IRELAND >>> >>> >>> >>> 353-1-246-7646 >>> >>> 1800-992-368 >>> >>> ISRAEL >>> >>> >>> >>> >>> >>> 1-80-9216162 >>> >>> ITALY >>> >>> MILAN: >>> >>> 39-02-3600-6007 >>> >>> 800-986-383 >>> >>> ITALY >>> >>> ROME: >>> >>> 39-06-8751-6018 >>> >>> 800-986-383 >>> >>> ITALY >>> >>> TORINO: >>> >>> 39-011-510-0118 >>> >>> 800-986-383 >>> >>> JAPAN >>> >>> OSAKA: >>> >>> 81-6-7878-2631 >>> >>> 0066-33-132439 >>> >>> JAPAN >>> >>> TOKYO: >>> >>> 81-3-6868-2631 >>> >>> 0066-33-132439 >>> >>> LATVIA >>> >>> >>> >>> >>> >>> 8000-3185 >>> >>> LUXEMBOURG >>> >>> >>> >>> 352-27-000-1364 >>> >>> 8002-9246 >>> >>> MALAYSIA >>> >>> >>> >>> >>> >>> 1-800-81-3065 >>> >>> MEXICO >>> >>> GUADALAJARA (JAL): >>> >>> 52-33-3208-7310 >>> >>> 001-866-376-9696 >>> >>> MEXICO >>> >>> MEXICO CITY: >>> >>> 52-55-5062-9110 >>> >>> 001-866-376-9696 >>> >>> MEXICO >>> >>> MONTERREY: >>> >>> 52-81-2482-0610 >>> >>> 001-866-376-9696 >>> >>> NETHERLANDS >>> >>> >>> >>> 31-20-718-8588 >>> >>> 0800-023-4378 >>> >>> NEW ZEALAND >>> >>> >>> >>> 64-9-970-4771 >>> >>> 0800-447-722 >>> >>> NORWAY >>> >>> >>> >>> 47-21-590-062 >>> >>> 800-15157 >>> >>> PANAMA >>> >>> >>> >>> >>> >>> 011-001-800-5072065 >>> >>> PERU >>> >>> >>> >>> >>> >>> 0800-53713 >>> >>> PHILIPPINES >>> >>> >>> >>> 63-2-858-3716 >>> >>> 1800-111-42453 >>> >>> POLAND >>> >>> >>> >>> >>> >>> 00-800-1212572 >>> >>> PORTUGAL >>> >>> >>> >>> 351-2-10054705 >>> >>> 8008-14052 >>> >>> ROMANIA >>> >>> >>> >>> 40-31-630-01-79 >>> >>> RUSSIA >>> >>> >>> >>> >>> >>> 8-10-8002-0144011 >>> >>> SAUDI ARABIA >>> >>> >>> >>> >>> >>> 800-8-110087 >>> >>> SINGAPORE >>> >>> >>> >>> 65-6883-9230 >>> >>> 800-120-4663 >>> >>> SLOVAK REPUBLIC >>> >>> >>> >>> 421-2-322-422-25 >>> >>> 0800-002066 >>> >>> SOUTH AFRICA >>> >>> >>> >>> >>> >>> 080-09-80414 >>> >>> SOUTH KOREA >>> >>> >>> >>> 82-2-6744-1083 >>> >>> 00798-14800-7352 >>> >>> SPAIN >>> >>> >>> >>> 34-91-414-25-33 >>> >>> 800-300-053 >>> >>> SWEDEN >>> >>> >>> >>> 46-8-566-19-348 >>> >>> 0200-884-622 >>> >>> SWITZERLAND >>> >>> >>> >>> 41-44-580-6398 >>> >>> 0800-120-032 >>> >>> TAIWAN >>> >>> >>> >>> 886-2-2795-7379 >>> >>> 00801-137-797 >>> >>> THAILAND >>> >>> >>> >>> >>> >>> 001-800-1206-66056 >>> >>> TURKEY >>> >>> >>> >>> >>> >>> 00-800-151-0516 >>> >>> UNITED ARAB EMIRATES >>> >>> >>> >>> >>> >>> 8000-35702370 >>> >>> UNITED KINGDOM >>> >>> BIRMINGHAM: >>> >>> 44-121-210-9025 >>> >>> 0808-238-6029 >>> >>> UNITED KINGDOM >>> >>> GLASGOW: >>> >>> 44-141-202-3225 >>> >>> 0808-238-6029 >>> >>> UNITED KINGDOM >>> >>> LEEDS: >>> >>> 44-113-301-2125 >>> >>> 0808-238-6029 >>> >>> UNITED KINGDOM >>> >>> LONDON: >>> >>> 44-20-7108-6370 >>> >>> 0808-238-6029 >>> >>> UNITED KINGDOM >>> >>> MANCHESTER: >>> >>> 44-161-601-1425 >>> >>> 0808-238-6029 >>> >>> URUGUAY >>> >>> >>> >>> >>> >>> 000-413-598-3421 >>> >>> USA >>> >>> >>> >>> 1-517-345-9004 >>> >>> 866-692-5726 >>> >>> VENEZUELA >>> >>> >>> >>> >>> >>> 0800-1-00-3702 >>> >>> VIETNAM >>> >>> >>> >>> >>> >>> 120-11751 >>> >>> >>> >>> >>> <USING THE ADOBE CONNECT ROOM.pdf><Open house meeting with CBI and the EPDP team .ics 17 Sept.ics>_______________________________________________ >>> Ntfy-gnso-epdp-team mailing list >>> Ntfy-gnso-epdp-team(a)icann.org <mailto:Ntfy-gnso-epdp-team@icann.org> >>> https://mm.icann.org/mailman/listinfo/ntfy-gnso-epdp-team <https://mm.icann.org/mailman/listinfo/ntfy-gnso-epdp-team> > > Visit our new website: cbi.org <http://cbi.org/> y en español www.cbi.org/es/ <http://www.cbi.org/es/> > ___ > David Plumb > Director, América Latina > Consensus Building Institute > +1 917 608 9056 > +56 9 6733 3088 > dplumb(a)cbi.org <mailto:dplumb@cbi.org> > Skype: david.s.plumb > www.cbi.org/es/ <http://www.cbi.org/es/>

1 0

Re: [Gnso-epdp-team] Section 4.4.8
by Hadia Abdelsalam Mokhtar EL miniawi 17 Sep '18

17 Sep '18

Hi Amr and All, I don't think that a final agreement was actually reached on moving items 4.4.2, 4.4.8, 4.4.9 and 4.4.10 from under the header “Purposes for Processing gTLD Registration Data”. The whole confusion in my opinion comes from two considerations the first is our lack of understanding of the interests which lets us sometimes put some interests that are typically ICANN purposes as third party purposes and the second is that when we talk about data processing we mix collection with disclosure. Recital 47 of the GDPR states that " The processing of personal data strictly necessary for the purposes of preventing fraud also constitutes a legitimate interest of the data controller concerned" Therefore fraud prevention constitutes a legitimate interest, and recital 49 of the GDPR states that the necessary and proportionate processing for network security also constitutes a legitimate interest. So when we speak about the original text of 4.4.8 "Supporting a framework to address issues involving domain name registrations, including but not limited to: consumer protection, investigation of cybercrime, DNS abuse, and intellectual property protection;" First we should not deduce that the text speaks only about the access, in order to have a framework through which access can be provided you should also have the data itself (that is the collection of the data). Second I would argue that the collection of the data for the above purpose is not only a third party's purpose but it is also an ICANN purpose As for the difference between a framework and a model, a framework is a guide or some principles that make you implement the model, while the model is the tool itself. I would rather see the actual model than just the principles. From: Amr Elsadr [mailto:aelsadr@protonmail.ch] Sent: Thursday, September 13, 2018 2:03 PM To: Arasteh Cc: Hadia Abdelsalam Mokhtar EL miniawi; gnso-epdp-team(a)icann.org Subject: Re: [Gnso-epdp-team] Section 4.4.8 Hi Hadia and Kavouss, The volunteer team working on 4.4.8 did so with the understanding that sections 4.4.2, 4.4.8, 4.4.9 and 4.4.10 would be moved out from under the header “Purposes for Processing gTLD Registration Data”. This was following Kurt’s email to the EPDP list on 4 September, titled “Project Plan Adjustments and Policy Organization”. We did consider an earlier suggestion by Mark; to split the processing purposes to two lists, one to achieve the purposes of controllers and one of third-parties. However, we did not pursue this too aggressively. Speaking for myself, I agree that 4.4.8 in both its original and proposed altered forms do not describe purposes for processing (for any party). I am not sure why a “model” would be preferable to a “framework”, so if you could elaborate on why you believe it to be more specific, I would be grateful. Within NCSG, we have considered both these terms, as well as others such as “Methodology” and “Mechanism”. We haven’t settled on any one, just yet. As Alex suggested in his original email, this is still a tentative proposal. We like it, or at least prefer it to other alternatives previously suggested, but we’re not exactly married to it just yet. :-) Thanks. Amr On Sep 13, 2018, at 12:49 PM, Arasteh <kavouss.arasteh(a)gmail.com<mailto:kavouss.arasteh@gmail.com>> wrote: Dear All I agree almost with what Hadia said Kavouss Sent from my iPhone On 13 Sep 2018, at 10:45, Hadia Abdelsalam Mokhtar EL miniawi <Hadia(a)tra.gov.eg<mailto:Hadia@tra.gov.eg>> wrote: Hi All, Dear Alex and Amr, First off thank you for your effort and time on this proposal. But are you saying that among the purposes of the processing of the data is the " identification of third-parties with legitimate interests". This is surely not one of the purposes for the processing of the data therefore a suggest removing it. So my suggestion would be. 4.4.8 Supporting a Model that provides access to parties with legitimate interests grounded in legal bases to Registration Data relevant to addressing specific issues involving domain name registrations; such as issues related to consumer protection, investigation of cybercrime, DNS abuse and intellectual property protection. I put model as I think it is more specific but I am fine with using the term framework if you see it more appropriate. I also suggest adding "such as issues related to" which would serve to provide examples of third parties with legitimate interest. Kind Regards Hadia From: Gnso-epdp-team [mailto:gnso-epdp-team-bounces@icann.org] On Behalf Of Alex Deacon Sent: Tuesday, September 11, 2018 10:34 PM To: gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Subject: [Gnso-epdp-team] Section 4.4.8 Hi All, As you know a group of us has been working to recommend an update to Section 4.4.8 of the temp spec. While we haven't come to full agreement on the update, we are pretty close and wanted to share the current/tentative output of the volunteer team with the broader team. 4.4.8 Supporting a framework that enables identification of third-parties with legitimate interests grounded in legal bases, and providing these third-parties with access to Registration Data relevant to addressing specific issues involving domain name registrations related to consumer protection, investigation of cybercrime, DNS abuse and intellectual property protection. The non-bold text was suggested by Amr/NCSG and the added bold text was an updated suggested by me/IPC and supported by the BC. Giving it a re-read again today I think additional word-smithing could be warranted, but for now I will resist and step away and let others share their thoughts. Alex -- ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team

4 6