[db-wg] Fwd: proposal: new attribute 'geofeed:

HI Hank, colleagues

Whilst I can't answer your basic question, I could say that if the
IETF approves a change to RPSL, with the RIPE Database data model
based on RPSL, in principle we should implement the RPSL change.

Perhaps another question, to the RIPE NCC legal team, if I have a
fixed IP address or block of addresses, is this geofeed location data
personal data under the terms of GDPR?

cheers
denis
co-chair DB-WG

On Wed, 6 Jan 2021 at 07:01, hank--- via db-wg <db-wg at ripe.net> wrote:
>
> I guess I am not understanding something.
> Why do we need a geofeed attribute?  What problem are we trying to solve?
>
> I understand why each block of IPs needs to be associated with a
> country, so that certain language specific auto-customizations will
> work.  But what purpose is there to know that a /24 is in central
> Amsterdam?  Is the purpose to assist marketers in geo-targetted sales?
>   Is the purpose for network engineering (not sure what major problem
> we have that needs this)?
>
> Is the purpose to know where you are so that in the event of an
> emergency (terror, tornado, etc) you can get emergency targeted
> alerts?  If so, then the geofeed has to be at the /32 level and since
> many if not most IPs are mobile, and that is where you will get the
> alert from - from your cellphone provider, I still don't quite
> understand the reason for a geofeed tag.
>
> Can someone clue me in?
>
> Thanks,
> Hank
>
> Caveat: The views expressed above are solely my own and do not express
> the views or opinions of my employer
>
>