Extensible Provisioning Protocol (EPP) SDKs

VeriSign implements to the entire Extensible Provisioning Protocol (EPP) standard. VeriSign has developed EPP SDKs, guides, and tools to help you develop your client applications for integration with the .com .net Registry Shared Registry Service (SRS), the Name Store platform (.tv, .cc, .jobs, and Domain Name Suggestion Service), the .name Registry, and for use with non-VeriSign Registries that implement to the EPP 1.0 RFCs:

• RFC 4930: Extensible Provisioning Protocol (TXT)
• RFC 4931: Extensible Provisioning Protocol (EPP) Domain Name Mapping (TXT)
• RFC 4932: Extensible Provisioning Protocol (EPP) Host Mapping (TXT)
• RFC 4933: Extensible Provisioning Protocol (EPP) Contact Mapping (TXT)
• RFC 4934: Extensible Provisioning Protocol (EPP) Transport Over TCP (TXT)

EPP SDK Bundles

VeriSign offers SDKs in Java and C++, where the EPP mappings and extensions supported by each language vary. The Java EPP SDK is built from a general core (gen) that implements RFC 4930 and RFC 4934. Developers have the option of using each mapping or extension independently or in a bundle, combined for convenience.

• Name Store/SRS Bundle includes all mappings and extensions for integration with the Name Store platform (.tv, .cc, .jobs, and Domain Name Suggestion Service) and the .com and .net Registries.
• NAME Bundle includes all mappings and extensions for integration with the .name Registry.
• COM NET RTK C++ Add-on for use with EPP-RTK-CPP 0.9.2. Available online from Sourceforge: EPP Registry/Registrar Toolkit

EPP Mappings and Extensions

Mapping or Extension

Name Store/ SRS Bundle

NAME Bundle

COM NET RTK C++ Add-on

RFC 4930: Extensible Provisioning Protocol (TXT)
RFC 4931: Extensible Provisioning Protocol (EPP) Domain Name Mapping (TXT)
RFC 4932: Extensible Provisioning Protocol (EPP) Host Mapping (TXT)
RFC 4933: Extensible Provisioning Protocol (EPP) Contact Mapping (TXT)
RFC 4934: Extensible Provisioning Protocol (EPP) Transport Over TCP (TXT)
RFC 3915: Domain Registry Grace Period Mapping (RGP) (TXT)
RFC 4310: Domain Name System (DNS) Security Extensions Mapping
Extensible Provisioning Protocol (EPP) Transport Over HTTP
RGP Poll Mapping (PDF)
ConsoliDate Mapping for the Extensible Provisioning Protocol (Sync)
NameStore Extension (PDF)
IDN Language Tag (PDF)
Email Forwarding Mapping (PDF)
Defensive Registration Mapping (PDF)
NameWatch Mapping (PDF)
Personal Registration Extension (PDF)
Suggestion Mapping (PDF)
Whois Info Extension (PDF)
.jobs Contact Extension (PDF)
Low Balance Mapping (PDF)

Development Tools

The EPP Tool is a set of definitive, context-based interactive examples intended for developers to help them create and troubleshoot their code design. The tool behaves as though it is a registrar application in the Operations Testing & Evaluation (OT&E) environment. The EPP Tool supports both the Name Store platform (NameStore), the .name Registry (DotName), and the .com .net Registry (Core). The EPP Tool has been enhanced to incorporate features of the Protocol Tool (multiple environments, local installation, customized command values), but keeping the ease of use features of the EPP Tool. The EPP Tool is now available for download for launching on a desktop or installing on a local server. It requires Java 5 or higher and an official Java Keystore for connecting to OT&E or Production.

The Protocol Tool is a Java Client that can connect to multiple environments (OT&E, Production, EPP SDK Stub Server) with a set of customizable templates and menu layouts that support Name Store, SRS (.com .net), and .name. The Protocol Tool can connect to servers using multiple transports in parallel (EPP/SSL, EPP/TCP, EPP/HTTPS, EPP/HTTP). It requires Java 1.4 or higher and an official Java Keystore for connecting to OT&E or Production. With the release of the EPP Tool 5, that merges the best features of the EPP Tool and the Protocol Tool, the Protocol Tool is deprecated.