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] country codes in the RIPE Database (was: ORGANISATION country code)
- Previous message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
- Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis walker
ripedenis at gmail.com
Wed Mar 8 04:00:31 CET 2023
Hi Randy On Wed, 8 Mar 2023 at 03:11, Randy Bush <randy at psg.com> wrote: > > > I suggest that this is not just a localized decision of the db-wg, but > > has global implications. > > +1, and this aside from the idea having other fatal flaws, as discussed > here before. Can you please be a little more specific? What is the global implication of deleting undefined and misleading data from the RIPE Database that no other data in the RIPE or other registries depends on? Can you summarise the fatal flows that follow from deleting this data? Perhaps the circumstances are different now to when these 'fatal flows' were discussed before. cheers denis co-chair DB-WG > > randy
- Previous message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
- Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]