September 2020 - GNSO-RPM-WG

Proposed Agenda for RPM PDP WG Meeting - Thursday, 01 October 17:00 UTC
by Julie Hedlund Sept. 30, 2020

Sept. 30, 2020

1 0

Proposed Amendment to Sunrise Rec 2 - Input by Friday 2 Oct
by Ariel Liang Sept. 30, 2020

Sept. 30, 2020

Dear WG members, Please find the proposed amendment to Sunrise Recommendation #2 in this google doc here: https://docs.google.com/document/d/1SmXWvS9M4TAtQ3gC3o4j9-jHaw3uIlWR_2D3lV2…. This amendment seeks to incorporate the extensive input provided by WG members during yesterday’s meeting; a separate google doc is created to facilitate your viewing. New/revised text is shown in redline. Please note that there is an alternative option to move the text highlighted in yellow into the “Context” section, if the WG determines this as a preferred approach. Please provide your input/suggestion on the mailing list by COB Friday, 2 October. The revised language, incorporating any further input from the WG, is scheduled to be finalized during the WG meeting on Tuesday, 6 October. Thank you, Mary, Julie, Ariel

1 0

ICANN69: GNSO Sessions - How to Get Organized and Remote Participation Details
by Julie Bisland Sept. 29, 2020

Sept. 29, 2020

Dear all, All ICANN69 GNSO sessions have been listed for your reference on the ICANN69 GNSO wiki page. For all access information and Zoom details however, please refer to the ICANN69 schedule on the meeting website. Registration is compulsory to access the meeting schedule. Access information will not be circulated via mailing lists. The ICANN meeting website, which ICANN Meetings’ Team has put together, allows you to download all GNSO-related meetings to your inbox calendar in one go. HOW TO DOWNLOAD ICANN69 SESSION INFORMATION TO YOUR CALENDARS: Step 1 - Create a profile and your personalized ICANN69 schedule Go to the Meeting Schedule webpage<https://69.schedule.icann.org/> and create a profile and login. Every session on the Full Agenda can be selected and added to your individual schedule by clicking the [cid:image001.png@01D6965B.0CB66A40] (blue ‘ + ’ box) in the upper right corner of each meeting. This adds it to your individual schedule, My Agenda, which you can then add to your calendar. See next step. Step 2 - To import your schedule into your calendar: once you’ve added all your chosen meetings to your schedule, click on [cid:image002.png@01D6965B.0CB66A40] (View My Agenda) * Click the down arrow next to Export * Select Export My Agenda (ics) * Open the exported meetings .ics and add to your chosen calendar * For Microsoft Outlook, right-click on the exported meetings .ics file and choose Show in Folder Right-click on the file, and select Open with Microsoft Outlook. Save & Close. Note: Your Agenda can only be exported from the desktop app; the ICANN69 phone app does not offer this feature Step 3 - All remote participation sessions will use Zoom rooms. You can find the Zoom room links for public meetings on the ICANN69 Meeting Schedule<https://69.schedule.icann.org/agenda#/?limit=20&sortByFields[0]=startsAt&so…>. PLEASE ENSURE YOU HAVE UPDATED YOUR ZOOM APP TO THE LATEST VERSION TO ACCESS ICANN69 SESSIONS. Please download the latest Zoom app<https://zoom.us/download> on your participation device (mobile or desktop computer). Need to learn or brush-up on using Zoom? Check out the Joining a Zoom Meeting Tutorial<https://support.zoom.us/hc/en-us/articles/201362193-Joining-a-Meeting>. Step 4 - Download the mobile app by searching for “ICANN Meetings” in your app stores. There are three options to connect your audio: 1) Via VoIP, choose Computer Audio (from a smartphone choose Call using Internet Audio) 2) Getting a dial out from Zoom to your phone, choose Call Me (from a smartphone choose Call My Phone) 3) Phoning into the audio bridge (access numbers and Meeting ID are provided for that option), choose Telephone Audio (from a smartphone choose Dial in) 3 LINKS TO BOOKMARK NOW: ICANN69 Meeting Schedule <https://69.schedule.icann.org/agenda#/?limit=20&sortByFields[0]=startsAt&so…> GNSO ICANN69 Wiki Page<https://community.icann.org/x/NwGNC> GNSO Session agendas<https://community.icann.org/x/CwGNC> For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

Notes and Action Items: RPM PDP WG Meeting 29 September 2020
by Ariel Liang Sept. 29, 2020

Sept. 29, 2020

Dear All, Please see below the action items captured by staff from the RPM PDP Working Group call held on 29 September 2020 at 13: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/x/xgG-C Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == Action Item: * Staff to propose the revised implementation guidance language for Sunrise Rec 2 based on today’s WG discussion, noting that the WG don’t have agreement to include the small group proposal re challenge mechanism but that the WG could (potentially) capture that discussion as part of context. WG Suggested Edits: * The WG accepted adding the word “intentionally” in the recommendation language. * Suggested options for the introduction sentence proceeding the bullet points: * The following is a non-exhaustive list of Registry Operator conduct that was identified in public comments as potentially having the effect of intentionally circumventing…; * The following are examples of Registry Operator conduct that some commentators raised in their public comments as potentially having the effect of intentionally circumventing ... etc.; * Some primary forms of perceived Sunrise misuse expressed by trademark owners of Registry Operators' conduct include... Some communities in the WG and commenters shared...  * Sunrise abuse of the type intended to be prohibited under this Recommendation include:  * Questions were raised with regard to what type of conducts that fall into the category of Sunrise abuse. Some WG members believe…. * Revise the first bullet to “Withholding, reserving, or self-allocating trademark-corresponding domains…” for grammatical reasons.   * Strike the term “or discouraging” as it introduce uncertainty. * Include "the WG did not agree on these examples"; "the WG also received views that pricing practices were not within its jurisdiction"; "other views emphasized the risk of targeting pricing decisions on legitimate business models, including the practice of identifying reserved names"  * The working group further notes that the IMPLEMENTATION of this recommendation is not intended to...  * Include a mention of the third party challenge mechanism proposal in the contextual language, as part of the discussion record, noting it did not receive widespread support in the WG but significant opposition. The question about how one could raise a complaint regarding a perceived violation of this recommendation still remains open. Discussion Notes: * “Perceived” Sunrise abuse is not helpful. If we can’t agree then we should be clear about it. * Maxim noted the concerns regarding the lack of safeguard for GeoTLDs in the implementation guidance language. * If we don't identify legitimate business practices, the preamble is meaningless  * intents are not important at implementation phase, there are no safeguards  * Also isn't it a bit chicken and an egg. If the new implementation of the recommendation' created the ambiguity that is complained of – won’t that become 'ICANN policy' itself therefore the preamble is rendered useless? Part of the concern is around language that is a bit open and can be misused. The language has huge potential of being used for extortion of money from Registries. If we just give free floating "registries can do bad things" language then many different things could happen inconsistent with what we agreed on * That's my concern, especially without a counterbalancing list of "we don't mean …."  * I note that the objections to the .madrid ALP included that it would interfere with TMCH registrants (and people here might agree)  * It’s not a red herring because this proposal is to cover new ground which is plausibly in the area Maxim has raised * We do not have consensus, so it opinion of some members and objected by some other members  * . sucks - what percent of all TLDs is that? it is less then 0.1%  * Mention the examples are shared in the public comments by trademark interests. It is not just groups like IPC and BC that provided the examples. If we want to clarify the language to make clear that we are talking about abuse perpetrated by ROs we can do that. Make it clear the examples are not WG agreed * if claims are still active at the later than sunrise registration - the harm is minimal (TM owner is notified and able to act)  * Reserving a name to a police dept is obviously legitimate. Reservation is a dynamical process, not static. For example, ICANN changed red Cross required list of reserved names almost 2 months ago. * But Sunrise period is concrete period for each TLD so intentional reservation practices circumventing Sunrise is the only issue. * Need to clarify what discriminatory pricing means – it is extremely high premium pricing, followed by extremely low land rush/GA pricing. Premium pricing and pricing alone are not basis for complaints. Need to be careful about the picket fence. * Direct price regulation will lead to issues in anti-monopoly agencies around the globe. * Is pricing really irrelevant when the price is based primarily on the value of a trademark corresponding to a given generic word?  * Go back to public comment to extract similar set of opposing opinions. * I take the point that the ALP needs to work better in order to provide a legitimate means of getting certain domains to certain parties without running afoul of Sunrise requirements. I don't think we can resolve ALP issues in context language--I just think a richer picture would help.With ALP it would have been much easier if we could have said something along the lines “The working group recommends there should be a predictable process to timely evaluate and approve or reject an ALP request”. * common words; dictionary words seems fair wording to add to the new Context language. Per the empirical research of Barton Beebe & Jeanne Fromer: in the US and Europe, 75-90% of the 1000 most used dictionary words are registered trademarks (in English; preliminary results suggest similar but somewhat lower results in other EU languages).The non-registered most-used dictionary terms include: “despite,” “died,” “difficult,” “disease,” “killed,” “lack,” “loss,” “older,” “problem,” "violence” “least,” “perhaps,” “probably,” “trying,” “drug,” “religious,” “wants,” “husband,” “wife,” “married,” “male,” “woman,” “daughter,” “herself,” and “himself”. * Again, were those proposed additions in the public comment? If not, we are just relitigating here. If they were, who said them? So what is in here already is from public comment. What others are suggesting is just re-litigation of their old positions. * Our goal here is to provide general guidance to an IRT which, if the Rec receives consensus, will be tasked with drafting a specific RA provision that more precisely delineates what registry conduct may trigger an enforcement action  * It is these kinds of judgment calls that should militate in favor of a third-party dispute resolution procedure applicable to this provision.Akin to picdrp  * With our recommendation to allow joint filings under pddrp, why isn't it a sufficient 3rd party enforcement mechanism to take action against discriminatory sunrise circumvention that results in second level infringement? why is something more, new, and undefined required?  * There is a concern that if we provide general guidance it continue to fail to translate into productive outcomes from IRT & GDS. * The question about how one could raise a complaint regarding a perceived violation of this recommendation still remains open. There is no widespread agreement and significant opposition to the third party challenge mechanism proposed by the small team. * But context doesn’t need to capture consensus views? At the very least surely we can say that someone the WG supported a new third-party challenge mechanism as a means of enhancing compliance around this proposed new RA provision. * I have no objection in trying to get to agree the implementation guidance, but do not think it is appropriate to compile everyone's various opinions and claim it is implementation guidance.  * I think we should give one more shot for a refined version of implementation guidance based on staff attempt at further revision based on today’s discussion. I think we can reach something generally agreeable with a few key refinements.   * Some members don’t believe the small team proposal on third party challenge mechanisms is in any way related to the recommendation. Just include it as some members suggested and raised it as an idea to supplement Rec 2. * If this proposal is mentioned, all the other proposals eliminated by the WG should also be mentioned. * It’s not “unrelated” to ICANN Compliance…. it would be coordinated with Compliance in a similar way PICDRP and PDDRP are.It’s clearly related because it is a challenge mechanism for the prohibited activity under this recommendation. * I do not think it can appear as just some thought external challenge and some did not - it is a policy rec that deserves a consensus call and we cannot simply send it along with equal treatment to other ideas, there is enough opposition to it that that would not be right.   * I don't believe we need a new 3rd party challenge mechanism for aggrieved trademark owners to communicate to ICANN Compliance a belief that they should enforce the new RA provision  * Unlimited number of third parties challenging domain names in an unpredictable manner will cause consumer confusion and loss of confidence.   * On what basis do you assert that? PICDRP and PDDRP didn’t have that effect  * We can simply put a header on the Deliberations (Opinions section) that none of the below ideas got consensus. That seems fine and universal.  * Agree that the IRT needs some guidance and that examples are useful. So something needs to go into the contextual language - maybe allow suggestions back to the list by Friday, close out on final language on list by next Tuesday. If no consensus on final language, then the context will only link to the public comments?

1 0

Post Call | Review of all Rights Protection Mechanisms (RPMs) in all gTLDS PDP WG | Tuesday, 29 September 2020 at 13:00 UTC
by Andrea Glandon Sept. 29, 2020

Sept. 29, 2020

Dear all, All recordings for the Review of all Rights Protection Mechanisms (RPMs) in all gTLDS PDP WG call held on Tuesday, 29 September 2020 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/xgG-C> and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript As a reminder only members can join the call, observers can listen to the recordings and read the transcript afterwards. Please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you would like to change your status from observer to member. For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-rpm-wg/> and the main wiki page<https://community.icann.org/x/wCWAAw>. Thank you. Kind regards, Andrea

1 0

Re: [GNSO-RPM-WG] DEADLINE COB 25 Sept - ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language:
by Kathy Kleiman Sept. 29, 2020

Sept. 29, 2020

Paul, we did talk and disagreed about processes awhile back. I've gone back and can see the basis for your confusion. There was an IPC group (with all members selected by the IPC) which met to come up with a set of new RPMs for New gTLDs - and went by the acronym of "IRT" with a different meaning. This IPC-group then presented its result to the GNSO and ICANN at the Sydney meeting, and there was great concern over its proposals presented to the Board (including the first joint ALAC-NCSG resolution). The Board asked the GNSO to create an expedited policy group to decide which additional RPMs met the approval of the full GNSO -- and on request of the ICANN Board, the GNSO Council created a STI (Special Trademarks Issues Review Team) which met with a pre-determined balance of representation from all GNSO Stakeholder Groups, as well as At-Large and other ACs. Very expedited timeframes. The Chair of the STI was David Maher of RySG and longtime General Counsel of the Public Interest Registry (implementation review teams, as you know, are run by ICANN Staff.). The STI - we (as we both remember) - reported back in only a few months to the GNSO Council. Our STI Report was reviewed and adopted by the GNSO Council and later the ICANN Board. Our policy recommendations then went to a traditional "IRT," for working through the details of the policy recommendations (including URS and TMCH) that we had made together. I include the framing paragraphs of the STI report below and the link -- and absolutely submit that overlapping acronyms make our lives difficult! Overall, the URS, TMCH and UDRP all pass the criteria for being GNSO-approved policies. And I must return to my concern that at least part of your proposal gives policy-making powers to a future "implementation review team" which is not the way we do things. Best, Kathy ------------------------------------------------------------------------------- STI Report - "Background and Approach Taken On 12 October 2009, the ICANN Board sent a letter1to the GNSO requesting its review of the policy implications of certain trademark protection mechanisms proposed for the New gTLD Program, as described in the Draft Applicant Guidebook and accompanying memoranda. Specifically, the Board Letter requested that the GNSO provide input on whether it approves the proposed staff model,or, in the alternative, the GNSO could propose an alternative that is equivalent or more effective and implementable. In response, the GNSO adopted a resolution creating the Special Trademarks Issues review team (STI) on 28 October 20092which included representatives from each Stakeholder Group, At-Large, Nominating Committee Appointees, and the GAC(identified on Annex 3), to analyze the specific rights protection mechanisms that have been proposed for inclusion into the Draft Applicant Guidebook." Page 2, https://gnso.icann.org/sites/default/files/filefield_8000/sti-wt-recommenda… Links: ------ [1] https://gnso.icann.org/en/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm

2 1

DEADLINE COB 25 Sept - ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language:
by Julie Hedlund Sept. 25, 2020

Sept. 25, 2020

Dear all, Per the WG Co-Chairs, please note the deadline for this action: Please send comments if any to this list not later than COB Friday, 25 September. Note also that the WG discussion of Sunrise Recommendation #2 and the original Implementation Guidance language will be on the agenda for the WG meeting on Tuesday, 29 September, to be followed by a separate discussion of the Sub Team 2 suggested Implementation Guidance language. As a reminder, here is a link to Sunrise Recommendation #2 and the original Implementation Guidance language: https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW…. Also as a reminder, here is the proposed Implementation Guidance language for Sunrise Recommendation #2 from Small Team 2: 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.” Kind regards, Mary, Ariel, and Julie From: GNSO-RPM-WG <gnso-rpm-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Tuesday, September 22, 2020 at 4:09 PM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [GNSO-RPM-WG] REMINDER - ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language: Dear All, Please see the action item below and post any comments to this list ASAP. Kind regards, Mary, Ariel, and Julie From: GNSO-RPM-WG <gnso-rpm-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 17, 2020 at 5:07 PM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [GNSO-RPM-WG] ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language: 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… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAq…>. 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(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 17, 2020 at 2:49 PM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)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+R…. 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/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAq…> -- 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-7u9papLZ4kEMUHNQNElMP… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> 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.

5 4

Proposed Agenda for RPM PDP WG Meeting - Tuesday, 29 September 13:00 UTC
by Julie Hedlund Sept. 25, 2020

Sept. 25, 2020

Dear RPM WG members, Please find the updated proposed agenda for the full WG meeting on Tuesday, 29 September at 13:00 UTC for 90 minutes. Draft Proposed Agenda: 1. Review Agenda and Updates to Statements of Interest 2. WG discussion of Sunrise Recommendation #2 and the original Implementation Guidance language, to be followed by a separate discussion of the Sub Team 2 suggested Implementation Guidance language; see: https://docs.google.com/document/d/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQyEW… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAq…>. 3. URS Final Recommendations – Revised URS Recommendation #3; see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMP… [docs.google.com] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> 4. URS Final Recommendations – Revised URS Recommendation #2, see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMP… [docs.google.com] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> 5. URS Final Recommendations – Revised URS Recommendation #8, continued from last meeting, see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMP… [docs.google.com] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> 6. Overarching Data Collection Recommendation; see: https://docs.google.com/document/d/1Yg6XP1USJFK7Ko5eQFD5EGNC4gwWM-vh07MGSqJ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Yg6XP1USJFK7…> 7. Individual Proposals Converted into Recommendations (time permitting), beginning with URS Recommendations; see: https://docs.google.com/document/d/1qjiKBaAAMNPctSIwP932OKT6vrgkFXxdVYVf6DA… 8. AOB Proposed Co-Chair rotation for chairing the meeting: Brian Beckham. Best Regards, Mary, Julie, Ariel

1 0

REMINDER - ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language:
by Julie Hedlund Sept. 25, 2020

Sept. 25, 2020

Dear All, Please see the action item below and post any comments to this list ASAP. Kind regards, Mary, Ariel, and Julie From: GNSO-RPM-WG <gnso-rpm-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 17, 2020 at 5:07 PM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)icann.org> Subject: [GNSO-RPM-WG] ACTION ITEM: Sunrise Recommendation #2 and Small Team 2 Suggested Language: 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… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAq…>. 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(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 17, 2020 at 2:49 PM To: "gnso-rpm-wg(a)icann.org" <gnso-rpm-wg(a)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+R…. 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/12w5W2bQcviAqLwoDVB0vVK0n7SKj3fzP48NQ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/12w5W2bQcviAq…> -- 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-7u9papLZ4kEMUHNQNElMP… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> 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.

2 1

Notes and Action Items: RPM PDP WG Meeting 24 September 2020
by Julie Hedlund Sept. 25, 2020

Sept. 25, 2020

Dear All, Please see below the action items captured by staff from the RPM PDP Working Group call held on 24 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-24+Review+of+all+R…. Best Regards, Julie Julie Hedlund, Policy Director == NOTES & ACTION ITEMS Actions: ALP Recommendation ACTION ITEM: Small Team to revise the proposal by COB Monday, 28 September for WG discussion on Thursday, 01 October. URS Final Recommendations – URS Recommendation #3 ACTION ITEM: Remove the two bullet points and put in a generic contextual language that the WG has reviewed the Wave 1 report and that the recommendation is not contradicting the Wave 1 recommendations; report at the next WG meeting. URS Recommendation #2: ACTION ITEM: Move the paragraph from URS Recommendation #3. Remove the bullet point and put in the generic language identified for #3. Report at the next WG meeting. New URS Recommendation: ACTION ITEM: Remove this as a recommendation and put the text and context into the background of the Final Report. URS Recommendation #7: ACTION ITEM: Delete the word “uniform” from “uniform set of basic guidance” and change the word “and” to “are” in “and each of the three URS elements listed in the original language of the Determination are addressed in the Determination.” URS Recommendation #8: ACTION ITEM: Staff to review the language of the URS and suggest revised text; review during the next meeting. Notes: 1. Updates to Statements of Interest: No updates provided. 2. Update on ALP Recommendation – Inquiry with GDS staff Background: -- Most ALPs were rejected because they were circumventing the RPMs. -- Some were taken into account for the QLP. Re: the Proposal: -- 45 days plus 7 days limitation on top of the 7 months is unclear. -- Doesn’t take into consideration time for a public comment period related to ALP applications and doesn’t allow time for back and forth between ALP applicant and ICANN org. Answering questions and receiving responses from registry operators. -- Current proposal didn’t include a reset option; without this ICANN would have to reject if they can’t get clarification within the set time frame. -- Any time period should consider these factors. -- Where ICANN determines to decline and makes a request for further information: ICANN org would need to analyze the plan and would require extensive effort and not sure what issues this is trying to solve. Summary: 1) not easily implementable due to lack of clarity of the timeline; not enough time for back and forth; 2) doesn’t seem to resolve the issues with the ALP. Discussion: ACTION ITEM: Small Team to revise the proposal by COB Monday, 28 September for WG discussion on Thursday, 01 October. 3. URS Final Recommendations – Revised URS Recommendation #4; see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMP… [docs.google.com] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> -- Staff has revised the contextual language based on the WG’s discussion at the meeting on Tuesday, 22 September. -- Added “current” before “compliance”. -- Put in new text “The Working Group agreed that ICANN org has the obligation to enforce compliance of URS Providers” in response to Jeff Neuman’s comments. -- Add the text in brackets, “Furthermore, the Working Group noted that its recommendation does not specifically require ICANN Compliance to enforce compliance against URS Providers; [ome other relevant ICANN org department(s) may be responsible for enforcing compliance against Providers (e.g., Procurement, Legal).]” -- Add a sentence at the end in response to comments from Maxim Alzoba: “However, the Working Group noted that the IRT is not asked to review all previous URS compliance cases as part of the implementation for this recommendation.” -- WG accepts the revised contextual language. 4. URS Final Recommendations, see: https://docs.google.com/document/d/1huKNcgg3VAk95oybb-7u9papLZ4kEMUHNQNElMP… [docs.google.com] [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1huKNcgg3VAk9…> a. URS Recommendation #3, page 10: Discussion: -- Conflicts with recommendation. We want them to get the information and pass it along. -- Suggest moving the context language that is highlighted to Recommendation #2. ACTION ITEM: Remove the two bullet points and put in a generic contextual language that the WG has reviewed the Wave 1 report and that the recommendation is not contradicting the Wave 1 recommendations; report at the next WG meeting. b. URS Recommendation #2: Discussion: -- Recommendation is to continue the current process. Suggestion to delete and summarize text as in the action item is consistent with the recommendation. ACTION ITEM: Move the paragraph from URS Recommendation #3. Remove the bullet point and put in the generic language identified for #3. Report at the next WG meeting. c. New URS Recommendation: Discussion: -- Question: Do we need to specify what terminology needs to be updated? -- Question: Do we need to make a recommendation on this? -- Not sure this needs to be a recommendation. -- Staff suggestion: This could be put into the background section of the report. ACTION ITEM: Remove this as a recommendation and put the text and context into the background of the Final Report. d. URS Recommendation #5: -- Recommendation language slightly changed based on public comments. -- Context is the same. -- Public Comment Review explains the change to the recommendation. -- WG accepts the revised recommendation without changes. e. URS Recommendation #7: -- WG agreed to add the following language to the recommendation: “specifically and at a minimum, that the relevant facts are spelt out and each of the three URS elements listed in the original language of the Determination and addressed in the Determination.” -- Is the intent of the recommendation is asking providers to work together to develop guidance or whether such guidance can be provided individually. Who should enforce the compliance? There is a recommendation separately on that. Discussion: -- WG didn’t clarify what it meant by “uniform”. Different providers can do it as they wish. They can get together if they wish, but they need to provide a baseline. -- Take out “uniform”? -- Change to “are addressed.” -- Make it clear that the IRT wouldn’t go against the notion of allowing providers’ discretion. IRT should make sure the providers are providing basic guidance. ACTION ITEM: Delete the word “uniform” from “uniform set of basic guidance” and change the word “and” to “are” in “and each of the three URS elements listed in the original language of the Determination are addressed in the Determination.” f. URS Recommendation #9: -- New text in green reflects the agreed-upon language from the WG deliberations on the public comments. -- This is Implementation Guidance for the IRT. -- The WG agrees with the new text. g. URS Recommendation #8: -- The contextual language changed in that text around a related URS question was removed as there was nothing conclusive on the question based on public comment. Moved the paragraph to the section on public comment review. Discussion: Re: “In addition, the Working Group agrees that a domain name suspension can be extended for one year as set out in the URS Rules and Procedure, but ownership of the domain name must not be transferred during this period to the winning Complainant or another Registrar.” -- On the new language, shouldn’t it be that ownership of the domain name must not be transferred during this period to the winning complainant or another registrar? Otherwise we are saying that it should never be transferred. -- After “the Working Group agrees that a domain name suspension can be extended for one year” add “as set out in the URS Rules and Procedure”. -- Is it actually the case that once the domain is on suspension that it couldn't be transferred if the claimant and the and the registration came to an agreement? If it isn’t correct that they can, then we seem to be changing things. -- If this language is referring to transfer during the extension suspension period that would be after there's been a decision and if the parties negotiate a settlement, which includes a domain transfer before any decision is rendered, that would end the URS action and wouldn't conflict with the rules. -- We’ve raised the issue of involuntary transfer by court order and that isn’t something we’ve discussed. We should come back to this item on the next call. -- Worried that we are starting to veer into substantive discussion on new issues. -- We should be clarifying language not raising new issues. ACTION ITEM: Staff to review the language of the URS and suggest revised text; review during the next meeting.

1 0