This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] proposal: new attribute 'geofeed:'
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sasha Romijn
sasha at mxsasha.eu
Thu Jan 7 15:49:27 CET 2021
Hello all, On 5 Jan 2021, at 19:29, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > On 5 Jan 2021, at 14:30, denis walker <ripedenis at gmail.com> wrote: >> >> Hi Ed >> >> Can you do a quick count on INETNUM and INET6NUM objects and see how >> many currently have a "remarks: Geofeed" attribute and if any have >> more than one. > > I found 47 inetnums, 17 inet6nums and 2 aut-num objects with a "remarks: Geofeed" attribute. I didn't find any with more than one. For what it’s worth, in IRRd the geofeed attribute will be supported in the next release. It’s optional, permitted once, and must be a URL. We don’t validate against additional “remarks: Geofeed” attributes. Remarks are for humans from IRRd’s perspective, and nothing is done with them except reproducing them in queries. Sasha
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] Fwd: proposal: new attribute 'geofeed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]