--- Begin Message ---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: % 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
--- End Message ---
- [db-wg] Foreign ROUTE objects in RIPE Database... denis walker via db-wg
- Re: [db-wg] Foreign ROUTE objects in RIPE... Lu Heng via db-wg
- Re: [db-wg] Foreign ROUTE objects in RIPE... Sascha Luck [ml] via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Nick Hilliard via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Sascha Luck [ml] via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Nick Hilliard via db-wg
- Re: [db-wg] Foreign ROUTE objects in RIPE... Clement Cavadore via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Nick Hilliard via db-wg
- Re: [db-wg] Foreign ROUTE objects in RIPE... Hank Nussbacher via db-wg
- Re: [db-wg] Foreign ROUTE objects in RIPE... Gert Doering via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Sander Steffann via db-wg
- Re: [db-wg] Foreign ROUTE objects... Lu Heng via db-wg
- Re: [db-wg] Foreign ROUTE objects in ... Piotr Strzyzewski via db-wg
- Re: [db-wg] Foreign ROUTE objects... Job Snijders via db-wg