Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements:
(a) ICANN standards, policies, procedures, and practices for which Verisign has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and
(b) Operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Verisign in a non-arbitrary manner and applicable to all registrars ("Operational Requirements"), including affiliates of Verisign, and consistent with Verisign's Registry Agreement with ICANN, as applicable, upon Verisign's notification to Registrar of the establishment of those terms and conditions.
Compliance with Operational Requirements. Registrar agrees to comply with, and shall include in its registration agreement with each Registered Name Holder as appropriate, operational standards, policies, procedures, and practices for the Registry TLD established from time to time by VNDS in a non-arbitrary manner and applicable to all registrars (“Operational Requirements”), including affiliates of VNDS, and consistent with VNDS's Registry Agreement with ICANN, as applicable, upon VNDS's notification to Registrar of the establishment of those terms and conditions.
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements:
(a) ICANN standards, policies, procedures, and practices for which Vox Populi has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and (b) Operational standards, policies, procedures, and practices for the Vox Populi TLDs established from time to time by Vox Populi in a non-arbitrary manner and applicable to all registrars ("Operational Requirements"), including affiliates of Vox Populi, and consistent with Vox Populi's Registry Agreement with ICANN, as applicable, upon Vox Populi's notification to Registrar of the establishment of those terms and conditions.
Compliance with Operational Requirements. Registrar agrees to comply with, and shall include in its registration agreement with each Registered Name
Compliance with Operational Requirements. The Registrar shall comply with each of the following requirements, as may be in effect from time to time, and, further shall include in its registration agreement with each Registrant an obligation for such Registrant to comply with operational standards, policies, procedures, and practices for the SLD established from time to time by the Registry in a non-arbitrary manner and applicable to all Registrars (Operational Requirements), including affiliates of the Registry, as applicable, upon the Registry’s notification to the Registrar of the establishment of those terms and conditions upon 90 (ninety) days’ notice, except in circumstances where a regulatory body or law enforcement mandates registries to meet shorter deadlines, in which case the Registrar will work with the Registry to agree on an appropriate date to implement such changes.
Compliance with Operational Requirements. The Registrar shall comply with each of the following requirements, as may be in effect from time to time, and, further, shall include in its registration agreement with each Registrant an obligation for such Registrant to comply with each of the following requirements:
i. ICANN standards, policies, procedures, and practices for which the Registry has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and
ii. Operational standards, policies, procedures, and practices for the TLD established from time to time by the Registry in a non-arbitrary manner and applicable to all Registrars (“Operational Requirements”), including affiliates of the Registry, and consistent with the Registry’s Registry Agreement with ICANN, as applicable, upon the Registry’s notification to the Registrar of the establishment of those terms and conditions upon 90-day notice, except in circumstances where a regulatory body (e.g. ICANN) or law enforcement mandates registries to meet shorter deadlines, in which case the Registrar will work with the Registry to agree on an appropriate date to implement such changes.
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements:
Compliance with Operational Requirements. Registrar shall comply with each of the following requirements, and further shall include in its registration agreement with each Registered Name Holder, as applicable, an obligation for such Registered Name Holder to comply with each of the following requirements: ICANN standards, policies, procedures, and practices for which Verisign has monitoring responsibility in accordance with the Registry Agreement or other arrangement with ICANN; and Operational standards, policies, procedures, and practices for the Registry TLD established from time to time by Verisign in a non- arbitrary manner and applicable to all registrars ("Operational Requirements"), including affiliates of Verisign, and consistent with Verisign's Registry Agreement with ICANN, as applicable, upon Verisign's notification to Registrar of the establishment of those terms and conditions. Resolution of Technical Problems or Breach of Agreement. Registrar agrees to employ necessary employees, contractors, or agents with sufficient technical training and experience to respond to and fix all technical problems concerning the use of the Supported Protocol, the APIs and the systems of Verisign in conjunction with Registrar's systems. Registrar agrees that in the event of significant degradation of the System or other emergency, or upon Registrar's violation of Operational Requirements or breach of this Agreement, Verisign may, in its sole discretion, temporarily suspend or restrict access to the System. Such temporary suspensions or restrictions shall be applied in a nonarbitrary manner and shall apply fairly to any registrar similarly situated. Prohibited Domain Name Registrations. In addition to complying with ICANN standards, policies, procedures, and practices limiting domain names that may be registered, Registrar agrees to comply with applicable statutes and regulations limiting the domain names that may be registered. ICANN Requirements. Verisign'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.
Compliance with Operational Requirements. The Borrower must have complied with all the Bank's operational requirements to the satisfaction of the Bank.
Compliance with Operational Requirements. The Customer must have complied with all the Bank’s operational requirements to the satisfaction of the Bank.
