Hi all 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? cheers denis co-chair DB-WG On Tue, 4 Jan 2022 at 10:00, Edward Shryane via db-wg <db-wg@ripe.net> wrote:
Hi Cynthia,
On 3 Jan 2022, at 19:44, Cynthia Revström <me@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-optio...
Regards Ed
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg