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/[email protected]/
[db-wg] proposal: new attribute 'geofeed:'
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Jan 5 09:45:26 CET 2021
On 2021-01-04 21:41, Randy Bush via db-wg wrote: >> What happens when someone (or someone's automated system) pushes an >> object with a "remarks: Geofeed" again? > > from draft-ietf-opsawg-finding-geofeeds > > Any particular inetnum: object MAY have, at most, one geofeed > reference, whether a remarks: or a proper geofeed: attribute when > one is defined. > > now all we need is for the someone or someone's automated system to read > the spec :) Of course the question is "what should happen in the bad case", eg. what's the expected behaviour if there are 2 or more "remarks: geofeed" attributes? Should the DB reject such an update? Should the geofeed client pick one at random? Should it pick the first one? Or the last one? Or none? Robert (speaking for myself)
- Previous message (by thread): [db-wg] proposal: new attribute 'geofeed:'
- Next message (by thread): [db-wg] proposal: new attribute 'geofeed:'
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]