- Gnso-rpm-providers - lists.icann.org

Providers Sub Team Call, 18 July - Proposed Agenda, Slides & Table
by Ariel Liang July 17, 2018

July 17, 2018

Dear Providers Sub Team, Many thanks to those who have responded to the staff inquiry. We noted the apologies from Justine and the potential apologies from Michael. Given there is no objection to the proposed time for the call (tomorrow, Wed 18 July at 12:00-13:30 UTC), staff will schedule the call and send out the invite. Please see below the proposed agenda and find the slide deck attached: 1. Review agenda 2. Finish reviewing the divergent responses from URS Providers (slide no.54 onward) 3. Review questions with similar/consistent responses from Providers in the table: https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v… 4. AOB Thank you for your time! Best Regards, Mary, Julie, Ariel, and Berry From: Justine Chew <justine.chew(a)gmail.com> Date: Monday, July 16, 2018 at 9:46 PM To: Ariel Liang <ariel.liang(a)icann.org> Cc: "gnso-rpm-providers(a)icann.org" <gnso-rpm-providers(a)icann.org> Subject: Re: [Gnso-rpm-providers] [Ext] Re: Providers Sub Team Meeting Canceled / Upcoming Call(s) Unfortunately, I am in a conflicting appointment (my) tomorrow night. Justine ----- On Tue, 17 Jul 2018, 04:34 Ariel Liang, <ariel.liang(a)icann.org<mailto:ariel.liang@icann.org>> wrote: Dear Providers Sub Team members, Thanks Michael for the comment and Phil for the clarification. This is a reminder on the question below – would Wed, 18 July 12:00-13:30 UTC work for a Sub Team meeting this week? Or do you prefer staff sending out a doodle poll to find an alternative time to meet? By noon EDT tomorrow (Tue, 17 July), if there is no objection to the Wed 12:00 UTC timeslot or request for a doodle poll, staff will schedule a call for the Sub Team on Wed at 12:00 UTC. The Sub Team would be tasked to finish reviewing the rest of the responses from Providers and identify potential follow-up questions and issues for further discussions. Best Regards, Mary, Julie, Ariel, and Berry From: Michael Karanicolas <mkaranicolas(a)gmail.com<mailto:mkaranicolas@gmail.com>> Date: Friday, July 13, 2018 at 2:24 PM To: Ariel Liang <ariel.liang(a)icann.org<mailto:ariel.liang@icann.org>> Cc: "gnso-rpm-providers(a)icann.org<mailto:gnso-rpm-providers@icann.org>" <gnso-rpm-providers(a)icann.org<mailto:gnso-rpm-providers@icann.org>> Subject: [Ext] Re: [Gnso-rpm-providers] Providers Sub Team Meeting Canceled / Upcoming Call(s) Hi all, Wednesday at 12 UTC is generally a fine timeslot for me - though I may or may not make it next week in particular, since I'm at conference. Michael On Fri, Jul 13, 2018 at 1:23 PM, Ariel Liang <ariel.liang(a)icann.org<mailto:ariel.liang@icann.org>> wrote: Dear Providers Sub Team members, Due to the low number of participants in today’s call, the meeting was unfortunately cancelled per Co-Chair’s direction. Would the Sub Team be able to meet on Wednesday, 18 July at 12:00-13:30 UTC to continue the deliberation? Staff would like to give you a heads up that the Document and TMCH Data Sub Teams are also scheduled to meet that day (simultaneously at 17:00-18:30 UTC). If we need to find an alternative time slot to ensure that more members could participate, staff can set up a doodle poll for the Sub Team. Please comment on the list whether 1) Wed 18 July 12:00-13:00 UTC would work for you, or 2) you prefer to use Doodle to identify an alternative timeslot. Thank you, and have a great weekend! Best Regards, Mary, Julie, Ariel, and Berry _______________________________________________ Gnso-rpm-providers mailing list Gnso-rpm-providers(a)icann.org<mailto:Gnso-rpm-providers@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rpm-providers _______________________________________________ Gnso-rpm-providers mailing list Gnso-rpm-providers(a)icann.org<mailto:Gnso-rpm-providers@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rpm-providers

1 0

Providers Sub Team Meeting Canceled / Upcoming Call(s)
by Ariel Liang July 17, 2018

July 17, 2018

Dear Providers Sub Team members, Due to the low number of participants in today’s call, the meeting was unfortunately cancelled per Co-Chair’s direction. Would the Sub Team be able to meet on Wednesday, 18 July at 12:00-13:30 UTC to continue the deliberation? Staff would like to give you a heads up that the Document and TMCH Data Sub Teams are also scheduled to meet that day (simultaneously at 17:00-18:30 UTC). If we need to find an alternative time slot to ensure that more members could participate, staff can set up a doodle poll for the Sub Team. Please comment on the list whether 1) Wed 18 July 12:00-13:00 UTC would work for you, or 2) you prefer to use Doodle to identify an alternative timeslot. Thank you, and have a great weekend! Best Regards, Mary, Julie, Ariel, and Berry

5 6

Updated Providers' Responses & Upcoming Calls
by Ariel Liang July 13, 2018

July 13, 2018

Dear Providers Sub Team members We hope this email finds you well. Staff have reviewed the ICANN62 Providers Sub Team session transcript and updated the table of Providers’ responses: https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…. The table now includes additional information/clarification received from the Providers, as well as action items captured during the session (noted in Column G). All of the added notes are indicated as such by the inclusion of the phrase “Additional Info (ICANN62)” prior to the notes, in the event it is easier to search the document. Session transcript can be accessed here: https://static.ptbl.co/static/attachments/180134/1530326354.pdf?1530326354 Staff would like to check whether you wish to hold a Sub Team meeting this week or next week? The task would be finishing reviewing the divergent responses from Providers, and starting to review the responses in the rest of the table. We look forward to your input/suggestion in order to schedule the upcoming call(s) accordingly. Thank you, Mary, Julie, Ariel, and Berry

5 7

Providers Sub Team Call, 13 July - Proposed Agenda, Updated Slides & Table
by Ariel Liang July 12, 2018

July 12, 2018

Dear Providers Sub Team members, In preparation for tomorrow (Friday, 13 July)’s call at 16:00 UTC, staff have updated the slide deck used during the ICANN62 session, incorporating new information/clarification received from Providers. Please find v5 attached. During the call, we may pick up from where we left and continue from slide no. 54. In addition, the table of responses from URS Providers has been also updated by incorporating issues for further discussion that were mentioned during ICANN62. They are included in the Column G of the table: https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v… Please see below the proposed agenda for tomorrow’s meeting: 1. Review agenda 2. Continue reviewing the divergent responses from URS Providers (slide no.54 onward) 3. Begin reviewing questions with similar/consistent responses from Providers in the table 4. AOB If staff may suggest, as we continue reviewing the data collected, the Sub Team may focus on 1) identifying potential follow-up questions to Providers to gain further information/clarification; and 2) identifying further issues for discussions (whether in the Sub Team or in the full WG) that may be helpful in moving toward the data analysis/substantive deliberation phase. Staff would assist by tracking all these in our notes and continue incorporating them in the table for the ease of reference. Thank you for your time and consideration. Best Regards, Mary, Julie, Ariel, and Berry From: Ntfy-gnso-rpm-providers <ntfy-gnso-rpm-providers-bounces(a)icann.org> on behalf of Julie Bisland <julie.bisland(a)icann.org> Date: Wednesday, July 11, 2018 at 7:09 PM To: "ntfy-gnso-rpm-providers(a)icann.org" <ntfy-gnso-rpm-providers(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ntfy-gnso-rpm-providers] Meeting invite / RPM Sub Team for URS Providers / Friday, 13 July 2018 Dear all, The call for the RPM Sub Team for URS Providers will take place on Friday, 13 July 2018 at 16:00 UTC for 90 minutes. 09:00 PDT, 12:00 EDT, 16:00 Paris CEST, 21:00 Karachi PKT, (Saturday) 01:00 Tokyo JST, (Saturday) 02:00 Melbourne AEST For other times: https://tinyurl.com/yd2f7plx [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yd2f7plx&d…> Instructions explaining how to connect the audio in the Adobe Connect room are attached. A calendar invitation has equally been sent and an ical (if your inbox doesn’t receive direct calendar invitations) is available here as attachment for you to download to your calendar. Adobe Connect room: https://participate.icann.org/ariel-liang/ If you’re having trouble joining, please check your plug ins: http://tinyurl.com/icannactest[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__tinyurl.com_icannactest…> Please allow yourself additional time before start of meeting to log into Adobe Connect. Agenda Wiki: [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> https://community.icann.org/x/DYtHBQ [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> For the best audio quality, we recommend you join the audio bridge as well. Please see Dial in Numbers and Participant Passcode below. If you require a dial-out or to send apologies (do not send to full working group) please send an email request with your preferred contact number to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please let me know if you have any questions. Thank you. With kind regards, Julie You're invited. You've been invited to a GlobalMeet® audio meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me[go.conferencinghub.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.conferencinghub.com…> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://16054755605,*,,5931373177#<tel://16054755605,*,,5931373177> Phone Only Control https://go.conferencinghub.com/2rmk4[go.conferencinghub.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__go.conferencinghub.com…> Access Number: 1-605-475-5605 Guest Passcode: 593 137 3177 Additional Access: USA: 1-605-475-5605 USA: 1-712-770-4204 USA: 1-719-955-1670 Canada, Calgary: +1 403 407 5794 Canada, Montreal: +1 514 669 5938 Canada, Toronto: +1 647 426 9166 Canada, Vancouver: +1 604 221 1239 Argentina, Buenos Aires: +54 (0) 11 5172 6004 Argentina (toll free): 0800 800 1224 Australia, Sydney: +61 (0) 2 8017 5839 Australia, Melbourne: +61 (0) 3 8687 0615 Australia, Brisbane: +61 (0) 7 3015 0531 Australia (toll free): 1 800 016 682 Austria, Vienna: +43 (0) 1 25302 1797 Austria (toll free): 0800 8866 3424 Bahrain, Manama: +973 1619 8754 Bahrain (toll free): 800 81105 Belarus (toll free): 8 820 0011 0347 Belgium, Brussels: +32 (0) 2 400 6946 Belgium (toll free): 0800 39623 Bosnia and Herzegovina: +387 7031 1471 Brazil, Sao Paulo: +55 11 4935 7167 Brazil, Rio de Janeiro: +55 21 4560 0001 Brazil (toll free): 0800 887 0234 Bulgaria, Sofia: +359 (0) 2 491 7758 Bulgaria (toll free): 00800 111 4961 Cambodia, Phnom Penh: +855 23 965 724 Canada (toll free): 1 855 950 3718 Chile, Santiago: +56 (0) 2 2666 0697 Chile (toll free): 171 800 835 774 China (national): +400 613 8203 China, Beijing: +86 10 5667 0008 China, Shanghai: +86 21 2039 7086 Colombia, Bogota: +57 1 508 8121 Colombia (toll free): 01 800 755 0071 Costa Rica (toll free): 800 542 5341 Croatia (toll free): 0800 7749 Cyprus (toll free): 800 97439 Czech Republic, Prague: +420 225 986 565 Czech Republic (toll free): 800 701 541 Denmark, Copenhagen: +45 32 72 78 22 Denmark (toll free): 80 70 35 96 Egypt (toll free): 0800 000 0543 Estonia, Tallinn: +372 622 6562 Estonia (toll free): 800 011 1580 Fiji (toll free): 00800 3323 Finland, Helsinki: +358 (0) 9 2310 1537 Finland (toll free): 0800 772 245 France, Paris: +33 (0) 1 70 37 16 78 France (toll free): 0800 947 301 France (national): 0811 655 116 France (national): 0821 231 672 Germany, Frankfurt: +49 (0) 69 2222 13417 Germany, Munich: +49 (0) 89 2030 31232 Germany (national): 01801 001 360 Germany (toll free): 0800 588 9166 Greece, Athens: +30 211 181 3853 Greece (toll free): 00800 128 822 Hong Kong: +852 3018 9112 Hong Kong (toll free): 800 933 624 Hungary, Budapest: +36 1408 8976 Hungary (toll free): 068 002 0146 Iceland (toll free): 800 9015 India, Delhi: +91 11 6641 1384 India, Mumbai: +91 22 6187 5036 India, Chennai: +91 44 6688 6062 India, Bangalore: +91 80 6127 6711 India (toll free): 1800 200 9416 Indonesia, Jakarta: +62 21 2188 9085 Indonesia (toll free): 007 803 321 8925 Ireland, Dublin: +353 (0) 1 526 9440 Ireland (national): 0818 270 272 Ireland (toll free): 1800 937 669 Ireland (national): 1890 907 642 Israel, Tel Aviv: +972 (0)3 721 7951 Israel (toll free): 1809 246 080 Italy, Milan: +39 02 3600 8016 Italy, Rome: +39 06 8750 0690 Italy (toll free): 800 148 217 Japan, Tokyo: +81 3 4588 9613 Japan, Osaka: +81 6 4560 2408 Japan (mobile): 0120 204 333 Japan (toll free): 0120 859 200 Japan (national): 0570 045 744 Jordan (toll free): 0800 22173 Kazakhstan (toll free): 8800 333 7564 Kenya, Nairobi: +254 (0)20 529 3582 South Korea, Seoul: +82 (0) 2 6007 0080 South Korea (toll free): 00798 6136 1451 Latvia, Riga: +371 6601 3637 Latvia (toll free): 8000 4410 Lithuania, Vilnius: +370 5205 5483 Lithuania (toll free): 8800 31309 Luxembourg: +352 2786 0002 Luxembourg (toll free): 800 24564 Malaysia, Kuala Lumpur: +60 (0) 3 7724 8008 Malaysia (toll free): 1 800 816 160 Mexico, Guadalajara: +52 33 4162 3988 Mexico, Mexico City: +52 55 8421 0335 Mexico, Monterrey: +52 81 4162 3637 Mexico (toll free): 01 800 733 4103 Morocco, Casablanca: +212 (0) 520 48 0030 Morocco (toll free): 0800 091 304 Netherlands, Amsterdam: +31 (0) 20 715 3986 Netherlands (toll free): 0800 023 1434 New Zealand, Christchurch: +64 (0) 3 974 2598 New Zealand, Wellington: +64 (0) 4909 4668 New Zealand, Auckland: +64 (0) 9 929 1824 New Zealand (toll free): 0800 452 951 Nigeria, Lagos: +234 1 277 5100 Norway, Oslo: +47 21 00 48 40 Norway (toll free): 800 56093 Oman (toll free): 800 77287 Panama, Panama City: +507 8 335 914 Panama (toll free): 00800 223 1391 Peru, Lima: +51 (0) 1 700 9572 Peru (toll free): 0800 78103 Philippines, Manila: +63 (0)2 395 3427 Philippines (toll free): 1 800 111 014 07 Poland, Warsaw: +48 22 295 3582 Poland (toll free): 00 800 121 4354 Portugal, Lisbon: +351 21 424 5175 Portugal (toll free): 800 788 163 Qatar (toll free): 00 800 100 492 Romania, Bucharest: +40 (0) 21 529 3904 Romania (toll free): 0800 885 825 Russia, Moscow: +7 495 646 1855 Russia (toll free): 8 800 500 9281 Saudi Arabia (toll free): 800 844 9953 Saudi Arabia (toll free): 800 850 0220 Serbia (toll free): 0800 190 703 Singapore: +65 6654 9120 Singapore (toll free): 800 616 3231 Slovakia, Bratislava: +421 (0)2 3321 5511 Slovakia (toll free): 0800 606 009 Slovenia, Ljubljana: +386 1888 8224 Slovenia (toll free): 0800 81212 South Africa, Johannesburg: +27 (0)11 589 8332 South Africa (toll free): 0800 999 441 Spain, Madrid: +34 91 114 7295 Spain, Barcelona: +34 93 800 1973 Spain (toll free): 900 828 072 Sri Lanka, Sri Lanka: +94 720 910 334 Sweden, Stockholm: +46 (0) 8 5065 3966 Sweden (toll free): 0200 125 599 Switzerland, Geneva: +41 (0) 22 595 4839 Switzerland, Zurich: +41 (0) 44 580 7228 Switzerland (toll free): 0800 841 684 Taiwan, Taipei: +886 (0) 2 2650 7327 Taiwan (toll free): 0800 666 587 Thailand, Bangkok: +66 (0) 2104 0763 Thailand (toll free): 001 800 6136 1471 Tunisia, Tunis: +216 31 378 120 Turkey, Istanbul: +90 212 375 5034 Turkey (toll free): 00800 4488 24338 Ukraine (toll free): 0800 500 871 UAE (toll free): 8000 3570 2660 UK (03): +44 (0)330 336 6003 UK (toll free): 0800 358 6404 UK (national): 0844 473 5011 UK (national): 0845 545 0030 USA /Canada (toll free): 1-800-375-2612 Uruguay (toll free): 0004 019 0274 Venezuela, Caracas: +58 212 720 2523 Venezuela (toll free): 0 800 100 8368 Vietnam, Hanoi: +84 24 4458 3313 Vietnam, Ho Chi Minh: +84 28 4458 1323 Vietnam (toll free): 122 801 81

1 0

Additional Clarifications from FORUM
by Ariel Liang July 10, 2018

July 10, 2018

Dear Providers Sub Team members, FORUM has provided additional clarifications to their responses to some of the questions. They can be found by searching “Second Supplement” in the attached document (Row 38, 76, 103, 108 in the response table/Google spreadsheet). FORUM also clarified that they relied solely on Examiner Responses to answer the following questions in the table (Row 9, 51, 90, 92, 94, 95). The response table has been updated accordingly, incorporating the new information from FORUM: https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v… Best Regards, Mary, Julie, Ariel, and Berry

1 0

FORUM's Supplemental Responses & Updated Slides for ICANN62
by Ariel Liang June 23, 2018

June 23, 2018

Dear Providers Sub Team Members, By COB Friday (22 June), FORUM submitted supplemental responses to the remaining 20 questions that were pending responses, as well as a few questions that they already responded previously. Staff have updated the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…> of the consolidated responses (FORUM’s supplemental responses are highlighted in yellow). The presentation slide deck for ICANN62 working session have also been updated accordingly (please find attached). All responses and attachments submitted by Providers are uploaded on this page: https://community.icann.org/x/FBu8B. Best Regards, Mary, Julie, Ariel, and Berry From: Ariel Liang <ariel.liang(a)icann.org> Date: Friday, June 22, 2018 at 12:15 PM To: "gnso-rpm-providers(a)icann.org" <gnso-rpm-providers(a)icann.org> Subject: RE: How to Structure ICANN62 Session (mailing list seems to experience significant delay in delivering messages, and staff are re-sending this message without attaching the presentation slide deck but including a download link) Dear Providers Sub Team Members, To facilitate the working session on Thursday at ICANN62, staff have prepared a slide deck for Option B (please download here: https://community.icann.org/download/attachments/79436564/RPM_URS_PDP_WG_Se…) . Hearing no input yet from the Sub Team about the structure of the session, staff would like to suggest that the Sub Team members focus on reviewing the questions with divergent responses, so that we could take advantage of the participation of all three URS Providers in the session. Please note that the slides only contain very high-level summary, key points, and quotes from Providers’ responses. The full responses should be referenced from the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…>. In addition, the slide deck also includes the questions that Sub Team already reviewed, as well as the follow up questions; some questions that have not received completed responses from one or more Providers are also included in the deck. If there is no significant objection to this approach, staff will inform the Providers about the format of the session and share the slide deck with them as a heads-up. Thank you, Mary, Julie, Ariel, and Berry From: Ariel Liang <ariel.liang(a)icann.org> Date: Wednesday, June 20, 2018 at 11:42 AM To: "gnso-rpm-providers(a)icann.org" <gnso-rpm-providers(a)icann.org> Subject: How to Structure ICANN62 Session Dear Providers Sub Team Members, Staff touched based with Co-Chairs earlier today to discuss ICANN62 session planning. Per Co-Chairs’ direction, we are seeking advice on how you wish to structure the working session in Panama (Thu, 28 June at 10:30-12:00 local time). Again, all three Providers will be attending the session either in person or remotely. If we may, staff would like to propose some suggestions: * The session would use an interaction format, with Q&A between the Sub Team members and the Providers. * There would be no formal presentations from the URS Providers; they are expected to provide further information/clarification, if needed, as the Sub Team goes through their responses. * Option A: * Sub Team will first ask the Providers to address the follow up questions developed in the previous call; * Sub Team will then pick up from where we left and continue going through the responses based on the order in the spreadsheet (starting from row 20); * Staff will display the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…> that contains the full responses from the Providers on the screen, with no additional slides. * Option B: * Sub Team will focus on reviewing the questions with divergent/different responses from the Providers (50 questions total); * Staff are happy to develop some slides (e.g., with high-level points summarizing the divergent responses for each question) to display on the screen to facilitate the discussions. However, Sub Team members should still reference the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…> on their own laptops for the full responses. At your earliest convenience, please be so kind to provide your preference for Option A or Option B, as well as additional ideas if any, so staff could relay the information/expectations to the Providers to assist their participation in the Sub Team working session at ICANN62. Thank you for your input! Best Regards, Mary, Julie, Ariel, and Berry

1 1

How to Structure ICANN62 Session
by Ariel Liang June 22, 2018

June 22, 2018

Dear Providers Sub Team Members, Staff touched based with Co-Chairs earlier today to discuss ICANN62 session planning. Per Co-Chairs’ direction, we are seeking advice on how you wish to structure the working session in Panama (Thu, 28 June at 10:30-12:00 local time). Again, all three Providers will be attending the session either in person or remotely. If we may, staff would like to propose some suggestions: * The session would use an interaction format, with Q&A between the Sub Team members and the Providers. * There would be no formal presentations from the URS Providers; they are expected to provide further information/clarification, if needed, as the Sub Team goes through their responses. * Option A: * Sub Team will first ask the Providers to address the follow up questions developed in the previous call; * Sub Team will then pick up from where we left and continue going through the responses based on the order in the spreadsheet (starting from row 20); * Staff will display the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…> that contains the full responses from the Providers on the screen, with no additional slides. * Option B: * Sub Team will focus on reviewing the questions with divergent/different responses from the Providers (50 questions total); * Staff are happy to develop some slides (e.g., with high-level points summarizing the divergent responses for each question) to display on the screen to facilitate the discussions. However, Sub Team members should still reference the spreadsheet<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…> on their own laptops for the full responses. At your earliest convenience, please be so kind to provide your preference for Option A or Option B, as well as additional ideas if any, so staff could relay the information/expectations to the Providers to assist their participation in the Sub Team working session at ICANN62. Thank you for your input! Best Regards, Mary, Julie, Ariel, and Berry

1 2

Reminder: Meeting Next Week? & Divergent Responses
by Ariel Liang June 19, 2018

June 19, 2018

Dear Providers Sub Team members, Following up on the action items, does the Providers Sub Team plan to meet next week prior to ICANN62? Please provide your input on the mailing list. If the Sub Team would like to meet, perhaps we could use the same time (12:00 UTC on Wed 20 June), which seems to work well for different time zones (a bit early for PST). In addition, staff have identified the questions that we have received divergent Reponses from Providers (word document attached). Please note: * There are about 50 questions that we have received divergent responses from Providers. This number may change after we receive responses from FORUM for the remaining 20 questions; * Besides the questions that we just received responses from the Providers, staff also reviewed the responses received earlier during the ICANN61 Provider presentation and follow up emails; * Staff included some quote and key points mentioned in Providers’ responses for reference, but the full responses should be referenced in the spreadsheet (see PDF attached OR Google spreadsheet version<https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v…>); * While the responses to some questions are not divergent, staff included the additional, notable information from the Providers in the word document. * In the spreadsheet, the row number (column A) of questions with divergent responses are colored in red. Staff have followed up with the Providers on their availability to attend ICANN62 sessions and will let the Sub Team know their response. Thank you, and have a good weekend! Best Regards, Mary, Julie, Ariel, and Berry

1 1

Recordings, Attendance & AC Chat | RPM Sub Team for URS Providers call on Wednesday, 13 June 2018
by Andrea Glandon June 18, 2018

June 18, 2018

Dear All, Please find the attendance & AC chat of the call attached, and the mp3 link & AC Recording below for the Review of all Rights Protection Mechanisms (RPM) Sub Team for URS Providers call held Wednesday, 13 June 2018 at 12:00 UTC. Apologies for the tardiness of this email. MP3: https://audio.icann.org/gnso/gnso-rpm-review-urs-providers-13jun18-en.mp3 <https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> AC Recording: https://participate.icann.org/p1mucabk4tb/<https://participate.icann.org/p1mucabk4tb/?OWASP_CSRFTOKEN=1e2a71dba3e404a9…> Attendance and recordings of the call is posted on agenda wiki page: https://community.icann.org/x/vSwFBQ The recording of the call is posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-rpm-providers/ Main wiki page for the working group: https://community.icann.org/x/wCWAAw[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Kind Regards, Andrea Glandon

1 0

Actions, Next Steps & Notes: RPM Data Sub Team 13 June 2018
by Ariel Liang June 13, 2018

June 13, 2018

Dear Providers Sub Team members, Per direction from the Co-Chairs, staff are sending this email to provide a summary of the discussion today and the next steps. The Sub Team reviewed the responses from Providers through page 7 of the spreadsheet attached (row 19) and identified follow up questions to seek further information/clarification from the Providers. Staff have updated the spreadsheet with these follow up questions (colored in blue), as well as Sub Team comments (placed in the “additional notes” column). The spreadsheet has also been updated to include row numbers for easier reference. You may also access the spreadsheet via this Google Doc: https://docs.google.com/spreadsheets/d/1I-qe_I4OkQT7IU_rjHMQVa9Ebj8Ik6vay1v… The Sub Team are tasked to review Providers’ responses and bring up points for discussions via the mailing list. By Friday, 15 June, the Sub Team will need to decide whether a call is needed prior to ICANN62. In addition, staff will circulate with the Sub Team questions that Providers’ responses are divergent by Friday, 15 June. We will check with the Providers and let the Sub Team know their availability to attend the ICANN62 RPM session. Please see below the action items and notes captured by staff. They have been posted to the wiki space at https://community.icann.org/x/vSwFBQ, which also publishes the recording, AC chat, and attendance records. Please note that these will be high-level notes and are not meant as a substitute for the transcript or recording. Best Regards, Mary, Julie, Ariel, and Berry ==== ACTION ITEMS * Staff to send an email by 13 June to the Sub Team summarizing the discussion today and the next steps. (DONE) * Staff to update/highlight the spreadsheet with the comments/follow up questions captured during the call. (DONE) * Staff to identity the divergent answers from providers and circulate with the Sub Team by Friday, 15 June. * Staff to let Sub Team know if the representatives from URS Providers would attend ICANN62. * Sub Team to review the spreadsheet and discuss via the mailing list; Sub Team to decide by the end of the week whether they need another call before ICANN62. COMMENTS ON PROVDER RESPONSES * ROW 7: * Delivering Notice of Complaint: Ask ADNDRC why they do not deliver the Notice of Complaint in hard copy. * Discuss potential difficulties created by GDPR. * ROW 12: * Note possible clerical issue concerning out of date email information. "1. Some Registry Operators communicate from email addresses different from the contacts present in ICANN's repository. In that case it is not possible to send them encrypted notifications with the PGP key." * ROW 14: * Follow up with ADNDRC about what they meant by "Yes". Incomplete complaints are not supposed to be accepted. * Ask the other two Providers (FORUM + ADNDRC) whether they accept the "Doe Complaint". * ROW 16: * Flag that FORUM seems to have confirmed that most of the data in the SMD file is difficult to read/remains encoded. Check further on jurisdiction of the trademark/ category of goods and services -- whether the examiners have those data. * ROW 18: * Follow up with FORUM on the suggested word limit. Look at the issue when we are discussing policy recommendations. * ROW 19: * Follow up with FORUM what triggers such suspicion. * Follow up with ADNDRC about how they conduct cross-checks. NOTES -- Received responses from URS Providers on 08 June by the deadline. -- Forum needs a bit more time to provide responses and will have them by ICANN62. -- The spreadsheet was circulated around 1200 UTC on 12 June. Concerns were expressed about not having more time to review the document. -- Light orange cells were questions sent to Providers, dark orange are responses with attachments, yellow is where Forum will provide additional responses. -- Could we use this meeting to do an overview to better understand what is in front of us. -- Prof. Tushnet can't be on the call today, but we circulated the 7 questions for which her data could provide answers. Prof. Tushnet provided answers and they are incorporated into the spreadsheet. Discussion of Responses from Providers: ROW 7: Re: URS Rule 2(a), Procedure 4.2 -- delivering Notice of Complaint: -- ADNDRC has not engaged with the practice of delivering the Notice of Complaint in hard copy. etc. -- Might want to discuss the potential difficulties from GDPR. Questions for ADNDRC: -- Why do you not deliver the Notice of Complaint in hard copy? -- Do you not follow the same rules? Answer: We all use the same rules and we have the same panelists. When a complaint comes in it gets sent to the most appropriate office, depending on location. -- Which office answered the questions? Answer: Carrie Shang, HKIAC. Other offices reviewed and commented. Discussion: -- Requirement is for the original complaint to be delivered via three separate means, but not subsequent communications. -- Can staff highlight anything from Prof. Tushnet that doesn't gibe? Answer from staff: Prof. Tushnet's answers are included in the Additional Notes column. Also, her answers are posted on the wiki at: https://community.icann.org/x/FBu8B ROW 12 Re: difficulties in communicating with Registry Operators: -- MFSD response -- Using different email addresses. Not a policy issue, but could be a clerical issue concerning out of date email information. "1. Some Registry Operators communicate from email addresses different from the contacts present in ICANN's repository. In that case it is not possible to send them encrypted notifications with the PGP key." --Question: How does ADNDRC receive complaints? Is it via email or via online form? Answer: We receive the complaint via online forms. ROW 14 Re: Accepting Complaints that do not contain all the elements required in URS Rule 3(b): -- ADNDRC: accepts complaints that might be incomplete. -- MFSD: accepts complaints even if Complainant does not provide the contact details of the Respondent ("Doe Complaint") because they are not available in the publicly accessible Whois or not otherwise known to the Complainant." -- Might be worth checking with the other providers to see if they have changed their processes because of GDPR in this case. -- Follow up with ADNDRC about what they meant by "Yes". Incomplete complaints are not supposed to be accepted. -- Ask the other two Providers (FORUM + ADNDRC) whether they accept the "Doe Complaint". -- Understand the Forum have. But agree we should have a formal response to this from both, re GDPR/Doe complaint ROW 16 Re: URS Rule 3(b)(v) concerning SMD Proof of Use: -- Flag that FORUM seems to have confirmed that most of the data in the SMD file is difficult to read/remains encoded. Check further on jurisdiction of the trademark/ category of goods and services -- whether the examiners have those data. -- The SMD file is only for demonstrating that proof of use has been provided. Doesn't seem to be needed to identify the trademark. ROW 18 Re: URS Procedure 1.2.7: 500-word limit: -- Follow up with FORUM on the suggested word limit. Look at the issue when we are discussing policy issues. ROW 19 re: URS Rule 3 (g) checking a domain cited in a URS complaint: -- Follow up with FORUM what triggers such suspicion -- Follow up with ADNDRC about how they conduct cross-checks NOTE: The Sub Team could use the time in Panama to continue progressing on this work ACTIONS: -- Staff to identity the divergent answers from providers and circulate with the Sub Team ahead of time -- Staff to prepare an email to the Sub Team, indicating we reviewed responses through page 7 , identify the things that we want to follow up with Providers, and staff to go through the document pointing answers that there are significant divergent for responses, and decide by the end of the week whether we need another Sub Team call before ICANN62 (send the email today), take the from the notes the follow up questions/comments, review the document/discuss on the email. -- Staff to let Sub Team know if we will have representatives from Providers in ICANN62.

1 0