Extensible Provisioning Protocol
≈ 6 min read
Names in other languages
- ČeštinaExtensible Provisioning Protocol
- DeutschExtensible Provisioning Protocol
- EnglishExtensible Provisioning Protocol
- FrançaisExtensible Provisioning Protocol
- PortuguêsExtensible Provisioning Protocol
- 한국어확장성 프로비저닝 프로토콜
- РусскийEPP
- УкраїнськаEPP
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
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, thereby also preventing domain hijacking. Before 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 fulfillment system. EPP 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, SOAP or HTTPS. However only HTTPS has seen some usage while the vast majority uses TCP.
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, thereby also preventing domain hijacking. Before 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 fulfillment system. EPP 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, SOAP or HTTPS. However only HTTPS has seen some usage while the vast majority uses TCP.
Adoption
The protocol has been adopted by a number of ccTLD domain name registries, such as: .ac, .ag, .ai, .as, .ar, .at, .au, .be, .br, .bz, .ca, .cat, .cc, .ch, .cl, .cn, .co, .cr, .cx, .cz, .dk, .dm, .ee, .es (over HTTPS), .eu, .fi, .fm, .fr, .gg, .gr (over HTTPS), .gs, .hn, .ht, .il, .im, .in, .io, .it (over HTTPS), .je, .ke, .ki, .ky, .kz, .la, .lc, .li, .lt, .lu, .lv, .md, .me, .mk, .mn, .ms, .mu, .mx, .na, .nf, .ng, .nl, .no, .nu, .nz, .pe, .pk, .pl (over HTTPS), .ps, .pt, .ru, .ro, .sc, .se, .sh, .si, .su, .tl, .tm .tv, .tw, .ua, .uk, .us, .vc, .ve and .za as well as ENUM registries such as those operating the +31, +41, +43, +44 and +48 country codes. ICANN has made it a condition in their base registry contract to offer an EPP service. Therefore, every gTLD has adopted the protocol. There are multiple open source implementations of EPP server software. The Council of Country Code Administrators (CoCCA) maintains an EPP server software used by around 59 ccTLDs and six gTLDs. Another open source software is FRED (maintained by CZ.NIC) which counts 11 ccTLDs as its users. An example command to create a domain could look like this: example.com 1 ns1.example.net ns2.example.net REG-1738 ADM-9374 OTH-2567 OTH-2567 y85NS%FJ4zeKuHXo uu28qbb2wo6o5bpk Note that the two host objects and three different contact objects had to be created beforehand to use them and the client had to be logged in already. The authInfo pw is a secret required in the transfer between registrars. The clTRID is a unique transaction ID for each command the client generates. A server response to the command above could look like this: Command completed successfully example.com 2023-03-12T12:00:00.0Z 2024-03-12T12:00:00.0Z uu28qbb2wo6o5bpk ma3fuaeuh7bzpgv9 The clTRID is the same as the client sent, while the svTRID is a unique transaction ID the server generates. The server returns a result code, message, and additional result data, such as the expiration date of the newly created domain.
EPP object status codes
There are two types of status codes: server and client. The difference is that all server status codes can only be set and removed by the registry, while the client status codes can also be set and removed by the registrar unless a server status code prohibits it. The server status codes are commonly used to handle domain abuse cases, mark the domain lifecycle stage, or offer extra security against unauthorized tampering, a service often referred to as Registry-Lock. The client status codes are commonly used also to handle abuse cases, non-payment, invalid contact data, or for a Registrar-Lock feature. The currently standardized server status codes are: The currently standardized client status codes are:
Related RFCs
, Generic Registry-Registrar Protocol Requirements , Extensible Provisioning Protocol (EPP) (obsoletes , which obsoleted ) , Extensible Provisioning Protocol (EPP) Transport over TCP (obsoletes )
EPP Objects RFCs
, Extensible Provisioning Protocol (EPP) Domain Name Mapping (obsoletes ) , Extensible Provisioning Protocol (EPP) Host Mapping (obsoletes ) , Extensible Provisioning Protocol (EPP) Contact Mapping (obsoletes ) , Extensible Provisioning Protocol (EPP) Organization Mapping
EPP Extension RFCs
, Guidelines for Extending EPP , Domain Registry Grace Period Mapping (e.g. Add Grace Period, Redemption Grace Period) , E.164 Number Mapping for the Extensible Provisioning Protocol (EPP) , ENUM Validation Information Mapping for the Extensible Provisioning Protocol , Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) (obsoletes , DNSSEC) , Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) , Allocation Token Extension for the Extensible Provisioning Protocol (EPP) , Organization Extension for the Extensible Provisioning Protocol (EPP) , Change Poll Extension for the Extensible Provisioning Protocol (EPP) , Registry Fee Extension for the Extensible Provisioning Protocol (EPP) , Login Security Extension for the Extensible Provisioning Protocol (EPP) , Extensible Provisioning Protocol (EPP) Unhandled Namespaces , Extensible Provisioning Protocol (EPP) Secure Authorization Information for Transfer , Registry Maintenance Notification for the Extensible Provisioning Protocol (EPP)
References
Text derived from https://en.wikipedia.org/w/index.php?oldid=1316327812 under CC BY-SA 4.0; modifications have been made.