| Comment Close Date | Statement Name | Status | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 27.08.2013 | Rights Protection Mechanism (RPM) Requirements | Voting | Hong Xue (APRALO) | 26.08.2013 | 02.09.2013 | 04.09.2013 00:01 UTC | 04.09.2013 00:01 UTC | 09.09.2013 | 10.09.2013 | 11.09.2013 | Karen Lentz karen.lentz@icann.org | TBC |
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.
FINAL VERSION TO BE SUBMITTED IF RATIFIED
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.
FIRST DRAFT SUBMITTED
The At-Large community supports the improvements made by ICANN in the revised Rights Protection Mechanism Requirements (RPM), released on 6 Aug 2013, in response to the IDN user community’s persistent requests to take action in order to prevent user confusion through the appropriate management of the IDN variants that are involved in the trademark measures.
Under the revised Requirements for the Sunrise Registration, a new gTLD Registry Operator that “has implemented IDN variant registration policies for the TLD” MAY register the IDN variant(s) as far as the corresponding trademark data has been generated by the Trademark Clearinghouse. At-Large community notes that the revision reflects the IDN user community’s request on removal of the unreasonable restriction on the registration of the IDN variant(s) of a valid trademark data over the Sunrise Period.
Under the revised Requirements for the Trademark Claims, a Registry Operator that “has established IDN variant policies for allocation of domain names in the TLD” 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. At-Large community hails the revision the most significant improvement to prevent the user confusion that may be caused by the IDN variants that are not available in the trademark data generated by the Trademark Clearinghouse. The Revision is completely consistent with the purpose of the Trademark Claims, i.e. provision of clear notice to the prospective domain name registrant of the scope of the Trademark Holder’s rights. Even without the informational support from the Trademark Clearinghouse, the Registry Operator are obliged to ensure “all labels in a variant set against the Domain Name Label List” be availed for Trademark Claims.
Notwithstanding all the important improvements that have been made, At-Large community finds that the implementation of the revisions regarding the IDN variants completely relies on the TLD Registry Operator’s “IDN variant policies”, which will result in differentiating treatment for the same trademark in the IDN characters involving variants across the TLDs. The complexity can still potentially cause the user confusion in the IDN community. At-Large therefore calls for the ICANN to encourage the Registry Operators to implement the coherent IDN variant policies in consultation with the corresponding IDN user community.
