[db-wg] re-evaluate route-object authorisation model

On Fri, Jun 26, 2015 at 08:14:49AM +0900, Randy Bush wrote:
> > If the address space is assigned by a different RIR then Creating a 
> > Route Object in RIPE should be disallowed.
> 
> sigh, let's try once more
>   o there are operators at euro ixen which require peers' routes be
>     registered in ripe irr.  we don't have to like it, it's just
>     business; get over it.
>   o there are folk who peer at those same ixen whose address space
>     was not assigned by ripe ncc.

Which IXPs? You are referring to route servers?

In November 2014 the group had some on and offline discussion about
setting a different value for the "source:" attribute in case the space
covered by the route-object was non-ripe-managed.

    https://www.ripe.net/ripe/mail/archives/db-wg/2014-November/004421.html

I still think this is a sound idea and am waiting on some external
factors to make this reality.

Kind regards,

Job