ICANN ICANN Email List Archives

[2gtld-intro]


<<< Chronological Index >>>    <<< Thread Index >>>

Detailed Comments on Module 1

  • To: <2gtld-intro@xxxxxxxxx>
  • Subject: Detailed Comments on Module 1
  • From: "Elisa Cooper" <Elisa.Cooper@xxxxxxxxxxxxxxx>
  • Date: Fri, 10 Apr 2009 16:44:37 -0600

MarkMonitor is pleased to provide the following comments on 'Module 1'.
Our consolidated comments were also sent to 2gtld-guide@xxxxxxxxx.

Section 1.1 - Creation of a gTLD Reserved Name List

An automatic "Reserve Name List" should be created for global brand
owners.  To be placed on this list, the global brand owner must have a
trademark that is registered in multiple international jurisdictions.
At least one of these jurisdictions must have a stringent examination
review process for trademark registrations.  Under this mechanism,
registry applicants would be required to check the "Reserve List" as a
resource before proposing a top level string, and names that are exactly
alike, or confusingly similar to a name on the Reserve Name List should
be summarily rejected. The database of reserved names can be operated
and/or maintained by a third-party, however, ICANN must retain ultimate
responsibility and accountability for its provision and use. There must
also be an appropriate challenge procedure for seeking the removal of a
name from this Reserve Name List.

Section 1.2.2.1 - Allow a New Designation for Single-Purpose or
Sponsored gTLDs
 
There are numerous rights holders with potential gTLDs that share
substantially the same or similar attributes of a community gTLD.  These
gTLDs do not share the attributes of an open gTLD given that they are
not available for registration by any potential registrant.  Examples
would include service and broadband providers, industry-wide
professional associations, and social networking sites.  These rights
owners should be recognized for the communities they represent, and as
such should receive the protections of a sponsored application. 




<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy