[db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Previous message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
dbwg at c4inet.net
Wed Oct 11 15:55:35 CEST 2017
On Mon, Oct 09, 2017 at 09:53:35PM +0100, Nick Hilliard wrote: >Sascha Luck [ml] via db-wg wrote: >> Not allowing >> "foreign" resources in the ripedb denies the reality that there >> will always be RIPE-allocated prefixes originated from >> non-RIPE-assigned ASNs and vice versa. > >Not true - you can easily run a whois query on whois.radb.net specifying >multiple sources, including RIPE: How does this fact falsify the fact that cross-RIR route: objects exist? Those have to be in *some* irrdb and as long as a cross-RIR irrdb doesn't exist, part of the data will be non-authenticated... cheers, Sascha Luck > >% bgpq3 -S RIPE,APNIC,LACNIC AS-FOO > >In fact, there is no way of writing a functioning irrdb querier which >can't handle specifying arbitrary irrdb source: options on a per-ASN basis. > >Nick
- Previous message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
- Next message (by thread): [db-wg] Foreign ROUTE objects in RIPE Database - final decision?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]