Adding nic handles to contact objects without one

Hello,

 "Eamonn" <Eamonn at ripe.net> writes:
 * 
 * Hi Joao,
 * 
 * I'd like to know what exactly are the advantages (and to whom) to
 * adding a nic-hdl to person objects which don't already have one ?
 * 

I think there are benefits for everyone. The database becomes more coherent, 
ambiguity between different people with the same name disappears (especially 
if as you say below, references by name are then substituted by references to 
NIC Handles).

 * In some cases a person (without a nic-hdl) has their name referenced
 * in other Db objects. This was before nic-hdls were mandatory. So if
 * you add a nic-hdl to such a person's person object what can be done to
 * those objects which reference his/her name ?

That, I think, is a discussion for these lists. Either the user does it or the 
RIPE NCC can do it if users wish to. Of course this can only be done for 
references by name corresponding to names that are unique in the database, 
otherwise we wouldn't know who to assign the object to and we shouldn't.

 * 
 * There is no way of distinguishing the names referenced in the contact
 * attributes of these objects since a similar name can refer to
 * different people.
 * 

Indeed.

 * Then you have the problem where these people created a new person
 * object for themselves when nic-hdls became mandatory and left their
 * old person object for dead. How will you overcome these old person
 * objects ?
 * 

Yes, that happened in the past. The software can cope with that now so we 
shouldn't see cases like those any more.
The cleanup I think is best done within the consistency project which is right 
now regaining speed (more on that soon...)

Regards,
Joao Damas
RIPE NCC