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] Notice: Fradulent RIPE ASNs
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Attempting to provide some transparency to RIPE NCC abuse handling (was Notice: Fradulent RIPE ASNs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Mon Jan 21 13:06:25 CET 2013
Hi, >> Even better! Then we also have an input/output view on the RIPE NCC >> fraud/complaint handling procedure. > > Ummmm... no. I meant 'even better when this is added to what I already suggested'. Publishing which resources have been revoked/reclaimed/etc (when possible including the name of the last holder) would be the most important part. Publishing both sides would make it possible for everyone to see which resources got complaints and which resources got revoked. Cheers, Sander
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Attempting to provide some transparency to RIPE NCC abuse handling (was Notice: Fradulent RIPE ASNs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]