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] Progress on NWI-4, assigning a whole allocation
- Previous message (by thread): [db-wg] Progress on NWI-4, assigning a whole allocation
- Next message (by thread): [db-wg] Removing "rev-srv:" remarks from inetnum objects in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Edward Shryane
eshryane at ripe.net
Thu Jul 20 08:27:28 CEST 2023
Hi Cynthia, > On 20 Jul 2023, at 00:32, Cynthia Revström via db-wg <db-wg at ripe.net> wrote: > > I think I still support this proposal if it would be realistic to > implement without breaking too many things. > Like what would the impact on RDAP be for example? > I guess what I am saying is that I want to see a proper impact > analysis before I can decide if I support it or not. > > -Cynthia > I'm working on an impact analysis for the tuple proposal (including RDAP and other RIPE NCC services), and hope to have it ready in the coming weeks. Requiring a tuple to distinguish between multiple inetnums with the same prefix but different status (ALLOCATED PA or ASSIGNED PA) *will* be a breaking change but will satisfy the NWI-2 problem statement: "Some believe that the main underlying issue here is that it is currently not possible to create an assignment that is the same size as an allocation in the RIPE Database" https://www.ripe.net/ripe/mail/archives/db-wg/2016-May/005242.html Regards Ed Shryane RIPE NCC
- Previous message (by thread): [db-wg] Progress on NWI-4, assigning a whole allocation
- Next message (by thread): [db-wg] Removing "rev-srv:" remarks from inetnum objects in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]