Re, weren't ccTLD domain registries supposed to remove their stuff from the database? Do a "whois -r -T domain -i notify notify@nic.gm". Which ccTLDs are still holding their registry data in the RIPE DB anyway? -- Ulf Kieber email: ukieber@cogentco.com Sr. Network Engineer voice: +49-69-299896-21 C.C.D. Cogent Communications Deutschland GmbH fax : +49-69-299896-40 Optical Internet www : www.cogentco.com Brilliantly Fast. Elegantly Simple. AIM : ulfkieber
Ulf, On 2004-10-22 18:36:32 +0200, Ulf Kieber wrote:
Re,
weren't ccTLD domain registries supposed to remove their stuff from the database?
There isn't a formal requirement about this. A couple of years ago the sheer size of ccTLD data caused several problems, thus the ccTLDs (especially big ones) were invited to implement their own whois services and they did so indeed, and removed their data from RIPE Whois DB.
Do a "whois -r -T domain -i notify notify@nic.gm".
Which ccTLDs are still holding their registry data in the RIPE DB anyway?
Some small ccTLDs seem like still using RIPE Whois DB as their whois service. Here is the number of domain objects split into their TLDs: 149428 arpa 1319 fo 1236 sm 1036 bg 693 mc 673 gm 182 no 172 il 76 gr 74 pl 64 lv 56 fi 33 tr 32 be 27 hu 24 gl 21 pt 14 md 13 at 11 is 10 ba 8 ie 8 ee 6 se 6 sa 5 es 4 uk 4 ru 4 ly 4 kz 4 jo 4 eu 4 cz 3 tn 3 si 2 va 2 ug 2 ke 2 it 2 ir 2 ga 2 cm 2 by 2 az 2 al FO and SM objects are slowly increasing, so I presume they are still using our DB as their whois service. The others look like left-overs. I think it would be a good idea to remove all forward domain objects from RIPE Whois DB, as the domain name allocation process is conceptually different than Routing Registry and Address Allocation processes. In the past ccTLDs were allowed to use the RIPE Whois DB as their whois service as they weren't big enough to support their own whois services and somehow it made sense to include ccTLD data there but I think this is not valid any more.
-- Ulf Kieber email: ukieber@cogentco.com Sr. Network Engineer voice: +49-69-299896-21 C.C.D. Cogent Communications Deutschland GmbH fax : +49-69-299896-40 Optical Internet www : www.cogentco.com Brilliantly Fast. Elegantly Simple. AIM : ulfkieber
-- Engin Gunduz RIPE NCC Software Engineering Department
On Mon, 25 Oct 2004, Engin Gunduz wrote:
Some small ccTLDs seem like still using RIPE Whois DB as their whois service. Here is the number of domain objects split into their TLDs: [...] 4 eu [...]
FO and SM objects are slowly increasing, so I presume they are still using our DB as their whois service. The others look like left-overs.
I thought, .eu will be ramp up in the future and you speek of left-over? ;-))))))) Regards Elmar -- _____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Fon: +49 231 9703-0 Elmar.Knipp@knipp.de Fax: +49 231 9703-200
Engin Gunduz wrote:
On 2004-10-22 18:36:32 +0200, Ulf Kieber wrote:
weren't ccTLD domain registries supposed to remove their stuff from the database?
There isn't a formal requirement about this. A couple of years ago the sheer size of ccTLD data caused several problems, thus the ccTLDs (especially big ones) were invited to implement their own whois services and they did so indeed, and removed their data from RIPE Whois DB.
Do a "whois -r -T domain -i notify notify@nic.gm".
Which ccTLDs are still holding their registry data in the RIPE DB anyway?
Some small ccTLDs seem like still using RIPE Whois DB as their whois service. Here is the number of domain objects split into their TLDs:
149428 arpa 1319 fo 1236 sm 1036 bg 693 mc 673 gm 182 no 172 il 76 gr 74 pl 64 lv 56 fi 33 tr 32 be 27 hu 24 gl 21 pt 14 md 13 at 11 is 10 ba 8 ie 8 ee 6 se 6 sa 5 es 4 uk 4 ru 4 ly 4 kz 4 jo 4 eu 4 cz 3 tn 3 si 2 va 2 ug 2 ke 2 it 2 ir 2 ga 2 cm 2 by 2 az 2 al
FO and SM objects are slowly increasing, so I presume they are still using our DB as their whois service. The others look like left-overs.
I think it would be a good idea to remove all forward domain objects from RIPE Whois DB, as the domain name allocation process is conceptually different than Routing Registry and Address Allocation processes. In the past ccTLDs were allowed to use the RIPE Whois DB as their whois service as they weren't big enough to support their own whois services and somehow it made sense to include ccTLD data there but I think this is not valid any more.
So I guess RIPE should talk to those ccTLDs, and if they confirm they're no longer use the RIPE DB that data, including dangling person objects, should be removed. The .gm domain objects aren't even protected, so actually everybody could delete those. -- Ulf Kieber email: ukieber@cogentco.com Sr. Network Engineer voice: +49-69-299896-21 C.C.D. Cogent Communications Deutschland GmbH fax : +49-69-299896-40 Optical Internet www : www.cogentco.com Brilliantly Fast. Elegantly Simple. AIM : ulfkieber
participants (3)
-
Elmar Knipp -
Engin Gunduz -
Ulf Kieber