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

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

Nick Hilliard nick at foobar.org
Sat Sep 30 13:55:27 CEST 2023

Edward Shryane via db-wg wrote on 29/09/2023 15:24:
> Following is the impact analysis for NWI-4 "Role of status: field in 
> multivalued status context" based on the use of the "inetnum:" and 
> "status:" tuple as a primary key.

Hmm. Ok.

Would it be useful to have a discussion about this at the upcoming 
meeting in Rome?

Nick

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