On 2022 Jan 03 (Mon) at 12:36:49 +0000 (+0000), Job Snijders via db-wg wrote: :Dear all, : :Like all good netizens, I tried to align information I publish in the :RIPE database to reality, but there is an obstacle: : : https://sobornost.net/~job/geofeed.png : : """Adding or modifying the "geofeed:" attribute of an object with a : prefix length greater or equal to 48 is not allowed.""" : :No such restriction exists if you use the 'remarks: Geofeed' approach, :as demonstrated here: : : $ whois -h whois.ripe.net 2001:67c:208c::/48 | grep Geofeed : remarks: Geofeed https://sobornost.net/geofeed.csv : :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? : :Kind regards, : :Job
I think that this restriction is silly. This /48 was assigned by RIPE NCC, there is no parent that you can add the geofeed to. I think the restriction in general should be lifted, but if a restriction *should* exist, then it should always be allowed for the smallest of the "assigned by RIPE NCC" / "allocated by RIPE NCC" sizes, even if that is a smaller size than what was issued by RIPE NCC. (e.g., in IPv6 you could always add the geofeed: attribute to a /48, even if it is inside an allocated /29). -- The reason computer chips are so small is computers don't eat much. -- 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
