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] Progress on NWI-4
- Previous message (by thread): [db-wg] Progress on NWI-4
- Next message (by thread): [db-wg] NWI update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Wed May 24 20:44:51 CEST 2023
Hello Wessel, Many thanks for your feedback. I agree there are drawbacks to using a combined status value. If there is consensus on using a tuple (similar to what we already do for route(6)) then the DB team will implement this. I also plan to mention NWI-4 during the DB-WG session tomorrow, any feedback is appreciated. Regards Ed Shryane RIPE NCC > On 24 May 2023, at 08:52, Wessel Sandkuijl via db-wg <db-wg at ripe.net> wrote: > > Hi, > > I've reviewed Ed's impact analysis for NWI-4 and his proposal to add a new status value "ALLOCATED-ASSIGNED PA". This will not cover all use cases and it's use will most likely be limited as most people are used to the "ALLOCATED PA" versus "ASSIGNED PA" status values. > > I would highly prefer the earlier alternative proposal to use a tuple (using both prefix and status) so no new status value is introduced to the RIPE database. > > Can this be moved forward? > > Regards, > > Wessel Sandkuijl > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [db-wg] Progress on NWI-4
- Next message (by thread): [db-wg] NWI update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]