ICANN Requirements. Registry Operator's obligations hereunder are subject to modification at any time as a result of ICANN-mandated requirements and consensus policies through the processes set forth in the Registry Agreement. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
ICANN Requirements. PIR’S obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
ICANN Requirements. Verisign's obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements, including consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
ICANN Requirements. Registrar acknowledges that Registry Operator’s obligations under this Agreement are subject to modification at any time as a result of ICANN-mandated requirements, including without limitation any Consensus Policies or Temporary Policies (as such terms are defined in the Registry Agreement), or other processes set forth in the Registry Agreement. Notwithstanding anything to the contrary in this Agreement, the Registry Operator may update, revise, amend, or change any Registry Policy without advance notice to the Registrar if such update, revision, amendment, or change is mandated by ICANN. Nothing in this Agreement entitles Registrar to enforce the Registry Agreement or any other agreement between Registry Operator and ICANN.
ICANN Requirements. Afilias’ obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
ICANN Requirements. Vox Populi's obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
ICANN Requirements. Registry’s obligations described in clause 3 are subject to modification as a result of changes to ICANN-mandated requirements and consensus policies. Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN
ICANN Requirements. VNDS’ Obligations hereunder are subject to modification at any time as the result of ICANN-mandated requirements and
ICANN Requirements. All Parties must comply with the ICANN Registrar Accreditation Agreement and all associated ICANN Accredited Registrar Requirements, including, but not limited to, the Expired Registration Recovery Policy, the Data Retention Policy, and the Transfer Policy, located at xxxxx://xxx.xxxxx.xxx, which are hereby incorporated to this Agreement (collectively “ICANN Agreements”). All ICANN Agreements are hereby agreed to by all Parties, and shall govern this Agreement and any applicable provisions not covered in this Agreement.
i. Identifying Xxx.xxx as Registrar. Partner shall identify the proper sponsoring registrar, determined by Xxx.xxx, upon inquiry from the customer or registered domain name holder.
ICANN Requirements. DotAsia's obligations hereunder are subject to modification at any time as the result of changes to ICANN-mandated requirements and consensus policies. Notwithstanding anything in this Agreement to the contrary, Registrar shall comply with any such ICANN requirements in accordance with the timeline defined by ICANN.
