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/db-wg@ripe.net/
[db-wg] RIPE Database Access Control
- Previous message (by thread): [db-wg] RIPE Database Access Control
- Next message (by thread): [db-wg] Filtering auth: attributes in the whois server (was: Re: Suggestion...)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Fri Mar 9 14:09:09 CET 2012
On 08/03/2012 11:29, Denis Walker wrote: > 1) We think it is more intuitive to have to ask to receive the personal > data, rather than be given it by default. I disagree. This will break lots of scripts out there except for the very small number of people/organisations who are hitting the database very hard. > 2) Regardless of default behaviour, we think when they hit the limit, > they should not get completely blocked. Instead, a user should still be > able to access the RIPE Database, but without receiving any personal > data in their query results. Ok, that is a sensible compromise yes. I.e. stuff like irrtoolset and rpsl queries will still work, but user information trawling won't. > We typically block about 50 IP addresses per day for excessive querying > of personal data. Most people who contact ripe-dbm with questions about > blocking did not realise they should use '-r' if they do not want > personal data. Seems a relatively constrained problem them. Again, I don't think that changing the default behaviour in order to reduce this 50 to something smaller is worthwhile, given the amount of trouble it will cause for everyone else who stays within the limits. Nick
- Previous message (by thread): [db-wg] RIPE Database Access Control
- Next message (by thread): [db-wg] Filtering auth: attributes in the whois server (was: Re: Suggestion...)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]