[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 ]
Jeroen Massar
jeroen at massar.ch
Thu Feb 24 16:50:57 CET 2022
> On 20220224, at 16:48, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > Hi Job, > >> On 24 Feb 2022, at 16:31, Job Snijders <job at fastly.com> wrote: >> >> Dear Ed, >> >> Thank you for the message. Apologies for nitpicking a bit more :-) > > Not at all, thank you for reviewing the details. > >> >> In the 'inet6num' listing you reference ">= /48", did you mean to write >> "> /48"? (which would conceptually align with the cut-off in ipv4: "> /24") >> > > This is intentional and as currently implemented, we do not allow geofeed on any assignments that are reasonably assumed to be related to one individual user. But one could have a /48 with linknets or even delegations of /56 that go to several separate users in the same city. At which point, pointing to the city is well, needed, and cannot currently be done. Greets, Jeroen
- 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 ]