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

On 03/01/2022 12:36, Job Snijders via db-wg wrote:
> I appreciate concerns about privacy, but I'm not wholly convinced
> restricting /48s from having a proper 'geofeed:' attribute is the best
> path forward.
> 
> How does the working group feel about this restriction? Is it useful?
> Should it be lifted? If the latter, what would be the process?

1. Feature parity should be enforced if the intention is to transition 
toward using the geofeed attribute over 'remarks: Geofeed', for certain. 
The last thing you need in this situation is for the old/bodge mechanism 
to be more featureful than the purpose-designed mechanism.

2. Should an individual assignee of a /48 determine that their privacy 
is indeed sacrosanct, then surely it is their decision (as the publisher 
of their own geofeed.csv file) to determine the level of location 
granularity that they are comfortable with?

'UK,,,' tells you nothing about me that you couldn't already infer from 
the headers from this email, and some data from the NLNOG ring.

I don't doubt that good guidance for ISPs that are populating this 
information will be important, particularly for /56s, /64s or smaller. 
However, it would fall squarely within the guidelines that already exist 
for Data Protection in their own territory.

-- 
Tom