Fwd: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Protection Mechanism (RPM) Requirements
Dear ALAC Colleagues, Hong Xue has provided an excellent draft on the revised Rights Protection Mechanism (RPM) Requirements that pertain to the TMCH here: < https://community.icann.org/x/11Z-Ag> My comments, which are posted on the wiki, are as follows: Dear Hong, This is an excellent draft. I generally agree with the statement, but there is an issue with regard to paragraph 3. The requirement that registries "MUST check all labels in a variant set against the Domain Name Label List for Trademark Claims before any domain names in the set are registered" works perfectly for languages with scripts that have consistent IDN tables like the Han script for the Chinese language. This is because the result of any check involving consistent IDN tables would yield the same results. For the Arabic script (the second most widely used writing system in the world after the Latin script), the result would not be consistent because the IDN tables for Arabic are inconsistent and would result in risks/confusion for registrants, trademark holders as well as end users. I think we need to draw from the SSAC Comment on Examining the User Experience Implications on Active Variant TLDs Report Recommendation 11 that states "When registries calculate variant sets for use in validation during registration, such calculations must be done against all of the implemented LGRs covering the scrit, which the label is applied for." Note that the SSAC refers to LGRs and not IDN Tables because there is a distinction and we can explain what that distinction is and why it is important to make that distinction. We should also make a recommendation on how to mitigate the problem faced by languages/scripts with inconsistent IDN Tables. I would be happy to draft the sections that apply to this problem. Rinalia ---------- Forwarded message ---------- From: ICANN At-Large Staff <staff@atlarge.icann.org> Date: Tue, Aug 27, 2013 at 3:31 AM Subject: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Protection Mechanism (RPM) Requirements To: "alac-announce@atlarge-lists.icann.org" < alac-announce@atlarge-lists.icann.org> Dear All, Olivier Crépin-Leblond, Chair of the ALAC, has asked that a call for comments be made on the draft "ALAC Statement on the Protection Mechanism (RPM) Requirements<https://community.icann.org/x/11Z-Ag>" in preparation for the start of the ALAC ratification process. The current draft, as well as additional information on the Public Comment, can be found on the At-Large Rights Protection Mechanism (RPM) Requirements Workspace<https://community.icann.org/x/11Z-Ag>. Please submit any comments on the workspace using the comments function by 02-September-2013 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> _______________________________________________ ALAC-Announce mailing list ALAC-Announce@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce At-Large Official Site: http://www.atlarge.icann.org
This is an excellent draft. I generally agree with the statement, but there is an issue with regard to paragraph 3.
The requirement that registries "MUST check all labels in a variant set against the Domain Name Label List for Trademark Claims before any domain names in the set are registered" works perfectly for languages with scripts that have consistent IDN tables like the Han script for the Chinese language. This is because the result of any check involving consistent IDN tables would yield the same results. For the Arabic script (the second most widely used writing system in the world after the Latin script), the result would not be consistent because the IDN tables for Arabic are inconsistent and would result in risks/confusion for registrants, trademark holders as well as end users.
I do believe the issue of SSAC has already been covered becuase it clearly refers to "all the lables" against "the Domain Name Label List". I cannot see what else it could mean. If it could be of any issue that is relevant, it is already been addressed in my last paragraph that askes ICANN and Registries to work with the corresponding language community to generate and valid IDN variants. Also our comments are at the policy level. I'm not comfortable to go to the technological details that are not the mission of this intervention. I guess there is no rules against at-large community to file 2 or more comments on the same document. If the SSAC is so essential to your comment, perhaps a separate comment would work better -- Professor Dr. Hong Xue Director of Institute for the Internet Policy & Law (IIPL) Beijing Normal University http://www.iipl.org.cn/ 19 Xin Jie Kou Wai Street Beijing 100875 China
---------- Forwarded message ---------- From: ICANN At-Large Staff <staff@atlarge.icann.org> Date: Tue, Aug 27, 2013 at 3:31 AM Subject: [ALAC-Announce] CALL FOR COMMENTS: ALAC Statement on the Protection Mechanism (RPM) Requirements To: "alac-announce@atlarge-lists.icann.org" < alac-announce@atlarge-lists.icann.org>
Dear All,
Olivier Crépin-Leblond, Chair of the ALAC, has asked that a call for comments be made on the draft "ALAC Statement on the Protection Mechanism (RPM) Requirements<https://community.icann.org/x/11Z-Ag>" in preparation for the start of the ALAC ratification process.
The current draft, as well as additional information on the Public Comment, can be found on the At-Large Rights Protection Mechanism (RPM) Requirements Workspace<https://community.icann.org/x/11Z-Ag>.
Please submit any comments on the workspace using the comments function by 02-September-2013 23:59 UTC.
Regards,
Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> _______________________________________________ ALAC-Announce mailing list ALAC-Announce@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce
At-Large Official Site: http://www.atlarge.icann.org _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
participants (2)
-
Hong Xue -
Rinalia Abdul Rahim