The Extensible Provisioning Protocol (EPP) is a flexible protocol designed for allocating objects within registries over the Internet. The motivation for the creation of EPP was to create a robust and flexible protocol that could provide communication between domain name registries and domain name registrars. These transactions are required whenever a domain name is registered or renewed. Prior to its introduction, registries had no uniform approach, and many different proprietary interfaces existed. While its use for domain names was the initial driver, the protocol is designed to be usable for any kind of ordering and fulfilment system. The EPP protocol is based on XML - a structured, text-based format. The underlying network transport is not fixed, although the only currently specified method is over TCP. The protocol has been designed with the flexibility to allow it to use other transports such as BEEP, SMTP, or SOAP. The protocol is the result of the IETF Provisioning Registry (provreg) working group, and was finalised in 2004. The protocol has been adopted by a number of domain name registries, such as .info, .org, .aero, .mobi, .ag, .au, .br, .bz, .eu, .gi, .hn, .in, .mn, .pl, .sc and .vc, as well as ENUM registries such as those operating the +43 and +41 country codes. EPP "codes" or "keys" are also required in the transfer of generic top-level domain names between registrars (.com, .net, .org, .biz, .info). .com and .net domain names only began requiring the EPP key from fourth quarter 2006.
Related RFCs
- RFC 3375 - Generic Registry-Registrar Protocol Requirements
- RFC 3730 - Extensible Provisioning Protocol (EPP)
- RFC 3731 - Using EPP for Domain Names
- RFC 3732 - Using EPP for Hosts
- RFC 3733 - Using EPP for storing contacts
- RFC 3734 - Using EPP over TCP obsoleted
- RFC 3735 - Guidelines on extending EPP
Starting from May of 2007 the Epp protocol was revised, and from now on the RFCs are the following
