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/[email protected]/
[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 ]
Randy Bush
randy at psg.com
Thu May 14 00:32:33 CEST 2015
> - 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. > I received feedback from various operators this morning that they would > like to be able to manage their resources from all over the global in a > single database/service. i think we already have one randy
- 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 ]