Technical Integration Guide - Afnic

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 353.4.5.1.Requesting a transfer (registrar change)First difference with the standard, is the element (elementitself of ) that cannot be used with the "roid" attributeto indicate that the given auth_info is linked to the holder or a contactassociated to the domain name itself. In our case the auth_info can only belinked to the domain name.During the transfer, the holder is cloned to the incoming registrar (unless a"contact" object with the exact same information already exists with thisregistrar). Important, this cloning happens once the transfer is approved bythe outgoing registrar.Eventhough it is planned by the RFC, the modification of the domain namevalidity period cannot be done. The same restrictions as for a creation applyto the element still considered as an optional element (inorder to keep things homogenous, we have kept exactly the same logic asthe creation operation). However, as the change is validated only at the endof the procedure and that it is at this moment that the new anniversary dateis indicated, the element is absent from the serveranswer.Last difference, an extension is necessary to allow the transfered domainname to be associated to technical and administrative contacts linked to theregistrar requesting the transfer as well as to specify if the potentialDNSSEC configuration (DS records) must be maintained in case of asuccessful transfer.Here are the specific elements found in the XML request sent by the client.Element nameNumber of occurrences 1 1 1 1-3The keepDS element is an XML boolean and must be set to a value among:0, 1, true, false. Its presence is mandatory.Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 35 -November 2009