IRR object attributes

[DamianZaremba]

This list is only referenced on 2 inet entries (it may also be submitted privately e.g. in the Google peering portal):

inetnum:        45.157.0.0 - 45.157.3.255
remarks:        Geofeed: https://raw.githubusercontent.com/civo/geofeed/master/civo-geofeed.csv

inetnum:        74.220.16.0 - 74.220.23.255
remarks:        Geofeed: https://raw.githubusercontent.com/civo/geofeed/master/civo-geofeed.csv

Note: RFC 9632 prefers using the geofeed attribute (as supported by RIPE), rather than remarks: geofeed.

I propose the existing inetnum & inet6num entries are updated with the geofeed attribute:

inet6num: 2a10:c880::/29
inetnum: 185.136.232.0 - 185.136.235.255
inetnum: 185.243.80.0 - 185.243.83.255
inetnum: 212.2.240.0 - 212.2.247.255
inetnum: 212.2.248.0 - 212.2.255.255
inetnum: 45.157.0.0 - 45.157.0.255
inetnum: 45.157.0.0 - 45.157.3.255
inetnum: 45.157.1.0 - 45.157.1.255
inetnum: 45.157.2.0 - 45.157.2.255
inetnum: 74.220.16.0 - 74.220.23.255
inetnum: 74.220.24.0 - 74.220.31.255
inetnum: 91.211.152.0 - 91.211.155.255

Note: the current remarks: geofeed entries should be removed per RFC 9632 (Any particular inetnum: object SHOULD have, at most, one geofeed reference, whether a remarks: or a proper geofeed: attribute when it is implemented.).