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] geofeed issue: can't add geofeed attribute to PI /48
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Hessler
phessler at theapt.org
Fri Feb 25 10:20:01 CET 2022
On 2022 Feb 25 (Fri) at 10:05:15 +0100 (+0100), Job Snijders via db-wg wrote: :On 2022-02-25 07:48, Peter Hessler via db-wg wrote: :> Alternatively, I propose we *drop* the geofeed: attribute and remove it :> from the database. : :Can you motivate the suggestion? : :The suggestion appears like a regression to me, we both see value in :“geofeed:” (provided we can actually use it), right? : The motivation is if the attribute is too restricted to be useful, then lets not encourage a broken implementation. (ps, the signature was chosen randomly and not changed ;) ). -- Shaw's Principle: Build a system that even a fool can use, and only a fool will want to use it.
- Previous message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
- Next message (by thread): [db-wg] geofeed issue: can't add geofeed attribute to PI /48
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]