On Wed, Jun 24, 2015 at 09:15:46AM +0200, Job Snijders wrote:
Already today the RIPE database supports this, you can create multiple route-objects covering the same prefix but with different "origin:" values.
I didn't know this. IMO, the saner way to go about that would be to have one route: object with a multiple (allowed) origin: values. Should be easier to evaluate programmatically, too.
The problem with that is that the authorization for the maintenance of such a "mixed" object becomes highly problematical.
Of course, this wouldn't be practical if it required authorisation from the inetnum: owner and every ASN owner on the list.
Exactly. Think of the "route" objects in the IRR as "these may be announced", not "these *are* being announced", and in a transition phase for a prefix (re-homing to another ISP), two route objects for the same route will be required. Regards, - Håvard