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/

The db-wg Archives

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

Starting: Fri Sep 1 08:00:57 CEST 2023
Ending: Sat Sep 30 19:36:08 CEST 2023
Messages: 16

• [db-wg] About IP resources   Cunchang Huang
• [db-wg] Whois release 1.108   Miguel Herran
• [db-wg] denying access to RIPE DB for proven spammers   Sergey Myasoedov
• [db-wg] denying access to RIPE DB for proven spammers   Ben Cartwright-Cox
• [db-wg] denying access to RIPE DB for proven spammers   Sergey Myasoedov
• [db-wg] denying access to RIPE DB for proven spammers   denis walker
• [db-wg] Fwd: Geofeed purpose   Theodoros Fyllaridis
• [db-wg] Whois release 1.108   Edward Shryane
• [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key   Edward Shryane
• [db-wg] RIPE Database Quarterly Planning Q4 2023   Edward Shryane
• [db-wg] Question about the status of the implementation of NWI-4   Erik Bais
• [db-wg] Question about the status of the implementation of NWI-4   Edward Shryane
• [db-wg] Question about the status of the implementation of NWI-4   Erik Bais
• [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key   Cynthia Revström
• [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key   Nick Hilliard
• [db-wg] Impact Analysis for NWI-4: using the inetnum and status tuple as a primary key   Randy Bush

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

[ List archive ] [ ]