Common use of Migration to Extensible Provisioning Protocol Plan Clause in Contracts

Migration to Extensible Provisioning Protocol Plan. Support of RRP and EPP: Subject to this Section 6, Registry Operator will support the RRP as a "thin" registry. Registry Operator will continue to support RRP until all impacted registrars have migrated to EPP, but in no event later than 18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. Dual RRP and EPP Operations: 1. Registry Operator will provide an extended period for impacted registrars to transition from RRP to EPP on a timeframe acceptable to registrars, but in no event later than18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. 2. Registry Operator’s RRP implementation will be completely replaced by EPP on a date determined jointly by Registry Operator, ICANN, and the registrar community, which date shall not be later than 18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. 3. Registry Operator’s EPP implementation will not support the use of authinfo codes to verify transfers until all registrars have migrated to EPP.

Migration to Extensible Provisioning Protocol Plan. Support of RRP and EPP: Subject to this Section 6, Registry Operator will support the RRP as a "“thin" ” registry. Registry Operator will continue to support RRP until all impacted registrars have migrated to EPP, but in no event later than 18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. Dual RRP and EPP Operations: 1. Registry Operator will provide an extended period for impacted registrars to transition from RRP to EPP on a timeframe acceptable to registrars, but in no event later than18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. 2. Registry Operator’s RRP implementation will be completely replaced by EPP on a date determined jointly by Registry Operator, ICANN, and the registrar community, which date shall not be later than 18 months after the deployment date of EPP unless otherwise agreed upon in writing by Registry Operator. 3. Registry Operator’s EPP implementation will not support the use of authinfo codes to verify transfers until all registrars have migrated to EPP.