hostcount features [Re: [ncc-services-wg] RIPE50 - NCC Services WG Draft Minutes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear Peter,
you wrote:

> First, it's never complete, so you only find those organisations who both
> happen to use the wrong IP addresses and are within your TLD, while
> nothing prevents them from using COM, BIZ or XXX {filter food} names as well.

You are perfectly right. I have been using only the `.cz' 
hostcount TLD raw data and no other TLD data because I thought 
that this was the most common kind of misuse here.

> Second, and more important, this kind of policing, although it has been done
> for years, might reduce the willingness of affected and other parties to
> allow AXFR access. Experience shows that many organisations have only and
> explicitly granted AXFR access to support the hostcount statistics data
> collection (and some DNS quality postprocessing). So, declaring "raw data
> access" a feature of the hostcount is detrimental to its success. It was a
> side effect that's gone.

Noone from our TLD has ever complained about my access to the 
hostcount data. If they did not like it, they probably just 
inhibited the AXFR access to their domains.

> -Peter
> 
> PS: Just to be clear: the DE hostcount raw data must not be published.

I had never even looked at it. Whan I was signing the 
Hostcount AUP statement I had explicitly written that I was 
interested only in the `.cz' TLD data.

Best regards,
Pavel Vachek, CESNET NIC, Prague.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFCxCE7Prynl47KNS4RApkFAKCSJVv2I9XqDvHXM8nmpAsH9H5EDACglI7B
IAVhKETXRk01V0wFvV989EQ=
=JoNT
-----END PGP SIGNATURE-----