Common use of Extensible Provisioning Protocol Clause in Contracts

Extensible Provisioning Protocol. Registry Operator intends to implementshall maintain the Extensible Provisioning Protocol ("EPP") in conformance with the Proposed Standard and Informational RFCs 37305730, 37315731, 37325732, 37335734, 3734, 37355910, and 3915 (and in the event Registry Operator accepts thick registration data RFC 5733) published by the Internet Engineering Task Force ("IETF") and/or any successor standards, versions, modifications or additions thereto as Registry Operator deems reasonably necessary. Subject to the Migration to Extensible Provisioning Protocol Plan described in Section 6 below, Registry Operator will support EPP in conformance with the aforementioned standards. Implementation of EPP is subject toIf Registry Operator reasonably determining that (i) the standard can be implemented in a way that minimizes disruption to customers; and (ii) the standard provides a solution for which the potential advantages are reasonably justifiable when weighed against the costs thatrequires the use of functionality outside of EPP RFCs, Registry Operator and its registrar customers would incur in implementing the new standard.must document EPP extensions using Internet-Draft format following the guidelines described in RFC 3735. Registry Operator is not required to submit documented EPP extensions to the IETF but to consider the recommendations on standardization described in section 2.1 of 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. Subject to the Migration to Extensible Provisioning Protocol Plan described in Part 6 below, Registry Operator intends to implementshall maintain shall implementmaintain the Extensible Provisioning Protocol ("EPP") in conformance with the Proposed Standard and Informational RFCs 373057303730, 373157313731, 37325732, 373357343732, 3734, 373559103735,RFCs 5730, 5731, 5732, 5734, 5910 and 3915 (and in the event Registry Operator accepts thick registration data RFC 5733) published by the Internet Engineering Task Force ("IETF") and/or any successor standards, versions, modifications or additions thereto as Registry Operator deems reasonably necessary. Subject to the Migration to Extensible Provisioning Protocol Plan described in Section Part 6 below, when Registry Operator implements EPP it will support EPP in conformance with the aforementioned standards. Implementation of EPP is subject toIf to If Registry Operator reasonably determining that (i) the standard can be implemented in a way that minimizes disruption to customers; and (ii) the standard provides a solution for which the potential advantages are reasonably justifiable when weighed against the costs thatrequires the use of functionality outside of EPP RFCs, Registry Operator and its registrar customers would incur in implementing the new standard.must implementingmust document EPP extensions using Internet-Draft format following the guidelines described in RFC 3735. Registry Operator is not required to submit documented EPP extensions to the IETF but to consider the recommendations on standardization described in section 2.1 2.1. of RFC 3735▇▇▇ ▇▇▇▇. Registry Operator will provide and update the relevant documentation of all the new standard. EPP objects Objects and Extensions supported to ICANN prior to deployment.