[GNSO-RPM-WG] [Ext] RE: REMINDER: Review Updated Final Report Sections - Input by 23 Oct

[Ariel Liang]

Hello Brian,

Thank you for providing these suggested edits. I have incorporated them as redline on this Google Doc (pp. 7-8): https://docs.google.com/document/d/1aSFKsXW9Z3CfBODC_T_7kY_rCVo_pTkiWUH0cFG1Gac/edit# If no objection from other members in the WG, we will accept these edits by COB Friday, 23 October.

Best Regards,
Ariel

From: BECKHAM Brian <brian.beckham at wipo.int>
Date: Wednesday, October 21, 2020 at 3:24 PM
To: Ariel Liang <ariel.liang at icann.org>, "gnso-rpm-wg at icann.org" <gnso-rpm-wg at icann.org>
Subject: [Ext] RE: [GNSO-RPM-WG] REMINDER: Review Updated Final Report Sections - Input by 23 Oct

Thanks Ariel,

Regarding the new proposal #3 on language, given that the goal was due process in attempting notice of the case, and given that the script of the TLD could be at least potentially applicable in ascertaining the case language, but whereas “language used by the registry and/or predominant language of the country/territory of the registry” (as it is currently stated in the 4th bullet) may in reality have zero bearing on the case (e.g., imagine a hypothetical Korean-scripted TLD managed by a Registry based in Ireland for corporate purposes), I thought the intent was to combine the 4th and 6th bullets to something like:


  *   the language/script used in the domain name (including the TLD), in particular if it is an Internationalized Domain Name.

I am not sure if the highlighting will show up on the mailing list, so to be clear, I have suggested adding “…(including the TLD), in particular…” because (a) in the WG call, we spoke about the potential relevance of the TLD in lieu of the location of the registry – see point above, and (b) even if the TLD is not an IDN, this fact can be relevant (i.e., the fact that a 2LD and/or TLD is in English could be as relevant to the language issue as if it is in another non-English script).

I also think the word “severe” in the 2nd para of the context overstates the case, and I do not believe there was agreement as to this qualifier (and certainly not if the Provider will send a translated Notice of Complaint document), so would propose deleting it.

Thanks for considering this in light of the prior WG conversations!

PS, I have tried to review the call and transcript, but the referred to link did not work for me:
https://community.icann.org/display/RARPMRIAGPWG/2020-10-13+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG.

Brian

From: GNSO-RPM-WG <gnso-rpm-wg-bounces at icann.org> On Behalf Of Ariel Liang
Sent: Tuesday, October 20, 2020 4:56 PM
To: gnso-rpm-wg at icann.org
Subject: [GNSO-RPM-WG] REMINDER: Review Updated Final Report Sections - Input by 23 Oct

Dear WG members,

This is a reminder for reviewing the updates on the following google docs (please see below). If you have any further input, please share on list no later than Friday, 23 Oct COB.

Thank you,
Mary, Julie, Ariel

From: Ariel Liang <ariel.liang at icann.org<mailto:ariel.liang at icann.org>>
Date: Tuesday, October 13, 2020 at 3:34 PM
To: "gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>" <gnso-rpm-wg at icann.org<mailto:gnso-rpm-wg at icann.org>>
Subject: Review Updated Final Report Sections - Input by 23 Oct

Dear WG members,

Thank you for your participation and input during today’s RPM sessions. Staff have completed today’s action items; please review the updated content in the following google docs:


  *   Phase 1 Final PDP Recommendations: https://docs.google.com/document/d/1aSFKsXW9Z3CfBODC_T_7kY_rCVo_pTkiWUH0cFG1Gac/edit# [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1aSFKsXW9Z3CfBODC_T_7kY_rCVo_pTkiWUH0cFG1Gac/edit__;!!PtGJab4!rxQoXzEfBQ9F3mkZicCuhxx52GWe4b7fqDWBQAh0OiZqpxYj4kCm9edn5CjJCyRm5OWy_Yw$>
     *   pp.6-10: Inserted the URS recommendation (converted from URS Proposal #34) regarding the language of proceeding and its contextual language.
     *   pp.10-11: Updated the URS recommendation regarding the translation of the Notice of Complaint to maintain consistency with the recommendation regarding the language of proceeding.
     *   pp.26-29: Inserted the TMCH recommendation regarding geographical indications and its contextual language approved by the WG.



  *   Annex: Charter Questions: https://docs.google.com/document/d/1hmF5eKnuwjv-Sk4cWfTkM_omKpr0kLH2SSUjAnkFWII/edit# [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1hmF5eKnuwjv-Sk4cWfTkM_omKpr0kLH2SSUjAnkFWII/edit__;!!PtGJab4!rxQoXzEfBQ9F3mkZicCuhxx52GWe4b7fqDWBQAh0OiZqpxYj4kCm9edn5CjJCyRm1LdChEw$>
     *   pp.18-21: Inserted the WG-approved text related to the ALP under Sunrise Q8(a), which concerns the review of ALP.
     *   pp.28-29: Rearranged the sentences related to the GPML (same updates have been incorporated in the “Background [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Jw_B6xGwc-Du9dMbCGjsQnsq40NbZWgT5aC86nP9UN0/edit__;!!PtGJab4!rxQoXzEfBQ9F3mkZicCuhxx52GWe4b7fqDWBQAh0OiZqpxYj4kCm9edn5CjJCyRmS2OZ_UQ$>” – p.11 and “Additional Marketplace RPMs [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1Kf-on75LuwwjI-qfvx5YwX5q5ztauB3ivGD3rInJu4Q/edit__;!!PtGJab4!rxQoXzEfBQ9F3mkZicCuhxx52GWe4b7fqDWBQAh0OiZqpxYj4kCm9edn5CjJCyRmj_aX9Xs$>” sections)

If you have any further comments/suggestions, please share on list no later than Friday, 23 October COB. These above items will be considered closed after the deadline.

Best Regards,
Mary, Julie, Ariel


World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rpm-wg/attachments/20201021/aeefa05e/attachment-0001.html>