Technical Integration Guide - Afnic

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 973.7. Return codes and error messsagesEventhough we strongly recommend to refer yourself to RFC 4930 that contains thecomplete list of all the return codes that can be sent by the EPP server following aclient command, we indicate further down the ones really implemented in ourserver. You will also find the list of error messages the server may return whennecessary.Correctly understanding the return codes is important. Their list will not evolve andthe codes are not ambiguous. As for the error messages it is not safe to script them.They can evolve with new administrative rules, some cases may be refined forinstance. Most of the time they will be associated to a part of the client request withthe problematic elements reproduced in the server answer. In addition, even if at thetime of writting this document, only the english language is available as a languagechoice, any new language will lead to the localisation of the messages. The returncodes are not impacted by this « problem ».Here is a message example returned by the server following an erroneouscommand:S:S:S: S: S: Parameter value policy errorS: S: S: dom-epp-defquruz-xucmexip.comS: S: not an AFNIC zoneS: S: S: S: S: FRNIC-11642-CLIENT-1254846489S: DEV-photon-11442-17-1254846489.34186S: S: S:3.7.1. Return codesReturn codes (element ) answer to a logic and are codedon 4 numbers. A problem with EPP is that the list is fixed and cannot beextended. Eventhough using a generic return code is possible and adding newcodes in the AFNIC extension, we have chosen to modify the sandard and add 3new codes to the existing list. The logic of the codes has been kept untouched.To recognize the new codes, you need to remember that the third number on theleft will alway be 9 ().You will also find in RFC 4930 the literal values associated to the codes that aresent in the element. If the server was to be localised, a correspondingtranslation would be given and the meaning of the heading would be kept.Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.frTechnical Integration Guide- 97 -November 2009