[anti-abuse-wg] RIPE Database Proxy Service Issues

Dear Florian

As Kaveh pointed out, the -r flag simply says don't recusively search
through the objects returned in response to the query and find referenced
personal data. But if the query itself is for a personal data object the
-r flag will have no effect.

Your query "-r r" is looking for all objects in the RIPE Database where
the primary key containes the letter 'r'. As most nic-handles end in
'-ripe' you queried for all persoanl data directly. This is why your
single query blocked you.

Your idea for a 'non blocking' query option is along the lines of our
technical suggestion from last year, which Axel referred to. Perhaps the
community would like to take another look at that as there was no
consensus last year. The current blocking mechanism is not optimal and
could be improved.

Regards
Denis Walker
Business Analyst
RIPE NCC Database Group

> * Thor Kottelin:
>
>> But Axel Pawlik also wrote:
>>
>>> > On 6 March 2012, the RIPE NCC proposed to change the default
>>> behaviour
>>> > of the query system to instead return only "ALLOWED" results if a
>>> user
>>> > had reached their daily personal data query limit, but there was
>>> > disagreement over this on the mailing list so the change was not
>>> > implemented.
>>
>> He also referred to
>> http://www.ripe.net/ripe/mail/archives/db-wg/2012-March/003885.html,
>> wherein
>> it is stated: 'The current blocking mechanism works on the basis of all
>> or
>> nothing. If you are not blocked, you can successfully query for any data
>> in
>> the RIPE Database. If you are blocked (either temporarily or
>> permanently),
>> any query from you is rejected with a "Denied access" error message.'
>>
>> I assume that the above explains your predicament.
>
> Oh, it seems so.  I guess it would be nice to have an option which
> says, "please process this query in a way which does not cause
> blocking".  I mistakenly assumed that "-r" would be that option, but
> it actually isn't.
>
>
>