Common use of Extensible Provisioning Protocol Clause in Contracts

Extensible Provisioning Protocol. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 3915, 5910, 5730, 5731, 5732, 5733 and 5734. If Registry Operator requires the use of proprietary EPP functionality, Registry Operator must document EPP extensions in Internet- Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.

Extensible Provisioning Protocol. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF) including all successor standards, modifications or additions thereto relating to the provisioning and management of domain names using the Extensible Provisioning Protocol (EPP) in conformance with RFCs 3915, 5910, 5730, 5731, 5732, 5733 and 5734. If Registry Operator requires the use of proprietary EPP functionality, Registry Operator must document EPP extensions in Internet- Internet-Draft format following the guidelines described in RFC 3735. Registry Operator will provide and update the relevant documentation of all the EPP Objects and Extensions supported to ICANN prior to deployment.