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] Decision on NWI-4 INETNUM status values
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Mon Apr 4 18:32:32 CEST 2022
denis walker wrote on 04/04/2022 17:00: > Maybe you can start by explaining why this change 'will' cause > breakage in the wild and how significant that breakage will be. Denis, you were clear in your email earlier today that you believe that your proposed solution for NWI-4 will cause problems. This is a good thing to put on the table because it allows for the possibility of discussing what level of breakage you think may be involved with your proposal. The more important issue is that as chair, you previously said that if there were no interest expressed in progressing NWI-4, that it would be dropped. But this turned into a request to the RIPE NCC to produce an impact / implementation report on a specific proposed solution, without any community discussion or any indication of consensus. If you want to propose some technical solutions to deal with this issue, I'm sure everyone would welcome this - although it would be normal to recuse yourself from the consensus call in this sort of situation. Nick
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]