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] Route objects for space administered by other RIRs
- Previous message (by thread): [db-wg] Route objects for space administered by other RIRs
- Next message (by thread): [db-wg] Route objects for space administered by other RIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Wed May 12 09:46:53 CEST 2021
Hi Erik, > On 12 May 2021, at 09:27, Erik Linder <erik.linder at gmail.com> wrote: > > > The proposed cleanup is to only remove route(6) objects from RIPE-NONAUTH which are not registered in *any* region: > too bad, because I have a use case where I have a couple of route objects in RIPE-NOAUTH but they are maintained by an old peering partner which seems to have no wish to help me remove those objects which are legit AFRINIC route objects. thus although I want to clean them, I can't. > > regards > Erik There is a RIPE policy to cleanup conflicting route(6) objects in the NONAUTH database: https://www.ripe.net/publications/docs/ripe-731 If you can create a ROA for the Afrinic prefix, a cleanup job will delete any conflicting route(6) for you. Regards Ed
- Previous message (by thread): [db-wg] Route objects for space administered by other RIRs
- Next message (by thread): [db-wg] Route objects for space administered by other RIRs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]