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 ]
Ronald F. Guilmette
rfg at tristatelogic.com
Thu Nov 5 00:09:05 CET 2015
In message <C01FCD42-551B-496F-AFFF-BF5561150580 at gmail.com>, Suresh Ramasubramanian <ops.lists at gmail.com> wrote: >Right now, most other lists that I see this thread start up on, there >are a few people who defend RIPE NCC - and a lot of people who dump on >it for this kind of thing. I like to think that I am neither defending nor dumping on either RIPE or RIPE NCC. I'm still too busy being flummoxed and mystified to do either of those other things. As I've said, everyone who cares about the quality of their data... from Google Voice, to Craigslist, to UPS... has already been doing the obvious thing for years, i.e. checking it. I'm still trying to get my arms around the idea that RIPE doesn't. That's so last century. And anyway, this isn't a RIPE NCC thing. It's a RIPE thing. As I understand it, RIPE decides and RIPE NCC implements. What am I missing? Regards, rfg
- 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 ]