<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="DE" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> So the geofeed attribute will be deleted from the database?<o:p></o:p> Do you have a timeframe for this implementation?<o:p></o:p> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> Von: db-wg <db-wg-bounces@ripe.net> Im Auftrag von Maria Stafyla via db-wg Gesendet: Donnerstag, 28. Juli 2022 13:33 An: db-wg@ripe.net Betreff: [db-wg] NWI-13 Geofeed Legal Analysis<o:p></o:p> </div> </div> <o:p> </o:p> Dear colleagues,<o:p></o:p> Following the legal update we provided on NWI-13: Geofeed at the DB WG session at RIPE 84, here is our analysis in case further discussion on this topic is needed. <o:p></o:p> Executive Summary:<o:p></o:p> - The RIPE Database is meant to contain specific information for its documented purposes.<o:p></o:p> - Information inserted in the geofeed attribute could in some cases qualify as personal data.<o:p></o:p> - The current purposes could explain geolocation information to be inserted only for ‘scientific research into network operations and topology’.<o:p></o:p> - This purpose does not justify the processing of personal data; therefore restrictions had to be put in place to avoid the processing of unnecessary personal data.<o:p></o:p> - The restrictions are now implemented based on the status of the registration.<o:p></o:p> - If the purposes of the RIPE Database have changed in the meantime, this should be established via the community processes and documented. In that case we will re-evaluate the situation and the need for restrictions. Until then, the restrictions remain necessary.<o:p></o:p> Legal Analysis:<o:p></o:p> The RIPE Database is meant to contain specific information for the purposes that are defined in the RIPE Database Terms and Conditions.<o:p></o:p> In terms of the _personal data_ inserted in there, the purpose that justifies its publication is to facilitate the coordination of network operations for the smooth and uninterrupted operation of Internet; this purpose explains why contact details of resource holders or their appointed contact persons are required. <o:p> </o:p> Before any new type of personal data is permitted to be inserted in the RIPE Database, we must evaluate if their processing is required for the purposes already defined and their processing can be considered in line with the basic personal data processing principles.<o:p></o:p> Although it is the responsibility of the party inserting personal data to ensure that they have the appropriate legal grounds before doing so, the RIPE NCC has also shared responsibilities with regards to the personal data in the RIPE Database. This is because the RIPE NCC is the party that is making the RIPE Database available and implements the instructions given by the RIPE community.<o:p></o:p> As mentioned in the Legal Review Impact Analysis, if the geofeed attribute is inserted for registrations of assignments that are reasonably assumed to be related to one individual user, then the attribute will be considered as containing personal data and GDPR will apply. This is why we have proposed to implement restrictions.<o:p></o:p> These restrictions are essential to avoid any processing of personal data that is not required or necessary for the currently defined purposes of the RIPE Database and to limit the RIPE NCC's liability as a party with shared responsibilities in relation to the personal data inserted in the RIPE Database. <o:p></o:p> Regarding the _(non-personal) data _inserted in the RIPE Database, it is also paramount that only data that is needed for the defined purposes of the RIPE Database is inserted.<o:p></o:p> According to the RIPE Database Terms and Conditions, introducing the geofeed attribute (with restrictions) would be considered in line and acceptable to be used only for scientific research into network operations and topology (see Art. 3).<o:p></o:p> We also understand that the purposes the RIPE Database must fulfil are not static but evolve over time.<o:p></o:p> The RIPE Database Requirements Task Force has recently concluded its work and, with regard to geolocation, it has established that, although there is an active user group for geolocation data, geolocation itself is not an objective that the RIPE Database should fulfil.<o:p></o:p> If the community's interests have changed since then and it is now agreed that geolocation is one of the purposes the RIPE Database must fulfil, this should be decided via the community's processes and reflected in the RIPE Database Terms and Conditions. <o:p></o:p> In line with the data management principles proposed by the RIPE Database Requirements Task Force, it would be prudent to approach this issue holistically, taking into account that other geolocation information is already provided in the RIPE Database (i.e. geoloc, country code attributes in ORG and resource objects). <o:p></o:p> On the basis of a new purpose for the geolocation information, we could then reassess the situation to understand whether the restrictions on the geofeed attribute are still necessary or whether it is justified to process personal data for this purpose.<o:p></o:p> Kind regards, Maria Stafyla Senior Legal Counsel RIPE NCC<o:p></o:p> </div> </div> </body> </html>