<<<
Chronological Index
>>> <<<
Thread Index
>>>
[nc-udrp] RE: Include new gTLD dispute resolutipn procedures?
Yes, the Terms of use are too broad. Yes, I believe it should be narrowed
to discuss specific issues. However, in discussing those issues, one should
not forget that there is ample jurisprudence (this was the best word I could
think of) in the new TLDs to be valuable to address these narrow subjects.
Hope that makes sense.
-----Original Message-----
From: Milton Mueller [mailto:mueller@syr.edu]
Sent: Saturday, November 09, 2002 5:29 PM
To: jse@adamspat.com; nc-udrp@dnso.org; Jeff.Neuman@neustar.us
Cc: bruce.tonkin@melbourneit.com.au
Subject: Include new gTLD dispute resolutipn procedures?
Jeff:
Were you not the same person who was complaining that
the existing terms of reference is too broad? Are you not
suggesting here that they become even broader? At any rate,
changes in the terms of reference need to go through the
NC. Since this TF has not executed step one of its initial
ToR, perhaps consideration of the new ones can wait
until progress is made on the old one.
>>> "Neuman, Jeff" <Jeff.Neuman@neustar.us> 11/08/02 10:36AM >>>
Can I request that the scope of the review be enhanced to cover the new
dispute policies from the new gTLDs. Since expansion is likely in the near
future, we should be looking at the hundreds of cases decided with respect
to the new TLDs. I do not believe that it would not be wise to ignore these
new processes.
Just my own 2 cents.
The information contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above. If the reader
of this message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that you
have received this e-mail message and any attachments hereto in error and
that any review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately by e-mail, and delete the original message.
The contents of this email do not necessarily represent the viewpoints or
opinions of the NeuStar Corporation. www.neustar.com
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|