Dear All, Please see the action item below from the WG meeting on 17 September: Sunrise Recommendation #2 and Small Team 2 Suggested Language: ACTION ITEM: Discuss WG suggested revisions to the Recommendation and Implementation Guidance along with the suggested language from Small Team 2. Please see the suggested revisions to Sunrise Recommendation #2 in the Google document at: https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-.... Please also review the following Suggested Language from Small Team: Suggestion Language from Small Team 2: “Implementation Guidance to Sunrise Recommendation 2: The IRT should explore the possibility of a third party challenge mechanism as one of the possible means, among others (for example, direct enforcement by ICANN Compliance) to implement this Recommendation to enforce the implementation of this recommended new RA provision. Any such third party challenge mechanism should include appropriate safeguards for registries.” Please post any comments or questions for discussion to this list ASAP. Kind regards, Mary, Ariel, and Julie From: GNSO-RPM-WG <gnso-rpm-wg-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org> Date: Thursday, September 17, 2020 at 2:49 PM To: "gnso-rpm-wg@icann.org" <gnso-rpm-wg@icann.org> Subject: [GNSO-RPM-WG] Notes and Action Items: RPM PDP WG Meeting 17 September 2020 Dear All, Please see below the action items captured by staff from the RPM PDP Working Group call held on 17 September 2020 at 17:00 UTC. Staff will post these to the wiki space. Please note that these are high-level notes and are not meant as a substitute for the recording, chat room, or transcript. The recording, Zoom chat, transcript and attendance records are posted on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/2020-09-17+Review+of+all+Ri.... Best Regards, Julie Julie Hedlund, Policy Director == NOTES & ACTION ITEMS Actions: Sunrise Recommendation #2 and Small Team 2 Suggested Language: ACTION ITEM: Discuss WG suggested revisions to the Recommendation and Implementation Guidance along with the suggested language from Small Team 2. Suggested Language from Small Team 1 on ALP relating to Sunrise Questions #3 and #4: ACTION ITEM: Staff will check with GDS to see if this recommendation is feasible. URS Final Recommendation (was #1): ACTION ITEM: Minor change in the contextual language – change from “the Working Group affirms” to “the Working Group further notes”. New URS Final Recommendation: ACTION ITEM: Remove the quoted text from Purpose 6-PA5 and move it to a footnote for reference. Notes: 1. Updates to Statements of Interest: No updates provided. 2. Sunrise Recommendation #2 and Small Team 2 Suggested Language; see: Suggested Language from Small Team 2<http://mm.icann.org/pipermail/gnso-rpm-wg/2020-September/004503.html> andhttps://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW-... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAqL...> -- Concerns raised by Maxim Alzoba about the two examples that they are too broad. -- Further to my point, as was noted earlier, this is a high-level policy recommendation; the IRT will be tasked with implementing this recommendation and our guidance should be sufficient to allow the IRT to craft an appropriately tailored RA amendment and (hopefully a challenge mechanism with appropriate safeguards built in so as to not inhibit legitimate registry activities -- I agree (I think) with Jason insofar as implementing this recommendation may necessitate a third party challenge mechanism akin to the PDDRP or pICDRP so aggrieved TM owners can challenge a registry activity and there can be a ruling as to whether the activity is legitimate or not. -- Concerns about misinterpretation if we are not clear. -- Perhaps we can just add a third bullet that says, “registry activities that have a bona fide legitimate basis or rationale are explicitly not intended to be inhibited by this provision”. -- As a staff suggestion for your consideration — perhaps we can include something to this effect: “The Working Group notes that this recommendation is not intended to preclude or restrict Registry operator’s legitimate business practice and pricing practice that are compliant with ICANN policies and procedures.”? -- Add to bullet point 1 (slightly revised)-- adding: "without countervailing rationale and/or reasonable activity by registries, including handling of dictionary terms.” -- Suggest addition to the Recommendation: “The Working Group recommends that the Registry Agreement for future new gTLDs include a provision stating that a Registry Operator shall not operate its TLD in such a way as to have the effect of [intentionally] circumventing the mandatory RPMs imposed by ICANN or restricting brand owners’ reasonable use of the Sunrise rights protection mechanism.” Text in brackets. -- Don’t think adding “intentionally” in the rec helps us because it doesn’t really address Maxim’s concern, because reserving a name intentionally as part of an ALP or something is still intentional. ACTION ITEM: Discuss suggested language from Small Team 1 on the list. Suggestion Language from Small Team 2: “Implementation Guidance to Sunrise Recommendation 2: The IRT should explore the possibility of a third party challenge mechanism as one of the possible means, among others (for example, direct enforcement by ICANN Compliance) to implement this Recommendation to enforce the implementation of this recommended new RA provision. Any such third party challenge mechanism should include appropriate safeguards for registries.” -- Why would the proposed additional implementation guidance language be a beneficial addition to the existing implementation guidance? Answer: Takes some of the burden off of Compliance. -- Does the phrase “explore the possibility of a third party challenge mechanism” encompass and authorize the IRT’s adoption and implementation of such a mechanism if it is found to be possible? Answer: To amend the language to “explore and if possible implement”. -- Would the challenge mechanism be operative against ICANN, a registry alleged to have circumvented a RPM, or both? Answer: It would be against the registry that is alleged to have circumvented it. There already is a way to challenge staff and Board actions. -- This would not be a mechanism as a way for ICANN Org Compliance to enforce – this would be a separate mechanism? Answer: Correct. Discussion: -- Opposed to this language. Sunrise Rec #2 itself is still vague. -- Registries agree by contract to comply, but IRTs cannot develop consensus policies or revise contract terms – so this is out of scope. -- This is putting one vagueness on top of another. -- What authority does an IRT have to do these types of things. -- Didn't an IRT create the URS, PDDRP, PICDRP, to name a few? -- Sunrise Rec #2 seems to beg for a third-party challenge mechanism. -- 1. Clause could include a clause to include a challenge mechanism. 2. IRTs do this sort of thing all the time (e.g. the AGB and all of the challenge mechanisms with it). -- Idea is that there would be an independent panel that an aggrieved party could go to – so not relying on ICANN Compliance and could be an independent review. -- Why isn't a complaint to ICANN compliance sufficient here? I agree with David that it's especially problematic to move from "vague standard applied by single decisionmaker" to "vague standard applied by various possible decisionmakers" -- Would this be a time-sensitive mechanism? -- Because in response to the complaints over the years on sunrise circumvention, ICANN has consistently said they could do nothing about it. -- Circumvention itself is not defined, so cannot be enforced. -- ICANN compliance would need to have a role, in a similar way it does in a PICDRP for instance; an independent panel would actually perform the substantive review and ICANN compliance would implement a panel finding, for example. -- If Rec 2 is "start doing something about it" then why isn't ICANN compliance the appropriate place? -- URS and PDDRP are not Consensus Policy either. They were created during implementation of the 2007 GNSO PDP on New gTLDs. -- Divergence in the WG on this suggested text. ACTION ITEM: Discuss the suggested language on the list. 3. Suggested Language from Small Team 1 on ALP relating to Sunrise Questions #3 and #4; see: http://mm.icann.org/pipermail/gnso-rpm-wg/2020-September/004505.html “The Working Group recommends guidance to the Implementation Review Team that the Approved Launch Program (ALP) Application Review Guidelines be reviewed and clarified in order to address feedback obtained by the working group regarding the length of time and complexity of process involved in seeking to obtain approval for an ALP, and in particular recommends that the IRT consider the following: 1. Where ICANN can not make a determination regarding an ALP application it will notify the Registry Operator to that effect within 45 days stating explicit reasons for needing more time and further, provide a decision date projection plan within a time period not to exceed another 30 days. There should be a reasonable expectation that all negotiations should be completed within a 7 month period. 2. Where ICANN determines to decline an ALP application or make a request for further information ICANN will include a full explanation of the aspects of the ALP application ICANN deems to be acceptable and the aspects ICANN deems to be unacceptable.” Discussion: -- The reference to an ALP being adopted is in the TMCH procedures if approved it is outside of or in contravention of Sunrise. This is directly related to the operation of the Sunrise. -- TMCH RPMs Requirements document that is incorporated by reference into the AGB and the RA (http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements-...). 4.5 deals with Launch Programs, specifically 4.5.2: Registry Operator MAY, prior to the start date of its Sunrise Period, apply to ICANN for approval to conduct a registration program not otherwise permitted by these TMCH Requirements. Such a registration program application could, for example, provide for authorization to implement programs set forth in Registry Operator’s application for the TLD, which, if set forth in reasonable detail in the application for the TLD, will carry a presumption of being approved, unless ICANN reasonably determines that such requested registration program could contribute to consumer confusion or the infringement of intellectual property rights. If Registry Operator seeks ICANN’s approval of a program under this Section 4.5.2, and such requested registration program is substantially similar to a...” ACTION ITEM: Staff will check with GDS to see if this recommendation is feasible. 4. URS Final Recommendations; see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMPW... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk95...> a. URS Final Recommendation (was #1): -- Recommendation language stays as is. -- Contextual language – inserted text to reflect the WG’s agreement to include the EPDP Phase 1 Recommendation #27 Wave 1 Report. ACTION ITEM: Minor change in the contextual language – change from “the Working Group affirms” to “the Working Group further notes”. b. New URS Final Recommendation: -- This is based on URS Question 1. -- It is a new recommendation based on responses received in the public comment. -- The context comes from the WG discussion of URS Question 1. -- The public comment review is based on the discussion of URS Question 1 and suggestion for a recommendation. Discussion: -- Questions about the contextual language. Concern that the reference to Purpose 6-PA5 is somehow binding. -- Staff noted that it is not binding and there was no change to the new recommendation resulting from the WG’s review of the ICANN org’s EPDP Phase 1 Recommendation #27 Wave 1 Report. ACTION ITEM: Remove the quoted text from Purpose 6-PA5 and move it to a footnote for reference.