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 ]

Edward Shryane eshryane at ripe.net
Tue Feb 22 13:33:23 CET 2022

Hi Job, Colleagues,

> On 22 Feb 2022, at 10:01, Job Snijders <job at sobornost.net> wrote:
> 
> On Tue, Feb 22, 2022 at 09:54:24AM +0100, Edward Shryane via db-wg wrote:
>> Not doing any validation is not an option given the Legal review.
> 
> Why not?
> 
> Kind regards,
> 
> Job

To be clear, the Legal review looked at the "geofeed:" attribute alone, and did not consider "remarks:". There is no requirement to validate "remarks:".

Given this, and thanks to your feedback, I will drop my suggestion to validate "remarks:", and update the impact analysis for "geofeed:" only.

Regards
Ed Shryane
RIPE NCC

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 ]