NCSG-DISCUSS Archives

NCSG-Discuss

NCSG-DISCUSS@LISTSERV.SYR.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Sun, 24 Feb 2013 14:46:43 -0500
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (876 bytes) , text/html (1546 bytes)
On Sun, Feb 24, 2013 at 12:44 PM, Avri Doria <[log in to unmask]> wrote:

> hi,
>
> In which case, if I really wanted honey for some reason I would apply for
> .miele or .דבש or .asali
>
> or register  honey.shop or honey.coop  or honey.ri.us or honey.eat or
> honey.farm or honey.food or .....
>
> I do  not see the point of arguing about what content someone allows in
> their gTLD.  And to me this largely comes down to a content issue.  We are
> saying that everyone has a right to put content under the TLD .honey.  And
> I just don't see it.
>

+1


>
> I also see it as an association issue.  Why does ICANN have authority to
> tell a gTLD owner who they must associate with, i.e who they must allow to
> use the gTLD they have been allocated.
>
>
agreed


-- 
Cheers,

McTim
"A name indicates what we seek. An address indicates where it is. A route
indicates how we get there."  Jon Postel


ATOM RSS1 RSS2