ICANN ICANN Email List Archives

[irt-final-report]


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

URS

  • To: irt-final-report@xxxxxxxxx
  • Subject: URS
  • From: gotchatickets <gotchatickets@xxxxxxxxx>
  • Date: Mon, 6 Jul 2009 12:11:00 -0700 (PDT)

To whom it May Concern,

The idea of changing the system initially sounded good as the WIPO system is 
flawed and targeted against domain name owners. 85% of the time, they choose in 
favor on the person making the claim.

Have you looked at some of those cases?

crew.com?

LH.com

salomon.com

The point is there needs to be a fair and equitable solution for all parties 
and URS is not it.

Some Facts...

Almost every dictionary word is trademarked and used in multiple ways with 
multiple meanings.

Almost every 2 and 3 letter combination is trademarked and used in multiple 
ways with multiple meanings.

Almost every saying or phrase used in language is trademarked, yet few are well 
know for their trademarked purpose.

The system needs to define what are acceptable uses for domain names. How can 
some cases vaildate domain parking and some cite it as a reason for the name to 
be transferred. 

How is this system better? How does it protect my rights? Why is this better 
than the current WIPO system?

The committee should propose MAJOR changes to UDRP, which has settled thousands 
of disputes, for both new and existing gTLDs. The system needs to be revamped 
to enhance the rights of registrants and complainants.

As a domain owner, there is no restitution for frivilous claims brought against 
names they are a registrant is "forced" to defend. In order to make the system 
more fair and balanced, I suggest that UDRP’s becomes a “loser pays system” to 
compensate trademark holders who are the victim of obvious and unquestionable 
trademark infringement, yet protect domain holders from the attempted theft of 
their property.  

Thank you for you time and consideration.


Respectfully,



Steven Newman

 


      



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

Privacy Policy | Terms of Service | Cookies Policy