12.07.2015 Views

Technical Integration Guide - Afnic

Technical Integration Guide - Afnic

Technical Integration Guide - Afnic

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TECHNICAL INTEGRATION GUIDE – February 25th, 2013 5<strong>Technical</strong> <strong>Integration</strong> <strong>Guide</strong>1. Preface1.1. About this documentThis integration guide contains all of the information required to implement theAFNIC domain management application interface.This interface offers two different ways accesses:• Web interface,• EPP (Extensible Provisioning Protocol): standard exchange protocolbetween a registry and its registrars.In regards to EPP, AFNIC has respected the standard described in the RFCs (see §3.8 RFCs.). This document only describes the specific points of AFNIC'simplementation of the protocol.1.2. Target audienceThis document is a technical document for developers that wish to have a detaileddescription of the interface and examples to help them with the integration. It doesnot go over the procedures again (See Procedure Manualwww.afnic.fr/en/ressources/reference/technical-guidebooks/proceduresmanual-for-registrars.html)nor The Naming Charter(www.afnic.fr/en/ressources/reference/charters/).Both documents are considered as already known.1.3. Typographical rulesThroughout the document we write:Between < > the xml markups describing the epp requestsIn a blue frame, examples of EPP requests.1.4. Revisions history24/11/2009 - V1.008/04/2010 - V1.108/06/2010 - V1.2 - Addition of missing EPP notifications31/08/2010 - V1.3 – Addition of EPP notification Portfolio deletionAssociation 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>- 5 -November 2009

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

Saved successfully!

Ooh no, something went wrong!