Common use of Compliance with Operational Requirements Clause in Contracts

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.

Appears in 9 contracts

Samples: Registry Agreement, Registry Agreement, Registry Registrar Agreement

AutoNDA by SimpleDocs

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-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.

Appears in 5 contracts

Samples: Registry Registrar Agreement, Registry Registrar Agreement, Registry Registrar Agreement

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 ’s Registry Agreement with ICANN, as applicable, upon VNDS's ’s notification to Registrar of the establishment of those terms and conditions.

Appears in 4 contracts

Samples: Registry Agreement (Verisign Inc/Ca), Registry Registrar Agreement (Go Daddy Group, Inc.), Registry Agreement (Verisign Inc/Ca)

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 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.

Appears in 2 contracts

Samples: Registry­registrar Agreement, Registry­registrar Agreement

AutoNDA by SimpleDocs

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 Cooperative Agreement with the United States Government or VNDS's Registry Agreement with ICANN, as applicable, upon VNDS's notification to Registrar of the establishment of those terms and conditions.

Appears in 1 contract

Samples: Registry Agreement

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