Validation Mechanism To be eligible for articulation, the student must show evidence of their CompTIA A+ certification and it must have been issued within three (3) years prior to their enrollment in the program.
Rights Protection Mechanisms and Abuse Mitigation ‐ Registry Operator commits to implementing and performing the following protections for the TLD:
i. In order to help registrars and registrants identify inaccurate data in the Whois database, Registry Operator will audit Whois data for accuracy on a statistically significant basis (this commitment will be considered satisfied by virtue of and for so long as ICANN conducts such audits).
ii. Work with registrars and registrants to remediate inaccurate Whois data to help ensure a more accurate Whois database. Registry Operator reserves the right to cancel a domain name registration on the basis of inaccurate data, if necessary.
iii. Establish and maintain a Domains Protected Marks List (DPML), a trademark protection service that allows rights holders to reserve registration of exact match trademark terms and terms that contain their trademarks across all gTLDs administered by Registry Operator under certain terms and conditions.
iv. At no cost to trademark holders, establish and maintain a Claims Plus service, which is a notice protection mechanism that begins at the end of ICANN’s mandated Trademark Claims period.
v. Bind registrants to terms of use that define and prohibit illegal or abusive activity.
vi. Limit the use of proxy and privacy registration services in cases of malfeasance.
vii. Consistent with the terms of this Registry Agreement, reserve the right to exclude from distribution any registrars with a history of non-‐compliance with the terms of the Registrar Accreditation Agreement.
viii. Registry Operator will be properly resourced to perform these protections.
Rights Protection Mechanisms Registry Operator shall implement and adhere to the rights protection mechanisms (“RPMs”) specified in this Specification. In addition to such RPMs, Registry Operator may develop and implement additional RPMs that discourage or prevent registration of domain names that violate or abuse another party’s legal rights. Registry Operator will include all RPMs required by this Specification 7 and any additional RPMs developed and implemented by Registry Operator in the registry-‐registrar agreement entered into by ICANN-‐accredited registrars authorized to register names in the TLD. Registry Operator shall implement in accordance with requirements set forth therein each of the mandatory RPMs set forth in the Trademark Clearinghouse as of the date hereof, as posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/tmch-‐requirements (the “Trademark Clearinghouse Requirements”), which may be revised in immaterial respects by ICANN from time to time. Registry Operator shall not mandate that any owner of applicable intellectual property rights use any other trademark information aggregation, notification, or validation service in addition to or instead of the ICANN-‐
Mitigation Measures Company shall take commercially reasonable measures (except measures causing it to incur out-of-pocket expenses which BNYM does not agree in advance to reimburse) to mitigate losses or potential losses to BNYM, including taking verification, validation and reconciliation measures that are commercially reasonable or standard practice in the Company’s business.
Dispute Resolution Mechanisms Registry Operator will comply with the following dispute resolution mechanisms as they may be revised from time to time: the Trademark Post-Delegation Dispute Resolution Procedure (PDDRP) and the Registration Restriction Dispute Resolution Procedure (RRDRP) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/pddrp and xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp, respectively). Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PDDRP or RRDRP panel and to be bound by any such determination; and the Uniform Rapid Suspension system (“URS”) adopted by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/urs), including the implementation of determinations issued by URS examiners. CONTINUED OPERATIONS INSTRUMENT The Continued Operations Instrument shall (a) provide for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6th) anniversary of the Effective Date, and (b) be in the form of either (i) an irrevocable standby letter of credit, or (ii) an irrevocable cash escrow deposit, each meeting the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof (which is hereby incorporated by reference into this Specification 8). Registry Operator shall use its best efforts to take all actions necessary or advisable to maintain in effect the Continued Operations Instrument for a period of six (6) years from the Effective Date, and to maintain ICANN as a third party beneficiary thereof. If Registry Operator elects to obtain an irrevocable standby letter of credit but the term required above is unobtainable, Registry Operator may obtain a letter of credit with a one-year term and an “evergreen provision,” providing for annual extensions, without amendment, for an indefinite number of additional periods until the issuing bank informs ICANN of its final expiration or until ICANN releases the letter of credit as evidenced in writing, if the letter of credit otherwise meets the requirements set forth in item 50(b) of Attachment to Module 2 – Evaluation Questions and Criteria – of the gTLD Applicant Guidebook, as published and supplemented by ICANN prior to the date hereof; provided, however, that if the issuing bank informs ICANN of the expiration of such letter of credit prior to the sixth (6th) anniversary of the Effective Date, such letter of credit must provide that ICANN is entitled to draw the funds secured by the letter of credit prior to such expiration. The letter of credit must require the issuing bank to give ICANN at least thirty (30) calendar days’ notice of any such expiration or non-renewal. If the letter of credit expires or is terminated at any time prior to the sixth (6th) anniversary of the Effective Date, Registry Operator will be required to obtain a replacement Continued Operations Instrument. ICANN may draw the funds under the original letter of credit, if the replacement Continued Operations Instrument is not in place prior to the expiration of the original letter of credit. Registry Operator shall provide to ICANN copies of all final documents relating to the Continued Operations Instrument and shall keep ICANN reasonably informed of material developments relating to the Continued Operations Instrument. Registry Operator shall not agree to, or permit, any amendment of, or waiver under, the Continued Operations Instrument or other documentation relating thereto without the prior written consent of ICANN (such consent not to be unreasonably withheld). If, notwithstanding the use of best efforts by Registry Operator to satisfy its obligations under the preceding paragraph, the Continued Operations Instrument expires or is terminated by another party thereto, in whole or in part, for any reason, prior to the sixth anniversary of the Effective Date, Registry Operator shall promptly (i) notify ICANN of such expiration or termination and the reasons therefor and (ii) arrange for an alternative instrument that provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period of one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date (an “Alternative Instrument”). Any such Alternative Instrument shall be on terms no less favorable to ICANN than the Continued Operations Instrument and shall otherwise be in form and substance reasonably acceptable to ICANN. Notwithstanding anything to the contrary contained in this Specification 8, at any time, Registry Operator may replace the Continued Operations Instrument with an Alternative Instrument that (i) provides for sufficient financial resources to ensure the continued operation of the critical registry functions related to the TLD set forth in Section 6 of Specification 10 to this Agreement for a period of three (3) years following any termination of this Agreement on or prior to the fifth anniversary of the Effective Date or for a period one (1) year following any termination of this Agreement after the fifth anniversary of the Effective Date but prior to or on the sixth (6) anniversary of the Effective Date, and (ii) contains terms no less favorable to ICANN than the Continued Operations Instrument and is otherwise in form and substance reasonably acceptable to ICANN. In the event Registry Operator replaces the Continued Operations Instrument either pursuant to paragraph 2 or this paragraph 3, the terms of this Specification 8 shall no longer apply with respect to the original Continuing Operations Instrument, but shall thereafter apply with respect to such Alternative Instrument(s), and such instrument shall thereafter be considered the Continued Operations Instrument for purposes of this Agreement. REGISTRY OPERATOR CODE OF CONDUCT In connection with the operation of the registry for the TLD, Registry Operator will not, and will not allow any parent, subsidiary, Affiliate, subcontractor or other related entity, to the extent such party is engaged in the provision of Registry Services with respect to the TLD (each, a “Registry Related Party”), to: directly or indirectly show any preference or provide any special consideration to any registrar with respect to operational access to registry systems and related registry services, unless comparable opportunities to qualify for such preferences or considerations are made available to all registrars on substantially similar terms and subject to substantially similar conditions; register domain names in its own right, except for names registered through an ICANN accredited registrar; provided, however, that Registry Operator may (a) reserve names from registration pursuant to Section 2.6 of the Agreement and (b) may withhold from registration or allocate to Registry Operator up to one hundred (100) names pursuant to Section 3.2 of Specification 5; register names in the TLD or sub-domains of the TLD based upon proprietary access to information about searches or resolution requests by consumers for domain names not yet registered (commonly known as, “front-running”); or allow any Affiliated registrar to disclose Personal Data about registrants to Registry Operator or any Registry Related Party, except as reasonably necessary for the management and operations of the TLD, unless all unrelated third parties (including other registry operators) are given equivalent access to such user data on substantially similar terms and subject to substantially similar conditions. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will, or will cause such Registry Related Party to, ensure that such services are offered through a legal entity separate from Registry Operator, and maintain separate books of accounts with respect to its registrar or registrar-reseller operations. If Registry Operator or a Registry Related Party also operates as a provider of registrar or registrar-reseller services, Registry Operator will conduct internal reviews at least once per calendar year to ensure compliance with this Code of Conduct. Within twenty (20) calendar days following the end of each calendar year, Registry Operator will provide the results of the internal review, along with a certification executed by an executive officer of Registry Operator certifying as to Registry Operator’s compliance with this Code of Conduct, via email to an address to be provided by ICANN. (ICANN may specify in the future the form and contents of such reports or that the reports be delivered by other reasonable means.) Registry Operator agrees that ICANN may publicly post such results and certification; provided, however, ICANN shall not disclose Confidential Information contained in such results except in accordance with Section 7.15 of the Agreement. Nothing set forth herein shall: (i) limit ICANN from conducting investigations of claims of Registry Operator’s non-compliance with this Code of Conduct; or (ii) provide grounds for Registry Operator to refuse to cooperate with ICANN investigations of claims of Registry Operator’s non-compliance with this Code of Conduct. Nothing set forth herein shall limit the ability of Registry Operator or any Registry Related Party, to enter into arms-length transactions in the ordinary course of business with a registrar or reseller with respect to products and services unrelated in all respects to the TLD. Registry Operator may request an exemption to this Code of Conduct, and such exemption may be granted by ICANN in ICANN’s reasonable discretion, if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (i) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator for the exclusive use of Registry Operator or its Affiliates, (ii) Registry Operator does not sell, distribute or transfer control or use of any registrations in the TLD to any third party that is not an Affiliate of Registry Operator, and (iii) application of this Code of Conduct to the TLD is not necessary to protect the public interest. REGISTRY PERFORMANCE SPECIFICATIONS DNS. Refers to the Domain Name System as specified in RFCs 1034, 1035, and related RFCs. DNSSEC proper resolution. There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.
Prevention of Avoidance The Parties shall implement as necessary requirements to prevent Financial Institutions from adopting practices intended to circumvent the reporting required under this Agreement.
PREVENTION OF BRIBERY 26.1 The Supplier represents and warrants that neither it, nor to the best of its knowledge any Supplier's Personnel, have at any time prior to the Commencement Date:
(a) committed a Prohibited Act or been formally notified that it is subject to an investigation or prosecution which relates to an alleged Prohibited Act; and/or
(b) been listed by any government department or agency as being debarred, suspended, proposed for suspension or debarment, or otherwise ineligible for participation in government procurement programmes or contracts on the grounds of a Prohibited Act.
26.2 The Supplier shall not during the term of this agreement:
(a) commit a Prohibited Act; and/or
(b) do or suffer anything to be done which would cause the Authority or any of the Authority's employees, consultants, contractors, sub-contractors or agents to contravene any of the Bribery Act or otherwise incur any liability in relation to the Bribery Act.
26.3 The Supplier shall during the term of this agreement:
(a) establish, maintain and enforce, and require that its Sub- contractors establish, maintain and enforce, policies and procedures which are adequate to ensure compliance with the Bribery Act and prevent the occurrence of a Prohibited Act; and
(b) keep appropriate records of its compliance with its obligations under clause 26.3(a) and make such records available to the Authority on request.
26.4 The Supplier shall immediately notify the Authority in writing if it becomes aware of any breach of clause 26.1 and/or clause 26.2, or has reason to believe that it has or any of the Supplier's Personnel have:
(a) been subject to an investigation or prosecution which relates to an alleged Prohibited Act;
(b) been listed by any government department or agency as being debarred, suspended, proposed for suspension or debarment, or otherwise ineligible for participation in government procurement programmes or contracts on the grounds of a Prohibited Act; and/or
(c) received a request or demand for any undue financial or other advantage of any kind in connection with the performance of this agreement or otherwise suspects that any person or Party directly or indirectly connected with this agreement has committed or attempted to commit a Prohibited Act.
26.5 If the Supplier makes a notification to the Authority pursuant to clause 26.4, the Supplier shall respond promptly to the Authority's enquiries, co-operate with any investigation, and allow the Authority to audit any books, records and/or any other relevant documentation in accordance with clause 22.
26.6 If the Supplier is in Default under clause 26.1 and/or clause 26.2, the Authority may by notice:
(a) require the Supplier to remove from performance of this agreement any Supplier's Personnel whose acts or omissions have caused the Default; or
(b) immediately terminate this agreement.
26.7 Any notice served by the Authority under clause 26.6 shall specify the nature of the Prohibited Act, the identity of the Party who the Authority believes has committed the Prohibited Act and the action that the Authority has elected to take (including, where relevant, the date on which this agreement shall terminate).
Mechanisms The Parties agree that their political dialogue shall be conducted:
(a) where appropriate and agreed by both Parties, at Head of State and Government level;
(b) at ministerial level, in particular in the framework of the Ministerial Meeting of the San Xxxx Dialogue;
(c) at senior official level;
(d) at working level; and shall make maximum use of diplomatic channels.
Erosion Prevention and Control Purchaser’s Operations shall be conducted reasonably to minimize soil erosion. Equipment shall not be operated when ground conditions are such that excessive damage will result. Purchaser shall adjust the kinds and intensity of erosion control work done to ground and weather condi- tions and the need for controlling runoff. Erosion control work shall be kept current immediately preceding ex- pected seasonal periods of precipitation or runoff.
Fraud Prevention A. To screen its employees and contractors to determine if they have been excluded from Medicare, Medicaid or any federal or state health care program. The Contractor agrees to search monthly the HHS-Office of Inspector General ("OIG") and Texas Health and Human Services Commission Office of Inspector General ("HHSC-OIG") List of Excluded Individuals/Entities ("LEIE") websites to capture exclusions and reinstatements that have occurred since the last search and to immediately report to HHSC-OIG any exclusion information the Contractor discovers. Exclusionary searches for prospective employees and contractors shall be performed prior to employment or contracting.
B. That no Medicaid payments can be made for any items or services directed or prescribed by a physician or other authorized person who is excluded from Medicare, Medicaid or any federal or state health care program when the individual or entity furnishing the items or services either knew or should have known of the exclusion. This prohibition applies even when the Medicaid payment itself is made to another contractor, practitioner or supplier who is not excluded.
C. That this contract is subject to all state and federal laws and regulations relating to fraud and abuse in health care and the Medicaid program. As required by 42 C.F.R. §431.107, the Contractor agrees to keep all records necessary to disclose the extent of services the Contractor furnishes to people in the Medicaid program and any information relating to payments claimed by the Contractor for furnishing Medicaid services. On request, the Contractor also agrees to furnish HHSC, AG-MFCU, or HHS any information maintained under 42 C.F.
