TLD Registry Operator Mediation Process Sample Clauses

TLD Registry Operator Mediation Process. (i) If a Complainant is a TLD registry operator and after completing the escalation process provided for in Section 7.2(a), the TLD registry operator may initiate mediation by delivering a written notice to the President of Contractor and the Secretary of ICANN. (ii) There shall be a single mediator who shall be selected by the agreement of the TLD registry operator and ICANN. ICANN shall propose a slate of at least five potential mediators, and the TLD registry operator shall select a mediator from the slate or request a new slate until a mutually agreed mediator is selected. The TLD registry operator may recommend potential mediators for inclusion on the slates selected by ICANN. ICANN shall not unreasonably decline to include mediators recommended by the TLD registry operator on proposed slates and the TLD registry operator shall not unreasonably withhold consent to the selection of a mediator on slates proposed by ICANN. (iii) The mediator shall be a licensed attorney with general knowledge of contract law and general knowledge of the DNS and ICANN. The mediator may not have any ongoing business relationship with ICANN, Contractor or the TLD registry operator. The mediator must confirm in writing that he or she is not, directly or indirectly, and will not become during the term of the mediation, an employee, partner, executive officer, director, consultant or advisor of ICANN, Contractor or the TLD registry operator. (iv) The mediator shall conduct the mediation in accordance with this Section 7.1(c), the laws of California and the rules and procedures of a well-respected international dispute resolution provider. (v) The arbitration will be conducted in the English language and will occur in Los Angeles County, California, unless another location is mutually agreed between ICANN, Contractor and the TLD registry operator.
Sample 1
AutoNDA by SimpleDocs

Related to TLD Registry Operator Mediation Process

  • CENTRAL GRIEVANCE PROCESS The following process pertains exclusively to grievances on central matters that have been referred to the central process. In accordance with the School Boards Collective Bargaining Act central matters may also be grieved locally, in which case local grievance processes will apply.

  • Grievance Mediation Nothing in this Article precludes the Parties from mutually agreeing to grievance mediation during any stage of the grievance procedure. The agreement shall be made in writing and stipulate the name of the person and the time line for grievance mediation to occur.

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting

  • Optional Mediation The Parties may mutually agree to non-binding mediation: (a) If the grievance is not resolved at Step 3, either Party may request that a Mediator be appointed to meet with the Parties, investigate and define the issues in dispute and facilitate a resolution. (b) The Mediator shall be appointed by mutual agreement between the Parties. (c) The purpose of the Mediator's involvement in the grievance process is to assist the Parties in reaching a resolution of the dispute, and anything said, proposed, generated or prepared for the purpose of trying to achieve a settlement is to be considered privileged and will not be used for any other purpose. (d) The expenses of the Mediator shall be equally borne by both Parties. (e) The grievance may be resolved by mutual agreement between the Parties.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Subcontracting for Medicaid Services Notwithstanding any permitted subcontracting of services to be performed under this Agreement, Party shall remain responsible for ensuring that this Agreement is fully performed according to its terms, that subcontractor remains in compliance with the terms hereof, and that subcontractor complies with all state and federal laws and regulations relating to the Medicaid program in Vermont. Subcontracts, and any service provider agreements entered into by Party in connection with the performance of this Agreement, must clearly specify in writing the responsibilities of the subcontractor or other service provider and Party must retain the authority to revoke its subcontract or service provider agreement or to impose other sanctions if the performance of the subcontractor or service provider is inadequate or if its performance deviates from any requirement of this Agreement. Party shall make available on request all contracts, subcontracts and service provider agreements between the Party, subcontractors and other service providers to the Agency of Human Services and any of its departments as well as to the Center for Medicare and Medicaid Services.

  • CENTRAL DISPUTE RESOLUTION PROCESS The following process pertains exclusively to disputes and grievances on central matters that have been referred to the central process. In accordance with the School Board Collective Bargaining Act, 2014 central matters may also be grieved locally, in which case local grievance processes will apply. In the event that central language is being grieved locally, the local parties shall provide the grievance to their respective central agents.

  • Mandatory Mediation Prior to and as a condition of either Party’s filing suit in state or federal court, the Parties shall engage in a mediated settlement conference in accordance with the North Carolina Superior Court Rules Implementing Statewide Mediation. The Parties shall mediate in good faith until settlement is reached or an impasse is declared by the mediator.

  • Good Offices, Conciliation or Mediation 1. The Parties may at any time agree to good offices, conciliation or mediation. They may begin at any time and be terminated by either Party at any time. 2. If the Parties agree, procedures for good offices, conciliation or mediation may continue while the dispute proceeds for resolution before an arbitral tribunal appointed under Article 15.5. 3. All proceedings under this Article shall be confidential and without prejudice to the rights of either Party in any further proceedings under the provisions of this Chapter.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!