On Wed, Oct 11, 2017 at 12:28 PM, Daniel Shaw via db-wg <db-wg@ripe.net> wrote:

On 11/10/2017, 14:09, Job Snijders via db-wg typed:

...

You as network operator can easily poll the APNIC or AFRINIC database. There are even a number of "IRR aggregation services" such as NTTCOM and RADB which mirror a ton of IRRs for your querying convenience.

Without commenting on the debate either way (in this mail, at this time), just a quick technical note: In fact, the RIPE DB mirrors the AFRINIC IRR data, so you at least as far as AFRINIC goes, provided there is IRR data in the AFRINIC DB, you can get it by querying the RIPE DB with the correct 'source:'

Correct. But if RIPE allows the creation of objects for which it has no authority over, what are users supposed to do when they see the contradicting data coming from RIPE and AFRINIC (to follow your example)? That's also the reason for the existence of the --resource query flag. Question is, why would we keep data that is not authoritative (and not mirror) in the RIPE DB? Agoston On Wed, Oct 11, 2017 at 12:28 PM, Daniel Shaw via db-wg <db-wg@ripe.net> wrote:

---------- Forwarded message ---------- From: Daniel Shaw <daniel@afrinic.net> To: Database WG <db-wg@ripe.net> Cc: Bcc: Date: Wed, 11 Oct 2017 14:27:56 +0400 Subject: Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision? On 11/10/2017, 14:09, Job Snijders via db-wg typed:

...

You as network operator can easily poll the APNIC or AFRINIC database. There are even a number of "IRR aggregation services" such as NTTCOM and RADB which mirror a ton of IRRs for your querying convenience.

Without commenting on the debate either way (in this mail, at this time), just a quick technical note: In fact, the RIPE DB mirrors the AFRINIC IRR data, so you at least as far as AFRINIC goes, provided there is IRR data in the AFRINIC DB, you can get it by querying the RIPE DB with the correct 'source:'

Cheers, Daniel