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] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key
- Previous message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key
- Next message (by thread): [db-wg] Agenda RIPE87 - Database Working Group
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Tue Nov 28 16:52:19 CET 2023
Dear colleagues, > On 13 Nov 2023, at 15:42, Edward Shryane via db-wg <db-wg at ripe.net> wrote: > > 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've uploaded a draft presentation for the NWI-4 discussion, please let me know any feedback: https://ripe87.ripe.net/wp-content/uploads/presentations/68-NWI-4-RIPE87.pdf I've summarised the requirement and two solutions proposed so far. I will be brief during the session, to leave most time for discussion. Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key
- Next message (by thread): [db-wg] Agenda RIPE87 - Database Working Group
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]