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/[email protected]/

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

Previous message (by thread): [db-wg] update on draft-spaghetti-grow-nrtm-v4-00
Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jeroen Massar jeroen at massar.ch
Fri Feb 11 17:16:24 CET 2022

> Hi Job, Colleagues,
> > On 3 Jan 2022, at 13:36, Job Snijders via db-wg <db-wg at ripe.net> 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? 
> > 
> I will ask our Legal team to re-examine the prefix size restriction and keep you and the DB-WG informed.
> Regards Ed Shryane RIPE NCC 

Hi Ed,

Did something come out of this?

It is a very silly restriction, especially for PI /48's but also for the simple fact that one can register very small prefixes (I've done IPv4 /28 and IPv6 /56) in the actual geofeeds file.

Greets,
 Jeroen

Previous message (by thread): [db-wg] update on draft-spaghetti-grow-nrtm-v4-00
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 ]