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

- should the authorisation model work differently for RIPE managed space versus non-RIPE managed space? Should we even continue to allow route-objects covering non-RIPE managed space?

some folk at euro ixen require route objects in ripe's irr. some folk who get address space from other rirs appear at those euro ixen and wish to peer.

I received feedback from various operators this morning that they would like to be able to manage their resources from all over the global in a single database/service.

i think we already have one randy