[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] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at sobornost.net
Tue Jan 4 10:38:59 CET 2022
On Tue, Jan 04, 2022 at 10:28:04AM +0100, denis walker via db-wg wrote: > If people want to add geofeed for smaller sizes this runs the risk of > maintaining a dual system, "geofeed:" and "remarks: geofeed". We could > end up with "remarks:" values being parsed as they used to be for > abuse contacts before we added "abuse-c:". > > My understanding was that a "geofeed:" could be added to a smaller > prefix and in the referenced url add data for any prefix you wish, > including a /48. > > Just for reference, for those of you who use the "geofeed:" attribute, > how many want to add data for a /48? Is this a wide scale issue or a > corner case? Seems all /48 PI assignments are affected. That's a couple of tens of thousands? Kind regards, Job
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- 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 ]