Reporting Total Compensation of Recipient Executives 1. Applicability and what to report. You must report total compensation for each of your five most highly compensated executives for the preceding completed fiscal year, if— i. the total Federal funding authorized to date under this award is $25,000 or more; ii. in the preceding fiscal year, you received— (a) 80 percent or more of your annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and (b) $25,000,000 or more in annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and iii. The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at xxxx://xxx.xxx.xxx/answers/execomp.htm.) 2. Where and when to report. You must report executive total compensation described in paragraph A.1. of this award term: i. As part of your registration profile at xxxxx://xxx.xxx.gov. ii. By the end of the month following the month in which this award is made, and annually thereafter.
Reciprocal Compensation The arrangement for recovering, in accordance with Section 251(b)(5) of the Act, the FCC Internet Order, and other applicable FCC orders and FCC Regulations, costs incurred for the transport and termination of Reciprocal Compensation Traffic originating on one Party’s network and terminating on the other Party’s network (as set forth in Section 7 of the Interconnection Attachment).
Traffic Not Subject to Reciprocal Compensation 7.2.1 Reciprocal Compensation shall not apply to interstate or intrastate Exchange Access (including, without limitation, Virtual Foreign Exchange Traffic (i.e., V/FX Traffic), Information Access, or exchange services for Exchange Access or Information Access. 7.2.2 Reciprocal Compensation shall not apply to Internet Traffic. 7.2.3 Reciprocal Compensation shall not apply to Toll Traffic, including, but not limited to, calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis. 7.2.4 Reciprocal Compensation shall not apply to Optional Extended Local Calling Scope Arrangement Traffic. 7.2.5 Reciprocal Compensation shall not apply to special access, private line, or any other traffic that is not switched by the terminating Party. 7.2.6 Reciprocal Compensation shall not apply to Tandem Transit Traffic. 7.2.7 Reciprocal Compensation shall not apply to Voice Information Service Traffic (as defined in Section 5 of the Additional Services Attachment). 7.2.8 Reciprocal Compensation shall not apply to traffic that is not subject to Reciprocal Compensation under Section 251(b)(5) of the Act. 7.2.9 Reciprocal Compensation shall not apply to Virtual Foreign Exchange Traffic (i.e., V/FX Traffic). As used in this Agreement, “Virtual Foreign Exchange Traffic” or “V/FX Traffic” is defined as calls in which an Onvoy Customer is assigned a telephone number with an NXX Code (as set forth in the LERG) associated with an exchange that is different than the exchange (as set forth in the LERG) associated with the actual physical location of such Customer’s station. For the avoidance of any doubt, Onvoy shall pay Frontier’s originating access charges for all V/FX Traffic originated by a Frontier Customer, and Onvoy shall pay Frontier’s terminating access charges for all V/FX Traffic originated by an Onvoy Customer.
Special Provisions Relating to the Holders of Incentive Distribution Rights Notwithstanding anything to the contrary set forth in this Agreement, the holders of the Incentive Distribution Rights (a) shall (i) possess the rights and obligations provided in this Agreement with respect to a Limited Partner pursuant to Articles III and VII and (ii) have a Capital Account as a Partner pursuant to Section 5.5 and all other provisions related thereto and (b) shall not (i) be entitled to vote on any matters requiring the approval or vote of the holders of Outstanding Units, (ii) be entitled to any distributions other than as provided in Sections 6.4(a)(v), (vi) and (vii), 6.4(b)(iii), (iv) and (v), and 12.4 or (iii) be allocated items of income, gain, loss or deduction other than as specified in this Article VI.
Files Management and Record Retention relating to Grantee and Administration of this Agreement a. The Grantee shall maintain books, records, and documents in accordance with generally accepted accounting procedures and practices which sufficiently and properly reflect all expenditures of funds provided by Florida Housing under this Agreement. b. Contents of the Files: Grantee must maintain files containing documentation to verify all funds awarded to Grantee in connection with this Agreement, as well as reports, records, documents, papers, letters, computer files, or other material received, generated, maintained or filed by Grantee in connection with this Agreement. Grantee must also keep files, records, computer files, and reports that reflect any compensation it receives or will receive in connection with this Agreement.
Transition of Registry upon Termination of Agreement Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, Registry Operator shall provide ICANN or any successor registry operator that may be designated by ICANN for the TLD in accordance with this Section 4.5 with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process; provided, however, that (i) ICANN will take into consideration any intellectual property rights of Registry Operator (as communicated to ICANN by Registry Operator) in determining whether to transition operation of the TLD to a successor registry operator and (ii) if Registry Operator demonstrates to ICANN’s reasonable satisfaction that (A) all domain name registrations in the TLD are registered to, and maintained by, Registry Operator or its Affiliates for their exclusive use, (B) 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 (C) transitioning operation of the TLD is not necessary to protect the public interest, then ICANN may not transition operation of the TLD to a successor registry operator upon the expiration or termination of this Agreement without the consent of Registry Operator (which shall not be unreasonably withheld, conditioned or delayed). For the avoidance of doubt, the foregoing sentence shall not prohibit ICANN from delegating the TLD pursuant to a future application process for the delegation of top-‐level domains, subject to any processes and objection procedures instituted by ICANN in connection with such application process intended to protect the rights of third parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument for the maintenance and operation of the TLD, regardless of the reason for termination or expiration of this Agreement.
Transition of Registry upon Termination of Agreement text for intergovernmental organizations or governmental entities or other special circumstances: “Transition of Registry upon Termination of Agreement. Upon expiration of the Term pursuant to Section 4.1 or Section 4.2 or any termination of this Agreement pursuant to Section 4.3 or Section 4.4, in connection with ICANN’s designation of a successor registry operator for the TLD, Registry Operator and ICANN agree to consult each other and work cooperatively to facilitate and implement the transition of the TLD in accordance with this Section 4.5. After consultation with Registry Operator, ICANN shall determine whether or not to transition operation of the TLD to a successor registry operator in its sole discretion and in conformance with the Registry Transition Process. In the event ICANN determines to transition operation of the TLD to a successor registry operator, upon Registry Operator’s consent (which shall not be unreasonably withheld, conditioned or delayed), Registry Operator shall provide ICANN or such successor registry operator for the TLD with any data regarding operations of the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such successor registry operator in addition to data escrowed in accordance with Section 2.3 hereof. In the event that Registry Operator does not consent to provide such data, any registry data related to the TLD shall be returned to Registry Operator, unless otherwise agreed upon by the parties. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event of a transition of the TLD pursuant to this Section 4.5. In addition, ICANN or its designee shall retain and may enforce its rights under the Continued Operations Instrument, regardless of the reason for termination or expiration of this Agreement.”]
File Management and Record Retention relating to CRF Eligible Persons or Households Grantee must maintain a separate file for every applicant, Eligible Person, or Household, regardless of whether the request was approved or denied. a. Contents of File: Each file must contain sufficient and legible documentation. Documents must be secured within the file and must be organized systematically.
Application of this Revenue Sharing Agreement to Notes The terms of this Revenue Sharing Agreement shall apply to each Note as if the terms of this Revenue Sharing Agreement were fully set forth in each Note.