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
Mon Jan 11 00:36:16 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. > > that wouldn't make a difference here. if the RIPE database points > immediately to personal information GDPR applies. cool! i was in need of an authoritative legal opinion. when are we removing the key-cert: and person: objects? > the precision of postal codes (e.g. in great britain) is a good point! as today's legal authority, can you tell me if gdpr applies to all parts of the british isles? asking for a friend. 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 ]