Greg,
> Does anyone have an idea of how many TLDs potentially will be
> registered?  For example, how many types of business (or any other
> organizational) classifications exist?  Would TLDs be restricted to
> marks only?
> 
> The reason I am asking is because once we get to the level of hundreds
> of thousands of TLDs, we risk the DNS performance problems that have
> been discussed earlier.  That would have an effect on the entire
> Internet.  So it seems at the very least, we need to proceed slowly in
> adding TLDs, so we can study its effect on DNS performance and make
> changes to it if necessary to allow it to scale.
 
Can DNS performance be monitored, to provide a *technical 
justification for limiting a given TLD size? Even if it depends on 
proocessor speed and thus Moore's Law, it would make the pill a 
lot easier to swallow: its no use being on the net if the traffic is in a 
permanent jam. Otherwise, peg registry size to the cost of living? 
Annual quotas? (Lets not even mention sliding costs of registration, 
unless there's a worthwhile charity to receive the proceeds.)


> > all of which, in my
> >humble but professional opinion, are likely to create confusion with
> >our friends over at ebay.com.
> 
> This seems to be a reasonable concern, given that there is already
> quite a bit of registration of companies in ccTLDs.  Wouldn't the
> companies who are interested in having those names in all (or even
> most) TLDs pursue the same avenues they are pursuing in the existing
> gTLDs?

Its actually unreasonable, but this is where trying everything to the 
almighty dollar gets you: bigger firms tie up more namespace, and 
further suborn *function (technical operation) to *form (advertising 
advantage).   In any case, if the consuming public is easily 
confused, surely it is used to that by now -- but say! doesnt that 
imply a commercial niche? Ebay.portal could provide a suitable 
map so folks could sort out which one they wanted.  (Hmmm, and 
then let that TLD be user-specifiable as the default...) 

kerry


Reply via email to