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

+1

This seems like legal might have forgotten that end user could mean a
legal entity (and probably does in far more cases than not).

Also I don't get why the geofeed attribute would not be acceptable,
when you can add an admin-c attribute with the individual end-users
name, address, and phone number.

It kinda seems like the geofeed attribute should be one of the least
problematic things in the RIPE DB from a PII perspective.
Especially when you consider things like how the NCC is just
publishing a URL and how a /47 could have a geofeed attribute
containing details for individual /48s (or even more specific
prefixes).

Could someone direct me to what NCC legal's reasoning behind this was?
(if it was published)

While I would assume they know lots about this as they work at the
NCC, I just don't understand the logic and it feels like maybe there
was a misunderstanding somewhere.

I feel like I am both a bad and good example as I do have a /48 PI
that is registered to me as a person, which is kinda what I am trying
to say is not common...
However a geofeed attribute is nothing compared to the fact that my
legal name, address, email address, and phone number are published in
the RIPE DB in order for me to have that PI resource.

So with regards to PI resources at least, not being able to do Geofeed
for /48 makes absolutely no sense to me, in what does it matter if I
publish which city I am in if my address is already published.
I think this would be the case for all PI resources as they are not to
be further assigned to customers and I do think that the address is
required according to some policy if I recall correctly.

-Cynthia

On Tue, Jan 4, 2022 at 7:18 PM Randy Bush via db-wg <db-wg at ripe.net> wrote:
>
> [ i wanted to write to you off-list, but illegal header mangling by the
>   list software prevented it. ]
>
> > The /48 prefix size is the maximum size suggested in the "BCOP for
> > Operators: IPv6 prefix assignment for end-users":
> > https://www.ripe.net/publications/docs/ripe-690#4-2--prefix-assignment-options
>
> i suspect some confusion caused by the term "end user."  i do not expect
> there are many assignments of /48s to individual human beings.  i
> suspect that what was meant by end "user was" more in the realm of a PoP,
> or head end, or ...
>
> end users in the PII sense tend to be given /56../64
>
> randy
>
> --
>
> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/