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] Fwd: Geofeed purpose
- Previous message (by thread): [db-wg] denying access to RIPE DB for proven spammers
- Next message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Theodoros Fyllaridis
tfyllaridis at ripe.net
Thu Sep 14 11:48:16 CEST 2023
Dear Colleagues, We would like to provide you with an update on the amendments to the RIPE Database Terms and Conditions. The RIPE Database Terms and Conditions may be amended by either the RIPE NCC (Article 8.2) or the Policy Development Process (Article 8.3). After a long discussion, the Database Working Group reached consensus that providing geolocation information is an agreed additional purpose of the RIPE Database. This consensus was not the outcome of the Policy Development Process. Based on this mandate, the RIPE NCC will work on amending the Terms and Conditions to include this new purpose, as per Article. 8.2 and according to the process set out in the Adoption Process for RIPE NCC Corporate Documents: https://www.ripe.net/about-us/legal/corporate-governance/adoption-process-for-ripe-ncc-corporate-documents. The proposed text will be based on the community's consensus that geolocation information about the usage of Internet number resources is necessary to facilitate Internet operations. The text will then be reviewed by the RIPE NCC Executive Board in accordance with the aforementioned Adoption Process for RIPE NCC Corporate Documents. Kind regards, Theodoros Fyllaridis Legal Counsel RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20230914/e2b0fc3f/attachment-0001.html>
- Previous message (by thread): [db-wg] denying access to RIPE DB for proven spammers
- Next message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]