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 WHOIS blocked
- Previous message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
- Next message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Tue Nov 18 11:24:23 CET 2014
Ronald F. Guilmette wrote: > Apparently, somebody @ RIPE NCC thinks that I have been too curious of late. s/somebody/something/ :-) > > How long should it take for this error to go away? About a day, I guess, unless you continue to hammer along... [...] > And anyway, can anyone here explain to me what the point is of limiting > WHOIS queries based on the source IP address? Some sort of (weak, we all know,) protection of mass harvesting of potentially personal data, *and* some sort of protection against run-away scripts from the same source. This is a pretty old mechanism and its shortcomings are known. [...] > More to the point, who is it, specifically, within RIPE NCC, that has > the authority to fix this? No one. And please stop accusing the NCC folks of stupidity and other useless stuff! Coming forward with proposals for removing or modifying the mechanisms imho would be the responsibility of the Community, either in AA-WG and/or DB-WG or maybe Services. IIRC, we had a brief discussion a while ago in DB-WG, regarding a more useful(?) configuration that would still honour resource queries *not* asking (implicitly or explicitly) for contact information or person objects. > Regards, > rfg Wilfried
- Previous message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
- Next message (by thread): [anti-abuse-wg] RIPE WHOIS blocked
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]