Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b).
(d) Registry Operator shall provide public query-‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Registry Services “Registry Services” are, for purposes of the Agreement, defined as the following: (a) those services that are operations of the registry critical to the following tasks: the receipt of data from registrars concerning registrations of domain names and name servers; provision to registrars of status information relating to the zone servers for the TLD; dissemination of TLD zone files; operation of the registry DNS servers; and dissemination of contact and other information concerning domain name server registrations in the TLD as required by this Agreement; (b) other products or services that the Registry Operator is required to provide because of the establishment of a Consensus Policy as defined in Specification 1; (c) any other products or services that only a registry operator is capable of providing, by reason of its designation as the registry operator; and (d) material changes to any Registry Service within the scope of (a), (b) or (c) above.
Vendor Registration In order to complete any transaction between a Customer and the Contractor, the Contractor must be registered in MyFloridaMarketPlace.
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).
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.
Requests for Registration (i) Subject to the following paragraphs of this Section 3(a), on or after the 180th day following the Initial Public Offering, a Demand Party shall have the right, by delivering a written notice to the Corporation, to require the Corporation to register, directly or indirectly, and pursuant to the terms of this Agreement, under and in accordance with the provisions of the Securities Act, the number of Registrable Securities requested to be so registered pursuant to the terms of this Agreement (any such written notice, a “Demand Notice” and any such registration, a “Demand Registration”); provided, however, that a Demand Notice may only be made prior to the expiration of the Coordination Committee if previously approved in writing by the Coordination Committee; provided, further that, the Corporation shall not be obligated to file a Registration Statement relating to any registration request under this Section 3(a) within a period of 180 days after the effective date of any other Registration Statement relating to any registration request under this Section 3(a) (except if the underwriters shall require a longer period, but in any event no more than 270 days). Following receipt of a Demand Notice for a Demand Registration in accordance with this Section 3(a), the Corporation shall use its reasonable best efforts to file a Registration Statement as promptly as practicable and shall use its reasonable best efforts to cause such Registration Statement to be declared effective under the Securities Act as promptly as practicable after the filing thereof.
(ii) No Demand Registration shall be deemed to have occurred for purposes of this Section 3 if the Registration Statement relating thereto (x) does not become effective, (y) is not maintained effective for the period required pursuant to this Section 3, or (z) the offering of the Registrable Securities pursuant to such Registration Statement is subject to a stop order, injunction, or similar order or requirement of the SEC during such period, in which case, such requesting holder of Registrable Securities shall be entitled to an additional Demand Registration in lieu thereof.
(iii) Within 10 days after receipt by the Corporation of a Demand Notice in accordance with this Section 3(a), the Corporation shall give written notice (the “Notice”) of such Demand Notice to all other holders of Registrable Securities and shall, subject to the provisions of Section 3(b) hereof, include in such registration all Registrable Securities with respect to which the Corporation received written requests for inclusion therein within 15 days after such Notice is given by the Corporation to such holders.
(iv) All requests made pursuant to this Section 3 will specify the number of Registrable Securities to be registered and the intended methods of disposition thereof.
(v) The Corporation shall be required to maintain the effectiveness of the Registration Statement with respect to any Demand Registration for a period of at least 180 days after the effective date thereof or such shorter period during which all Registrable Securities included in such Registration Statement have actually been sold; provided, however, that such period shall be extended for a period of time equal to the period the holders of Registrable Securities are required to refrain from selling any securities included in such Registration Statement at the request of the Corporation or an underwriter of the Corporation pursuant to the provisions of this Agreement.
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.
Accuracy of Orders; Customer Signatures You shall be responsible for the accuracy, timeliness and completeness of any orders transmitted by you on behalf of your customers by any means, including wire or telephone. In addition, you agree to guarantee the signatures of your customers when such guarantee is required by the Company and you agree to indemnify and hold harmless all persons, including us and the Funds’ transfer agent, from and against any and all loss, cost, damage or expense suffered or incurred in reliance upon such signature guarantee.
Accounting and Reports to the Certificateholders, the Internal Revenue Service and Others The Administrator shall deliver to each Certificateholder, as may be required by the Code and applicable Treasury Regulations, or as may be requested by such Certificateholder, such information, reports or statements as may be necessary to enable each Certificateholder to prepare its federal and state income tax returns. Consistent with the Trust’s characterization for tax purposes as a disregarded entity so long as the Depositor or any other Person is the sole Certificateholder, no federal income tax return shall be filed on behalf of the Trust unless either (i) the Owner Trustee shall be provided with an Opinion of Counsel that, based on a change in applicable law occurring after the date hereof, or as a result of a transfer permitted by Section 3.04, the Code requires such a filing or (ii) the Internal Revenue Service shall determine that the Trust is required to file such a return. In the event that there shall be two or more beneficial owners of the Trust, the Administrator shall inform the Indenture Trustee in writing of such event, (x) the Administrator shall prepare or shall cause to be prepared federal and, if applicable, state or local partnership tax returns, with all such necessary information provided to it, required to be filed by the Trust and shall remit such returns to the Depositor (or if the Depositor no longer owns any Certificates, the Certificateholder designated for such purpose by the Depositor to the Owner Trustee in writing) at least (5) days before such returns are due to be filed, and (y) capital accounts shall be maintained by the Administrator for each Certificateholder in accordance with the Treasury Regulations under Section 704(b) of the Code reflecting each such Certificateholder’s share of the income, gains, deductions, and losses of the Trust and/or guaranteed payments made by the Trust and contributions to, and distributions from, the Trust. The Depositor (or such designee Certificateholder, as applicable) shall promptly sign such returns and deliver such returns after signature to the Administrator and such returns shall be filed by the Administrator with the appropriate tax authorities. In the event that a “tax matters partner” (within the meaning of Code Section 6231(a)(7)) is required to be appointed with respect to the Trust, the Depositor or its designee is hereby designated as tax matters partner or, if the Depositor is not a Certificateholder, the Certificateholder selected by a majority of the Certificateholders (by Percentage Interest) shall be designated as tax matters partner. In no event shall the Certificateholder or the Depositor (or such designee Certificateholder, as applicable) be liable for any liabilities, costs or expenses of the Trust or the Noteholders arising out of the application of any tax law, including federal, state, foreign or local income or excise taxes or any other tax imposed on or measured by income (or any interest, penalty or addition with respect thereto or arising from a failure to comply therewith) except for any such liability, cost or expense attributable to any negligent act or omission by the Owner Trustee or the Depositor (or such designee Certificateholder, as applicable), as the case may be, in breach of its obligations under this Agreement.
