April 2019 - GNSO-RPM-WG - lists.icann.org

ACTIONS & NOTES: RPM PDP WG 08 August 2018
by Ariel Liang Feb. 11, 2020

Feb. 11, 2020

Dear All, Please see below the action items and notes captured by staff from the RPM PDP WG call held on 08 August 2018 (17:00-18:30 UTC). Staff have posted to the wiki space the action items and notes. Please note that these will be high-level notes and are not meant as a substitute for the recording. The recording, AC chat, and attendance records are posted on the wiki at: https://community.icann.org/x/uwNpBQ Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == ACTION ITEMS: * Brian Beckham to send to the WG a WIPO FAQ with regard to “Doe Complaint”. * Renee Fossen to provide more information on HSTS-preloaded domain suspension issues in the written responses. * Staff to recirculate the Super Consolidated URS Topics Table document * WG members to provide substantive comment and raise anything they believe is missing on the WG mailing list by COB Tue, 14 Aug. Co-Chairs will then discuss among themselves to determine further actions/process. * WG members to finish reviewing the rest of the Super Consolidated URS Topics Table document, including page 24-35, during next week’s call. Later period to discuss larger policy issues. NOTES: Review Agenda/Statements of Interest * George Kirikos has become a member of the At-Large Community: https://community.icann.org/display/gnsosoi/George+Kirikos+SOI General Comment on the Super Consolidated URS Topics Table Document * The topics in the table were developed by the WG members and deliberated on by the WG & URS Sub Teams. Each Sub Team then did very substantial work on data collection and reviewing what came back. While the actual Sub Team recommendations and suggestions captured in this document are what is intended the WG should discuss - to see if it wishes to develop policy or operational recommendations - discussion over what should be on the actual list of topics should not be reopened unless the WG agrees to do so. We encourage all WG members to review all the previous reports from each Sub Team, and all the documents they worked on. They are linked in this Super Consolidated document (page 2). * The Super Consolidated document is a summary of findings and suggestions by the Sub Teams. The Table does not mean to limit/restrict recommendations from the WG members. If there is any issue overlapping with UDRP, can possibly be carried over to the phase II of the PDP. * Is it possible to add additional topics to the Super Consolidated Table? One WG member said that access to the Courts, for example, is a topic he raised, which isn't in the table. Statute of Limitations, whether URS should apply to legacy gTLDs as a consensus policy, are just a few of the topics not in the table. He brought it up in November 2017 (see: https://mm.icann.org/pipermail/gnso-rpm-wg/2017-November/002585.html ) and it was reflected in a later document. That's a critical issue for registrants. if they don't have access to the courts to challenge a URS decision, then it's a huge denial of their rights. * While the chart is not meant to foreclose further discussion, it is a good faith attempt at capturing the work of the sub teams. The purpose of today's, and likely the next few, calls was to make sure this was an accurate and comprehensive reflection of our discussions so far. That said, WG members should bear in mind that we are seeking consensus, so items which are unlikely to achieve that may not be appropriate to reflect as a recommendation, but could be included in public comments on the Initial Report. Also, before adding items to this chart, we will want to work with staff to see whether such topics was previously discussed, and if so, the level of agreement/consensus. In other words, it is not necessary final, but is equally an opportunity to reintroduce topics which have been discussed, but for which consensus is/was not possible. * Could we create a list of "missing issues" -- a list of issues raised in this call (and calls to follow); we can evaluate the nature and weight of these ideas later. * Regarding the Action Items highlighted in column 3 of the table, Providers ST will do a first pass of the responses from the Providers to the follow-up questions, and then discuss the issues that they identified and proposed suggestions with the full WG. Limited filing period (page 3) * One WG member believes that there should be limitation for filing period to bring URS Complaints, so the domain registered many years ago would not be subject to unfair treatment. He said a registrant who owns a domain for 20 years, for example, shouldn't have to be concerned about a policy that can take their domain down with very short time period to respond. * Other WG members said this was discussed, and did not achieve agreement. That would only even be an option if the trademark pre-dated. This is unlikely to be a situation in practice where a URS was brought because it would probably not be a "slam dunk" case after 20 years unless there had been a change of circumstances. * On the issue of delay and laches - as reported by the Docs Sub Team, the data did not provide any basis for which a policy recommendation should be made. The Providers and Practitioners Sub Teams also did not uncover any specific issues that came to either practitioners' or providers' attention. Administrative Review (page 3-4) * One WG member asked whether ICANN should bring Providers into contractual relationship in order to enforce the URS Rules & Procedures. Another member said it probably need to be ICANN’s legal department to enforce the rules & procedure. * URS Providers have MoU with ICANN. Whether it is ICANN’s compliance department or legal department to enforce the rules & procedures, it should not be controversial that Providers must abide by them. * An MOU could be legally enforceable, depending on the circumstances. 500-word Complaint limit (page 4-5) * On 500-word Complaint Limit - Practitioners' survey results were split (out of 12, 5 agree it's sufficient, 4 disagree); results included feedback from some that the word limit was too low: "arbitrary and often insufficient" and "should be slightly increased". * One member said he understands and generally agrees with the decision not to suggest an expansion of the word limit, he wonders if there aren't situations (multi- domain challenges, etc.) where a Complainant or Respondent might be given the opportunity to request an expansion. This point can be captured for decisional phase. * Another member suggested that perhaps providers can provide stats on the average word length of complaints, to see how close to the 500 words they are at present. (i.e. a table of distributions, e.g. 10% under 200 words, 20% between 201 and 300, etc.) Amending the Complaint in light of GDPR/Temp Spec (page 5-6) * One member believes that 2-3 days might not be a good rule (e.g. weekends, time to research, etc.). Maybe 5 business days. * WIPO’s approach to “doe complaints” has been very helpful and provides some comfort that the lack of true registrant/registrant organization data masked due to GDPR will not result in a deficient complaint for an omitted respondent. * ACTION ITEM: Brian Beckham to send to the WG a WIPO FAQ with regard to “Doe Complaint”. * Forum is asking for amendment of the complaint in UDRP - under the rules that's not allowed in URS. SMD Files (page 6-7) * SMD files are used for limited purpose of demonstrating the use. * Recollection is that SMD files would be passed to the Examiners and relay the critical information related to the TM registration. That's why some people are surprised by the limited info SMD files would provide. * The SMD files contain some basic human-readable information, with the rest of the information coded. For example, the trademark itself is human-readable but the applicable Nice classification is coded. A SMD file is used by registries/registrars for validation, and as Greg noted, to demonstrate use. From the TMCH provider: http://www.trademark-clearinghouse.com/help/faq/which-information-does-smd-… * If the intent of the STI was that the SMD file would be a file summary, that got lost somewhere along the way, way before the SMD file was designed by the TMCH providers. * Rules 3(b)(v) Specify the trademark(s) or service mark(s) on which the complaint is based and the goods or services with which the mark is used including evidence of use –which can be a declaration and a specimen of current use in commerce - submitted directly or by including a relevant SMD (Signed Mark Data) from the Trademark Clearinghouse * It might be useful to look at the spec that they relied on. But the real question is how should the examiner get the relevant data about the Complainant’s mark. The SMD file is probably not the answer, if it was ever intended to be. * the Examiner is not required to second-guess the SMD file. Its existence is sufficient that the mark has had use validated by the TMCH. Other Topics (page 7-8) * These are policy proposals can be brought up when WG members are proposing changes to the URS policy itself. Charter asks us to address the question whether the URS should become a consensus policy applicable to legacy domains. Charter is not specific regarding whether such discussion should occur in phase I or phase II. This feedback illustrates that the ST didn't get to propose policy changes, it is for the WG to discuss and propose changes. * when we reference the STI and IRT reports, we need to keep in mind they only had about 1-2 months to complete their work and produce a report; they were not standard PDP working groups and had limited charters and mandates, which were set by the Board * This is feedback from one Provider, who may want to grow their business. Practitioners survey are from Complaints' side. Need to have a balanced solution when considering the input. * There were plenty of practitioners that represent registrants in the Subgroup, although their experience was largely with the UDRP. Duration of response period (Page 11) * One member believes that if the URS continues in its current form, it would affect valuable domain names. The ones the registrants that do want to defend them, 14 days are not sufficient. 20 days may be more appropriate. It should be based on the age of the domain name. If a domain is 3 months, it will have a shorter period to respond. If you own a domain name for 5-10 years, response period would be longer so less urgency. * Several other WG members disagree. The URS is supposed to be an expedited proceeding so increasing the length of time of a streamlined proceeding defeats the purpose. At most, there could be an additional 3 or 4 days extension period for cause. The point is that there are enough circumstances that give rise to the URS 'quick response' that we should NOT make assumptions into policy. It is an assumption that an "aged" domain would not require a fast response. In Mexico, we have not been able to file a domain name case due to Courts ignorance about the subject and also, because it could take years to be solved. We're spinning out fo control - extending the time to respond to URS cases just because a domain registration is not new defeats the purpose of fast action to take down an infringing domain once it's discovered. The URS is meant to address clear and convincing cases of infringement. A person registers a domain name for less than $50 and brand owner find out about at some point and then files an injunction in court for tens of thousands of dollars. Where is the balance. Examiners Guide (page 13) * The WIPO guidance for examiners took 1500 hours to develop. * The WIPO guidance is relevant to the URS, the elements are shown are the same and the differences include the burden of proof, word limit, etc. A lot of WIPO guidance goes to the shade of grey issues. URS is for clear black/white cases, so if there is a URS guidance it would likely be abbreviated. Duration of Suspension Period & Review of Implementation (page 21-23) * One WG member suggests to find out how much cost for registries & registrars to comply with the URS rules and procedures. Need to get data/feedback from the registries/registrars. * Other WG members are not sure "cost of implementation of URS" for Registries/Registrars is relevant to effectiveness of URS. We don't need to do a cost/benefit analysis (the costs & benefits aren't ICANN's), the providers, registrars, registries need to be asked if they are overburdened by the costs of compliance. * There is an action item to contact the registries/registrars about these issues. Timing TBD due to Sunrise & Claims survey launch. Other topics (page 23-24) * One WG member thinks the HSTS issue is not difficult to fix. The Providers need to improve their technical applicability to resolve the issue. Renee Fossen from Forum disagrees. * ACTION ITEM: Renee Fossen to provide more information on HSTS-preloaded domain suspension issues in the written responses. NEXT STEPS * ACTION ITEM: Staff to recirculate the Super Consolidated URS Topics Table document and ask all WG members to provide substantive comment and raise anything they believe is missing on the WG mailing list by COB Tue, 14 Aug. Co-Chairs will then discuss among themselves to determine further actions/process. * ACTION ITEM: WG to finish reviewing the rest of the Super Consolidated URS Topics Table document, including page 24-35. Later period to discuss larger policy issues.

20 45

RPM PDP WG Sunrise Sub Team Status Report 26 April 2018
by Julie Hedlund April 26, 2019

April 26, 2019

Dear members of the RPM PDP WG, On behalf of David McAuley and Greg Shatan, Co-Chairs of the Sunrise Sub Team, please see below the weekly progress report to the full RPM PDP WG. David acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-24+Sub+Team+for+Su…> on Wednesday, 24 April. Current Status: The Sub Team continued discussion of preliminary recommendations and review of individual proposals with respect to the Sunrise Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+Drafts%2C+Res…. At the meeting on 24 April the Sub Team discussed tentative preliminary recommendations with respect to question 1 with related individual proposal #9, and question 5(a). The Sub Team began discussion of question 6 and related proposals #2 and #4. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, the Sub Team Co-Chairs agreed to open discussion threads on the list on question 1 with related individual proposal #9, and on question 5(a). At meeting on 02 May, the Sub Team will continue discussion of agreed Sunrise Charter Question 6, in conjunction with Proposals #2 & #4, discuss agreed Sunrise Charter Question 8, and (if time permits) discuss agreed Sunrise Charter Question 9, in conjunction with Proposal #13. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

RPM PDP WG Trademark Claims Sub Team Status Report 25 April 2019
by Julie Hedlund April 25, 2019

April 25, 2019

Dear members of the RPM PDP WG, On behalf of Martin Silva and Roger Carney, Co-Chairs of the TM Claims Sub Team, please see below the weekly progress report to the full RPM PDP WG. Roger acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-24+Sub+team+for+Tr…> on Wednesday, 24 April. Current Status: The Sub Team continued discussion of preliminary recommendations and review of individual proposals with respect to the Trademark Claims Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+drafts%2C+res…. At the meeting on 24 April the Sub Team continued the discussion of tentative preliminary recommendations with respect to question 1 and related individual proposal #5, as well as the reference to question 3. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, the Sub Team Co-Chairs agreed to initiate discussion threads on the list on question 1 and related individual proposals #5 and #6, and on question 3. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

RPM PDP WG Sunrise Sub Team Status Report 22 April 2018
by Julie Hedlund April 22, 2019

April 22, 2019

Dear members of the RPM PDP WG, On behalf of David McAuley and Greg Shatan, Co-Chairs of the Sunrise Sub Team, please see below the weekly progress report to the full RPM PDP WG. Greg acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-17+Sub+Team+for+Su…> on Wednesday, 17 April. Current Status: The Sub Team continued discussion of preliminary recommendations and review of individual proposals with respect to the Sunrise Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+Drafts%2C+Res…. At the meeting on 17 April the Sub Team discussed tentative preliminary recommendations with respect to question 4(a), (b), (c), and (d) with related individual proposal #11. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, per the action item from the 03 April meeting, staff provided draft language for preliminary recommendations for which proposals have been discussed. Also, per the action from the 17 April meeting, staff have started separate discussion threads on the Sub Team email distribution list on question 3 (including Proposals #10 & #11) and question 4. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

RPM PDP WG Trademark Claims Sub Team Status Report 19 April 2019
by Julie Hedlund April 18, 2019

April 18, 2019

Dear members of the RPM PDP WG, On behalf of Martin Silva and Roger Carney, Co-Chairs of the TM Claims Sub Team, please see below the weekly progress report to the full RPM PDP WG. Martin acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-17+Sub+team+for+Tr…> on Wednesday, 17 April. Current Status: The Sub Team continued discussion of preliminary recommendations and review of individual proposals with respect to the Trademark Claims Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+drafts%2C+res…. At the meeting on 17 April the Sub Team continued the discussion of tentative preliminary recommendations with respect to question 2(a),(b), (c), (d), and (e), and related individual proposals #1 and #12. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, per the action item from the 03 April meeting, staff provided draft language for preliminary recommendations for which proposals have been discussed. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

RPM PDP WG Sunrise Sub Team Status Report 12 April 2018
by Julie Hedlund April 12, 2019

April 12, 2019

Dear members of the RPM PDP WG, On behalf of David McAuley and Greg Shatan, Co-Chairs of the Sunrise Sub Team, please see below the weekly progress report to the full RPM PDP WG. David acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-10+Sub+Team+for+Su…> on Wednesday, 10 April. Current Status: The Sub Team continued discussion of preliminary recommendations with respect to the Sunrise Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+Drafts%2C+Res…. At the meeting on 10 April the Sub Team discussed tentative preliminary recommendations with respect to question 3 with related individual proposal #10, and began a discussion of question 4 with related individual proposal #11. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, per the action item from the 03 April meeting, staff provided draft language for preliminary recommendations for which proposals have been discussed. This draft language will be circulated to the sub team for review. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

RPM PDP WG Trademark Claims Sub Team Status Report 12 April 2019
by Julie Hedlund April 12, 2019

April 12, 2019

Dear members of the RPM PDP WG, On behalf of Martin Silva and Roger Carney, Co-Chairs of the TM Claims Sub Team, please see below the weekly progress report to the full RPM PDP WG. Martin acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-10+Sub+team+for+Tr…> on Wednesday, 10 April. Current Status: The Sub Team continued discussion of preliminary recommendations with respect to the Trademark Claims Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+drafts%2C+res…. At the meeting on 10 April the Sub Team discussed tentative preliminary recommendations with respect to question 2, and related individual proposals #1 and #12. See individual proposals at: https://community.icann.org/x/R6EWBg. In addition, per the action item from the 03 April meeting, staff provided draft language for preliminary recommendations for which proposals have been discussed. This draft language will be circulated to the sub team for review. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May.

1 0

PLEASE READ: Transitioning to Zoom
by Nathalie Peregrine April 11, 2019

April 11, 2019

Dear all, As you may already know<https://www.icann.org/news/blog/transitioning-icann-s-remote-participation-…>, ICANN is replacing the Adobe Connect tool with Zoom. As with all transitions, there will be a learning curve for community members as well as for staff but through the tools, information and proposed next steps outlined below, we hope we can make this transition is as smooth as possible. The complete roll out is expected to be finalized by ICANN65, Marrakech, however many groups will be noticing their calls scheduled on Zoom as of next week. Please see below a few pointers which we hope will help get everyone ready. How is staff preparing for the transition? Staff has received training, has viewed training videos and has had the opportunity to go through practice runs in Zoom rooms. This should facilitate our assistance in getting you all up to speed and work with the different groups on transitioning existing practices to the zoom environment. What is available to the community to prepare for the transition? Staff is reaching out to Stakeholder Group and Constituency, as well as PDP Working Group, leadership teams to introduce them to Zoom and ensure they will be comfortable running their first sessions with this new tool. Staff will also present Zoom to community members at the beginning of each conference call to ensure all understand the different functions and how to use them. The attached Welcome to Zoom! document will be presented at the same time. SOAC Support staff will be present during each call to assist. What stays the same? (please open the Welcome to Zoom! document for a visual) Zoom rooms still show participant and chat pods. The public chat pods will be archived and circulated as per usual, the private chat content remains inaccessible to ICANN Org staff). Documents can still be viewed in the Zoom room but please note that this sharing is a screen share which means it is no longer possible to scroll through documents unless the person who is sharing their screen does so. It is possible to join the audio via audio bridge (telephone) or via the computer. Zoom VoIP quality is excellent. It will still be possible to get a dial out for those unable to connect to the Zoom room. What changes? (please open the Welcome to Zoom! And the FAQ documents) Participants need to click on the participant list and the chat to activate them. This just takes two seconds. The content of the chat only appears from participant connection time. This means if you joins 4 mins late, you will not be able to access the first 4 mins of the chat. Zoom is notified of this and is looking into resolving the issue. The entire content of the chat transcript will however be available immediately after the end of the call once it gets posted / circulated by the host. Several documents can be viewed at the same time if several staff members are screensharing, this will allow you to navigate (as applicable) to Notes, Agenda and Documents in your own time during the call. Documents will be able to be shared via the chat to allow all to download materials to their computers during the call. The mobile app does not require you to remain in the app in order to hear the zoom room audio. Please open the attached FAQ document for any additional queries you may have. If you have any comments, questions or suggestions, please let us know – our objective is to make sure this transition is as smooth as possible. Kind regards, The GNSO Team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/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

RPM PDP WG Trademark Claims Sub Team Status Report 08 April 2019
by Julie Hedlund April 8, 2019

April 8, 2019

Dear members of the RPM PDP WG, On behalf of Martin Silva and Roger Carney, Co-Chairs of the TM Claims Sub Team, please see below the weekly progress report to the full RPM PDP WG. Martin acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-03+Sub+team+for+Tr…> on Wednesday, 03 April and the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-03-27+Sub+team+for+Tr…> on Wednesday, 27 March. Roger acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-03-11+ICANN64+Kobe+-+…> on Monday, 11 March at ICANN64. Current Status: The Sub Team continued discussion of preliminary recommendations with respect to the Trademark Claims Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+drafts%2C+res…. At the meeting on 11 March at ICANN64 the Sub Team discussed tentative preliminary recommendations with respect to questions 1 and 3(b). At the meeting on 27 March the Sub Team discussed tentative preliminary recommendations with respect to question 2(a), (b), (c), (d), and (e). At the meeting on 03 April the Sub Team discussed tentative preliminary recommendations with respect to question 3(b). Staff also were given the action to draft language for preliminary recommendations for which proposals have been discussed. This draft language will be provided to the sub team for review. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May. On 22 and 29 May the Sub Teams will provide reports on all preliminary recommendations to the WG.

1 0

RPM PDP WG Sunrise Sub Team Status Report 08 April 2018
by Julie Hedlund April 8, 2019

April 8, 2019

Dear members of the RPM PDP WG, On behalf of David McAuley and Greg Shatan, Co-Chairs of the Sunrise Sub Team, please see below the weekly progress report to the full RPM PDP WG. Greg acted as chair during the meeting<https://community.icann.org/display/RARPMRIAGPWG/2019-04-03+Sub+Team+for+Su…> on Wednesday, 03 April. Current Status: The Sub Team continued discussion of preliminary recommendations with respect to the Sunrise Charter questions. See the Charter questions and the summary table on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/Documents%2C+Drafts%2C+Res…. At the meeting on 03 April the Sub Team completed the discussion of preliminary recommendations with respect to question 3. Staff also were given the action to draft language for preliminary recommendations for which proposals have been discussed. This draft language will be provided to the sub team for review. Next Steps: Per the revised timeline in the Proposed Process for TMCH Sunrise & Trademark Claims Sub Teams, the goal is for the Sub Team to complete the development of preliminary recommendations based on all data reviewed to date and the review of individual proposals by 15 May. On 22 and 29 May the Sub Teams will provide reports on all preliminary recommendations to the WG.

1 0

**REMINDER: UPDATED EOI DEADLINE 8 APRIL 2019** Expressions of Interest Sought for Chair of GNSO EPDP on the Temporary Specification for gTLD Registration Data – Phase 2
by Julie Bisland April 5, 2019

April 5, 2019

https://www.icann.org/news/announcement-2019-03-01-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> LOS ANGELES –1 March 2019 – The Generic Names Supporting Organization (GNSO) is looking for expressions of interest to chair Phase 2 of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. The EPDP Team recently completed its Phase 1 work and is expected to commence planning for Phase 2 at ICANN64 meeting in Kobe, Japan. During Phase 2, the EPDP Team will work on a system for standardized access to non-public registration data, topics identified in the annex to the Temporary Specification, as well as a number of carry over items from Phase 1. The GNSO Council is looking to appoint a neutral Chair to the EPDP Team. With such an important issue under consideration, significant responsibility comes with the role to ensure the success of deliberations. The EPDP Team is expected to have regular calls, although it may be necessary to hold calls more frequently if need arises. Additionally, the EPDP Team may have face-to-face meetings in order to meet the required milestones of the EPDP. The EPDP Team is expected to start developing the work plan for Phase 2 at ICANN64 in Kobe for which the GNSO Council may provide further guidance. There will be no compensation associated with the role of the EPDP Team Chair; however, travel associated with any face-to-face meetings may be supported by ICANN org. To express interest in this role, please submit an Expression of Interest to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org> by 22 March 2019 at 14:00 UTC. Please answer the following questions: · What is your interest in this position? · What particular skills and attributes do you have that will assist you in chairing the EPDP? · What is your knowledge of the Temporary Specification for gTLD Registration Data, EPDP Team's Phase 1 work and associated challenges and requirements particularly as it relates to the EPDP? · What is your experience in and knowledge of the GNSO Policy Development Process, ICANN's consensus policies, ICANN's registry agreements and the Registrar Accreditation Agreement related to gTLD registration data? · Are you able to commit the time required and necessary work needed to chair the EPDP, noting that this to a certain extend will be dependent on the EPDP Team's work plan for phase 2 which is under development? · Conflict of Interest Statement – do you have any affiliation with or involvement in any organization or entity with any financial or non-financial interest in the subject matter of this EPDP? · Please also include: · A link to an up-to-date Statement of Interest (SOI) - https://community.icann.org/display/gnsosoi/New+SOIs · A statement confirming your commitment and ability to act neutrally. Application materials will be reviewed by the Council leadership and will not be shared publicly. Names of applicants, including the recommended candidate, will be shared with the GNSO Council for its consideration. The Council leadership is expected to provide its recommendation to the GNSO Council in time for the GNSO Council meeting on 18 April 2019. Additional questions and inquiries can be sent to EOI-EPDPTeam-Chair(a)icann.org<mailto:EOI-EPDPTeam-Chair@icann.org>. More Information · Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> · Additional information about the EPDP is located in Annex-A1 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> of the ICANN Bylaws and the EPDP Manual [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> [PDF, 345 KB]. · EPDP Charter<https://community.icann.org/x/0opHBQ> · EPDP wiki<https://community.icann.org/x/IYEpBQ> · EPDP Phase 1 Final Report [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…> [PDF, 2.7 MB] About EPDP On 17 May 2018, the ICANN Board approved the Temporary Specification for gTLD Registration Data. The Board took this action to establish temporary requirements for how ICANN and its contracted parties would continue to comply with existing ICANN contractual requirements and community-developed policies related to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). The Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement (RA) and Registrar Accreditation Agreement (RAA). Following adoption of the Temporary Specification, the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." This Consensus Policy development process on the Temporary Specification would need to be carried out within a one-year period. Additionally, the scope includes discussion of a System for Standardized Access to Non-Public Registration Data. However, the discussion of a Standardized Access System will occur only after the EPDP Team has comprehensively answered a series of "gating questions" and non-objection by the GNSO Council. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. ANNEX A – CHAIR RESPONSIBILITIES AND EXPECTATIONS As outlined in the GNSO Working Group Guidelines, the purpose of a Chair is to call meetings, preside over working group (WG) deliberations, manage the process so that all participants have the opportunity to contribute, and report the results of the WG to the Chartering Organization. These tasks require a dedicated time commitment as each call has to be prepared, the agenda concretized, and relevant material has to be reviewed. The Chair shall be neutral. While the Chair may be a member of any group which also has representation on the EPDP Team, the Chair shall not act in a manner which favors such group. The Chair shall not be a member of the PDP Team for purposes of consensus calls. In addition, it is required – that interested candidates have considerable experience in Chairing working groups, and direct experience with at least one GNSO Policy Development Process throughout its lifecycle would be an advantage. Familiarity with the functioning of a Working Group is important to understand the various leadership skills that are necessary to employ during a WG's lifecycle. For example, a chair has to ensure that debates are conducted in an open and transparent matter and that all interests are equally represented within the WG's discussions. During the later stages of a WG when recommendations are drafted, a Chair will benefit from understanding the viewpoints of various members to ensure that an acceptable and effective outcome – ideally in form of consensus – can be achieved. In short, the EPDP Team Chair is expected to: 1. Attend all EPDP Team meetings to ensure continuity and familiarity with the subject matter and the on-going discussions; 2. Prepare meetings by reading all circulated materials; 3. Be familiar with the subject matter, including but not limited to GDPR and data protection laws, and actively encourage participation during the calls 4. Be active on the EPDP Team mailing list and invite EPDP Team participants to share their viewpoints; 5. Drive forward the EPDP Team and assure that discussions remain on point; 6. Work actively towards achieving policy recommendations that ideally receive full consensus; 7. Ensure that particular outreach efforts are made when community reviews are done of the EPDP Team's output; 8. Underscore the importance of achieving overall representational balance on any sub-teams that are formed; 9. Encourage and, where necessary, enforce the ICANN Standards of Behavior and resolve any conflicts in a timely manner. 10. Co-ordinate with ICANN staff and ensure that the EPDP Team is supported as effectively as possible 11. Conduct consistent timely reporting to the GNSO Council on the progress of the EPDP. Finally, as also pointed out the in GNSO Working Group Guidelines, 'appointing a co-chair(s) or vice-chair(s) may facilitate the work of the Chair by ensuring continuity in case of absence, sharing of workload, and allowing the Chair to become engaged in a particular debate.' As a result, similar tasks and skills are expected from vice chairs, although the overall workload may be reduced as a result of being able to share this with the Chair. Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/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

Re: [GNSO-RPM-WG] [Ext] Re: Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior
by Julie Hedlund April 5, 2019

April 5, 2019

Hi Paul, You may try it without the [icann.org] append, as in: https://www.icann.org/resources/pages/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> That should resolve. Best, Julie From: Paul Keating <Paul(a)law.es> Date: Wednesday, March 13, 2019 at 8:51 PM To: Julie Hedlund <julie.hedlund(a)icann.org>, "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [Ext] Re: [GNSO-RPM-WG] Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior I get a page does not exist error. From: GNSO-RPM-WG <gnso-rpm-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, March 13, 2019 at 10:08 AM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [GNSO-RPM-WG] Recent Correspondence Related to Complaints Issues within the RPM PDP WG & Expected Standards of Behavior Dear RPM PDP Working Group members, Please see the recent correspondence related to Complaints Issues within the Rights Protection Mechanisms PDP Working Group and Expected Standards of Behavior. These letters were posted on ICANN Org’s correspondence page on 9 & 10 March: https://www.icann.org/resources/pages/correspondence [icann.org] [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>.” Best regards Julie, Ariel & Mary _______________________________________________ GNSO-RPM-WG mailing list GNSO-RPM-WG(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg[cid:image001.png@01D4D99B…

3 3