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] NWI reviews: NWI-6 Applicable data model not clear from contextless objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sasha Romijn
sasha at mxsasha.eu
Fri Oct 9 09:44:17 CEST 2020
Hello, On 8 Oct 2020, at 00:35, George Michaelson via db-wg <db-wg at ripe.net> wrote: > I am following this discussion. My primary concerns are the effects on > tools, of a new type:value assertion appearing in the RPSL. If this is > not a high barrier to deployment it has consequences beyond geofeed: > marker for us. I doubt this is a significant issue, because there are already several custom different RPSL attributes used by various RPSL databases. RIPE has sponsoring-org on inetnums, some have last-modified on their objects, and I think there are several other arbitrary attributes already. Tools should be capable of encountering attributes they don’t understand. I am in favour of this proposal. Encoding structured information into a free-form remarks field seems sloppy and error prone. I don’t see any downsides to adding the new optional attribute, and it’s fairly simple to implement. Sasha
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] NWI reviews: NWI-6 Applicable data model not clear from contextless objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]