[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] RIPE Database Quarterly Planning Q1 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Tue Jan 4 09:45:52 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
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] RIPE Database Quarterly Planning Q1 2022
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]