September 2018 - Gnso-epdp-team

Proposed Agenda - EPDP Team Meeting #13 - 13 September at 13.00
by Caitlin Tubergen Sept. 12, 2018

Sept. 12, 2018

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, Marika, Berry and Caitlin ============ EPDP Meeting #13 Agenda Thursday, 13 September 2018 Roll Call & SOI Updates (2 minutes) 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 at 13.00 UTC Other updates, if applicable Review data matrix formed from RDS work and Thomas’s chart (50 minutes) Objective of discussion: Charter questions b1 and b2 (collection of data by registrar) to be answered (or considered) in substantive discussion. High-level overview of chart Discuss proposed amendments to chart Note: relevant charter questions: · b1) What data should registrars be required to collect for each of the following contacts: Registrant, Tech, Admin, Billing? · b2) What data is collected because it is necessary to deliver the service of fulfilling a domain registration, versus other legitimate purpose as outlined in part (A) above? Agree on next steps Introduction to Appendix A (50 minutes) Objection of discussion: Charter questions f1 - f3 (publication of data by registry/registrar) to be answered (or considered) in substantive discussion; EDPB advice re: collection of full WHOIS data and registration of legal persons to be considered in substantive discussion. Substantive discussion on §§2 – 4 Note: relevant charter questions: · f1) Should there be any changes made to registrant data that is required to be redacted? If so, what data should be published in a freely accessible directory? · 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? Agree on next steps Confirm action items and questions for ICANN Org, if any (5 minutes) Wrap and confirm next meeting to be scheduled for Tuesday 18 September at 13.00 UTC.

3 3

Slides - EPDP Team Meeting #13 - 13 September at 13.00
by Marika Konings Sept. 12, 2018

Sept. 12, 2018

Dear All, Please find attached the slides for Thursday’s meeting. In relation to agenda item 4 (Introduction to Appendix A), please make sure to have the DSI for Appendix A handy (see https://community.icann.org/x/ExxpBQ) Similarly, the data matrix for item 3 can be found on Thursday’s meeting page: https://community.icann.org/x/2gONBQ (under background documents). Best regards, Caitlin, Berry and Marika From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Tuesday, September 11, 2018 at 22:54 To: GNSO EPDP <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #13 - 13 September at 13.00 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, Marika, Berry and Caitlin ============ EPDP Meeting #13 Agenda Thursday, 13 September 2018 1. Roll Call & SOI Updates (2 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 at 13.00 UTC * Other updates, if applicable 1. Review data matrix formed from RDS work and Thomas’s chart (50 minutes) Objective of discussion: Charter questions<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…> b1 and b2 (collection of data by registrar) to be answered (or considered) in substantive discussion. * High-level overview of chart * Discuss proposed amendments to chart * Note: relevant charter questions<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>: · b1) What data should registrars be required to collect for each of the following contacts: Registrant, Tech, Admin, Billing? · b2) What data is collected because it is necessary to deliver the service of fulfilling a domain registration, versus other legitimate purpose as outlined in part (A) above? * Agree on next steps 1. Introduction to Appendix A (50 minutes) Objection of discussion: Charter questions<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…> f1 - f3 (publication of data by registry/registrar) to be answered (or considered) in substantive discussion; EDPB advice<https://www.icann.org/en/system/files/correspondence/jelinek-to-marby-05jul…> re: collection of full WHOIS data and registration of legal persons to be considered in substantive discussion. * Substantive discussion on §§2 – 4 * Note: relevant charter questions: · f1) Should there be any changes made to registrant data that is required to be redacted? If so, what data should be published in a freely accessible directory? · 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? * 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 0

REMINDER Re: Applications for ICANN63 Travel Support - deadline 13 September 2018
by Marika Konings Sept. 12, 2018

Sept. 12, 2018

Reminder – the deadline for applications is Thursday 13 September. To facilitate your planning, here is the list of EPDP Team meetings scheduled for ICANN63: Saturday 20 October 2018 08:30 - 18:30: EPDP Team F2F meeting Sunday 21 October 2018 17:00 - 18:30: EPDP team prep for HIT session Monday 22 October 2018 15:15 - 16:45: HIT: EPDP on the Temporary Specification for gTLD Registration Data - Review of Draft Report & Recommendations Wednesday 24 October 2018 17:00 - 18:30: EPDP Team Thursday 25 October 2018 08:30 - 10:15: EPDP Team Best regards, Marika From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Thursday, September 6, 2018 at 10:50 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Applications for ICANN63 Travel Support - deadline 13 September 2018 Dear All, As discussed during the meeting, please find attached the requirements, criteria and process to apply for travel support for ICANN63. The deadline for applications is Thursday 13 September. 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

Data Processing and data disclosure
by Kavouss Arasteh Sept. 11, 2018

Sept. 11, 2018

| Dear Thomas, In discussing Data Processing Data Disclosure today *Let me bring to your kind attention the followings;:* *Some elementary dedfinition of data proccessing* *"Data processing is t**he conversion of data into usable and desired form. **This conversion or “processing” is carried out using a predefined sequence of operations either manually or automatically. Most of the data processing is done by using computers and thus done automatically. The output or “**processed”** data can be obtained in different forms like image, graph, table, vector file, audio, charts or any other desired format depending on the software or method of data processing used * Data processing may involve - Validation – Ensuring that supplied data is correct and relevant. - sorting – "arranging items in some sequence and/or in different sets." - Summarization – reducing detail data to its main points. - Aggregation – combining multiple pieces of data. - Analysis – the "collection, organization analysis, interpretation and presentation of data." - Reporting – list detail or summary data or computed information. - Classification – separation of data into various categories. Data processing also referred to as "the collection and manipulation of items of data to produce meaningful information. In this sense it can be considered a subset of *information processing *, "the change (processing) of information in any manner detectable by an observer." Having said that I wish to recall that : 1. you referred to Article 2 of GPDR stating that data proccessing is associated with sata disclosure in that Article.May you kindly advise which part of Article 2 such reference is made 2. You talked about data disclosure while we were discussing Data Access or Data Transfer these are totally different things 3. If anyone says that Data Transfer or data access is part of data process, it is not totally valid .It is preferable that analysis of these two totally different issues be done from technical point of view and are left to technical people One can once collects data does make nothing or either transfer that unprocessed data to a recipient or record that data elsewhere . That entity could also process the date (,Data Processing ) as described above. I therefore request you to kindly make difference between " Data Process" , ",Data transfer " which may roughly referred as " Data Transfer ". One should allow the expert in data Communication express their views without misleading by mixing " Data Process" , ",Data transfer " which may roughly referred as " Data Transfer ". When people refers to GDPR needs to recognized that the authors were mostly administrative and legal people without engineering background. They normally good to write theoretical text in form of policy without acknowledging their implementations For some of us data Access may have little sense whereas for many others the purpose of Data Access , among other things are law enforcement, combating cybercrime, countering cyber-attack and preserve the security, stability and resiliency of DNS not merely from preservation of commercial interests but for establishing/ maintaining public order Regards Kavouss

1 0

Recordings, Attendance & AC chat from the GNSO Temp Spec gTLD RD EPDP held Tuesday, 11 September 2018
by Terri Agnew Sept. 11, 2018

Sept. 11, 2018

Dear all, Please find the attendance and AC chat attached to this email. The MP3 and AC recording below from the GNSO Temp Spec gTLD RD EPDP call held on Tuesday, 11 September 2018 at 13:00 UTC. These have also been posted on the agenda wiki page: https://community.icann.org/x/1gONBQ MP3: https://audio.icann.org/gnso/gnso-epdp-gtld-registration-data-specs-11sep18… AC Recording: https://participate.icann.org/p3bt85i37p4/ ** 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

Notes and action items from today's EPDP Team Meeting - 11 September 2018
by Marika Konings Sept. 11, 2018

Sept. 11, 2018

Dear All, Below, please find notes and action items from today’s EPDP Team Call. As a reminder, our next meeting will be Thursday, 13 September, 13:00 UTC. Best regards, Caitlin, Berry, and Marika =============== EPDP Team Meeting #12 Tuesday, 11 September 2018 Notes and Action Items High-level Notes/Actions: Action item #1: EPDP Team to review slides in relation to the updates (especially with regard to scheduling of topics going forward) from the EPDP Team Chair and share any comments / questions with the mailing list. Action item #2: All members, alternates and liaisons to complete the GDPR training as soon as possible but no later than 17 September. Action item #3: GDPR session with Becky Burr scheduled for 18 September. EPDP Team members to submit questions in advance to allow for adequate preparation. The session time will be posted as soon as it is available. Action item #4: EPDP Leadership team to submit triage report to GNSO Council. Action item #5: EPDP Team to review outstanding action items - see https://community.icann.org/x/NwSNBQ Action item #6: EPDP Team to review email from Kurt re. Registrar purposes (see https://mm.icann.org/pipermail/gnso-epdp-team/2018-September/000337.html) and provide input by Friday 14 September at 19.00 UTC at the latest. Action item #7: EPDP Team to review overview of purposes table and provide input on whether this provides an accurate picture. Focus should be on the purposes for collection and other processing (Registrar, Registry and ICANN), but not access (Third party interests) as these will be considered in further detail in the context of the standardized access discussion. Also consider whether purposes are sufficiently specific? Team input to commence now and will finishby 19.00 UTC on Friday 14 September. Thomas and Benedict will take that input to create an agenda for the Tuesday meeting. Action item #8: Support team to put overview of purposes table into google doc to facilitate input from EPDP Team. Action item #9: Support team to collate RySG proposal and Margie's proposal into one document. Action item #10: EPDP Team to provide input at the latest by Friday 14 September 19.00 UTC on Margie's proposal as well as RySG proposal in relation to Appendix C in view of wrapping up this discussion during next Tuesday's meeting. Questions for ICANN Org from the EPDP Team: None All Action items: Notes & Action items These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/2IpHBQ. 1. Roll Call & SOI Updates * Attendance will be taken from Adobe Connect * Please remember to mute your microphones when not speaking, and state your name before speaking for transcription purposes. * Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. 2. Welcome and Updates from EPDP Team Chair Action item #1: EPDP Team to review slides in relation to the updates from the EPDP Team Chair and share any comments / questions with the mailing list. Enhanced working methods * Received many comments about diving into substance and deal with administrative matters over email. * See proposed enhancements outlined in the slides. It may feel like hopping around, but the objective is to create more time for review and discussion. Update on status of GDPR training Action item #2: All members, alternates and liaisons to complete the GDPR training as soon as possible but no later than 17 September. Action item #3: GDPR session with Becky Burr scheduled for 18 September. EPDP Team members to submit questions in advance to allow for adequate preparation. Triage report * completed and will be submitted to GNSO Council. Action item #4: EPDP Leadership team to submit triage report to GNSO Council. Action item #5: EPDP Team to review outstanding action items - see https://community.icann.org/x/NwSNBQ Other updates, if applicable * EPDP Timeline - note there are 10 meetings remaining to ICANN63. Little time remaining to come to agreement on recommendations for Initial Report. * Any ideas / suggestions on how to expedite progress are welcome. 3. Next steps: Section 4, Appendix C * Work done by Benedict and Thomas - section 4.4 to be subdivided into parts: * Registrar purposes for processing data * Registry purposes for processing data * ICANN purposes for processing data * Third-party purposes for processing data * See also email circulated by Kurt in relation to registrar purposes. Idea is to put these into google doc so further input can be provided and hopefully can be finalized shortly. * Document prepared by Benedict and Thomas: none should be taken as carved in stone. Should be able to revisit language in the matrix. Other teams are working on some of the sections on this list. Objective is to obtain more clarity about the purposes and whose purposes those are - who is the group / entity pursuing a certain purpose. Some may need to be further clarified and/or regrouped. This should be taken as a first step. * EPDP Team encouraged to speak up where they disagree so that those issues can be addressed. * Is a registrant column needed? Shouldn't registrant at a minimum be able to verify independent of their own registrar what information is stored about them? The information right is enshrined in the GDPR so that is already a legal right. Purposes are for controllers as such, Registered Name Holder may not need to be added. * Aiming to group certain purposes together. * Being able to identify patterns of abusive registrations is a technique not a purpose, similar to the supporting a framework for research access. Consider removing it. * Helpful starting point. * Concern about enabling the prevention and detection of cybercrime - revised draft language is not an ICANN purpose but a third party one. Could open the door to collect additional data which may not be supported by ICANN's mission. * ICANN purposes broadly define the reasons for collection. Rather than to exhaustively try to list third party interests, acknowledge that those exists and ask third parties to act as controllers for the data that they access / process. In that way, they are legally responsible - probably better suited for the access model discussion. * Reflecting the rights of a Registered Name Holder - any objection to accepting this as a purpose pursued by Registrar, Registry and ICANN purpose? Isn't this also a purpose of the registered name holder? Consider adding an additional column. To be updated in next iteration. Agreement that this is a purpose that is pursued by Registry, Registrar, ICANN as well as Registered Name Holder. * Providing access to accurate, reliable and uniform Registration Data consistent with GDPR - proposed to be parked until the group discusses disclosure / access. * Need to understand what the definitive purposes / legitimate interests are. May need further guidance on the legitimate interests as otherwise it will not be possible to get clarity around this. * Consider using a more generic term instead of referring directly to GDPR. * Enabling a reliable mechanism for contacting the Registered Name Holder * Enabling a reliable mechanism for identifying the Registered Name Holder * Interests vs purposes - need to clarify what this means. When we talk of 'third party interests' (note the plural) that is a generic recognition that third parties have an interest in the data * Are there situations in which RNH has contacted the Registry, for example in the case of cybersecurity, malware situation? LE and security researchers may prefer to work with registries in certain circumstances. * Consider whether table should be in google doc or word to facilitate input and collection of comments. Support team to put table in google doc to facilitate input. Action item #6: EPDP Team to review overview of purposes table and provide input on whether this provides an accurate picture. Focus should be on the purposes for collection and other processing (Registrar, Registry and ICANN), but not access (Third party interests) as these will be considered in further detail in the context of the standardized access discussion. Also consider whether purposes are specific enough? Input to be circulated by 19.00 UTC on Friday 14 September. Action item #7: Support team to put overview of purposes table into google doc to facilitate input from EPDP Team. Appendix C * See email circulated by Margie proposing retention of certain aspects of Appendix C. Benefit to the community that certain principles are addressed, especially where those specifically apply to WHOIS. For example, principles for disclosure. Maintain transparency and accountability in relation to certain sections. Need to add on standard terms in relation to third party access. * Summarizing existing legislation but not using exact references is problematic. Similarly, if further updates are made in the future. This creates uncertainty and difficulties. * Published guidance will be helpful, but this may not need to go into the agreements? This guidance could help inform implementation where details would be fleshed out. * Need additional time to review proposed retention of certain aspects - provide further input on the list or either on a future call. * Are terms/principles to third parties who access non-public data for consideration now or during standardized access model? Are part of Appendix C now so should be considered here. Does that mean that access is discussed prior to gating questions being answered? How to memorialize that there will be third party access without necessarily going into the details and run ahead of the standardized access model conversation. Objective here is that it confirms that there will be an access process and that contracted parties are required to adhere to it. "Requiring" contracting parties to adhere to an access model presumes that the model itself complies with the law(s). * Should chart, in updated form, be retained? Is it helpful to have there? Mixed responses. May not be appropriate for inclusion in a contract. Could serve as an illustrative document. EPDP Team is tasked to develop a policy so its recommendations may not necessarily translate directly into contractual requirements, there may be other ways in which implementation is carried out. * No agreement yet on a framework for access, only agreement for now for Rr and Ry to provide access as outlined in temporary specification. Action item #8: Support team to collate RySG proposal and Margie's proposal into one document. Action item #9: EPDP Team to provide input at the latest by Friday 14 September 19.00 UTC on Margie's proposal as well as RySG proposal in relation to Appendix C in view of wrapping up this discussion during next Tuesday's meeting. 4. Review data matrix formed from RDS work and Thomas’s chart High-level overview of chart Discuss proposed amendments to Chart Agree on next steps * Deferred to next meeting 5. Introduction to Appendix A * Deferred to next meeting 6. Confirm action items and questions for ICANN Org, if any 7. Wrap and confirm next meeting to be scheduled for Thursday 13 September at 13.00 UTC. 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-…>.

2 1

Meeting Invitation / Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Thursday, 13 September 2018 at 13:00 UTC
by Andrea Glandon Sept. 11, 2018

Sept. 11, 2018

Dear all, Non-members can follow the EPDP call taking place on Tuesday’s and Thursday’s at 13:00 UTC via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, 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…> Agenda wiki page: https://community.icann.org/x/2gONBQ Kind Regards, Andrea Glandon

1 0

Email discussion for THURSDAY meeting
by Kurt Pritz Sept. 11, 2018

Sept. 11, 2018

Hi Everyone: In preparation for THURSDAY’s call, I have been through the notes and the distillation of them since the last meeting where we discussed §4.4 of the Temporary Specification. In order to make headway on a few issues, I wish to make a few comments and pose a few questions. I am not taking any side in these questions but think there is the opportunity is a few cases to narrow issues down so they can be resolved to the entire group’s satisfaction. I am admittedly cherry-picking some issues that might be resolved on email. If the §4.4 subsection is not listed here, I think a meeting discussion is required. I note that the discussion we had in Thursday’s meeting was preliminary and additional thoughts can be introduced at any time. I also note that these were the proposals made by the registrar representatives and not adequately considered by all at the time of the meeting. Perhaps the support team can set thesis up in a comment-only google doc - one for each topic - to create a tool for discussing these. Issues below, thanks and regards, Kurt 1). §4.4.1 thus far, acceptable as written in the Temporary Specification: "Reflecting 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;” Is there disagreement with this conclusion by any group? 2) In §4.4.3, it was recommended that in "Enabling a reliable mechanism for identifying and contacting the Registered Name Holder for a variety of legitimate purposes more fully set out below,” that the “identifying' be lined out. The Business Constituency and ALAC recommended that “identifying” be left in the subsection. The initial question for the ALAC and BC is to flesh out this point of view and describe what purpose is lost by taking the word “identifying” out (or gained by having it included)? I.e., describe a set of circumstances where, in the case that “identifying” was left out, an opportunity to correct / avoid illegal or abusive behavior would be lost. With that legitimate purpose confirmed, those supporting the removal of "identifying” (NCSG and registrars) would be asked to describe how including “identifying” unnecessarily reveals personal data that the word “contacting” does not. A brief look at definitions and synonyms for “identifying” indicates that it is a manner in which to establish contact - so without being conclusory, this might work out the same from a data perspective in either case. 3) §4.4.4 thus far, it is agreed to remove this: "Enabling a mechanism for the communication or notification of payment and invoicing information and reminders to the Registered Name Holder by its chosen Registrar;" 4) In §4.4.5:. "Enabling a mechanism for the communication or notification to the Registered Name Holder of technical issues and/or errors with a Registered Name or any content or resources associated with such a Registered Name;” It was recommended that “content” be taken out, with some other phrases to result in: “Enabling a mechanism for the communication or notification to the Registered Name Holder of technical issues and/or errors with a Registered Name or any content or resources associated with such a Registered Name;” . This was found to be generally acceptable except that ALAC requested that we, "ask ICANN Org to provide more context on why "content" was added to this section.” That is being done and the issue discussion will await that response. 5). In §4.4.6, it was recommended that the section be deleted, "Enabling a mechanism for the Registry Operator or the chosen Registrar to communicate with or notify the Registered Name Holder of commercial or technical changes in the domain in which the Registered Name has been registered” ALAC recommended that the paragraph should remain, stating, "Reference to registry is still relevant.” The question for registries and registrars: If some registries have a legitimate interest in personal data, is this the section where that purpose is described? If yes, should it remain in this form or an alter form? 6) In §4.4.10, it was recommended that the section be deleted, "Facilitating the provision of zone files of gTLDs to Internet user,” because, "registrars are not aware of a registrar purpose for publication of zone files.” There were no comments regarding this section. Question: Does anyone object to this deletion? If yes, or what purpose is this data to be put? 7) In §4.4.11, it was recommended that the section be deleted, "Providing mechanisms for safeguarding Registered Name Holders' Registration Data in the event of a business or technical failure, or other unavailability of a Registrar or Registry Operator,” because, "this is covered in registrar data escrow.” There were no comments regarding this section. Question: Does anyone object to this deletion? 8) Regarding §4.4.12. "Coordinating dispute resolution services for certain disputes concerning domain names,” It was suggested that this be changed to,"Coordinating dispute resolution services for URS and UDRP” Both the IPC and ALAC indicated that "dispute resolution can be used in other contexts,” and "We cannot leave just these two DRPs.” The question for IPC, ALAC and presumably others is to flesh out this point of view and describe a set of circumstances where the registrar edition would be inadequate. Is it to anticipate new policies or practices such as UDRP and URS or is it to address domain disputes in a different way? By identifying those additional purposes, we might be able to apply Thomas’ and Benedict’s construct to address those purposes.

3 2

Proposed Agenda - EPDP Team Meeting #12 - 11 September at 13.00 UTC
by Marika Konings Sept. 11, 2018

Sept. 11, 2018

Dear All, Please find below the proposed agenda for Tuesday’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 #12 Agenda Tuesday, 11 September 2018 1. Roll Call & SOI Updates 2. Welcome and Updates from EPDP Team Chair * Enhanced working methods * Update on status of GDPR training * Triage report * Review outstanding action items * Other updates, if applicable 3. Next steps: Section 4, Appendix C 4. Review data matrix formed from RDS work and Thomas’s chart * High-level overview of chart * Discuss proposed amendments to Chart * Agree on next steps 1. Introduction to Appendix A 2. Confirm action items and questions for ICANN Org, if any 3. Wrap and confirm next meeting to be scheduled for Thursday 13 September at 13.00 UTC.

7 6

Meeting duration
by Arasteh Sept. 11, 2018

Sept. 11, 2018

Dear Kurt I wish to once again reiterate my initial request repeated several time that A) Having two meeting each two hours with one day in between us bothering B) the two hours duration is not supported since after 90 mints everybody ,in particular,yourself becomes tired and the efficiency of the meeting diminished Pls seriously consider that and at least reduce the duration to 90 mints Regards Kavouss Sent from my iPhone

2 1