Hi Ronald
I understand your viewpoint, but I think it is a bit harsh to criticise the
judgement of the early developers of the routing system. As Sandra explained in
this posthttps://www.ripe.net/ripe/mail/archives/db-wg/2017-October/005707.html
the early model was based on ASs. Then as the reliance moved more towards IPs
the systems and procedures were modified to encompass the changing model. And
also not all RIRs operated an IRR for many years so the ROUTE objects had to go
somewhere. And Internet abuse may not have been much of a concern during the
development of the early routing system and later modifications.
It is generally accepted now that there are serious concerns with the current
model and we are all working towards resolving these issues.
cheersdenisco-chair DB WG
From: Ronald F. Guilmette via db-wg <[email protected]>
To: Database WG <[email protected]>; RIPE Routing Working Group
<[email protected]>
Sent: Thursday, 11 January 2018, 2:23
Subject: Re: [db-wg] [routing-wg] Last Call - creation of new out of region
ROUTE(6) objects
In message <cakr6gn3zuq-rcix4jaxiio5ntenewwntkfzr2-2vrgc5wjc...@mail.gmail.com>
George Michaelson <[email protected]> wrote:
>I do not believe any future ROUTE and ROUTE6 object creation should
>be permitted routinely, for non-RIPE address space, inside the RIPE
>NCC routing registry.
I would go futher than that and say that it was a colossal error in
judgement to have EVER allowed any of this nonsense.
I have a massive quantity of never before revealed evidence showing just
how prodigiously various crooks and spammers have abused this "feature".
I will share that, if there is anyone on these lists who is as yet
unconvinced of either the ability or willingness of various crooks and
spammers to drive the proverbial truck through this massive, gaping and
absurd security hole, mostly with respect to IPv4, but also, as has been
described by others, with respect to IPv6 as well.
It is well past time for RIPE to stop allowing any random, arbitrary, and
unidentified orangutan with a keyboard to determine what routes are placed
into the global routing table.
Regards,
rfg
