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 ]
Suresh Ramasubramanian
ops.lists at gmail.com
Wed Apr 17 15:42:35 CEST 2019
Is this despite RIPE operating a routing registry as a subset of the IRR and allowing ASNs to announce their routing policies? Despite RIPE allocating ASNs that are used in routing? On 17/04/19, 7:09 PM, "anti-abuse-wg on behalf of Peter Koch" <anti-abuse-wg-bounces at ripe.net on behalf of pk at DENIC.DE> wrote: On Tue, Mar 19, 2019 at 01:41:22PM +0100, Marco Schmidt wrote: >> BGP hijacking completely negates the purpose of a (Regional Internet) Registry. >> >This is unclear to me. The Registry registers address space, not routes.
- 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 ]