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.
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).
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
Domestic Subcustodians and Securities Depositories The Custodian may deposit and/or maintain, either directly or through one or more agents appointed by the Custodian, Investments of the Fund in any Securities Depository in the United States, including The Depository Trust Company, provided such Depository meets applicable requirements of the Federal Reserve Bank or of the Securities and Exchange Commission. The Custodian may, at any time and from time to time, appoint any bank as defined in Section 2(a)(5) of the 1940 Act meeting the requirements of a custodian under Section 17(f) of the 1940 Act and the rules and regulations thereunder, to act on behalf of the Fund as a Subcustodian for purposes of holding Investments of the Fund in the United States.
CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.
Appointment of Subcustodians; Use of Securities Depositories (a) Bank is authorized under this Agreement to act through and hold Customer's Global Assets with subcustodians, being at the date of this Agreement the entities listed in Schedule 1 and/or such other entities as Bank may appoint as subcustodians ("Subcustodians"). At the request of Customer, Bank may, but need not, add to Schedule 1 an Eligible Foreign Custodian where Bank has not acted as Foreign Custody Manager with respect to the selection thereof. Bank shall notify Customer in the event that it elects to add any such entity. Bank shall use reasonable care, prudence and diligence in the selection and continued appointment of such Subcustodians. In addition, Bank and each Subcustodian may deposit Global Assets with, and hold Global Assets in, any securities depository, settlement system, dematerialized book entry system or similar system (together a "Securities Depository") on such terms as such systems customarily operate and Customer shall provide Bank with such documentation or acknowledgements that Bank may require to hold the Global Assets in such systems.
(b) Any agreement Bank enters into with a Subcustodian for holding Bank's customers' assets shall provide that: (i) such assets shall not be subject to any right, charge, security interest, lien or claim of any kind in favor of such Subcustodian or its creditors, except a claim of payment for their safe custody or administration or, in the case of cash deposits, except for liens or rights in favor of creditors of the Subcustodian arising under bankruptcy, insolvency or similar laws; (ii) beneficial ownership of such assets shall be freely transferable without the payment of money or value other than for safe custody or administration; (iii) adequate records will be maintained identifying the assets as belonging to Customer or as being held by a third party for the benefit of Customer; (iv) Customer and Customer's independent public accountants will be given reasonable access to those records or confirmation of the contents of those records; and (v) Customer will receive periodic reports with respect to the safekeeping of Customer's assets, including, but not limited to, notification of any transfer to or from Customer's account or a third party account containing assets held for the benefit of Customer. Where a Subcustodian deposits Securities with a Securities Depository, Bank shall cause the Subcustodian to identify on its records as belonging to Bank, as agent, the Securities shown on the Subcustodian's account at such Securities Depository. The foregoing shall not apply to the extent of any special agreement or arrangement made by Customer with any particular Subcustodian.
(c) Bank shall have no responsibility for any act or omission by (or the insolvency of) any Securities Depository. In the event Customer incurs a loss due to the negligence, bad faith, willful misconduct, or insolvency of a Securities Depository, Bank shall make reasonable endeavors to seek recovery from the Securities Depository.
(d) The term Subcustodian as used herein shall mean the following:
(i) a "U.S. Bank" as such term is defined in rule 17f-5; and
(ii) an "Eligible Foreign Custodian" as such term is defined in rule 17f-5 and any other entity that shall have been so qualified by exemptive order, rule or other appropriate action of the SEC.
(iii) For purposes of clarity, it is agreed that as used in Section 5.2(a), the term Subcustodian shall not include any Eligible Foreign Custodian as to which Bank has not acted as Foreign Custody Manager.
(e) The term 'securities depository' as used herein when referring to a securities depository located outside the U.S. shall mean an "Eligible Securities Depository" as defined in rule 17f-7, or that has otherwise been made exempt pursuant to an SEC exemptive order.
(f) The term 'securities depository' as used herein when referring to a securities depository located in the U.S. shall mean a "Securities Depository" as defined in rule 17f-4.
Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.
Foreign Subcustodians and Securities Depositories Unless instructed otherwise by the Fund, the Custodian may deposit and/or maintain non-U.S. Investments of the Fund in any non-U.S. Securities Depository provided such Securities Depository meets the requirements of an "eligible securities depository" under Rule 17f-7 promulgated under the 1940 Act, or any successor rule or regulation ("Rule 17f-7") or which by order of the Securities and Exchange Commission is exempted therefrom. Prior to the time that securities are placed with such depository, but subject to the provisions of Section 8.5 below, the Custodian shall have prepared an assessment of the custody risks associated with maintaining assets with the Securities Depository and shall have established a system to monitor such risks on a continuing basis in accordance with Section 8.5. Additionally, the Custodian may, from time to time, appoint (a) any bank, trust company or other entity meeting the requirements of an “eligible foreign custodian” under Rule 17f-5 or which by order of the Securities and Exchange Commission is exempted therefrom, or (b) any bank as defined in Section 2(a)(5) of the 1940 Act meeting the requirements of a custodian under Section 17(f) of the 1940 Act and the rules and regulations thereunder, to act on behalf of the Fund as a Subcustodian for purposes of holding Investments of the Fund outside the United States.
NEGOTIATIONS PROCEDURES 3.1 The Board and SEE shall each exchange, in writing, at the first negotiations session, the names of persons who shall serve as their respective representatives for negotiations, up to ten (10). Each party shall also designate the person on its team who will serve as spokesperson. Other persons may be permitted to attend negotiation sessions for resource purposes upon prior mutual agreement of the parties. (revised 2012-13)
3.2 No later than April 15 of each ensuing year, either SEE or the Board shall submit a written request for negotiations to commence to the other party, if it desires there to be negotiations for that year. If no such request is made during the time period above, negotiations will not take place for the ensuing year. (revised 2012-13)
3.3 The first negotiation session shall occur on a mutually agreeable date. (revised 2012-13)
3.4 The Board and SEE shall share their initial written concerns at least one week prior to scheduled negotiations. Subsequent initial concerns may only be submitted upon mutual agreement of the parties. (revised 2012-13)
3.5 Only those members who comprise the negotiation teams will be present in the room during negotiations except for the OEA advocate and clerical assistance. Other parties may be permitted to be present only by mutual agreement of the parties. (revised 2012-13)
3.6 Negotiations shall be conducted in closed sessions. No recordings or official transcripts shall be made without mutual agreement of the parties.
3.7 Negotiations will only be conducted between the designated representatives of the parties and only in regular negotiations sessions at the times, dates, and places mutually agreed upon by the parties. The time, date, place and agenda of subsequent sessions will be set by mutual agreement of the parties prior to the close of each negotiations session.
3.8 Negotiations sessions shall be scheduled outside the regular work day of the representatives of the bargaining unit, except by mutual agreement.
3.9 Releases to the news media will be by mutual agreement only. However, neither the Board nor SEE shall be prohibited from communicating with its own members.
3.10 When tentative agreement is reached on any item, it shall be reduced to writing, and signed and dated by the spokesperson of each team. When tentative agreement is reached on all items, they shall be submitted first as a package by SEE to the bargaining unit for ratification and then by the Superintendent to the Board for ratification.
