RFC 3730 EPP March 2004 2.9.1.2. EPP Command. . . . . . . . . 22 2.9.2. Query Commands. . . . . . . . . . . . . . . . . 23 2.9.2.1. EPP Command . . . . . . . . . 24 2.9.2.2. EPP Command. . . . . . . . . . 26 2.9.2.3. EPP Command. . . . . . . . . . 27 2.9.2.4. EPP Query Command. . . . . 32 2.9.3. Object Transform Commands . . . . . . . . . . . 34 2.9.3.1. EPP Command. . . . . . . . . 34 2.9.3.2. EPP Command. . . . . . . . . 35 2.9.3.3. EPP Command . . . . . . . . . 37 2.9.3.4. EPP Command. . . . . . . . 38 2.9.3.5. EPP Command. . . . . . . . . 41 3. Result Codes. . . . . . . . . . . . . . . . . . . . . . . . . 42 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 48 4.1. Base Schema . . . . . . . . . . . . . . . . . . . . . . 49 4.2. Shared Structure Schema . . . . . . . . . . . . . . . . 58 5. Internationalization Considerations . . . . . . . . . . . . . 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 62 8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . 62 9. References. . . . . . . . . . . . . . . . . . . . . . . . . . 63 9.1. Normative References. . . . . . . . . . . . . . . . . . 63 9.2. Informative References. . . . . . . . . . . . . . . . . 64 Appendix A: Object Mapping Template . . . . . . . . . . . . . . . 65 Appendix B: Media Type Registration: application/epp+xml. . . . . 67 Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . 68 Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 69 1. Introduction This document describes specifications for the Extensible Provisioning Protocol (EPP) version 1.0, an XML text protocol that permits multiple service providers to perform object provisioning operations using a shared central object repository. EPP is specified using the Extensible Markup Language (XML) 1.0 as described in [XML] and XML Schema notation as described in [XMLS-1] and [XMLS- 2]. EPP meets and exceeds the requirements for a generic registry registrar protocol as described in [RFC 3375]. EPP content is identified by MIME media type application/epp+xml. Registration information for this media type is included in an appendix to this document. EPP is intended for use in diverse operating environments where transport and security requirements vary greatly. It is unlikely that a single transport or security specification will meet the needs of all anticipated operators, so EPP was designed for use in a Hollenbeck Standards Track