Technical Integration Guide - Afnic

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 101• « other operation in progress »• « glue is needed for this name server »• « holder identification problem prevents it's usage »• « holder identification problem prevents operation »• « legal issue prevents operation »• « pending request prevents operation »• « mandatory admin or technical contact is missing »• « similar domain name already exists »• « domain name MUST have, at least, TWO different name servers »• « domain name MUST have either 0 or, at least, TWO different nameservers »The second list refers to errors that can be returned during contact operations.• « country code is illegal »• « country code is undefined »• « street is illegal »• « street is undefined »• « post code is illegal »• « post code is undefined »• « city is illegal »• « city is undefined »• « city cedex is illegal for this country »• « city cedex is illegal »• « birth place geographical check failure »• « non-profit announcePage mandatory if publishedDate present »• « non-profit publishedDate mandatory if announcePage present »• « can't update contact disclosure restriction for legal entitie holders »• « can't update contact disclosure restriction for tech class »• « can't update contact country code for tech class »• « can't update phone number »• « 'legalStatus' value is illegal »• « phone number is illegal »• « fax number is illegal »• « bogus organization contact without extended data. Should not exist.Must not be used in operations »• « waldec ID prohibited if 'legalStatus' is set to 'company' »• « non-profit publishedDate prohibited if 'legalStatus' is set to'company' »• « 'siren' or 'trademark' element missing while it's mandatory »• « 'trademark' element value seems to be syntaxically incorrect accordingAFNIC rules »• « role objects can't be updated through EPP interface »• « 'siren' element value seems to be syntaxically incorrect accordingAFNIC rules »• « contact handle is illegal »• « registrant doesn't exist »3.8. RFCsHere is a reminder of the RFCs to imperatively read on which our EPPimplemenntation was done:Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 101 -November 2009