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] geofeed issue: can't add geofeed attribute to PI /48
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Mon Feb 21 17:10:38 CET 2022
Hi Ed Can you clarify this comment... > > Our Legal team have considered the concerns from a part of the community regarding the eligible size for “geofeed:” validation and concluded the following: > Since resources with prefix size equal to the size distributed/registered by the RIPE NCC to a resource holder is not considered to be personal data, an equal prefix size may receive the “geofeed:” validation. > > Accordingly, we will allow "geofeed:" on ALLOCATED PA or top-level ASSIGNED PI (for IPv4) and ALLOCATED-BY-RIR on top-level ASSIGNED PI (for IPv6). Are you saying you will ONLY allow geofeed on resources with these status values? What about SUB-ALLOCATED PA and AGGREGATED-BY-LIR? The nature of these status values suggests they are not personal data. "an equal prefix size may receive the “geofeed:” validation." Or are you saying any object with a size equal to any allocation can have a "geofeed:" attribute? That would mean a /24 for IPv4. cheers denis co-chair DB-WG
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]