Per‐TLD Activity Report Sample Clauses

Per‐TLD Activity Report. This report shall be compiled in a comma separated‐value formatted file as specified in RFC 4180. The file shall be named “PPSP‐tlds‐yyyymm.csv”, where “PPSP” is the identifier assigned by ICANN to the Provider; “yyyymm” is the year and month being reported. The file shall contain the following fields per each TLD with at least 1 domain name using the Provider's services:
AutoNDA by SimpleDocs

Related to Per‐TLD Activity Report

  • CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.

  • Diversity Report The Contractor shall report to each Customer, spend with certified and other minority business enterprises. These reports shall include the period covered, the name, minority code and Federal Employer Identification Number of each minority business utilized during the period, Commodities provided by the minority business enterprise, and the amount paid to each minority business on behalf of each purchasing agency ordering under the terms of this Contract.

  • 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

  • REPORT ON CONTRACT SALES ACTIVITY AND ADMINISTRATIVE FEE PAYMENT A. CONTRACT SALES ACTIVITY REPORT. Each calendar quarter, Supplier must provide a contract sales activity report (Report) to the Sourcewell Supplier Development Administrator assigned to this Contract. Reports are due no later than 45 days after the end of each calendar quarter. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Supplier must submit a report indicating no sales were made). The Report must contain the following fields: • Participating Entity Name (e.g., City of Staples Highway Department); • Participating Entity Physical Street Address; • Participating Entity City; • Participating Entity State/Province; • Participating Entity Zip/Postal Code; • Participating Entity Contact Name; • Participating Entity Contact Email Address; • Participating Entity Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Supplier. B. ADMINISTRATIVE FEE. In consideration for the support and services provided by Sourcewell, the Supplier will pay an administrative fee to Sourcewell on all Equipment, Products, and Services provided to Participating Entities. The Administrative Fee must be included in, and not added to, the pricing. Supplier may not charge Participating Entities more than the contracted price to offset the Administrative Fee. The Supplier will submit payment to Sourcewell for the percentage of administrative fee stated in the Proposal multiplied by the total sales of all Equipment, Products, and Services purchased by Participating Entities under this Contract during each calendar quarter. Payments should note the Supplier’s name and Sourcewell-assigned contract number in the memo; and must be mailed to the address above “Attn: Accounts Receivable” or remitted electronically to Sourcewell’s banking institution per Sourcewell’s Finance department instructions. Payments must be received no later than 45 calendar days after the end of each calendar quarter. Supplier agrees to cooperate with Sourcewell in auditing transactions under this Contract to ensure that the administrative fee is paid on all items purchased under this Contract. In the event the Supplier is delinquent in any undisputed administrative fees, Sourcewell reserves the right to cancel this Contract and reject any proposal submitted by the Supplier in any subsequent solicitation. In the event this Contract is cancelled by either party prior to the Contract’s expiration date, the administrative fee payment will be due no more than 30 days from the cancellation date.

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

  • CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.

  • eXtensible Business Reporting Language The interactive data in eXtensible Business Reporting Language included or incorporated by reference in the Registration Statement fairly presents the information called for in all material respects and has been prepared in accordance with the Commission’s rules and guidelines applicable thereto.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Servicer Compliance Statement On or before March 1 of each calendar year, commencing in 2007, the Servicer shall deliver to the Owner and any Depositor a statement of compliance addressed to the Owner and such Depositor and signed by an authorized officer of the Servicer, to the effect that (i) a review of the Servicer’s activities during the immediately preceding calendar year (or applicable portion thereof) and of its performance under this Agreement and any applicable Reconstitution Agreement during such period has been made under such officer’s supervision, and (ii) to the best of such officers’ knowledge, based on such review, the Servicer has fulfilled all of its obligations under this Agreement and any applicable Reconstitution Agreement in all material respects throughout such calendar year (or applicable portion thereof) or, if there has been a failure to fulfill any such obligation in any material respect, specifically identifying each such failure known to such officer and the nature and the status thereof.

  • Regulatory Reports Since January 1, 2013, Company and its Subsidiaries have duly filed with the FRB, the FDIC, the Florida Office of Financial Regulation and any other applicable Governmental Authority, in correct form, the reports and other documents required to be filed under applicable Laws and regulations and have paid all fees and assessments due and payable in connection therewith, and such reports were, in all material respects, complete and accurate and in compliance with the requirements of applicable Laws and regulations. Other than normal examinations conducted by a Governmental Authority in the Ordinary Course of Business of Company and its Subsidiaries, no Governmental Authority has notified Company or any of its Subsidiaries that it has initiated or has pending any proceeding or, to Company’s Knowledge, threatened an investigation into the business or operations of Company or any of its Subsidiaries since January 1, 2013 that would reasonably be expected to be material. There is no material unresolved violation, criticism, or exception by any Governmental Authority with respect to any report or statement relating to any examinations or inspections of Company or any of its Subsidiaries. There have been no material formal or informal inquiries by, or disagreements or disputes with, any Governmental Authority with respect to the business, operations, policies or procedures of Company or any of its Subsidiaries since January 1, 2013.

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