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

Sascha Luck [ml] dbwg at c4inet.net
Fri Nov 6 15:00:56 CET 2015

On Fri, Nov 06, 2015 at 02:14:15PM +0100, Job Snijders wrote:
>Intuitively it would appear that RIPE NCC would have to strike a deal
>with the other 4 RIRs to be allowed to retrieve those email addresses,
>as some RIRs hide / rate-limit email addresses because of
>abuse/privacy concerns.

This wouldn't be a one-way street, presumably, it would also
involve the NCC exporting such data to other RIRs. 
That is currently somewhat thin ice for EU-sourced data: 
http://curia.europa.eu/jcms/upload/docs/application/pdf/2015-10/cp150117en.pdf

rgds,
Sascha Luck

• Previous message (by thread): [db-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 ]