This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[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 ]
Randy Bush
randy at psg.com
Fri Jan 8 18:15:41 CET 2021
> 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. 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
- 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 ]