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] 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 ]

Nick Hilliard nick at foobar.org
Mon Oct 9 22:53:35 CEST 2017

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

• 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 ]