Legitimate TLD claims? (Re: [ga-roots] ICANN Policy -- revisedversion)

[Marc Schneiders <marc@schneiders.org>]

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