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] 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] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Fri Nov 6 16:10:35 CET 2015
On 06/11/2015 14:00, Sascha Luck [ml] wrote: > 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 personal information is not exported for route: objects, therefore this does not apply: > remarks: **************************** > remarks: * THIS OBJECT IS MODIFIED > remarks: * Please note that all data that is generally regarded as personal > remarks: * data has been removed from this object. > remarks: * To view the original object, please query the RIPE Database at: > remarks: * http://www.ripe.net/whois > remarks: **************************** Nick
- Previous message (by thread): [db-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
- Next message (by thread): [db-wg] [routing-wg] Solving the issue of rogue ROUTE objects in the RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]