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 ]
Nick Hilliard
nick at inex.ie
Thu May 14 11:32:50 CEST 2015
On 14/05/2015 00:32, Randy Bush wrote: >> - should the authorisation model work differently for RIPE managed >> space versus non-RIPE managed space? Should we even continue to >> allow route-objects covering non-RIPE managed space? > > some folk at euro ixen require route objects in ripe's irr. some folk > who get address space from other rirs appear at those euro ixen and wish > to peer. ixps which build route server configurations using ixp manager can apply arbitrary IRR source tags (or combinations) on a per-customer basis. Nick
- 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 ]