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

>
>
> > and note that, with one mouth, job has said that the ripe irr is the
> > only one he will trust.
>
> Unsure if i follow you exactly, but indeed, I only trust the RIPE IRR
> when it comes to RIPE managed space.
>

Why then, do you expect anyone to trust RIPE IRR for all the un-RIPE
managed space which can be freely added, to permit RIPE managed space
related objects to be made?

Surely from a consistency point of view (and yes, its reductionist, but so
is software) this means we shouldn't be trusting all the additional objects
added 'for your convenience' under the open password maintainer?

-G


>
> Kind regards,
>
> Job
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20150627/b0b38737/attachment.html>