[db-wg] Temporary origins
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Thu Jun 25 18:31:15 CEST 2015
On Thu, Jun 25, 2015 at 05:28:29PM +0100, Sascha Luck [ml] wrote: > 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. I disagree. Especially since I already today have software that can deal with multiple route-objects covering the same prefix, I don't feel inclined to break the current practise. :-) > Of course, this wouldn't be practical if it required authorisation > from the inetnum: owner and every ASN owner on the list. Correct. Kind regards, Job
- Previous message (by thread): [db-wg] Temporary origins
- Next message (by thread): [db-wg] Temporary origins
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]