October 2019 - Gnso-epdp-team

Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Thursday, 10 October 2019
by Terri Agnew Oct. 8, 2019

Oct. 8, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Thursday, 10 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/yyuhrges Agenda Wiki: https://community.icann.org/x/AYYCBw 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…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Terri If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann Enter passcode on telephone: 7349

1 0

For your review - updated accreditation building block
by Marika Konings Oct. 7, 2019

Oct. 7, 2019

Dear EPDP Team, In line with the action item assigned to the staff support team, we’ve gone ahead and updated the accreditation building block (see https://drive.google.com/a/icann.org/file/d/1u6MI1HI3_0jxHul4GVTsWDIp8SiMm_…) This updated version aims to reflect the deliberations to date as well as the different contributions provided. You will note that we’ve attempted to separate policy recommendations from implementation guidance in relation to this topic. This building block is expected to be the main agenda item for Thursday’s meeting (10 October), so please make sure to review in advance of the call. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

2 1

Updated building block E - retention and destruction of data
by Caitlin Tubergen Oct. 7, 2019

Oct. 7, 2019

Dear EPDP Team: Further to EPDP Support Staff’s action, please find the updated version of Building Block E (retention and destruction of data). The edits intend to capture the Team’s discussion from the last meeting. As the building block is in the form of a Google Doc, please provide suggested edits directly in the document by Monday, 7 October. Thank you. Best regards, Marika, Berry, and Caitlin

6 5

Proposed Agenda - EPDP Team Meeting #23 - Tuesday 8 October at 14.00 UTC
by Marika Konings Oct. 7, 2019

Oct. 7, 2019

Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which has been scheduled for Tuesday 8 October at 14.00 UTC. Best regards, Caitlin, Berry and Marika EPDP Phase 2 - Meeting #23 Proposed Agenda Tuesday, 8 October 2019 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) a) Welcome of new ICANN Org liaison – Eleeza Agopian b) Accreditation building block homework c) Status of building blocks<https://community.icann.org/x/k5ICBw> 4. Finalization of questions to ICANN Org / ICANN Board (15 minutes) a) Introduction of letter developed by CPH (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-October/002580.html) b) Feedback from EPDP Team c) Confirm next steps 5. Acceptable use policy<https://docs.google.com/document/d/1irlBo_oE5WqxTir5URaxlpPWTn17cnjDz72L79g…> (building block d & h) – Second reading (15 minutes) a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 6. Criteria & content of requests<https://docs.google.com/document/d/1EOZY0oNiBrtAOZeka3LCMwyMiaGjSJLVDTcyVl4…> (building block a) – Second reading (15 minutes) a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 7. Receipt of acknowledgement<https://docs.google.com/document/d/1dSepSTKmaceu3oB1YLpp1wgdrJoERIQq7fg_8Ud…> (building block k) – second reading (if time allows) a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 8. Wrap and confirm next EPDP Team meeting (5 minutes): a) Thursday 10 October 2019 at 14.00 UTC b) Confirm action items c) Confirm questions for ICANN Org, if any 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

**Reminder** Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Tuesday, 08 October 2019
by Julie Bisland Oct. 7, 2019

Oct. 7, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 08 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/yx8p2vkf [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yx8p2vkf&d…> Agenda Wiki: https://community.icann.org/x/HZACBw 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…> Meeting Audio Cast (for 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Terri If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> Enter passcode on telephone: 7349

1 0

Proposed letter from EPDP to ICANN board
by Anderson, Marc Oct. 3, 2019

Oct. 3, 2019

All, Pursuant to action item #8 from the LA face-to-face meeting (see below), the Contracted party team members drafted the attached letter to the ICANN Board. The goal as stated in the letter is to seek input from the Board on the scope of operational responsibility and level of liability (related to decision-making on disclosure of non-public registration data) they are willing to accept on behalf of the ICANN organization along with any prerequisites that may need to be met in order to do so. Best, Marc From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> On Behalf Of Caitlin Tubergen Sent: Thursday, September 12, 2019 8:39 PM To: gnso-epdp-team(a)icann.org Subject: [EXTERNAL] [Gnso-epdp-team] High-level notes and action items - EPDP Team F2F - 9-11 September Dear EPDP Team: Below, please find high-level notes and action items from the face-to-face meeting. As a reminder, the next EPDP Phase 2 meeting will be Thursday, 19 September at 14:00 UTC. The Legal Committee will meet on Tuesday, 17 September at 14:00 UTC. Wishing everyone safe travels home. Best regards, Marika, Berry, and Caitlin -- Action Items 1. Alex Deacon, Milton Mueller and other willing volunteers to draft a write up of a potential accreditation model, taking into account the Team’s F2F discussions, in advance of the Thursday, 19 September meeting. 2. IPC, BC, SSAC, and GAC reps to separately draft a vision for their “ideal accreditation model” in order to assist the group with what the baseline accreditation requirements could be as well as the attendant benefits of accreditation within the architecture of an SSAD by Wednesday, September 18. 3. Support Staff to create a table (in the form of a Google Doc) which includes a column for each lawful basis and a column for what a requesting party would be required to provide in its request, what is the expected response time, is automation likely, what are the standardized categories that may fall within that lawful basis, etc. Following receipt of the table, the EPDP Team members to populate the contents of the table. If there are commonalities, policy recommendations can be drafted accordingly. 4. Support staff to create a Google Doc in which EPDP Team Members are to review and consider the types of disclosure decision models (in other words, who is making the ultimate determination to disclose non-public registration data - contracted party or ICANN) and what would make these options acceptable to the different groups by Thursday, September 19. 5. EPDP Team to review the legal memos and come back with the most relevant points that need to be factored in as the Staff Support Team produces the 1.0 draft by Thursday, September 19. 6. James and Mark Sv. to work together on a revised proposal for Building Block L (SSAD query policy) by Thursday, September 19. When discussing updates to Building Block L, Team members to consider if it is within the Team’s charter to continue discussing this issue. 7. Matt C. to review the legal advice on how to perform the balancing test and update Alan Woods’ initial balancing test document into a simple guide to conduct the balancing test to be included in the next iteration of the zero draft by Thursday, September 19. 8. Contracted party Team members to draft letter to ICANN Board, outlining scenarios discussed, including where the disclosure decision lies within the SSAD, and inquire whether there are any options the Board would not be amenable to. High-level Notes ACCREDITATION–Building Block F Straw Proposals Presented prior to Discussion: Milton Mueller and Alex Deacon Outcome / Agreements * EPDP Team did not agree on accreditation process or assignments; however, it agreed that a small group would consider the Team’s discussion during the F2F and develop a proposal for a subsequent discussion. * The EPDP Team agreed to separate authentication from authorization. The team did not agree that the accreditor would perform the authorization function. Discussion Notes Purpose ••••••••• Remove burden from entity providing disclosure ••••••••• Provide code of contract or series of contracts ••••••••• Spread liability (without diminishing protections for data subjects) ••••••••• Provide process pathway to track data / monitoring Who serves as accreditor ••••••••• Entity develops request or proposal ••••••••• Competent authority with legal basis; demonstrates consistency with Article 42 and 43 ••••••••• EPDP sets outline and principles and assessment activities Accreditor Tasks Authentication – confirm identity Establish preliminary determination on lawful basis Consider how to manage volume requests NOTE: Authorization process is not necessarily with the accreditor. Sub-team will consider whether Authorization should rest with another entity or with the accreditor or unique criteria Role: Certifying Accreditor No Agreement, options discussed: ••••••••• ICANN – difficult because they process of data ••••••••• Independent Data Trust ••••••••• DPA Role: Accreditation Body(ies) ••••••••• WIPO ••••••••• Law enforcement–each country would have one entry point. i.e. in U.S. it might be FBI or in other countries, it would be the national country. ••••••••• Europol and Interpol–agree this is not possible for law enforcement agencies, at least not for certain countries ••••••••• Limit # of accrediting bodies to be able to manage system ••••••••• Create track for entities that are not accredited Role: Auditor Agree that auditing is needed; unclear who should conduct audits Role & Process: De-Accreditation EPDP agrees that de-accreditation should be a component Accreditor must be compliant with DPAs Need to establish how to do this, such as: ••••••••• Safeguards, prevent entity from setting up shop next door ••••••••• Remedial action, i.e. may not shut down immediately, some corrective action is possible Decision to Disclose Joint Controller Who Balances? Entity with Legal Basis Options: Who Decides? {Note: EPDP did not decide on preferred option in LA. Group will consider options and potentially write a letter to Board to frame questions} JC Agreement •• Responsibilities identified in agreement; CPs cannot increase their risk •• Must be correct to manage liability / risk •• Liability is clearly defined (ICANN or CPs) •• Establish Joint and Severable Liability Contracted Parties ICANN Independent Data Trust PROS/CONS + Most accountable to data subject + Has physical access to data - Lack of consistency with hundreds of CPs applying policy to make decision to disclose - ICANN unable to indemnify CPs (maybe, shared risk possible) + Bird & Bird Memo states that CPs are controllers and retain liabilities PROS/CONS + Reduce risk of liability to CPs + Provides consistency + One party that performs decision and auditing role might be preferable + Build body of work / decisions consistently Considerations for all Options Standardized clearing house Timely Response Insurance to alleviate risk or establishing risk fund may be possible ICANN sets rules so it has to be a joint controller SSAD Not required by law Goal = predictable Easier Building Block N, Financial Sustainability Outcome: Staff to develop Draft 1.0 with implementation guidelines consistent with the F2F discussion. Note: The EPDP noted the need to make SSAD Determination and consider cost-benefit analysis before finalizing approach to financial sustainability. Set Up Cost of Providing and Making Available an Investigative Tool Cost Sharing Share cost across the system Direct and indirect beneficiaries Share costs across the system CPs contribute intangible resources via in-house staff, etc. Use Look at other Models ANTICIPATED BENEFITS: Certainty to Process Cost Savings FLIP CHARTS Each stakeholder group contributed principles / ideas to ignite the conversation. SSAC All participants have costs: * Central system = ICANN * CPs: receive, review, reply * Requestors: accreditation, query-making Issue subsidies? Letting market work RDS as basic service / core service Passing costs to requestors: May burden victims. GAC 1. Any financing model should not be profit/revenue generating 2. System should not provide financial disincentives to requestors acting on behalf of public authorities CPH 1. Any financial model should not be profit/revenue generating 2. Cost Neutral and borne by beneficiaries 3. Not a hidden tax / pass through charge to registrants / data subject 4. Integration costs represent CPH contributions ALAC Consider: ••••••••• Costs ••••••••• Cost Savings ••••••••• Accreditation costs borne by users ••••••••• Charge / Requestor: consideration of public interest exception ••••••••• Chares passed through to registrants seems inevitable (it’s part of the infrastructure) NCSG Costs [potential funder] 1. Capital / set up costs [Large Users] 2. Accreditation costs [Flat fee per time period] 3. Usage costs (per request) [per request fee, cost-based. Higher for non-accredited] 4. Insurance costs [unsure] 5. Audit / enforcements [unsure, ICANN / DPAs?] CSG OK for cost-sharing to vary by volume, requestor type, legal obligation, etc. Fees on per-request basis are problematic Must not create disincentives to costs reductions

1 1

Notes and action items - EPDP Phase 2 meeting #22 - 3 October 2019
by Caitlin Tubergen Oct. 3, 2019

Oct. 3, 2019

Dear EPDP Team, Below, please find the notes and action items from today’s call. As a reminder, the next EPDP Team call will be Tuesday, 8 October at 14:00 UTC. Best regards, Marika, Berry, and Caitlin -- EPDP Phase 2 - Meeting #22 Thursday, 3 October 2019 at 14.00 UTC Action Items ICANN org liaisons to informally share draft questions with ICANN org. Following review of CPH letter, the EPDP Team will determine if CPH draft questions should be included in a formal letter to ICANN org, ICANN Board, or both. EPDP Team to continue providing feedback (by group) into the lawful basis comparison table by Wednesday, 9 October at 16:00 UTC. EPDP Support Staff to review the feedback provided and provide a summary to the EPDP Team by Thursday, 10 October. James Bladel to provide an illustrative but non-exhaustive list of examples of illegitimate requests or requests of an abusive nature by Tuesday, 8 October. James to also consider how the list could be included in the building block I/L (query policy). (Note: Mark Sv. has offered to assist.) EPDP Support Staff to provide suggested updates to building block L (query policy) based on today’s discussion following receipt of James and Mark Sv’s updates. Notes 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/ZwPVBQ. 1. Roll Call & SOI Updates (5 minutes) · Attendance will be taken from Zoom · 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. Confirmation of agenda (Chair) · Following Chris D’s suggestion from the F2F meeting, the CPH will be circulating a draft letter to the EPDP list shortly. The draft letter includes questions to the ICANN Board. 3. Welcome and housekeeping issues (Chair) (5 minutes) a) Update from legal committee · LC met on Tuesday and continued discussing draft questions, some of which came out of the F2F meeting. · At this time, no additional questions have been agreed to. · Volunteers from the LC will be drafting high-level summaries of the legal memos from Batch 1. · The next LC meeting will be Tuesday, 15 October b) Finalization of questions to ICANN Org · Suggestion to ask these questions to the Board · Recommend referring the questions to Org, or sending to both Org and Board · Do these draft questions differ greatly from the CPH letter? · Recommend tabling this draft letter until the EPDP Team has reviewed the draft CPH letter · ICANN org needs to determine if this is a board or an org question. ICANN legal may need to be consulted on this. The EPDP Team needs an authoritative answer from ICANN on these answers. · Action: ICANN org liaisons to informally share draft questions with the org, as appropriate. Following review of CPH letter, the EPDP Team will determine if CPH draft questions should be included in a formal letter to ICANN org or the ICANN Board. c) Lawful basis input document [docs.google.com] – status · During F2F meeting, it was agreed to look at building blocks in conjunction with the lawful bases. For example, with respect to content and criteria of a request, is there a different set of information that is required for a 6(1)(d) vs. a 6(1)(e) request? · There may not be a difference in requirements b/w the lawful bases · Question: are groups still planning to provide feedback or if, alternatively, this is no longer a helpful exercise? · Tying the request to lawful basis in not a good match - it’s unnecessarily constraining the exercise. · Groups to continue providing input to the lawful basis table by 8 October, and Support Staff to summarize input for the EPDP Team. d) Status of building blocks · The building blocks are all housed on a separate wiki page · When work has been completed, the building block will be marked in green · The other objective of the status page is to show when building blocks will be discussed, and when input following a discussion is due · Because the building blocks are in Google Doc format, the EPDP Team may provide feedback in advance 4. Query Policy [docs.google.com] (building block i & l) – second/final reading (15 minutes) a) Overview of updates made in response to input received during F2F meeting (James Bladel, Mark Svancarek) b) Feedback from EPDP Team · “not legitimate or of an abusive nature” - will that be defined in this policy development phase, or is that developed in the implementation phase? · This is a question that EPDP Support Staff flagged in the Zero Draft - noting that examples would be helpful. · This question will likely be kicked down to the implementation review team; however, there is needs to be some leeway for the disclosing entity. An illustrative, but non-exhaustive list would be helpful · Consider using SSAC advice here, which was included in the BC accreditation example · One challenge is making sure everyone can understand the policy language - specificity is helpful here. Refer to SSAC advice. · This language was provided in a use case. · Just as the system can recognize abusive behavior, there needs to be flexibility for the requestor to make high-volume requests. ICANN itself may need to make high-volume requests as well. · Abusive and vexatious can be content specific. It may also be helpful to provide guidelines on what is NOT considered abusive. · If the recipient of a request, and a requestor has sent 10,000 queries and another requestor who has sent three requests, could the requestor who sent three be potentially blocked from a response while the 10,000 queries are being handled. · If there are a provider who has to answer 10,000 from one and three from another, the provider must serve all 10,003 · This building block is closely related to the financial building block, b/c this is not a free service. That may be one of the natural rate-limiting factors - payment for requests. · The language here was from the use case discussed in Marrakech. Brian and Mark had agreed to review subpoint b, but that homework may no longer be necessary. · Perhaps subpoint a and b can be combined · Keeping the two separate makes sense, but place a full stop after misuse of the system. · The language should ensure that if there is redacted data, the public data should be provided along with it. · There was a suggestion that the response should not include public data elements - it would be helpful if the inclusion of public data elements are a must, should, should not, etc. · If this system displays public and non-public data elements, it will be used for both. The concern would be that the system will be used when public data fields are sufficient. · Assuming there is a centralized system, there may well be a decision made to integrate WHOIS with the SSAD - it may be an effective way to unify those two systems - that’s an implementation decision, and it shouldn’t be forbidden · It does not make sense that anyone would build a separate system for SSAD and would not leverage the existing system. If authentication to the SSAD fails, it would simply return the public data. · Assuming that people are using the SSAD are requesting nonpublic data - it is fairly trivial to return the nonpublic information with the private information. There is framing of the topic that is invalid, specifically in reference to fee structure. One of the responsibilities of Rys and Rrs is to provide core services of WHOIS. Refer to SSAC101. Because of rate limits in the current environment, it is very hard to get public information. Tucows the second largest registrar in the world, but they limit users to one query per minute. · In principle, no objection to returning full WHOIS record along with undisclosed information. However, the people that want this are planning to set up some sort of automated query system that would use the data for anything. · Challenge is this is not a technical issue; if it is coming through SSAD, a human being has to review the request - if a public WHOIS channel, it’s automated. One query per minute, is 86,000 queries per day. If a user of the system is warranted in making 86,000 queries per day, curious as to what the entity may be using the data for. Potential solution - this is conditional - if you submit a request through SSAD and it is successful, you get the full data in return. · Proposal: The response must include the public data elements related to the domain name registration associated with the requested non-public data. · If the Team could somehow assume that there is a system in which one entity will be responsible for taking on the responses and the disclosure responsibility, the conversation could be easier. · Why does the language, “each request needs to be evaluated on its own merits” need to be here - seems like a truism · Statement should remain · What is the purpose of the footnote added by James and Mark? · The purpose is if these go forward, these are applicable to the system in the Rr’s governance with ICANN and would not eliminate their use in other products and services by companies that are contracted parties with ICANN. Other products such as SSL and hosting may have valid & legitimate reasons to share data outside of SSAD. c) Confirm next steps · Team to revisit this building block when James has provided the non-exhaustive list · Staff to reword the language re: return of public data for valid requests 5. Acceptable use policy [docs.google.com] (building block d & h) – Second reading (15 minutes) a) Overview of updates made following first reading b) Feedback from EPDP Team c) Confirm next steps 6. Criteria & content of requests [docs.google.com] (building block a) – Second reading (15 minutes) d) Overview of updates made following first reading e) Feedback from EPDP Team f) Confirm next steps 7. Wrap and confirm next EPDP Team meeting (5 minutes): a) Tuesday 8 October 2019 at 14.00 UTC b) Confirm action items c) Confirm questions for ICANN Org, if any

1 0

Post Call | GNSO Temp Spec gTLD RD EPDP – Phase 2 | Thursday, 03 October 2019 at 14:00 UTC
by Terri Agnew Oct. 3, 2019

Oct. 3, 2019

Dear all, All recordings for the GNSO Temp Spec gTLD RD EPDP – Phase 2 held on Thursday, 03 October 2019 at 14:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/-4UCBw> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript As a reminder only members and alternates can join the call, observers can join via audio cast, listen to the recordings and read the transcript afterwards. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-team/> and the main wiki page<https://community.icann.org/x/IYEpBQ>. Thank you. With kind regards, Terri

1 0

Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Tuesday, 08 October 2019
by Terri Agnew Oct. 3, 2019

Oct. 3, 2019

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 08 October 2019 at 14:00 UTC for 120 minutes. (calls will be scheduled for 120 minutes but aim to keep to 90 minutes) 07:00 PDT, 10:00 EDT, 16:00 Paris CEST, 19:00 Karachi PKT, 23:00 Tokyo JST, (Friday) 01:00 Melbourne AEDT For other times: https://tinyurl.com/yx8p2vkf Agenda Wiki: https://community.icann.org/x/HZACBw 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…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Kind Regards, Terri If needed, an option to join via telephone has been added for this meeting. **New join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.adigo.com_icann&d=D…> Enter passcode on telephone: 7349

1 0

FW: EPDP Board Liaison Appointment - Becky Burr
by Marika Konings Oct. 3, 2019

Oct. 3, 2019

Dear EPDP Team, For your information, please see the notification from Board Support below. Staff will make the necessary updates to the mailing list and discuss with Leon how to manage the transition on the legal committee. Welcome to Becky, and thanks to Leon for all his efforts! Best regards, Caitlin, Berry and Marika From: Wendy Profit <wendy.profit(a)icann.org> Date: Tuesday, October 1, 2019 at 17:12 To: Marika Konings <marika.konings(a)icann.org> Cc: David Olive <david.olive(a)icann.org>, Mary Wong <mary.wong(a)icann.org>, Secretary <secretary(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org> Subject: EPDP Board Liaison Appointment - Becky Burr Dear Marika, After a review by the Board Governance Committee (BGC), the BGC has agreed that Becky Burr will replace León Sánchez as the Board appointed member on the EPDP team. Please adjust your internal lists and ensure that the EPDP team is notified of this change and that any mailing lists you manage are adjusted accordingly. Thank you, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

8 8