[db-wg] re-evaluate route-object authorisation model
- Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
- Next 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 09:17:00 CEST 2015
On Sat, Jun 27, 2015 at 06:32:10AM +0200, George Michaelson wrote: > > > 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? I don't recall expecting that? Did i in some earlier email forget to insert a criticial 'not' in a sentence or something? > 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? Yes, the open password maintainer is a thorn in our side. Relevant to the discussion: https://ripe70.ripe.net/archives/video/132/ (Title is actually 'IRR Homing project')
- Previous message (by thread): [db-wg] re-evaluate route-object authorisation model
- Next message (by thread): [db-wg] re-evaluate route-object authorisation model
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]