[anti-abuse-wg] Draft Anti-Abuse Working Group Minutes - RIPE 60

frank at powerweb.de wrote:

> Conclusion: because RIPEs members are not willing to take
> responsibility and abuse will continue forever.

We don't know what the members think, or are prepared to do.  Sure, we
are told in no uncertain terms what the NCC thinks the members think -
but the members I have spoken to certainly don't think that way.  So is
it that the members don't effectively voice their opinions - or could it
be that just one member of the NCC staff wants us all to believe that
everyone thinks what he wants everyone to think?

>> why AS43074 and 193.109.246.0/23 are no longer in the RIPE database.
>> But AS43074 (announcing 193.109.246.0/23) is being routed by STARNET
> Well, thats clearly a mistake of STARNET then.

Such mistakes are often associated with appropriate revenue adjustments.

> You should talk to them, if STARNET is one of your upstream providers.
> The should really filter there routes against route objects.

Starnet connect (to the UK) at LINX.  LINX policies are clearly stated
- their members can do whatever they like (as far as LINX is concerned)

>> Unfortunately removing rDNS etc won't stop that malware spreading.
> True, but revocation of route objects does.

Only for some communities.  Route objects are only relevant in parts
of the RIPE service region.  And certainly not in North America etc.
See: http://www.robtex.com/as/as31252.html

-- 
Richard