<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: Legitimate TLD claims? (Re: [ga-roots] ICANN Policy -- revised version)
The domain name I registered at NameSlinger works just fine. The plugin
doesn't however. Have to manually set dns. I am the proud owner of
PinkyAndTheBrain.ICANNBoD now. Created on the fly.
The only conflict that tld has is with the ICANN BoD. Think I'll be hearing
from WIPO soon?
Doubtful, since no one is likely to ever see it function in their browser.
But other companies will come. They will be more technically sound. The
funny thing is on ICANN's present course they aren't helping their corporate
friends any. Users will enable their dns settings so more tlds to be
available to them. The same thing ICANN and the others have counted on, that
the majority don't care or know what is going on, is the very same reason
they will do this. They don't care that these other tlds aren't controlled
by ICANN.
I believe some still believe their Pinky And the Brain plan to control the
Internet will still work somehow. It won't. The party is over, unless ICANN
does a 180 and does what it is supposed to be doing. It has to do it quickly
because the companies going the other way and the users won't wait for the
long drawn out calculated thing that the BoD calls a plan.
Disagree all you like. But factas are facts. New Companies with new ideas
who will give the user what they want are here. Other roots are here. The
users are here. None of that will go away and none of that fits into the
plan for ICANN.
ICANN is a single point of failure at this point. What happens to points of
failure on the Internet?
Tell you what Stuart. The next draft you put out, I'll put it up at my site
PinkyAndTheBrain.ICANNBoD. I'm sure someone here can help you with your DNS
settings so you can see it.
I may sound sarcastic here. But that is because the BoD does not seem to be
listening. What is cool is that the press is starting to. Would you rather I
post my sarcasm here or in the press?
Unless it starts to look like someone is going to listen to the users and
what they want I think here is a waste of my sarcasm and I'll take it
elsewhere.
I really hope the ICANN BoD does start to listen to someone who does NOT
have a financial gain in mind when making it's next decisions. The lawyers
are not helping you. They ARE the problem or at least one of the biggest
problems.
Good luck.
Chris McElroy aka NameCritic
----- Original Message -----
From: "Marc Schneiders" <marc@schneiders.org>
To: "Jefsey Morfin" <jefsey@wanadoo.fr>
Cc: <ga-roots@dnso.org>
Sent: Monday, June 18, 2001 2:35 PM
Subject: Legitimate TLD claims? (Re: [ga-roots] ICANN Policy -- revised
version)
> On Mon, 18 Jun 2001, at 22:58 [=GMT+0200], Jefsey Morfin wrote:
>
> > The problem is that the New.net's and NameSlinger's TLDs are legally
valid.
> > First come, first serve.... They will have to be purchased back from
them.
> > They are no cybersquatters: just an economic model with as much merit as
> > bug.biz. NameSlinger is carefull about not colliding.
>
> Sure, NameSlinger seems to try to avoid colliding, New.Net has not
> done that at all. So I suppose your approval of New.Net is limited to
> the one or two TLDs of them that do not collide.
>
> As for NameSlinger: they claim too much. They look like
> Name.Space. Not many take Name.Space's claim seriously (or just a
> small part of it), not even in alt root circles.
>
> One company cannot claim the whole 'world', not even if customers ask
> for it.
>
> By the way, nameslinger's dns for their TLDs does not seem to work, at
> the moment in any case(*). Maybe I should try to register coca.cola
> with them and see if it works :-)
>
> (*)
> pan:marc {126} dig @nomad.tallship.net go. ns
>
> ; <<>> DiG 8.3 <<>> @nomad.tallship.net go. ns
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
> ;; QUERY SECTION:
> ;; go, type = NS, class = IN
>
> ;; ANSWER SECTION:
> go. 2D IN NS ns2.nameslinger.com.
> go. 2D IN NS ns1.nameslinger.com.
>
> ;; ADDITIONAL SECTION:
> ns2.nameslinger.com. 2D IN A 209.61.177.32
> ns1.nameslinger.com. 2D IN A 209.61.186.11
>
> ;; Total query time: 195 msec
> ;; FROM: pan.bijt.net to SERVER: nomad.tallship.net 204.107.129.2
> ;; WHEN: Mon Jun 18 23:34:17 2001
> ;; MSG SIZE sent: 20 rcvd: 103
>
> pan:marc {127} dig @ns2.nameslinger.com. go. ns
>
> ; <<>> DiG 8.3 <<>> @ns2.nameslinger.com. go. ns
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; res_nsend to server ns2.nameslinger.com. 209.61.177.32: Operation
> timed out
> pan:marc {128} dig @ns1.nameslinger.com. go. ns
>
> ; <<>> DiG 8.3 <<>> @ns1.nameslinger.com. go. ns
> ; (1 server found)
> ;; res options: init recurs defnam dnsrch
> ;; wrong query name:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
> ADDITIONAL: 0
> ;; QUERY SECTION:
> ;; go, type = A, class = IN
>
> ;; AUTHORITY SECTION:
> . 1D IN SOA
> A.ROOT-SERVERS.NET. hostmaster.nsiregistry.NET. (
> 2001043001 ; serial
> 30M ; refresh
> 15M ; retry
> 1W ; expiry
> 1D ) ; minimum
>
>
> ;; wrong query name:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
> ADDITIONAL: 0
> ;; QUERY SECTION:
> ;; go, type = A, class = IN
>
> ;; AUTHORITY SECTION:
> . 1D IN SOA
> A.ROOT-SERVERS.NET. hostmaster.nsiregistry.NET. (
> 2001043001 ; serial
> 30M ; refresh
> 15M ; retry
> 1W ; expiry
> 1D ) ; minimum
>
>
> ;; res_nsend to server ns1.nameslinger.com. 209.61.186.11: Operation
> timed out
>
>
> --
> This message was passed to you via the ga-roots@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga-roots" in the body of the message).
> Archives at http://www.dnso.org/archives.html
>
--
This message was passed to you via the ga-roots@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-roots" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|