Dear colleagues, We are following the discussion on updating the purposes of the RIPE Database to accommodate geolocation. Until then we need to perform validation according to the legal analysis based on the current purpose. If there are updates on the discussion on the purposes of the database, we will re-evaluate the situation. In the meantime, this is how we plan to update the validation of the "geofeed:" attribute:
(1) Firstly, the current validation based on prefix size is inadequate as it doesn't account for the intended use. We will replace the validation by prefix size with validation by "status:" value. (2) Resources allocated or assigned by the RIPE NCC to a resource holder are not considered personal data and can use "geofeed:", including: inetnum: ALLOCATED PA, ASSIGNED PI inet6num: ALLOCATED-BY-RIR, ASSIGNED PI (3) Resources with a "status:" not intended for individual assignment can also use "geofeed:" including: inetnum: SUB-ALLOCATED PA, AGGREGATED-BY-LIR, LIR-PARTITIONED PA, ASSIGNED ANYCAST inet6num: ALLOCATED-BY-LIR, AGGREGATED-BY-LIR, ASSIGNED ANYCAST (4) Resources that are reasonably assumed to be related to one individual user cannot use the "geofeed:" attribute. inetnum: ASSIGNED PA inet6num: ASSIGNED (5) LEGACY resources are not in scope. If there is interest in using "geofeed:" with legacy resources we can evaluate. We intend to implement these changes in the next Whois release. Regards, Ed Shryane RIPE NCC > On 28 Jul 2022, at 13:33, Maria Stafyla via db-wg <[email protected]> wrote: > > > Dear colleagues, > > 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. > -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
