February 2018 - Gnso-rpm-providers

Proposed Agenda for Providers Sub Team - Wed 28 Feb
by Ariel Liang Feb. 28, 2018

Feb. 28, 2018

Dear Sub Team members, In preparation for tomorrow’s call (Wed, 28 Feb at 23:00 UTC – APAC time zone rotation), staff wish to propose the following agenda for your consideration: 1. Sub Team continue reviewing and developing objective questions with regard to the URS Rules (Section 9 et seq.), and then proceed with the URS Procedures, MoU between ICANN and Providers, and the Providers’ Supplemental Rules that contain variations. 2. Next steps/next meeting * Reporting at ICANN61 * Review questions from Practitioner / Documents Sub Teams to Providers * Number of future meetings; planning/building timeline for completing questions for URS Providers Regarding agenda item 2a, staff believes that the WG Co-Chairs plan to use some part of the RPM sessions at ICANN61 for reports and discussions of the work of the various Sub Teams. As such, for tomorrow’s Sub Team call, staff would recommend the Sub Team to allocate some time to agree on what and how you will be reporting back to the full group at ICANN61. Regarding agenda item 2b, staff would like to give the Sub Team a heads up that the Documents and Practitioners Sub Teams have been proposing some questions targeting the Providers. They will share these questions with the Providers Sub Team shortly. The Sub Team may need to decide how to incorporate these questions in the list of questions for Providers. Regarding agenda item 2c, staff would like to remind the Sub Team that the full WG has previously agreed to invite URS Providers to attend future meeting(s) to answer questions. It would be beneficial for the Sub Team to follow a set timeline and deliver questions to the Providers in a timeline manner. Related to this point, it would be helpful for the Sub Team to estimate the number of future meetings needed to complete the review of the pertinent documents, as well as the deliberation of the questions, factoring APAC time zone rotation. It would be ideal if the Sub Team could wrap up the work shortly after ICANN61 (e.g. April). Last, staff has completed the action item related to URS Examiners’ qualifications (shared last week and attached the file again), and is in process developing the table that maps URS Rules, Procedures, and Supplemental Rules. Thank you all for your review and consideration of the suggested agenda! Best Regards, Ariel

1 0

Summary Notes from the Sub Team URS Documents Meeting 21 February
by Julie Hedlund Feb. 23, 2018

Feb. 23, 2018

Hello everyone, Per the staff action item from the RPM PDP Working Group Co-Chairs, please find attached summary notes for your reference from the meeting of the Sub Team URS Documents on 21 February. Best regards, Julie Julie Hedlund, Policy Director

1 0

Re: [Gnso-rpm-providers] [Ext] RE: List of Examiners on URS Providers' Website
by Ariel Liang Feb. 23, 2018

Feb. 23, 2018

My pleasure. Happy to help! Best Regards, Ariel From: Carrie Shu Shang <cshang(a)hkiac.org> Date: Thursday, February 22, 2018 at 7:16 PM To: Ariel Liang <ariel.liang(a)icann.org>, "gnso-rpm-providers(a)icann.org" <gnso-rpm-providers(a)icann.org> Subject: [Ext] RE: [Gnso-rpm-providers] List of Examiners on URS Providers' Website Thanks Ariel, Very helpful. _____________________________________________________________________ Carrie Shang ADR Counsel | Hong Kong International Arbitration Centre Address: 38/F, Two Exchange Square, 8 Connaught Place, Central, Hong Kong Tel: +852 2525 2381 Fax: +852 2524 2171 E-mail: cshang(a)hkiac.org<mailto:sgrimmer@hkiac.org> Webpage: http://www.hkiac.org[hkiac.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hkiac.org_&d=DwMF-g…> _____________________________________________________________________ ________________________________ From: Gnso-rpm-providers [gnso-rpm-providers-bounces(a)icann.org] on behalf of Ariel Liang [ariel.liang(a)icann.org] Sent: Friday, February 23, 2018 7:31 AM To: gnso-rpm-providers(a)icann.org Subject: [Gnso-rpm-providers] List of Examiners on URS Providers' Website Hello everyone, As per staff action item, please find attached a document about the Examiners’ information on the three URS Providers’ websites. Besides checking Examiners’ qualifications, staff also included information related to language skills, location of the Examiners, etc. The additional information may be useful when we discuss the URS Rules Section 9 next week. Welcome your input and comment. Thank you, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [Gnso-rpm-providers] [Ntfy-gnso-rpm-providers] **Changed Time to 23:00 UTC** Meeting invite / RPM Sub Team for URS Providers / 28 February 2018 at 23:00 UTC
by Susan Payne Feb. 23, 2018

Feb. 23, 2018

Hi all I will be travelling next Wednesday and about to catch a flight. I will do my best to join but please accept my apologies in advance if I’m unable to join. Susan Payne Head of Legal Policy | Valideus Ltd E: susan.payne(a)valideus.com<mailto:susan.payne@valideus.com> D: +44 20 7421 8255 T: +44 20 7421 8299 M: +44 7971 661175 23:00 UTC** / Please be sure to update calendars Dear all, The call for the RPM Sub Team for URS Providers: To develop and review questions for the URS providers will take place on Wednesday, 28 February 2018 at 23:00 UTC for 90 minutes. 15:00 PST, 18:00 EST, (Thursday) 00:00 Paris CET, (Thursday) 04:00 Karachi PKT, (Thursday) 08:00 Tokyo JST, (Thursday) 10:00 Melbourne AEDT For other times: https://tinyurl.com/ybfqjvgy[tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_ybfqjvgy&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…> Agenda Wiki: https://community.icann.org/x/8xm8B[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, Terri [GlobalMeet] [https://cobranding-pgi.s3.amazonaws.com/1/Logo1.png] 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 <USING THE ADOBE CONNECT ROOM.pdf> <RPM Sub Team for URS Providers 28 Feb.ics> _______________________________________________ Ntfy-gnso-rpm-providers mailing list Ntfy-gnso-rpm-providers(a)icann.org<mailto:Ntfy-gnso-rpm-providers@icann.org> https://mm.icann.org/mailman/listinfo/ntfy-gnso-rpm-providers

1 0

List of Examiners on URS Providers' Website
by Ariel Liang Feb. 23, 2018

Feb. 23, 2018

Hello everyone, As per staff action item, please find attached a document about the Examiners’ information on the three URS Providers’ websites. Besides checking Examiners’ qualifications, staff also included information related to language skills, location of the Examiners, etc. The additional information may be useful when we discuss the URS Rules Section 9 next week. Welcome your input and comment. Thank you, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

3 2

Time Zone Rotation - 23:00 UTC?
by Ariel Liang Feb. 22, 2018

Feb. 22, 2018

Hello everyone, Staff would like to ask your input on potential time zone rotation for the Providers Sub Team calls. Among the 11 people<https://community.icann.org/x/3BW8B> in the Sub Team (nine members + one observer + one WG Co-Chair), three people are located in the APAC time zone, two in Europe, and six in North/South America. The 18:00 UTC time is especially inconvenient for those in the APAC time zone. Would it be helpful that we hold the meeting at 23:00 UTC periodically? This would be 7am in Singapore/HK/ Kuala Lumpur, and 11pm in the UK. It is still not ideal, but it would be better than 18:00 UTC when APAC colleagues most likely could not attend. Of course, the frequency of the rotation depends on the number of future Sub Team meetings that we foresee. Perhaps we will gain more clarity after next week’s call. In the meantime, please let the group know whether holding meeting at 23:00 UTC would be feasible, and if so, whether we can do that for next week’s call. If not, do you have suggestions on alternative time? Thank you for your consideration! Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

7 6

Action & Notes: RPM Sub Team for Providers call on Wednesday, 21 February 2018 18:00 UTC
by Ariel Liang Feb. 21, 2018

Feb. 21, 2018

Dear All, Below are the action items and notes staff captured from the RPM Providers Sub Team meeting today (21 February 2018). The notes from the call are posted to the Sub Team wiki space, together with the call recording and Adobe Connect chat and attendance records. Please note that these notes are not meant as a substitute for the recording. Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN) == ACTION ITEMS: * Sub Team to continue reviewing and developing objective questions with regard to the URS Rules, and then proceed with the URS procedures, MoU between ICANN and Providers, and the Providers’ Supplemental Rules that contain variations. * Staff to check whether the Providers maintain and make public available the list of URS examiners and their qualifications; staff to present the findings (e.g., screenshots) before or during the next Sub Team meeting (with regard to section 6a) * Staff to create a table that lists/maps the URS Rules, URS procedures, Providers’ Supplemental Rules; the table should include columns for suggested questions and notes. * When reviewing Providers’ Supplemental Rules, Sub Team to revisit Section 2(c), 5(a)(iv), 5(a)(v), 5(e), 5(k), and 7 in the URS Rules, and to check the Providers’ forms. NOTES: I. Starting point for developing questions for URS Providers * Review the level of compliance of URS Providers and understand whether they follow the ICANN rules & procedures and in compliance with the MoU; this can be large checked by the Sub Team of ICANN staff. * Ask what guidance that Providers have formally or informally given to the examiners * See how implementation is done and how specific rules are approached. E.g., How examiners are selected? What background they have? What kind of training they have? How they determine the standard of proof in URS cases? II. Review of the URS Rules and propose questions 2. Communications (a)(b) * How do Providers send notification to the Respondent? * Have Providers received responses from Respondents after the deadline? * Is the deadline long enough? * Do Providers have any notification of delayed communications? * Do Providers have any notification of non-delivery of communications? (c) * In Providers’ Supplemental Rules, are there reasonable ways of communicating? (f) * What percentage of communications were done in ways rather than electronically/via the Internet? (g) * Do Providers conform with the communications timeline in accordance with this provision? (j) * If Respondents did not receive notifications the first time, how could they report on the bounce back? 3. The Complaint (a)(b) * Do Providers accept complaint that don't contain all the elements required? * Do Providers ask additional information beyond what is required in the URS Rules? Discussion: We could check the forms Providers use for compatibility. (e) * Has any Provider used rules related to abusive complaint at all? Has any penalty been set forward? * How have Providers complied with their MOU para 2(b)(viii) with regard to establishing and maintaining a process to monitor URS abuse Discussion: Not sure how much inferences we could draw if not many cases that abusive complaint was applied. Most of the cases have been won by the Complaint. Perhaps check the complaint abuse case database on the Provider's site? (g) * Has a Provider conducted check on whether a domain case is already subject to an open and active URS or UDRP proceeding? If so, how did they find out? * Do Providers rely on the information provided by the Complaint? * Does anyone check for court cases in the event a Respondent doesn't respond? * How do Providers view their responsibility under the provision 3(g)? Discussion: * Don’t need to worry too much about this provision. It is a responsibility of a Provider, and the Complaint may run the risk of being abusive if the case is filed with other URS Providers or UDRP. If a case is filed with different Providers, the parties are obligated to inform the Provider if other channels are utilized. * The rule didn't provide clarification on whose responsibility it is to check whether the domain name case is already in an open and active URS or UDRP proceeding. * There are several cases that a TM holder has put out a URS proceeding when the Respondent couldn't respond. * Unless the Complaint was withdrawn on a without prejudice basis, then they can refile and should not be considered as abusive. * What file extension do .SMD files carry? There is no SMD file requirement. Providing a .SMD file is a simpler way to provide the data if a trademark has been registered in the TMCH. The TMCH sends the TM-holder an .SMD file as confirmation. This provision allows TM holders to forward that file to the Provider as their TM proof. 4. Notice of Complaint and Locking of Domain (b) * Are Providers checking WHOIS info in order to determine the language to be used to transmit the Notice of Complaint? Discussion: Language question is covered in Rule 9 (c) * Are Providers following this provision of rules? 5. The Response (a) (iii) * Have Providers gotten Responses alleging any abusive complaint? If so, how did Providers act in those cases? (a) (iv) Discussion: * The terminology used in this provision needs to be modified to be consistent. Not clear what does legal proceedings encompass. * Possible Recommendation: Standardization of language/terminology used in the URS Rules. * We should see Providers’ forms. There may be different pieces of information required, depending on the forms. This can be done when Supplemental Rules are being reviewed. (a) (v) * Is the statement included in the Providers’ forms? (e) * How often has the Respondent asked for an extension? * How often has the Complaint asked for an extension? * What is considered "exceptional cases"? Discussion: Sub Team should review how Providers handle this provision in their Supplemental Rules. (f) * Has the Provider ever received affirmative claims for relief by the Respondent for reasons beyond an abusive complaint? (g) * Has the Provider conducted a compliance check for a Respondent for factors beyond the two items stated in the provision? (i) * How many Responses were determined non-compliant? * How many Responses were filed but with fees not paid? * Can Providers identify any cases in which they determined the Responses is non-compliant for reasons other than the payment of the fee? Discussion: * This provision should be addressed in the Practitioners Sub Team. * Asking these questions can give us a subset of cases to review their decisions for. * Respondents don't need to pay any fee unless there are 15 domain cases or more. Reexamination fee applicable for <15 domains (k) Discussion: * The language used in this provision seems super-confusing & could be clarified. * Sub Team will not try to form a question now. Check this when reviewing the Supplemental Rules. It seems like an odd fact situation. 6. Examiner (a) ACTION: Staff to check whether the Providers maintain and make public available the list of URS examiners and their qualifications and present the findings (e.g., screenshots) before or during the next Sub Team meeting. (b) * Did the Providers make the examiners aware of their needs to be impartial and independent? * Has there been any circumstance that gave rise to justifiable doubt of the independence/impartiality of an examiner? If so, did the examiner disclose this before and/or during the case proceeding? If no, what happened? * Does the Respondent have the ability to point out the conflict of interest/bias from the examiner? Can they do so in their responses? * Is there a situation that a Respondent was aware of the conflict of interest of an examiner? Is there a situation that a Respondent pointed this out? * Is there any possibility for examiner-shopping? Discussion: * Who decides exactly on impartiality or independence of an examiner? “Independence”, “impartiality”, and “justifiable doubt” are subjective standards. Would it be useful to dig more into the phrases to understand what they means, what constitutes a conflict, and how does a Provider look into that? Whether it is based on initial disclosure by the examiner, or the interpretation of the standards? * This question is also related to the background and expertise of the examiners. * General rules should be established so that people are confident that examiners are not biased. * There may be professional conduct requirements/guidelines to enforce the impartiality and independence of the examiner. 7. Communication Between Parties and the Examiner Discussion: Sub Team will revisit this provision when reviewing Providers' Supplemental Rules. 8. General Powers of the Examiner (d) * Does the Provider know any situation that the nominal registrant changed after the complaint was filed? If so, how did the Provider handle it? * How many complaints have been dismissed on the basis of the wrong Respondent being named, where the domain was registered with a privacy/proxy service?

1 0

Recordings, Attendance, & AC Chat for RPM Sub Team for URS Providers call on Wednesday, 21 February 2018
by Terri Agnew Feb. 21, 2018

Feb. 21, 2018

Dear all, Please find the attendance and AC Chat transcript attached to this email, and the MP3 and Adobe Connect recording below for the Review of all Rights Protection Mechanisms (RPM) Sub Team for URS Providers held Wednesday, 21 February 2018 at 18:00 UTC. Attendance and recordings of the call is posted on agenda wiki page: https://community.icann.org/x/_Ri8B MP3: <https://audio.icann.org/gnso/gnso-rpm-review-urs-providers-21feb18-en.mp3> https://audio.icann.org/gnso/gnso-rpm-review-urs-providers-21feb18-en.mp3 Adobe Connect recording: <https://participate.icann.org/p5hsmgf4tds/?OWASP_CSRFTOKEN=1606aaffffef62ce 66f816ddb69d4c60c61173e4ac6e610e3fb9c1fa3d197b3a> https://participate.icann.org/p5hsmgf4tds/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar ** Please let me know if your name has been left off the list ** Mailing list archives: <http://mm.icann.org/pipermail/gnso-rpm-providers/> http://mm.icann.org/pipermail/gnso-rpm-providers/ Main wiki page for the working group: https://community.icann.org/x/wCWAAw Thank you. Kind regards, Terri

1 0