Registry requirements?

[Aveek Datta <MoNoLiTH+@CMU.EDU>]

Switch off the FCFS argument for a sec (I plan to submit my own proposal on
a replacement), I have a question. What's to stop domain name hoarding at
the TLD level? Sure it'll require more money than to hoard at the second
level domain level, but it can be done.

Let's say Microsoft sees this whole process and goes, hmmm, I want this and
that and this and that. For example, let's say they want .WEB (this is not
in dispute or support of IoDesign's claim, just an example).

Now Microsoft has immense resources and lawyers so I'm sure they can grab at
least some TLDs. Let's say they get .WEB. I can just imagine

NETSCAPE.WEB 	IN	CNAME	EXPLORER.WEB

In other words, what's to stop a "registry" from rejecting all applications
from people it doesn't like?  Are we going to force registries to be open to
all? Or open to at least a defined group? And then who defines the groups
that are not exclusionary enough to constitute domain name hoarding? For
example Microsoft might say .WEB is only for Microsft related enterprises.
Would there be any regulations against such? 

Just a thought.
Aveek


 Aveek Datta           _ _ _   _                Email: aveek@andrew.cmu.edu
    _ __  ___ _ _  ___| (_) |_| |_     |W|   HomePage:         datta.ml.org
  _| '  \/ _ \ ' \/ _ \ | |  _| ' \ _  |E|    FreeDNS:           www.ml.org
 (_)_|_|_\___/_||_\___/_|_|\__|_||_(_) |B|       Work:      www.itc.cmu.edu