Re: Call for (R) trademark domain(s)

[Jeff Williams <jwkckid1@ix.netcom.com>]

Ben and all,

Benjamin Azevedo wrote:

> Ray Hallman wrote:
> >
> >      So, we *could* ask the US Post Office (or any inter-national Post Office)
> > if there is *any* precedence for associating Trademarks with the Postal Address
> > system.  A lot of good business could be generated from the association of
> > Trademarks with the postal addressing system!  -Ray
> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > On Thu, 19 Feb 1998, Wm Mark Clifford wrote:
> > (---)
> > > The prototype trademark domain space would be <trademark>.TM.US and
> > > would be managed by the USPTO.  Since these are the experts in
> > > trademarks, they would "properly" manage the registry with sufficient
> > > flexibility and robustness to deal with the issues they have to deal
> > > with.  Internet users would recognize that a registration ending in
> > > .TM.US is indeed a trademark and that the USPTO is carefully managing
> > > the registration of trademarks to the best of its ability within the
> > > limits or technology.  If you want to register a smell, they will help
> > > you with that.  (Right?)
> > (---)
> >
> > A TM.nTLD really doesn't solve the problem. Will ford.tm.us be used ny the
> > car company or the model agency?
> >
> > Regards,
> >
> > Mikael
> >
> Ray Hallman wrote:
> >
> >      So, we *could* ask the US Post Office (or any inter-national Post Office)
> > if there is *any* precedence for associating Trademarks with the Postal Address
> > system.  A lot of good business could be generated from the association of
> > Trademarks with the postal addressing system!  -Ray
> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > On Thu, 19 Feb 1998, Wm Mark Clifford wrote:
> > (---)
> > > The prototype trademark domain space would be <trademark>.TM.US and
> > > would be managed by the USPTO.  Since these are the experts in
> > > trademarks, they would "properly" manage the registry with sufficient
> > > flexibility and robustness to deal with the issues they have to deal
> > > with.  Internet users would recognize that a registration ending in
> > > .TM.US is indeed a trademark and that the USPTO is carefully managing
> > > the registration of trademarks to the best of its ability within the
> > > limits or technology.  If you want to register a smell, they will help
> > > you with that.  (Right?)
> > (---)
> >
> > A TM.nTLD really doesn't solve the problem. Will ford.tm.us be used ny the
> > car company or the model agency?
> >
> > Regards,
> >
> > Mikael
> >
>
> As you noticed even considering just trademark owners there
> will be duplications.
>
> This makes clear that:
>   1)Some sort of further breakdown is needed in order to
>     accomplish with these multiple trademarks.
>
>   2)This problem is NOT caused by other domain name holders.

  I am hartned to hear this from someone with some sense.

>
>
> So, the idea of spliting name spece in a "trademark" space
> and a "non-trademark" space helps in creating less conflicts
> and permmiting that both groups have their domains.

  For an interim solution, this should work fine.  However until
Trademark law including International Trademark Law has
caught up with the technology age, problems will still remain.

>
>
> In the "trademark" TLDs, having a domain would be an evidence
> for the customer and anybody else that this particular domain
> name reflects a trademark.
>
> Conversely, in generic, non-trademark TLDs, no assumption
> should be done associating domain name with trademarks.
> They are just addresses in these TLDs.

  Correct.  This is also true in your purposed "Trademark TLD" name space.

>
>
> Benjamin Azevedo
>
> --
> DOMAIN-POLICY administrivia should be sent to <listserv@lists.internic.net>
> To unsubscribe send a message with only one line "SIGNOFF DOMAIN-POLICY"
> For more help regarding Listserv commands send the one line "HELP"

 Regards,

--
Jeffrey A. Williams
DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com