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:

Appears in 5 contracts

Samples: Registry Agreement, Registry Agreement, itp.cdn.icann.org

AutoNDA by SimpleDocs

Migration to Extensible Provisioning Protocol Plan. Support of RRP and EPP: Subject to this Section Part 6, Registry Operator will support the RRP as a "thin" registry. Registry Operator shall deploy a production interface for EPP no later than July 1, 2005 unless otherwise agreed to in writing by Registry Operator and ICANN. When Registry Operator implements EPP, it 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:.

Appears in 2 contracts

Samples: Registry Agreement, Registry Agreement

AutoNDA by SimpleDocs

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:

Appears in 1 contract

Samples: Registry Agreement (Verisign Inc/Ca)

Time is Money Join Law Insider Premium to draft better contracts faster.