This means in some sense RIPE's security policies reflect what European ISPs and similar wanted, for good or ill.
Traditional routing has always been very, very open. Like a club where anyone is welcome and if new folks mess stuff up it just gets fixed.
Several IRRs used to allow RPSL changes by email to their systems with only maintainer auth and no verification of route ownership (e.g. you register with the IRR, then publish Google routes).
It’s all getting hardened nowadays with things like no more email, layers of verification, RPKI, etc.
It’s not necessarily what folks want but how this stuff had traditionally been handled. Thankfully it’s all changing because of events like this.
Comments
Traditional routing has always been very, very open. Like a club where anyone is welcome and if new folks mess stuff up it just gets fixed.
Several IRRs used to allow RPSL changes by email to their systems with only maintainer auth and no verification of route ownership (e.g. you register with the IRR, then publish Google routes).
It’s all getting hardened nowadays with things like no more email, layers of verification, RPKI, etc.
It’s not necessarily what folks want but how this stuff had traditionally been handled. Thankfully it’s all changing because of events like this.