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
Colleagues
Based on the proposal by Tim for NWI-5 and the following discussions, the DB-WG
co-chairs would like the RIPE NCC to schedule implementation of the following
actions:
-Remove the ASN authorisation requirement for ROUTE(6) object creation
-Deprecate the "mnt-routes:" attribute in the
Hi all
Every week I get this email and usually just delete it. But as we have just
been discussing cleaning up RIPE-NONAUTH I decided to look at it this week. I
have some questions now.
It includes these lines:Prefixes from unregistered ASNs in the Routing Table:
45
Number of
Hi guys
There is a corner case where invalid ROUTE(6) objects may occur in the source:
RIPE database. Before NWI-5 a ROUTE(6) object could be created either by the
address space holder or the ASN holder. Both had to authorise the creation, but
whoever created the object would maintain it.
Routing Working Group
Sent: Wednesday, 17 October 2018, 23:18
Subject: Re: [routing-wg] source: RIPE may also contain invalid ROUTEs
Hi Denis,
Can you point us to one example object?
Kind regards,
Job
On Wed, Oct 17, 2018 at 22:23 denis walker via routing-wg
wrote:
Hi guys
There is a corner case
