geofeed: RPSL attribute (draft-ymbk-opsawg-finding-geofeeds)

[job]

Is your feature request related to a problem? Please describe.

It seems https://tools.ietf.org/html/draft-ymbk-opsawg-finding-geofeeds-03 is overloading a remarks: field with an attribute which then points to a URL. We can easily improve on this as there is no clash with other attribute names.

Describe the solution you'd like

IRRdv4 should allow setting, mirroring and outputting a geofeed: attribute.

Only 1 geofeed: attribute is allowed per inetnum object. The attribute is not allowed in other RPSL object classes

Additional context

https://tools.ietf.org/html/draft-ymbk-opsawg-finding-geofeeds-03

example:

inetnum: 192.0.2.0 - 192.0.2.255  # example
geofeed: https://example.com/geofeed.csv
source: XXX

[randyqx]

this would be very cool.

btw, erik whacked me that s/inetnum/inetnum & inet6num/

[mxsasha]

This seems reasonable. We can do basic URL validation for syntax too (for authoritative objects).

For mirroring this would actually already work: IRRd accepts unknown attributes from mirrors, like sponsoring-org in inet6num in RIPE.

[mxsasha]

@job To be clear: this is an optional attribute in both inetnum and inet6num, may only occur once, must be a valid HTTP/HTTPS URL? The draft doesn't specify beyond "URL", so it could be argued we should allow FTP too.

[job]

@job To be clear: this is an optional attribute in both inetnum and inet6num, may only occur once, must be a valid HTTP/HTTPS URL? The draft doesn't specify beyond "URL", so it could be argued we should allow FTP too.

Yes, this is an apt summary. HTTP and HTTPS scheme for now are probably fine