Technical Integration Guide - Afnic

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 633.5. Managing a contactA few basic rules:• Contacts all have a nic-handle that can be used to reference them indifferent domain name operations. The nic-handle is NEVER reassignedafter removal of contact.• Holder contacts must be created before being used in a domain nameoperation.• The qualification data is linked to the holder. The qualification process isdone on the contacts.Please note this general information on how postal addresses are managed, thatis to say:• On the contrary to what is indicated in RFC 5731, only one element of type can be indicated.• On the contrary to what is indicated in RFC 5731, only the type "loc" forpostal addresses is accepted.3.5.1. Contact CreationTo create a contact object used as holder, AFNIC requests information that arenot available in the standard EPP mapping for "contact" objects, it is necessaryto offer an extension.In addition, for a contact that requires a difference between first name and lastname, must contain the last name when the element of the given extension contains the first name of thecontact. In a concrete matter, for any « individual » holder contact, this elementis mandatory.Another necessary adaptation of the standard contact mapping (RFC 5733),because uncompatible with our procedures, is the element.Eventhough it is mandatory it is not taken into account by our server. Thisimplies that on the contrary to the EPP standard, the registrar has no choice inthe contact identifier during its creation request. AFNIC allocates the contactidentifiers according to its own algorithms. Of course, in case of a successfulcreation, the identifier is indicated in the server answer. On the other hand thisidentifier can be the one of an already existing contact if the registrar send thesame information contained in this contact. For this last case, we add anextension in the server answer.Another mandatory element that is not taken into account because not used isthe element. Indeed it is not possible to associate apassword to a contact object. But as we did for , we have decidedto keep the sent request to ensure a more simple compatibility with the existingclient codes. The element, optional in the contact mapping,Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 63 -November 2009