[db-wg] NWI-3 - AFRINIC IRR Homing
- Previous message (by thread): [db-wg] NWI-3 - AFRINIC IRR Homing
- Next message (by thread): [db-wg] NWI-3 - AFRINIC IRR Homing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Wed Jul 27 21:43:22 CEST 2016
On Wed, Jul 27, 2016 at 07:32:48PM +0000, ripedenis at yahoo.co.uk wrote: > Hi Tim > Can we have some up to date numbers on how many (if any): <snip - leaving that for NCC/NIC staff> > Assuming any exist: > -How do you propose to handle any objects that have a version in both > databases that are different? Can't they just co-exist? And whoever can meet the authorisation requirements can delete either one of them. I think this is a question for AfriNIC to consider, not for the RIPE NCC staff. > -What do you propose to do with set objects that reference any of > these objects? What type of set objects are you specifically referring too? Generally operators use set expanders that span multiple databases. Speaking for myself in any of the networks I operate I don't see an issue whether the route objects are in RIPE or in AfriNIC's IRR. Just make sure your data source mirrors AfriNIC. > -How do you propose to handle any routing policy statements in other > ASN objects that refer to any objects from this set of affected > ROUTE(6) or ASN objects? Can't those references remain? References don't need to terminate in the same database. Kind regards, Job
- Previous message (by thread): [db-wg] NWI-3 - AFRINIC IRR Homing
- Next message (by thread): [db-wg] NWI-3 - AFRINIC IRR Homing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]