We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Through the CNS Clearing Process Sample Clauses

Through the CNS Clearing Process. (1) Except as provided below, the securities in the Creation Basket Deposit (“Deposit Securities”) of any domestic Fund must be delivered through the NSCC to a DTC account maintained at the Custodian on or before the Domestic Contractual Settlement Date (defined below). The AP must also make available on or before the Domestic Contractual Settlement Date, by means satisfactory to the Trust, immediately available or same day funds estimated by the Trust to be sufficient to pay the cash component of the Creation Basket Deposit (the “Cash Component”), together with the applicable purchase Transaction Fee. Any excess funds will be returned following settlement of the issue of the Creation Unit of Shares of the Trust. The “Domestic Contractual Settlement Date” is the next Business Day following the Purchase Order Date (t + 1) or such later Business Day, not to exceed three Business Days after the Purchase Order Date, as agreed to between the AP and the Transfer Agent when the Purchase Order is placed. Except as provided in the next two paragraphs, a Creation Unit of Shares of any Fund will be issued in accordance with the terms, conditions and guarantees as set forth in CNS agreements to which the Custodian and AP have entered into. (2) The Trust reserves the right to permit or require the substitution of an amount of cash (i.e., a “cash in lieu” amount ) to be added to the Cash Component to replace any Deposit Security with respect to any domestic Fund which may not be available in sufficient quantity for delivery or which may not be eligible for transfer through the CNS Clearing Process, or which may not be eligible for transfer through the systems of DTC and hence not eligible for transfer through the CNS Clearing Process, additional cost, if any, to acquire the omitted securities will be at the expense of the AP. (3) Any settlement outside the CNS Clearing Process is subject to additional requirements and fees as discussed in the Prospectus.
Through the CNS Clearing Process. (1) Except as provided below, Deposit Securities of any Domestic Fund must be delivered through the NSCC to a DTC account maintained at the Custodian on or before the Domestic Contractual Settlement Date (defined below). The AP must also make available on or before the Contractual Settlement Date, by means satisfactory to the Trust, immediately available or same day funds estimated by the Trust to be sufficient to pay the Cash Component next determined after acceptance of the Purchase Order, together with the applicable purchase Transaction Fee. Any excess funds will be returned following settlement of the issue of the Creation Unit of Shares of the Trust. The “Domestic Contractual Settlement Date” is the earlier of (i) the date upon which all of the required Deposit Securities, the Cash Component and any other cash amounts which may be due are delivered to Trust and (ii) the trade date plus three (t +3)
Through the CNS Clearing Process. Except as provided below, the Redemption Baskets must be delivered through the NSCC to a DTC account maintained by the Custodian on or before the Settlement Time, after acceptance of the Redemption Order, together with receipt of the Transaction Fee. The Redemption Distribution will be credited to the Participant at the Settlement Time through the CNS system, assuming timely delivery of Redemption Baskets and the Transaction Fee through the CNS system in accordance with the terms, conditions and guarantees as set forth in the CNS agreements to which the Custodian and Participant have entered into.

Related to Through the CNS Clearing Process

  • Authorized Sub-processors Customer agrees that MailChimp may engage Sub-processors to process Customer Data on Customer's behalf. The Sub-processors currently engaged by MailChimp and authorized by Customer are listed in Annex A.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • 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.

  • 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.

  • Board Approval of Foreign Subcustodians Unless and except to the extent that the Board has delegated to the Custodian and the Custodian has accepted delegation of review of certain matters concerning the appointment of Subcustodians pursuant to Subsection 8.3, the Custodian shall, prior to the appointment of any Subcustodian for purposes of holding Investments of the Fund outside the United States, obtain written confirmation of the approval of the Board of Trustees or Directors of the Fund with respect to (a) the identity of a Subcustodian, and (b) the Subcustodian agreement which shall govern such appointment, such approval to be signed by an Authorized Person. An Instruction to open an account in a given country shall comprise authorization of the Custodian to hold assets in such country in accordance with the terms of this Agreement. The Custodian shall not be required to make independent inquiry as to the authorization of the Fund to invest in such country.

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

  • Sub-processor For the purposes of this Agreement, the term “Sub-processor” (sometimes referred to as the “Subcontractor”) means a party other than LEA or Provider, who Provider uses for data collection, analytics, storage, or other service to operate and/or improve its software, and who has access to PII.

  • Data Protection During Transmission DST shall encrypt, using an industry standard encryption algorithm, personally identifiable Fund Data when such data is transmitted.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • 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).