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/[email protected]/
[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] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Sun Jan 20 02:43:35 CET 2013
In message <2C4F5FA7-C670-4253-AE43-0C4BF5DE1A21 at steffann.nl>, Sander Steffann <sander at steffann.nl> wrote: >The RIPE documents don't say anything about the RIPE NCC contacting law >enforcement AFAIK. With all the different countries and all their >different laws that might be harder to do for the RIPE NCC than in the >ARIN region. But if it's possible: good idea. It is not only possible... as the ARIN example would seem to indicate it is even _advisable_. What is the disincentive for these same crooks coming back and doing the same thing all over again next month, using a brand new set of fradulent documents, signatures, company charters, etc. ? Regards, rfg
- Previous message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
- Next message (by thread): [anti-abuse-wg] Notice: Fradulent RIPE ASNs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]