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] 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 ]

Job Snijders job at sobornost.net
Fri Feb 25 10:05:15 CET 2022

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?

Kind regards,

Job

• 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 ]