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
- 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 00:04:50 CEST 2015
On Sat, Jun 27, 2015 at 05:54:08AM +0900, Randy Bush wrote: > >> o there are operators at euro ixen which require peers' routes be > >> registered in ripe irr. we don't have to like it, it's just > >> business; get over it. > > > > from the point of view of ixp operations, insisting in ripe-irr is > > neither necessary nor a good idea. > > i gave up trying to explain that to peers a long time ago. I wouldn't mind reaching out to those 'euro ixen' you mentioned. Can you either onlist or offlist tell me? > 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. Kind regards, Job
- 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 ]