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] Proposal to accept same INET(6)NUM objects with different status
- Previous message (by thread): [db-wg] [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment
- Next message (by thread): [db-wg] Proposal to accept same INET(6)NUM objects with different status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Apr 16 23:09:39 CEST 2015
Dear DB-WG Members Proposal: I propose to allow two INET(6)NUM objects with the same value of inet(6)num attribute and different status to be put into the DB. Problem description: According to current DB/business rules it is impossible to put into the database two INET(6)NUM objects with the same value of inet(6)num attribute and different status. This situation is quite problematic when an LIR which receive /22 from the last /8 cannot put this exact /22 with "ASSIGNED PA" status into the DB (this will result with en error). The current practice is way from being ideal - one have to divide this /22 to at least two smaller assignments. This problem is more relevant but not limited to the new LIRs which receive their initial and only allocation and assign it as one single block to themselves. Some possible problems to be addressed: 1. Should this be limited to certain top/bottom status pairs (like ALLOCATED PA->ASSIGNED PA). IMHO yes. 2. Shoud DB return both INET(6)NUM object matching the query? I'm open to both options (special query flag could be introduced if necessary). 3. How to delete/modify correct INET(6)NUM object. While deleting, exact copy must match. While modifying, status line select the one to be modified. Looking for your comments. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [db-wg] [ncc-announce] [news] Phase 1 of Deprecation of "changed:" Attribute Deployed to RIPE Database Release Candidate Environment
- Next message (by thread): [db-wg] Proposal to accept same INET(6)NUM objects with different status
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]