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] 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 ]
denis walker
ripedenis at gmail.com
Mon Apr 4 18:00:46 CEST 2022
On Mon, 4 Apr 2022 at 17:41, Nick Hilliard <nick at foobar.org> wrote: > > denis walker wrote on 04/04/2022 16:16: > > Many people have asked for a solution to this problem over recent years. > > The chairs have tried to get some discussion on the topic many times. > > Perhaps now we can have that discussion... > > Sounds good - so long as the discussion comes before the solution! :-) Maybe you can start by explaining why this change 'will' cause breakage in the wild and how significant that breakage will be. cheers denis co-chair DB-WG > > 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 ]