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] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Wed Mar 20 09:36:06 CET 2019
On Wed, 20 Mar 2019, Hank Nussbacher wrote: (...) > I think we have different expections from criminals. I view the criminals as > ones who analyze every RFC and every standard to determine where they can be > abused or manipulated for their benefit. A sanction that would be > implemented 18 months later would allow the evil LIR enough time to sell > their resources to some other LIR such that they would not lose such > resources. > > -Hank Hi, Afaik, transfers are traceable. Not sure if they can be "reverted", but if LIR A transfers to LIR B, and if it is possible to establish that the same entity/org controls LIR A and LIR B, this should only be a matter of filing a report with all the details (referencing LIR A and B). Regards, Carlos
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]