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

**Reminder** Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call | Thursday, 22 August 2019 at 14:00 UTC
by Julie Bisland Aug. 21, 2019

Aug. 21, 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, 22 August 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/y6h37wuq [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_y6h37wuq&d…> Agenda Wiki: https://community.icann.org/x/oqajBg 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 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, Andrea

1 0

REVISED: Question for legal advisors
by Alan Greenberg Aug. 19, 2019

Aug. 19, 2019

At Mark's suggestion, I have reformatted/reworded this for additional (hopefully) clarity. ============== Background: If information is to be requested released to third parties, the controller or other party(ies) must decide whether the need for the data outweighs the data subject's right to privacy. If the decision is made by a human, the competing needs/rights can be carefully weighed to decide whether the request should be honoured. If we are to consider any form of automated decision process, it is unlikely that we can build a sufficiently robust artificial intelligence engine to carry out the balancing operation. That raises the question of to what extent, based on appropriate accreditation processes, can we rely on the vetting during accreditation and the commitments made by the requester in order to be accredited can be relied upon. Examples: As a simple case, if a UDRP provider (who is authenticated as such) makes a request claiming it is for an ongoing UDRP process, can it be presumed that it is an authentic request and simply grant it. For a more nuanced situation, if a cyber security researcher who has been properly accredited (the Anti-Phishing WG as an example) makes a request for specific data, can we assume that given the process under which they are accredited, we can be assured that they need this data, have no practical alternative way of addressing the issue, and will only use/store the data appropriately Perhaps other specific cases should be cited in the question, but we do need guidance in the general case. Summary: Without being able to rely on the reputation and assurances of the requester, I do not see how ANY automated process will be possible. Question: If a requester is properly vetted (accredited, authenticated) and has provided assurances they understand they may only request data that meets the balance test (ie their need is sufficiently great that it warrants releasing to them otherwise redacted data), can an automated system presume that the GDPR balancing test has been satisfied? Of course, accreditation could be revoked if it comes to light that inappropriate requests are being made. At 24/07/2019 04:27 PM, Alan Greenberg wrote: As requested during the last meeting, here is a question to go to the Legal Committee looking for a clear legal opinion. =============================== If information is to be requested released to third parties, the controller or other party(ies) must decide whether the need for the data outweighs the data subject's right to privacy. If the decision is made by a human, the competing needs/rights can be carefully weighed to decide whether the request should be honoured. If we are to consider any form of automated decision process, it is unlikely that we can build a sufficiently robust artificial intelligence engine to carry out the balancing operation. That raises the question of to what extent, based on appropriate accreditation processes, can we rely on the vetting during accreditation and the commitments made by the requester in order to be accredited can be relied upon. Specifically, if a requester is properly vetted and provides assurances (and proof?) they understand the balancing that must be done, can the automated system presume that the balancing test has been satisfied. Of course, accreditation could be revoked if it comes to light that inappropriate requests are being made. In one simple case, if a UDRP provider (who is authenticated as such) make a request claiming it is for an ongoing UDRP process, can it be presumed that it is an authentic request and simply grant it. A less clear case is that of a cyber security researcher who has been properly accredited (the Anti-Phishing WG as an example). Perhaps other specific cases should be cited in the question, but we do need guidance in the general case. Without being able to rely on the reputation and assurances of the requester, I do not see how ANY automated process will be possible. Alan

5 8

Proposed Agenda - EPDP Team Meeting #15
by Marika Konings Aug. 19, 2019

Aug. 19, 2019

Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 22 August 2019 at 14.00 UTC. As a reminder: * IPC tol confirm when the updates have been made to address the input received on IP 5 (by Tuesday 20 August at the latest) * SSAC 3 has already been updated to address the input received (see google doc link below) Please review these documents as well as SSAC 1 ahead of the meeting. Best regards, Caitlin, Berry and Marika ================================== EPDP Phase 2 - Meeting #15 Proposed Agenda Thursday, 22 August 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) Confirm timeline for publication of zero draft and planning for F2F meeting: · Circulation of zero draft to the EPDP Team: Tuesday 27 August · Extraordinary EPDP Team meeting to present zero draft and get initial reactions from EPDP Team: Thursday 29 August at 20.00 UTC (note, this meeting will be in addition to the regular EPDP Team meeting at 14.00 UTC) · Conduct survey to assess which aspects of the zero draft are of most concern and as such should be prioritized for the F2F meeting: Monday 2 – Wednesday 4 September. · Confirm priority items for F2F meeting and confirm ‘homework’ for F2F meeting: Thursday 5 September (regular EPDP Team meeting) b) Update from Legal Committee 4. Use case – second/final reading: Providers requesting access required to facilitate due process in the UDRP and URS<https://docs.google.com/document/d/1ZMK6pw7i3oQ6I26n07kQv7tfsr8zKdBc/edit#h…> (IP 5) (45 minutes) a) Review updates made to use case to reflect input received (IPC) b) Feedback from EPDP Team c) Confirm next steps 5. Use case – final reading: Investigation of criminal activity where domain names are used. Typical specific example: phishing attack <https://docs.google.com/document/d/1iK9ygUOo8ntLWC_7dx3bS195W2ivkqHH/edit?t…> (SSAC 3) a) Review updates made to use case to reflect input received (SSAC) b) Feedback from EPDP Team c) Confirm next steps 6. Use case – first reading: When a network is undergoing an attack involving a domain name, and the operator(s) of that network need to contact the domain owner to remediate the security issue (DDOS, Botnet, etc.)<https://community.icann.org/download/attachments/111386876/Use%20Case%20-%2…> (SSAC1) a) Introduction to use case (SSAC) b) Feedback from EPDP Team c) Confirm next steps 7. Any other business (5 minutes) 8. Wrap and confirm next EPDP Team meeting (5 minutes): a) Thursday 29 August 2019 at 14.00 UTC (5 minutes) 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

On the subject of ICANN's Bylaws...
by James M. Bladel Aug. 17, 2019

Aug. 17, 2019

Good morning, Colleagues- During yesterday’s call, a few folks mentioned that ICANN’s Bylaws contain commitments to uphold “Competition” and “Consumer Choice/Consumer Trust”. These references to the Bylaws were offered in support of the proposed Use Case that RDS data should be a primary resource for consumers who are seeking to verify the operator of a website, or check the reputation of business, or to dispute a commercial transaction. For clarity, it’s worth noting that the predominant context for “competition” in ICANN’s Bylaws is specific to the domain name industry, esp. Registries and Registrars. And this makes sense, given that the industry prior to ICANN had no concept of “competition” or “consumer choice”; all domain transactions were handled by a single provider. Additionally, mentions of “consumer protection”, “consumer choice”, and “consumer trust” within the Bylaws are contained within Section 4.6(d), which outlines the “Periodic Reviews”, and are an element of the 2012 New gTLD program. These sections were ported to the Bylaws from the Affirmation of Commitments, and were drafted when many feared that new gTLDs would confuse consumers and undermine trust/confidence in the DNS. Taken together, it’s not correct to conclude that WHOIS/RDS data is intended to replace or preempt more widely recognized alternative tools for online consumers, like: * SSL certificates, verified by Certificate Authorities (CA) and supported by all modern browsers * Trust certificates (issued by organizations like the Better Business Bureau, Trustwave, McAffee, SiteLock, and card processors like Visa/Mastercard) * Reputation/review services like Google ratings, Yelp, and Facebook or Amazon reviews, and * The “About Us” or “Contact Us” or “Customer Support” links on merchant websites, which are omnipresent for legitimate businesses and required by law in many areas. But if this is still a point of divergence among the EPDP members, then perhaps we could consult ICANN Legal about the extent of their “Competition” and “Consumer Trust” mandate, and whether they believe ICANN is on the hook for the integrity & consumer satisfaction for all commercial activity taking place anywhere on the Internet. J. ------------- James Bladel GoDaddy

7 12

Zero draft and LA F2F meeting
by Janis Karklins Aug. 17, 2019

Aug. 17, 2019

Dear EPDP Team, Following on from yesterday’s discussions on the zero draft for the LA F2F meeting and the support expressed by many of you for this approach, I wanted to share the proposed timeline for sharing the zero draft with you and subsequent input & planning for the LA F2F meeting: - Circulation of zero draft to the EPDP Team: Tuesday 27 August - Extraordinary EPDP Team meeting to present zero draft and get initial reactions from EPDP Team: Thursday 29 August at 20.00 UTC (note, this meeting will be in addition to the regular EPDP Team meeting at 14.00 UTC) - Conduct survey to assess which aspects of the zero draft are of most concern and as such should be prioritized for the F2F meeting: Monday 2 – Wednesday 4 September. - Confirm priority items for F2F meeting and confirm ‘homework’ for F2F meeting: Thursday 5 September (regular EPDP Team meeting) Please let me know if you have any further questions or comments. Best regards JK

2 1

Notes and action items - EPDP Phase 2 Meeting #14 - 15 August 2019
by Caitlin Tubergen Aug. 15, 2019

Aug. 15, 2019

Dear EPDP Team, Please find the notes and action items from today’s Phase 2 EPDP Team meeting below. As a reminder, the Phase 2 Legal Committee will meet on Tuesday, 20 August at 14:00 UTC, and the Phase 2 EPDP Team will meet on Thursday, 22 August at 14:00 UTC. Thank you. Best regards, Marika, Berry, and Caitlin -- EPDP Phase 2 - Meeting #14Thursday, 15 August 2019 at 14.00 UTCAction Items Groups are welcome to provide additional comments in response to early input in the Early Input Google Doc over the next two weeks (by 29 August). Support Staff will consider input received when compiling the Zero Draft document. EPDP Team members to provide feedback on the IP-5 use case via the IP-5 Use Case Google doc by Friday, 16 August. IPC EPDP Team members to review comments and distribute updated use case by Tuesday 20 August in preparation for a final reading on Thursday, 22 August. SSAC EPDP Team members to review comments received for SSAC 3 (Investigation of criminal activity where domain names are used. Typical specific example: PHISHING ATTACK) and distribute updated version of use case to EPDP Team by Tuesday 20 August in preparation for a final reading on Thursday, 22 August. SSAC EPDP Team members to distribute use case for SSAC 1 (When a network is undergoing an attack involving a domain name, and the operator(s) of that network need to contact the domain owner to remediate the security issue (DDOS, Botnet, etc.)) by Tuesday 20 August in preparation for a final reading on Thursday, 22 August. ALAC EPDP Team members to review comments received on ALAC 1 (Online buyers identifying and validating the source of goods or services/ Internet users validating the legitimacy of an email or a website to protect themselves) and distribute updated version of the use case by Tuesday, 27 August in preparation for final reading on Thursday, 29 August. 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.EPDP Phase 2 - Meeting #14Proposed AgendaThursday, 15 August 2019 at 14.00 UTC1. Roll Call & SOI Updates (5 minutes) Attendance will be taken from Zoom Remember to mute your microphones upon entry to Zoom. 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) (5 minutes)a. Travel support for ICANN66 – update on applications received Please refer to this link to view the EPDP Members who have applied for travel support: https://community.icann.org/display/EOTSFGRD/EPDP+Travel+Support+-+Phase+2 b. Reminder to book travel for September F2F in Los Angeles 4. Review of SO/AC/SG/C Early Input (45 minutes)a. Issues / clarifying questions identified (see https://docs.google.com/document/d/13ynT-XM5CDDyTDW0rsZdpt91ym7QrjUD/edib. Consider how to factor early input into drafting of Initial Report The Google Doc link shows all early input received. The input is organized by the category/charter question. Rather than go comment by comment, the groups were invited to review the input and provide clarifying questions. Input was provided by the BC and the RrSG. How would the group like to review this input? Support Staff has factored in this input in preparing the Zero Draft Possible path forward: opposition comments can be responded to in writing Those groups who provided initial input and whose initial input has been contested or objected to in the Google Doc, can respond in the Google doc Once substantive issues are discussed, the early inputs will be pulled and see where there is agreement and disagreement The Zero Draft will contain all substantive issues Skepticism on this approach - reviewing this on Google docs would require off-line discussions on every topic online Only groups directly participating in the EPDP provided comments. The Team has little time to get its work done, so as an alternative, proposal to do nothing with it. It provides good reference to everyone to explore each other’s viewpoints. However, since all early input submitters are represented on the Team, these views can be represented in the substantive calls themselves. There may be some items that do not correspond to Charter questions and the assumption was that the Team will review the items that do not correspond to the Charter questions. The Charter question feedback would discussed during the substantive discussion. Recommend getting clarity on the legal questions so that the Team has more clarity when reviewing the Zero draft. Bird & Bird is not planning to attend the F2F in Los Angeles. Nothing in the Zero Draft is carved in stone; it is easier to start working on something already written rather than drafting by committee c. Confirm next steps, if any Encourage those who would like to engage in online comments about early input to continue editing the Google Doc. All feedback will be taken into account in the writing of the Zero draft. 5. Use case – first reading: Providers requesting access required to facilitate due process in the UDRP and URS (IP 5) (45 minutesa. Introduction to use case (IPC) This use case is for participants in the UDRP/URS process Data is needed to know against whom the UDRP will be filed - whether multiple domain names can be included in a single complaint Data is also used to see if the alleged infringer acted in bad faith Based on who the registrant is, the issue may be resolved without filing a UDRP Lawful basis of entity disclosing the data - mostly 6(1)(b) and 6(1)(c) If the UDRP decision is appealed in court and data needs to be provided based on a subpoena, data may be processed in this context. Accreditation could be useful in some cases, e.g., WIPO, NAF, but the Team needs to think about what benefit that would provide b. Feedback from EPDP Team Safeguards are where the policy comes from - what are the steps the Team needs to go through to test this use case. What does the CP do to actually process this use case Important to note that the UDRP was designed in a way that does not take data protection into account at all - not everything in the UDRP’s existing procedures would be considered compliant with data protection law The UDRP was not drafted with GDPR in mind, but the core of the UDRP - proving that an entity has rights in a name and one entity who, in bad faith, registered a name it had no rights in. It may be helpful to have a legal look at required notices sent to a registrant when it registers a name and whether that is sufficient The RrSG will provide more comprehensive comments following this call. A URS and UDRP can be submitted without knowing who the respondent is. Perhaps disclosure could be to the UDRP Provider, and not the Complainant. Also, the Complainant can contact the Respondent, using the required contactability mechanisms. Trademark owners are being asked to prove a registrant has no rights and acted in bad faith - this is very difficult to do if you do not know who the registrant is Regarding specificity, instead of giving blanket criticism, it would be helpful to give an example of a safeguard you would propose adding. Issues with contractual basis as a lawful basis - this does not entail the contact b/w the registrant and the disclosing party. The relevant contractual relationship is b/w the data subject and the recipient of the data - as this does not exist in this use case, it may not be applicable here. If the recipient of the data decides not to file a UDRP/URS, is that a violation? The 6(1)(b) is vis-a-vis the data subject and not the entity who processes the data. This use case is in the context of a UDRP or URS that has been filed, not a “we might file”. Please refer to the Bird & Bird memo from Phase 1 regarding lawful basis. It is not acceptable to receive data after a UDRP has been filed. This Team is not here to test whether this is a valid use case - this is raw material to feed into the policy recommendations. This debate boils down to the question of legal basis. This use case is based on the legitimate interest of a third party - it is 6(1)(f). There shouldn’t be an artificial incentive to file UDRP cases. It is legitimate to request disclosure, to get the disclosure and then decide not to file a UDRP case - there should be no penalty for not filing. For third parties, it is a 6(1)(f). Disagree that this is a 6(1)(f) - believe this is a 6(1)(b) The Alan W. document describes how 6(1)(f) works - this is valuable if Team members do not have an understanding of 6(1)(f). In this particular use case, safeguards may be different if this is a 6(1)(b). How can every possible life situation be reflected in a policy? Is it possible to draw more general conclusions? Following the policy, a lot of work will have to be done on best practices, but this may not be part of the policy. c. Confirm next steps Brian to send updated use case to the Team following this call Staff to put updated version in Google Docs Team to provide input on updated version by tomorrow, Friday, 16 August Brian and IPC colleagues to distribute updated use case, factoring in comments received by Tuesday, 20 August 6. Any other business (5 minutes) Zero draft will be used as a tool for discussion in LA F2F, and will contain both draft policy principles and building blocks gleaned from EPDP Team’s discussions to date to assist Team in arriving at policy recommendations Next week, goal to try to close SSAC case, IP case Initial reading of SSAC 1 (When a network is undergoing an attack involving a domain name, and the operator(s) of that network need to contact the domain owner to remediate the security issue (DDOS, Botnet, etc.)) will be next Thursday, 22 August ALAC case will be discussed the following week (Thursday, August 29) 7. Wrap and confirm next EPDP Team meeting (5 minutes): Thursday 22 August 2019 at 14.00 UTC (5 minutes) Confirm action items Confirm questions for ICANN Org, if any

1 0

Post Call | GNSO Temp Spec gTLD RD EPDP – Phase 2 | Thursday, 15 August 2019 at 14:00 UTC
by Andrea Glandon Aug. 15, 2019

Aug. 15, 2019

Dear all, All recordings for the GNSO Temp Spec gTLD RD EPDP – Phase 2 held on Thursday, 15 August 2019 at 14:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/n6ajBg> (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, Andrea

1 0

Meeting Invitation: Observers GNSO Temp Spec gTLD RD EPDP - Phase 2 call | Thursday, 22 August 2019 at 14:00 UTC
by Andrea Glandon Aug. 15, 2019

Aug. 15, 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, 22 August 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/y6h37wuq Agenda Wiki: https://community.icann.org/x/oqajBg 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 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, Andrea

1 0

Updated UDRP/URS Use Case
by King, Brian Aug. 15, 2019

Aug. 15, 2019

Hi Team, Here it is. Brian J. King Director of Internet Policy and Industry Affairs T +1 443 761 3726 markmonitor.com<http://www.markmonitor.com> MarkMonitor Protecting companies and consumers in a digital world

1 0

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

Aug. 15, 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, 15 August 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/yy9zq8vs [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yy9zq8vs&d…> Agenda Wiki: https://community.icann.org/x/n6ajBg 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 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