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 ]
Sascha Luck [ml]
aawg at c4inet.net
Tue Nov 3 14:59:54 CET 2015
On Tue, Nov 03, 2015 at 07:18:45PM +0530, Suresh Ramasubramanian wrote: >I doubt - >1. You are being asked to code this for RIPE NCC Irrelevant, I'm talking about the LIR contacts or end-users being made to deal with this. >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. You know nothing about me. What I do or do not have experience with is none of your concern. If you want to make this personal, go right ahead. I'm not afraid of any amateur spook, I have had to deal with the real thing. >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. All the "outraged howls" I've seen in this thread are from so-called "security experts" with evidently little or no experience in LIR operations. rgds, Sascha Luck
- 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 ]