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] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key

• Previous message (by thread): [db-wg] geolocation purpose
• Next message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Mon Nov 13 15:42:22 CET 2023

Hi Randy, Nick,

> On 30 Sep 2023, at 19:36, Randy Bush <randy at psg.com> wrote:
> 
>> Would it be useful to have a discussion about this at the upcoming
>> meeting in Rome?
> 
> iff it was a discussion, not walls of powerpoint
> 
> randy

I asked the DB-WG Co-chairs for time on the agenda at the DB-WG session to discuss the NWI-4 implementation, as I think there will be a larger audience than organising a separate discussion.

If you do want to meet beforehand, I'm available all that week also.

Regards
Ed Shryane
RIPE NCC

• Previous message (by thread): [db-wg] geolocation purpose
• Next message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]