Skip to main content

Public Comment Invited: Implementing Rights Protection Mechanisms in the Name Collision Mitigation Framework

Forum Announcement: Comment Period Opens on Date: 25 August 2014
Categories/Tags:
  • Top-Level Domains
  • Second-Level Domains
  • Contracted Party Agreements
  • Intellectual Property
Purpose (Brief):

ICANN is posting for public comment a paper [PDF, 114 KB] discussing various alternatives to providing Rights Protection Mechanisms for second level domain names once they are released for allocation. Consistent with the Name Collision Occurrence Management Framework [PDF, 926 KB] approved on 30 July 2014, the Board New gTLD Program Committee directed staff to provide each registry operator a Name Collision Occurrence Assessment ("Name Collision Assessment"), issued on 4 August 2014.

Per the Name Collision Occurrence Assessment, for names included on the SLD Block List of the registry's Alternate Path to Delegation Report and recorded in the Trademark Clearinghouse that the registry withheld from allocation during its Sunrise Period or Claims Period, the registry must continue to withhold these names from allocation while ICANN consults with the community. This paper examines operational and other considerations for several possible approaches regarding the appropriate Rights Protection Mechanisms for release of SLD Block List names.

Public Comment Box Link: https://www.icann.org/public-comments/name-collision-rpm-2014-08-25-en

More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."