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 ]
Randy Bush
randy at psg.com
Thu May 14 11:47:59 CEST 2015
>> 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. yes, and peval() and other tools take an IRR instance list. but i have enough windmills without tilting at this one. you wanna peer with brunhilde, you play by her rules. when i saddle up rosenantes, it is to get all this to be rpki-based origin validation instead. 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 ]