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/anti-abuse-wg@ripe.net/
[anti-abuse-wg] WHOIS (AS204224)
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Tue Nov 3 14:48:45 CET 2015
I doubt - 1. You are being asked to code this for RIPE NCC 2. You get all that much spam to filter out - as far as I can see from linkedin, your previous experience is all in desiging and running IXPs and coordinating peering - I wouldn’t presume to argue with you about any of those. So while you’d rather have the spam, there are people that need to filter much larger userbases, that would very much rather not. Yet, all the outraged howls in this thread I hear come mostly from people who are from a routing or an addressing background rather than from any kind of a security background. I suppose if many of your [and this is a collective your] colleagues with actual security and postmaster roles were to attend RIPE meetings, there wouldn’t be this highly comfortable consensus that everything is running just fine. —srs > On 03-Nov-2015, at 7:12 PM, Sascha Luck [ml] <aawg at c4inet.net> wrote: > > There are LIRS that register many thousands of objects. Even > small LIRs can have many hundreds. Is the idea that they employ > someone full-time to solve captchas for the NCC (another idea > from this discussion)? > Frankly, I'd rather have the spam, at least I can filter that.
- Previous message (by thread): [anti-abuse-wg] WHOIS (AS204224)
- Next message (by thread): [anti-abuse-wg] WHOIS (AS204224)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]