"should we have a geofeed attribute that accepts a URL, or just a remarks attribute with a value prefixed with Geofeed?"
"remarks: Geofeed https://example.com/geofeed.csv" vs "geofeed: https://example.com/geofeed.csv"
and we're currently trying to bridge two tensions. there will be a long transition from remarks: to geofeed:. the next draft will try and finesse that with words along the vein of Ideally, RPSL would be augmented to define a new RPSL geofeed: attribute in the inetnum: class. Until such time, this document defines the syntax of a Geofeed remarks: attribute which contains a URL of a geofeed file. The format MUST be as in this example, "remarks: Geofeed " followed by a URL which will vary. inetnum: 192.0.2.0/24 # example remarks: Geofeed https://example.com/geofeed.csv Any particular inetnum: object MAY have, at most, one geofeed reference. the other tension is that this all needs to work across all five regions and their non-homogenous syntaxes and services. randy