[db-wg] Fwd: proposal: new attribute 'geofeed:
- Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Kafka
mika at net-cat.at
Sun Jan 10 07:36:28 CET 2021
On 2021-01-08 18:15, Randy Bush via db-wg wrote: >> If the geofeed doesn't contain the above mentioned means to directly >> or indirectly identify a natural person then GDPR don't apply, >> especially if the geofeed refers only to a country or province. > > note that the geofeed spec, RFC8805, is separate from the rpsl-based > means to find the geofeed files, draft-ietf-opsawg-finding-geofeeds. that wouldn't make a difference here. if the RIPE database points immediately to personal information GDPR applies. > i was not involved in the geofeed spec, but it was done by friends of > the family who gossip :) > > i was told that the reason there is no postal code in the geofeed file > spec is because, in some cases, it resolves with sufficient precision to > identify individuals. > > randy the precision of postal codes (e.g. in great britain) is a good point! MiKa
- Previous message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]