12.07.2015 Views

Technical Integration Guide - Afnic

Technical Integration Guide - Afnic

Technical Integration Guide - Afnic

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 11A precaution is necessary during the development of clients that connect to ourEPP server. Indeed, we indicate several times in the following pages that someoperations will answer with a 1000 return code. This behavior is expected innormal working conditions of the domain registration chain.We differenciate between minor, major and blocking problems.A minor problem represents a problem on the chain that does not affect thegood reception of the requests. The chain is then asynchronous until theproblem is solved. Any operation affected by the problem will exceptionallyanswer with a 1001 return code during that time and notifications will be issued.For a minor problem, operations on « contact » objects, notification queuesconsultations and EPP operations like « querry » will not be affected.In case of a blocking problem, the server reacts in a more radical way and nooperations like « transform » on domain names can be taken into account. Anerror message « command failed » (code 2400) is then returned for any newcommand.3.2.3. Auth_info managementThe EPP protocol allows the use of an auth_info for domain names that areused for transfer operations (registrar change).The operations described hereafter allow the registrars to use our EPP server toretrieve the auth_info codes of their complete domain portfolio and modifythem if necessary.In addition, as the use of this auth_info code is mandatory for any registrarchange, a rule forces the registrar in charge of the domain name to give it to thedomain holder. Each registrar is free to choose the best way to issue thisinformation to the holder.3.2.4. Implementation choice of the notifications listWe have chosen to indicate during any server answer the number of messages inthe queue (unless there is none, in which case this information does not appear).RFC 5730 obliges to communicate this information only in the cases of answersto the commands and makes it optional for any other type of commands.In concrete terms, this implies that as soon as a message is notified to aregistrar, the registrar is informed by the presence of the element inany answer to commands sent to the server. It is strongly advised to read thesemessages as they arrive, they may contain operation follow-ups, technicalmodifications or transfer request you might find interesting to answer.3.2.5. DNSSEC supportThe EPP server manages the secDNS-1.1 extention as described in RFC 5910,excluding any other versions. Implementation specifications are as follows:Association Française pour le Nommage Internet en Coopération | www.afnic.fr | contact@afnic.frTwitter : @AFNIC | Facebook : afnic.fr<strong>Technical</strong> <strong>Integration</strong> <strong>Guide</strong>- 11 -November 2009

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!