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 ]
Töma Gavrichenkov
ximaera at gmail.com
Sun Mar 24 02:08:53 CET 2019
Peace, > A new RIPE Policy proposal, 2019-03, "BGP Hijacking is > a RIPE Policy Violation", is now available for discussion. Alright, folks, what I'm trying to do now is to stress the conditions. Let's say it's 2021 and IPv6 is fully deployed, and IPv4 is no more. [now no one could say I'm pessimistic, right?] How's that policy supposed to work then? E.g. I'm the attacker, I start the hijacking, I continue that for 10 weeks until I'm denied membership. I don't lose any valuable address space at the time because it's just IPv6 which is totally disposable. I then switch to another LIR account I've obtained before, and start doing the same thing, at a cost of a generous sign-up fee. What's the value of the 2019-03 proposal then? -- Töma
- 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 ]