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/db-wg@ripe.net/

[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 ]

Edward Shryane eshryane at ripe.net
Tue Jan 4 10:00:54 CET 2022

Hi Cynthia,

> On 3 Jan 2022, at 19:44, Cynthia Revström <me at cynthia.re> wrote:
> 
> This seems weird, I would assume it should be greater than 48, not
> greater than or equal to 48.
> 
> Ed, can you confirm if this is intended or not?
> 

We currently only allow "geofeed:" to be added to IPv6 prefixes *smaller* than /48, the message is consistent (i.e. greater than or equal to /48 is *not* allowed).

We are following Legal's recommendation not to allow geofeed to be added for assignments that are reasonably assumed to be related to one individual user.

The /48 prefix size is the maximum size suggested in the "BCOP for Operators: IPv6 prefix assignment for end-users": https://www.ripe.net/publications/docs/ripe-690#4-2--prefix-assignment-options

Regards
Ed

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 ]