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]/
[ncc-services-wg] Re: [db-wg] Clean up of unreferenced person/role objects
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Clean up of unreferenced person/role objects
- Next message (by thread): [ncc-services-wg] Clean up of unreferenced person/role objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo.vegoda at icann.org
Thu Apr 19 19:11:25 CEST 2007
On Apr 19, 2007, at 5:22 PM, Shane Kerr wrote: [...] > (*) For example, a worse problem would be referencing the wrong > person/role object. This can happen like so: > > - Person object X created > - Months pass... > - Person object X deleted by this process > - Person object Y created with same "nic-hdl:" as object X > - User who created person object X decides to use it, but actually > refers to object Y (since it has the same "nic-hdl:") > > The user who created person object X assumes it is still fine, because > the usual notification was not received, and in any case it was > probably protected by "mnt-by:". > > Of course, this is an unlikely corner case. :) This case could also be avoided by making it impossible to re-use a nic-hdl. I believe that is already the case for organisation objects. Putting it in place for person and role objects would probably be a good thing. But I doubt it's an urgent requirement and I wouldn't want to delay this cleanup. Regards, -- Leo Vegoda IANA Numbers Liaison
- Previous message (by thread): [ncc-services-wg] Re: [db-wg] Clean up of unreferenced person/role objects
- Next message (by thread): [ncc-services-wg] Clean up of unreferenced person/role objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]