[db-wg] geofeed issue: can't add geofeed attribute to PI /48

Dear Ed,

Thank you for the message. Apologies for nitpicking a bit more :-)

On Thu, Feb 24, 2022 at 04:28:39PM +0100, Edward Shryane via db-wg wrote:
> > On 24 Feb 2022, at 13:19, Job Snijders <job at sobornost.net> wrote:
> > On Mon, Feb 21, 2022 at 03:56:00PM +0100, Edward Shryane wrote:
> >> 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).
> > 
> > For completeness sake, can you clarify which types of objects (under the
> > new rules) are NOT eligible to specify the 'geofeed:' RPSL attribute?
> 
> The Legal review in November recommended:
> 
> "if the geofeed attribute is inserted for registrations of assignments
> that are reasonably assumed to be related to one individual user, then
> the attribute will be considered personal data. "
> 
> And from the clarification this week:
> 
> "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. "
> 
> Following these recommendations, for inetnum:
> 
> - ALLOCATED PA: Allocated by RIPE NCC, Geofeed is allowed
> - ALLOCATED UNSPECIFIED: Not assigned to an invididual, Geofeed is allowed
> - LIR-PARTITIONED PA: Not assigned to an individual, Geofeed is allowed
> - SUB-ALLOCATED PA: Not assigned to an individual, Geofeed is allowed
> - ASSIGNED PA: Second-level resource may be assigned to an individual, Geofeed is not allowed on prefix size > /24
> - ASSIGNED PI: Allowed on top-level PI assignments from RIPE NCC. Second-level resource may be assigned to an individual, Geofeed is not allowed on prefix size > /24
> - ASSIGNED ANYCAST: Not assigned to an individual. Geofeed is allowed.
> - LEGACY: May be used by an individual. Geofeed is not allowed on prefix size > /24
> 
> And for inet6num:
> 
> - ALLOCATED-BY-RIR: top-level allocation by RIPE NCC, geofeed is allowed
> - ALLOCATED-BY-LIR: not assigned to an individual, geofeed is allowed
> - AGGREGATED-BY-LIR: not assigned to an individual, geofeed is allowed
> - ASSIGNED: second-level resource may be assigned to an individual, geofeed is not allowed on prefix size >= /48
> - ASSIGNED ANYCAST: not assigned to an individual, geofeed is allowed
> - ASSIGNED PI: second-level resource may be assigned to an individual, geofeed is not allowed on prefix size >= /48

In the 'inet6num' listing you reference ">= /48", did you mean to write
"> /48"? (which would conceptually align with the cut-off in ipv4: "> /24")

Kind regards,

Job