June 2019 - Gnso-epdp-team - lists.icann.org

FW: Phase 2 Early Input from Business Constituency
by Margie Milam June 24, 2019

June 24, 2019

fyi From: "Mark Svancarek (CELA)" <marksv(a)microsoft.com> Date: Monday, June 24, 2019 at 7:41 AM To: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Cc: Margie Milam <margiemilam(a)fb.com>, "sdelbiancoATnetchoice.org" <sdelbianco(a)netchoice.org> Subject: Phase 2 Early Input from Business Constituency Attached is the late early input on Phase 2 from the BC. Mark + Margie + Steve

1 0

Early input and early input review tool posted
by Marika Konings June 22, 2019

June 22, 2019

Dear EPDP Team, You can find the early input received by the 21 June deadline here: https://community.icann.org/x/zIWGBg. You can also find on the same wiki page the early input review tool that the staff support team has created to facilitate your review of the input received. 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…>.

1 0

RrSG response to EPDP Team Phase 2 Early Input
by Sarah Wyld June 21, 2019

June 21, 2019

Hello team, Please find attached the RrSG response to EPDP Team Phase 2 Early Input form. Safe travels to Marrakech. -- Sarah Wyld Domains Product Team Tucows +1.416 535 0123 Ext. 1392

1 0

**Updated** ICANN65: GNSO Sessions How to Get Organized and Remote Participation Details
by Julie Bisland June 21, 2019

June 21, 2019

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN Meetings’ Team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN65 Meeting Schedule [65.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__65.schedule.icann.org_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/sYiGBg> Step 1 - Create a profile and your personalized ICANN65 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. · Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. · Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. Step 3 All sessions allowing remote participation will use Zoom rooms, which you can find on the ICANN65 Meeting Schedule [65.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__65.schedule.icann.org_…> and on the <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> GNSO Remote Participation Wiki Page<https://community.icann.org/x/sYiGBg>. There are three options to connect your audio: 1) Via VoIP, choose Computer Audio 2) Getting a dial out from Zoom to your phone, choose Call Me 3) Phoning into the audio bridge (access numbers and Meeting ID are provided for that option), choose Telephone Audio If you cannot log into the Zoom room, but wish to connect via telephone only, refer to the GNSO Remote Participation Wiki Page<https://community.icann.org/x/sYiGBg> for access numbers and individual Meeting IDs. (Updated) To listen only, find your meeting on the schedule<https://65.schedule.icann.org/> and select the audio streaming option. Step 4 Please download the mobile app by searching for “ICANN65” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Marrakech to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

Notes and action items from EPDP Meeting #7 - 20 June 2019
by Caitlin Tubergen June 20, 2019

June 20, 2019

Dear All, Please find the notes and action items from today’s EPDP Team meeting below. Safe travels to Marrakech. Best regards, Marika, Berry, and Caitlin EPDP Meeting #7 20 June 2019 Action Items Alex Deacon and Chris Lewis-Evans to develop an additional use case(s) using this template to share with the EPDP Team at the face-to-face meeting at ICANN65. Reminder to please provide feedback on the Next Steps for Priority 2 items by Friday, 28 June. 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 Remember to mute your microphones upon entry to Zoom, which is typically the first icon on the left on the bottom toolbar. Please 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. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (10 minutes) Request for additional resources for F2F meetings submitted (see https://www.icann.org/en/system/files/correspondence/drazek-to-chalaby-12ju…) · This letter was sent to the Board on 12 June 2019, and we are awaiting a response. The letter includes tentative dates for a September face-to-face meeting. · There may be an opportunity to engage ICANN org re: interaction with EDPB during ICANN65 - please review the letter forwarded from Janis to the EPDP Team shortly before this meeting. 4. Topic c: Define user groups, criteria and purposes / lawful basis per user group · Question to CPH: can CPH please respond regarding if there is any other group other than law enforcement that it believes could receive access/disclosure to non-public registration data? · CPH tried to provide very specific feedback on the purposes document. · At a high level, the CPH was hesitant to come up with positive feedback on many of the purposes due to the concern that a potential security researcher could knock on a registrar’s door and demand personal data with little specificity. · CPH does not think law enforcement needs a specific purpose, as it is already accounted for in GDPR. · The point of the feedback of CPH was not to point out that there was only one legitimate purpose. Instead, the feedback was specific to the purposes as drafted in the document. · CPH believes it cannot define what legitimate purposes are. That is not to say these may not be legitimate purposes - it depends on what is being requested and for what purpose. · It may be helpful to start with the legal basis. · From now on, the Chair asks the Team to think of how we can move this forward and come up with proposals. · Using 6(1)(f) in very limited cases is correct. The Team needs to relate the legitimate interests back to the work done in Phase 1. · Proposal to move things forward - it may be helpful to sequence things slightly differently. It may be helpful to start with civil claims. Public authorities cannot use 6(1)(f). That will primarily put our focus on 6(1)(c) for law enforcement. The law enforcement needs a legal basis for making that request. Non-European law enforcement could use 6(1)(f), which means it could be easier for non-European law enforcement to receive data. It would be helpful to get clarity from outside counsel on European vs. non-European law enforcement. · What is consistent with ICANN’s mission? There could be millions of legitimate interests that are consistent with ICANN’s mission. One thing the Team needs to ensure is that it doesn’t stray from ICANN’s narrow mission. · When the Team says “this is not a purpose because a balancing act will be performed” this presents a definitional problem. Regarding the assertion that you cannot show up and say that you are a security researcher and you need data - that seems to be an orthogonal discussion. From a policy perspective, once you have a discussion that the purpose is theoretically lawful, you can have a policy discussion about bias. · The Team should use the term purpose instead of legitimate interest. The other questions are ancillary questions. At this time, the Team should decide what the purposes are. This work is clearly within ICANN’s scope. · The GDPR defines in the recitals some purposes for security. When someone makes a request, the requestor needs to state their legitimate purpose. · The CPH comments were not meant to be obstructionist. If the Team is discussing legitimate interests, we are only talking about one thing - 6(1)(f). Disagree that we should use the word purposes just because it was used in the Charter - the Charter was not drafted by GDPR experts. · There is no purpose or group that is guaranteed, but we do need to start somewhere. · Some have objected to the categorization of all third party request being 6(1)f. In certain cases 6(1)b may also apply some have argued. However, whether or not 6(1)b is applicable may depend on who the controller is for the data. This may be an issue for which further legal guidance may be required? · Public interest would require a legal act vesting ICANN / CPs with performing a task in the public interest. There does not seem to be any such legal act at this stage. · What about 6(1)d - vital interest of the data subject or another natural person? Can this also be used by LE or other parties? EPDP Team should further consider what other legal basis can be used. · Proposed approach forward: move this into real life cases, similar to how this has done for the review use case. – Review use case prepared by Thomas Rickert (60 minutes) a. Overview of use case - Trademark owners requesting data to take legal action against cybersquatters (Thomas Rickert) b. EPDP Team input c. Confirm next steps – e.g. modification of template, identification of other use cases and volunteers to develop these further. · Note that there was a request from the IPC to defer this to the F2F meeting. Conduct first reading here, followed by a second reading during the F2F meeting. · See observations shared by Thomas with the mailing list: · 1. The document I sent is an attempt to help our group’s discussions. It looked like we could not really agree on an approach to get your work started. · 2. The use case is intentionally kept very limited in scope so that we can focus on one scenario without getting lost in detail or distracted. That is not to say that there can be associated requests or requests different in nature that warrant a different assessment. · 3. The document is based on the work Thomas did at eco when we drafted the eco GDPR domain industry playbook, so Thomas will not claim to have authored the entire document. The good ideas are from other playbook team members. Put the blame on Thomas for the things you do not like. · 4. The document does not reflect an ISPCP position. It was an AI Thomas accepted in personal capacity and is a draft that will likely be subject to change based on EPDP Team deliberations. · Use case: trademark owners requesting data to take legal action against cybersquatters. (see template shared that defines the user groups / user characteristics, why is non-public registration data requested, lawful basis, general safeguards) · This example focuses on trademark only, not patent or copyright. · The EDPB has specifically requested that ICANN’s disclosure model has specific safeguards in place, and, accordingly, a list of safeguards has been provided in this example. · Boolean searches and reverse look-up searches did not come from ICANN, but rather, from third party vendors, and therefore - those have not been included here. · Disclosure request must be directed at the contracted party who houses the data, unless there is a centralized model · Re: data elements that are necessary - name, organization, and postal address. Email address, phone and fax are questionable and may not be necessary for this purpose. · Item F - last point to be discussed - how you can get eligibility for filing disclosure requests - providing evidence of ownership of intellectual property. Feedback from the Team: · Could this methodology work for other use cases? · This methodology could be helpful for moving forward. · Figuring out where to start in this exercise can be challenging. It would be helpful to keep the use case as narrowly-scoped as possible and walk through it from start to finish. · Do any team members feel the template used by Thomas would not work? · This is a great way to proceed at this point; however, how can we proceed afterwards? We do not have the resources to deal with every possible use case in this level of detail. · Question to Team: are there volunteers to write up other use cases following this methodology? · Re: working with this template - the level of amendments may be to keep or eliminate some of the columns on the left. · The template may evolve through the Team’s discussions. · Re: asking for volunteers to develop more use cases - disagree with that path forward. Instead, the Team should work on fleshing out this use case further. · Proposal from Chair to go through the details of this proposed use case - will go line by line on Tuesday. However, we need volunteers for other use cases; otherwise, we will not make substantive progress by November. · Support walking this example all the way through first. Following that, it will be helpful to go through the other big picture use cases. · IPC volunteers to provide additional IP examples. · GAC will come forward with public safety examples. · What is the end point? If we are trying to document all potential use cases, that will be an infinite job. · The goal is not to go through every use case, but instead, to see if we can identify commonalities. · It may be helpful to put a limit on the number of use cases we are going to review at this point. While working on this, we need to look at how this work can be generalized. · At the moment, we are discussing a maximum of five cases. · Thank you to Thomas for providing this example. We will move forward and await additional examples from IPC and GAC for discussion. 5. ICANN65 EPDP Team F2F Meetings (15 minutes) a. Review proposed agenda · The draft ICANN65 agenda has been circulated - unless there is disagreement we will proceed as noted in the agenda. · The Tuesday meeting will be used to review any early input received - the deadline for input is tomorrow. · We will also go through Thomas’ example in detail. · Michael Palage has reached out to EPDP Leadership regarding a unified access model, and similar to Steve Crocker, we will invite him to speak in Marrakech. · On Thursday, ICANN org will join us to discuss engagement with DPAs. · We will then continue discussion of Thomas’ example and building blocks for the SSAD. b. EPDP Team Input · Some groups have noted they may need more time for providing early input. When would be the last date the input could be provided, and noting the request, it may be helpful to remove this from the Tuesday agenda. · ALAC came to the conclusion that early input was asking for answers to all of the charter questions this Team is responsible for answering. Discussing this type of early input may be impractical at this stage. · The Team will review any input received by 21 June. If 30 minutes for this topic is not enough, we can adjust as necessary. · There is no requirement for any group to provide input if it is of the view that their input has already been provided. The requirement is to ask for input, not for groups to provide input. · GAC is working on input, but the GAC is not following the questions directly. This is a much bigger undertaking than initially thought. However, the input may be better discussed on Thursday. · The Team will follow the provided agenda, but if need be, the agenda can be adjusted. c. Confirm next steps 6. Any other business (5 minutes) a. Priority 2 small team meetings update -Reminder - Call schedule remaining priority 2 worksheets: TBC (post ICANN65) Accuracy and WHOIS ARS - Deadline for providing input for those that were not able to attend the calls – proposed 20 June 2019. · We have had three scheduled meetings on Priority 2 worksheets. Members in attendance went through all six worksheets and they are finalized for review by the team. Please review the worksheets and the next steps by next Friday, 28 June. · There will be no meeting the week after Marrakech. (Cancelled 4 July) The next meeting following ICANN65 will be 11 July. · Feedback: the NCSG is concerned with the pace of Phase 2. Tackling multiple issues in parallel is proving difficult to keep up with - can leadership please reconsider this approach? · We will further discuss this concern in Marrakech as we build out the work plan. May need to consider if/how to delegate tasks to other group members for faster progress. 7. Wrap and confirm next meeting taking place at ICANN65 (Meeting room: Tichka) on Tuesday 25 June from 8.30 – 15.00 local time (5 minutes) a. Confirm action items b. Confirm questions for ICANN Org, if any

1 0

Recordings, Attendance & Zoom Chat / EPDP - Phase 2 / Thursday, 20 June 2019
by Julie Bisland June 20, 2019

June 20, 2019

Dear all, Please find the attendance attached to this email, and links to the audio recording, zoom recording (audio, visual, rough transcript) and chat below from the EPDP – Phase 2 call held on Thursday, 20 June 2019 at 14:00 UTC. These have also been posted on the agenda wiki page: https://community.icann.org/x/IpyjBg Audio Recording: https://icann.zoom.us/recording/play/Gb3eIUtcJMma4sZwD81n16HQ9ir90l6UQQ1c2r… Zoom Recording (includes visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/recording/play/HTYaMZs9M8-gfcAHHwSVkzxtZri7IgKb8Q68uj… Chat Transcript: https://icann.zoom.us/recording/download/-kEuGUUbc9mCG9sDH3YQCHABA53L5CKtwE… ** 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, Julie

1 0

Proposed Agenda - EPDP Team Meeting #7 on Thursday 20 June at 14.00 UTC
by Marika Konings June 20, 2019

June 20, 2019

Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 20 June at 14.00 UTC. Please review the attached documents in advance of the meeting. Best regards, Caitlin, Berry and Marika EPDP Phase 2 - Meeting #7 Proposed Agenda Thursday, 20 June 2019 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (10 minutes) * Request for additional resources for F2F meetings submitted (see https://gnso.icann.org/sites/default/files/file/field-file-attach/drazek-to…) 4. Review of third party legitimate interests (10 minutes): i. Carry out the obligations and responsibilities of a law enforcement agency; ii. Confirm the identity of an entity before completing an online purchase/acquisition; iii. Report a technical issue with the domain name; iv. Fulfill a licensing or regulatory requirement; v. Carry out academic research, a study and/or statistical analysis; vi. Carry out security operations, investigation, and research; vii. Prevent intellectual property infringement; viii. Validate domain name ownership for SSL cert requests; ix. (for the registrant) Assess what data a controller holds that pertains to their domain name registration. * Are these comprehensive? Any third party legitimate interest missing from the list? * Are these too high level, too detailed or just right? 5. Topic c: Define user groups, criteria and purposes / lawful basis per user group – Review use case prepared by Thomas Rickert (50 minutes) * Overview of use case - Trademark owners requesting data to take legal action against cybersquatters – see attached * Review already submitted third party legitimate interests (LE – see document reviewed during last week’s meeting https://community.icann.org/x/7ISGBg, Security operations, investigation, and research – see submission from SSAC on the mailing list https://mm.icann.org/pipermail/gnso-epdp-team/2019-June/002141.html ) * EPDP Team input * Confirm next steps – e.g. modification of template, identification of other use cases and volunteers to develop these further. 6. ICANN65 EPDP Team F2F Meetings (15 minutes) * Review proposed agenda (see draft agenda) * EPDP Team Input * Confirm next steps 7. Any other business (5 minutes) * Priority 2 small team meetings update Reminder - Call schedule remaining priority 2 worksheets: · TBC (post ICANN65) Accuracy and WHOIS ARS Deadline for providing input for those that were not able to attend the calls – proposed 20 June 2019. 8. Wrap and confirm next meeting taking place at ICANN65 (Meeting room: Tichka) on Tuesday 25 June from 8.30 – 15.00 local time (5 minutes) * Confirm action items * 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…>.

2 1

Fwd: letter from Mr. Marby re: Planned ICANN org Communications to European Data Protection Board Regarding the Expedited Policy Development Process
by Janis Karklins June 20, 2019

June 20, 2019

Team members, Pls see attached letter from CEO of ICANN that I received few days ago. JK ---------- Forwarded message --------- From: Tina Shelebian <tina.shelebian(a)icann.org> Date: Tue, Jun 18, 2019 at 2:48 PM Subject: letter from Mr. Marby re: Planned ICANN org Communications to European Data Protection Board Regarding the Expedited Policy Development Process To: kdrazek(a)verisign.com <kdrazek(a)verisign.com>, karklinsj(a)gmail.com < karklinsj(a)gmail.com> Cc: Cassia Oliveira <cassia.oliveira(a)icann.org>, Diana Middleton < diana.middleton(a)icann.org>, Eleeza Agopian <eleeza.agopian(a)icann.org>, Goran Marby <goran.marby(a)icann.org> Tina Shelebian on behalf of Göran Marby Dear Mr. Drazek and Mr. Karklins, Attached please find letter from Mr. Marby with information regarding Planned ICANN org Communications to European Data Protection Board Regarding the Expedited Policy Development Process. Best regards, *Tina Shelebian* *Executive Assistant**, Office of the President & CEO * *Internet Corporation for Assigned Names and Numbers (ICANN)* *12025 Waterfront Drive, Suite 300* *Los **Angeles**, CA 90094-2536* *Direct: (310) 578-8**90**6* *tina.shelebian(a)icann.org <tina.shelebian(a)icann.org>*

2 1

**Call on in 15 minutes** Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call / Thursday, 20 June 2019 at 14:00 UTC
by Julie Bisland June 20, 2019

June 20, 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, 20 June 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) 00:00 Melbourne AEST For other times: https://tinyurl.com/y4tk8eka [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y4tk8eka&d…> Agenda Wiki: https://community.icann.org/x/IpyjBg 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/stream02 <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream02.m3u <https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> If needed, an option to join via telephone has been added for this meeting. Passcode: EPDP Telephone numbers: 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 RIO DE JANEIRO: 55-21-40421490 0800-7610651 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 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 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 Thank you. Kind Regards, Terri

1 0

Re: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #7 on Thursday 20 June at 14.00 UTC
by Marika Konings June 19, 2019

June 19, 2019

Dear EPDP Team, Please find attached a document to facilitate deliberations for agenda item 4. This document groups together the input received to date on the proposed third party legitimate interests. Note that time on the agenda for this topic has been extended to 30 minutes. Also attached is an updated version of the proposed agenda for the EPDP Team meetings at ICANN65 for agenda item 6. Updates include, amongst others, a proposed lunch time briefing by Michael Palage on the Differentiated Registrant Data Access Model. Similar to the briefing by Steve Crocker, the hope is that this will help inform and inspire the EPDP Team’s approach for SSAD. Please note that further updates may be made to the F2F agenda based on your input during tomorrow’s meeting as well as progress made. Best regards, Caitlin, Berry and Marika From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, June 18, 2019 at 16:28 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Proposed Agenda - EPDP Team Meeting #7 on Thursday 20 June at 14.00 UTC Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 20 June at 14.00 UTC. Please review the attached documents in advance of the meeting. Best regards, Caitlin, Berry and Marika EPDP Phase 2 - Meeting #7 Proposed Agenda Thursday, 20 June 2019 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (10 minutes) * Request for additional resources for F2F meetings submitted (see https://gnso.icann.org/sites/default/files/file/field-file-attach/drazek-to…) 4. Review of third party legitimate interests (30 minutes): i. Carry out the obligations and responsibilities of a law enforcement agency; ii. Confirm the identity of an entity before completing an online purchase/acquisition; iii. Report a technical issue with the domain name; iv. Fulfill a licensing or regulatory requirement; v. Carry out academic research, a study and/or statistical analysis; vi. Carry out security operations, investigation, and research; vii. Prevent intellectual property infringement; viii. Validate domain name ownership for SSL cert requests; ix. (for the registrant) Assess what data a controller holds that pertains to their domain name registration. * Are these comprehensive? Any third party legitimate interest missing from the list? * Are these too high level, too detailed or just right? 5. Topic c: Define user groups, criteria and purposes / lawful basis per user group – Review use case prepared by Thomas Rickert (50 minutes) * Overview of use case - Trademark owners requesting data to take legal action against cybersquatters – see attached * Review already submitted third party legitimate interests (LE – see document reviewed during last week’s meeting https://community.icann.org/x/7ISGBg, Security operations, investigation, and research – see submission from SSAC on the mailing list https://mm.icann.org/pipermail/gnso-epdp-team/2019-June/002141.html ) * EPDP Team input * Confirm next steps – e.g. modification of template, identification of other use cases and volunteers to develop these further. 6. ICANN65 EPDP Team F2F Meetings (15 minutes) * Review proposed agenda (see draft agenda) * EPDP Team Input * Confirm next steps 7. Any other business (5 minutes) * Priority 2 small team meetings update Reminder - Call schedule remaining priority 2 worksheets: · TBC (post ICANN65) Accuracy and WHOIS ARS Deadline for providing input for those that were not able to attend the calls – proposed 20 June 2019. 8. Wrap and confirm next meeting taking place at ICANN65 (Meeting room: Tichka) on Tuesday 25 June from 8.30 – 15.00 local time (5 minutes) * Confirm action items * 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…>.

2 1