Hi, On Fri, Jul 29, 2022 at 02:33:07PM +0200, Edward Shryane via db-wg wrote:
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.
In which way would "status:" differenciate between business customers and personal end users?
(4) Resources that are reasonably assumed to be related to one individual user cannot use the "geofeed:" attribute. inetnum: ASSIGNED PA inet6num: ASSIGNED
"ASSIGNMENT" = "one *individual* user" is not a valid assumption. It's a customer. Maybe. It might be an enterprise with 100 offices, or Joe Random Personal User. Why is nobody listening here? Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279