On Mon, 3 Jan 2022 at 18:19, Randy Bush via db-wg <
db-wg@ripe.net> wrote:
> I appreciate concerns about privacy, but I'm not wholly convinced
> restricting /48s from having a proper 'geofeed:' attribute is the best
> path forward.
drumroll! and the best path forward is? :)
My personal preference would be for the restriction to be lifted. I’m sceptical the restriction is achieving its intended purpose, and at the same time it seems to be hindering Geofeed deployment.
my non-ecc memory is that this is ncc legal trying not to get highly
specific. i.e. it is not a wg matter.
To me it seems this database feature is broken: I can reference my geofeed file via one method, but not via another (nicer) method.
Regardless of the cause of the dysfunctionality, I think the Database Working Group is the appropriate forum to discuss the problem of being unable to use the geofeed RPSL attribute in database objects.
Kind regards,
Job