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] Solving the issue of rogue ROUTE objects in the RIPE Database

Previous message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Next message (by thread): [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Randy Bush randy at psg.com
Fri Nov 6 22:49:07 CET 2015

> STEP 1
> 
> Any ROUTE object submitted for creation in the RIPE Database involving
> an out of region resource (address space and/or ASN) where that out of
> region resource does not exist in the authoritative RIR database (has
> not been allocated or assigned), reject the creation.
> 
> The RIPE NCC mirrors the operational data from all the other 4 RIRs.
> These mirrors are updated daily as well as the RIRs daily stats. It is
> easy to determine if a resource is registered in the authoritative
> database.

most other rir irr instances are unused.  radb is used.  i think there
is an altdb which is used.

randy

Previous message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Next message (by thread): [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]