Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐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 per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
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
Request for Registration Subject to the provisions of subsection 2.1.4 and Section 2.4 hereof, at any time and from time to time on or after the date the Company consummates the Business Combination, the Holders of at least a majority in interest of the then-outstanding number of Registrable Securities (the “Demanding Holders”) may make a written demand for Registration of all or part of their Registrable Securities, which written demand shall describe the amount and type of securities to be included in such Registration and the intended method(s) of distribution thereof (such written demand a “Demand Registration”). The Company shall, within ten (10) days of the Company’s receipt of the Demand Registration, notify, in writing, all other Holders of Registrable Securities of such demand, and each Holder of Registrable Securities who thereafter wishes to include all or a portion of such Holder’s Registrable Securities in a Registration pursuant to a Demand Registration (each such Holder that includes all or a portion of such Holder’s Registrable Securities in such Registration, a “Requesting Holder”) shall so notify the Company, in writing, within five (5) days after the receipt by the Holder of the notice from the Company. Upon receipt by the Company of any such written notification from a Requesting Holder(s) to the Company, such Requesting Holder(s) shall be entitled to have their Registrable Securities included in a Registration pursuant to a Demand Registration and the Company shall effect, as soon thereafter as practicable, but not more than forty five (45) days immediately after the Company’s receipt of the Demand Registration, the Registration of all Registrable Securities requested by the Demanding Holders and Requesting Holders pursuant to such Demand Registration. Under no circumstances shall the Company be obligated to effect more than an aggregate of three (3) Registrations pursuant to a Demand Registration under this subsection 2.1.1 with respect to any or all Registrable Securities; provided, however, that a Registration shall not be counted for such purposes unless a Form S-1 or any similar long-form registration statement that may be available at such time (“Form S-1”) has become effective and all of the Registrable Securities requested by the Requesting Holders to be registered on behalf of the Requesting Holders in such Form S-1 Registration have been sold, in accordance with Section 3.1 of this Agreement.
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).
Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”
1.6.2 Response format: Registrar Name: Example Registrar, Inc. Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxx@xxxxxxx.xxx WHOIS Server: whois.example-‐registrar.tld Referral URL: xxxx://xxx.xxxxxxx-‐registrar.tld Admin Contact: Xxx Registrar Phone Number: +1.3105551213 Fax Number: +1.3105551213 Email: joeregistrar@example-‐registrar.tld Admin Contact: Xxxx Registrar Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: janeregistrar@example-‐registrar.tld Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216 Email: johngeek@example-‐registrar.tld >>> Last update of WHOIS database: 2009-‐05-‐29T20:15:00Z <<<
Annual Officer’s Certificate; Notice of Servicer Replacement Event (a) The Servicer will deliver to the Issuer, with a copy to the Indenture Trustee, on or before March 30th of each year, beginning on March 30, 2019, an Officer’s Certificate, dated as of December 31 of the immediately preceding year, providing such information as is required under Item 1123 of Regulation AB.
(b) The Servicer will deliver to the Issuer, with a copy to the Indenture Trustee within five (5) Business Days after having obtained knowledge thereof written notice in an Officer’s Certificate of any event which with the giving of notice or lapse of time, or both, would become a Servicer Replacement Event. Except to the extent set forth in this Section 3.9(b), Section 7.2 and Section 9.22 of this Agreement and Section 3.12 and Section 6.5 of the Indenture, the Transaction Documents do not require any policies or procedures to monitor any performance or other triggers and events of default.
(c) The Servicer will deliver to the Issuer, on or before March 30th of each year, beginning on March 30, 2019, a report regarding the Servicer’s assessment of compliance with the Servicing Criteria specified in Exhibit C as applicable to the Servicer during the immediately preceding calendar year, including disclosure of any material instance of non-compliance identified by the Servicer, as required under paragraph (b) of Rule 13a-18, or Rule 15d-18 of the Exchange Act and Item 1122 of Regulation AB, or such other criteria as mutually agreed upon by the Seller and the Servicer.
USER REGISTRATION You may be required to register with the Site. You agree to keep your password confidential and will be responsible for all use of your account and password. We reserve the right to remove, reclaim, or change a username you select if we determine, in our sole discretion, that such username is inappropriate, obscene, or otherwise objectionable.
Trustee, Paying Agents, Conversion Agents, Bid Solicitation Agent or Note Registrar May Own Notes The Trustee, any Paying Agent, any Conversion Agent, Bid Solicitation Agent (if other than the Company or any Affiliate thereof) or Note Registrar, in its individual or any other capacity, may become the owner or pledgee of Notes with the same rights it would have if it were not the Trustee, Paying Agent, Conversion Agent, Bid Solicitation Agent or Note Registrar.
Registrar, Transfer Agent and Paying Agent The Issuer shall maintain (i) an office or agency where Notes may be presented for registration (“Registrar”), (ii) an office or agency where Notes may be presented for transfer or for exchange (“Transfer Agent”) and (iii) an office or agency where Notes may be presented for payment (“Paying Agent”). The Registrar shall keep a register of the Notes (“Note Register”) and of their transfer and exchange. The registered Holder of a Note will be treated as the owner of such Note for all purposes and only registered Holders shall have rights under this Indenture and the Notes. The Issuer may appoint one or more co-registrars, one or more co-transfer agents and one or more additional paying agents. The term “Registrar” includes any co-registrar, the term “Transfer Agent” includes any co-transfer agent and the term “Paying Agent” includes any additional paying agents. The Issuer may change any Paying Agent, Transfer Agent or Registrar without prior notice to any Holder. The Issuer shall notify the Trustee in writing of the name and address of any Agent not a party to this Indenture. If the Issuer fails to appoint or maintain another entity as Registrar, Transfer Agent or Paying Agent, the Trustee shall act as such. The Issuer or any of its Subsidiaries may act as Paying Agent, Transfer Agent or Registrar. The Issuer initially appoints The Depository Trust Company, its nominees and successors (“DTC”) to act as Depositary with respect to the Global Notes. The Issuer initially appoints the Trustee to act as the Paying Agent, Transfer Agent and Registrar for the Notes and to act as Custodian with respect to the Global Notes.
Voter Registration When designated by the Secretary of State, the Contractor agrees to become a voter registration agency as defined by 17 V.S.A. §2103 (41), and to comply with the requirements of state and federal law pertaining to such agencies.
