[db-wg] Proposal to accept same INET(6)NUM objects with different status
- Previous message (by thread): [db-wg] Proposal to accept same INET(6)NUM objects with different status
- Next message (by thread): [db-wg] Proposal to cleanup some hack's with status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Sun Apr 19 16:43:23 CEST 2015
Hi, On Thu, Apr 16, 2015 at 11:09:39PM +0200, Piotr Strzyzewski wrote: > 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. I can see the issue you describe, but I do not like the proposed solution - the network+mask in the inet(6)num object is the unique key, and should stay the unique key (= no combination with status: for a combined key). Personally, I'd just put two half-sized ASSIGNED PA inet(6)nums into the DB, with the same extra info... Gert Doering -- speaking as a user of the DB -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 811 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20150419/5955dd89/attachment.sig>
- Previous message (by thread): [db-wg] Proposal to accept same INET(6)NUM objects with different status
- Next message (by thread): [db-wg] Proposal to cleanup some hack's with status values
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]