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 ]
Nick Hilliard
nick at foobar.org
Mon Apr 4 14:55:44 CEST 2022
denis walker via db-wg wrote on 04/04/2022 13:38: > If there are no objections to this, the co-chairs now ask the RIPE NCC > to produce an impact/implementation report to add this new status > value and include the business rules to restrict it's use. Denis, This came up in an email of yours from February: https://www.ripe.net/ripe/mail/archives/db-wg//2022-February/007295.html > The chairs make no recommendation on this item. But if there is no > discussion we will simply mark NWI-4 as cancelled. and here: https://www.ripe.net/ripe/mail/archives/db-wg//2022-February/007314.html > Is this a problem that you think needs to be solved? If 'yes' then we > need to hear your thoughts. If 'no' then the chairs will cancel NWI-4 > and move on... Was there any discussion about why this changed from: "not going to implement" to "going to implement"? Separately, has there been any discussion about this new status value, "ALLOCATED-ASSIGNED PA"? This is a significant change to the semantics of this key, and it's one which will cause breakage in the wild. 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 ]