This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] re-evaluate route-object authorisation model
- Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Sat Jun 27 14:41:32 CEST 2015
On Sat, Jun 27, 2015 at 02:35:20PM +0200, George Michaelson wrote: > On 27 June 2015 at 09:17, Job Snijders <job at ntt.net> wrote: > > > 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? > > > > I don't recall expecting that? Did i in some earlier email forget to > > insert a criticial 'not' in a sentence or something? > > So those route objects which refer to RIPE managed space, and non-RIPE > managed space. Do you filter them out? The ones which have non-RIPE > objects inserted? > > I thought you meant that if it was in the RIPE IRR you trusted it. I > didn't realize you were performing a post-check on the origination of > the referred elements in route and other objects. Maybe some forward looking statements caused confusion, there may be a discrepancy between what we have today in the database, what I have today deployed in the network, what I wish we had and where we are heading :-) I suggest we focus again on the topic at hand.
- Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]