What is EPP?
Extensible Provisioning Protocol (EPP) is a new way of registering and maintaining domain names.
How EPP works
EPP is a client-server protocol where all communications use XML as defined by a series of schemas.
The normal conversation between a client and the server will be:
* Client connects to server over SSL.
* Server identifies itself and the commands and extensions that it supports.
* Client logs in by supplying login name and password.
* Client polls the server to see if there are any notifications waiting to be collected and then collects them (or it could do this later).
* Client issues commands to server, which then replies immediately with response status.
* Client then idles until it has more commands to send, polling periodically for any notifications.
Benefits of using EPP
The main benefits of using EPP are:
* Responses to commands are generally instant. A command can be issued to register a domain, get a response and then confirm with the customer that this has happened all in real time.
* Investment in EPP client programming should be transferrable when integrating with the EPP service of other registries.
* Choosing when to collect notifications that we send you and can be sure that you have received them.
What you need to use EPP
You will either need to write your own EPP client or buy one off the shelf. EPP is not intended for an individual to type out an EPP command in the same way that you can with the Automaton. Your software will then need to be able to connect directly to the EPP server using SSL.
To connect to our EPP server you need to register for this service. We also provide an EPP testbed to allow you to test your EPP implementation.
CO.ZA custom extensions of EPP
EPP is an international standard, and is specified in RFCs 5730 to 5734. However, it was developed largely by those working for gTLD registries, who have a very different data model from us. As a result the .co.za registry extended the standard definitions for domains, contacts and hosts to enable EPP to be used with its own data structure and to have access to the larger range of domain management commands used in the .co.za domain name system. Currently in development is a standard EPP implementation that more closely matches other gTLD registries. Standard EPP can be used with .co.za, however registrars will not have access to a number of functions that are specific to the .co.za registry.
All of the extensions created and implemented by the .co.za registry conform to the guidelines for extending EPP given in RFC 5730.
To summarise the differences with the .co.za registry:
- * Developed unique mapping for domains and contacts to reflect the stored data.
- * Added a new object; named account; that represents account structure.
- * Used the EPP transfer command to represent unique release operation. This was considerably simpler to understand than using the EPP command extension mechanism.
- * Objects use local timestamps rather tha UTC timestamps. The timestamp returned in the element is UTC as specified in RFC 5730.
Domain Life Cycle
The EPP Protocol uses various commands to address and perform registry related functions. Below are links to examples of the current available functions of the co.za registry system.
ZACR Available Integrations
The ZACR offers the following zones for EPP integration and Technical Accreditation. Please click on the zone name to proceed tothe Accreditation Criteria for that zone:
Last update: 25-08-2014 07:40:40
All issues and questions relating to the co.za EPP Registry Registrar System must be raised in the Contact/Support pages through the Registrar Portal. This is to ensure that our support department tracks and addresses all issues. Log in to the Registrar Portal and submit a support request online.
Click here for the latest status updates.