This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[anti-abuse-wg] RIPE Database Proxy Service Issues
- Previous message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
- Next message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Wed Jan 2 20:43:36 CET 2013
* 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.
- Previous message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
- Next message (by thread): [anti-abuse-wg] RIPE Database Proxy Service Issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]