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.
Book-Entry System Provided (i) the Bank has received a certified copy of a resolution of the Board specifically approving deposits of Fund assets in the Book-Entry System, and (ii) for any subsequent changes to such arrangements following such approval, the Board has reviewed and approved the arrangement and has not delivered an Officer's Certificate to the Bank indicating that the Board has withdrawn its approval:
(a) The Bank may keep Portfolio Securities in the Book-Entry System provided that such Portfolio Securities are represented in an account ("Account") of the Bank (or its agent) in such System which shall not include any assets of the Bank (or such agent) other than assets held as a fiduciary, custodian, or otherwise for customers;
(b) The records of the Bank (and any such agent) with respect to the Fund's participation in the Book-Entry System through the Bank (or any such agent) will identify by book entry the Portfolio Securities which are included with other securities deposited in the Account and shall at all times during the regular business hours of the Bank (or such agent) be open for inspection by duly authorized officers, employees or agents of the Fund. Where securities are transferred to the Fund's account, the Bank shall also, by book entry or otherwise, identify as belonging to the Fund a quantity of securities in a fungible bulk of securities (i) registered in the name of the Bank or its nominee, or (ii) shown on the Bank's account on the books of the Federal Reserve Bank;
(c) The Bank (or its agent) shall pay for securities purchased for the account of the Fund or shall pay cash collateral against the return of Portfolio Securities loaned by the Fund upon (i) receipt of advice from the Book-Entry System that such Securities have been transferred to the Account, and (ii) the making of an entry on the records of the Bank (or its agent) to reflect such payment and transfer for the account of the Fund. The Bank (or its agent) shall transfer securities sold or loaned for the account of the Fund upon
(i) receipt of advice from the Book-Entry System that payment for securities sold or payment of the initial cash collateral against the delivery of securities loaned by the Fund has been transferred to the Account; and
(ii) the making of an entry on the records of the Bank (or its agent) to reflect such transfer and payment for the account of the Fund. Copies of all advices from the Book-Entry System of transfers of securities for the account of the Fund shall identify the Fund, be maintained for the Fund by the Bank and shall be provided to the Fund at its request. The Bank shall send the Fund a confirmation, as defined by Rule 17f-4 of the 1940 Act, of any transfers to or from the account of the Fund;
(d) The Bank will promptly provide the Fund with any report obtained by the Bank or its agent on the Book-Entry System's accounting system, internal accounting control and procedures for safeguarding securities deposited in the Book-Entry System;
Use of Book-Entry System The Fund shall deliver to PFPC Trust certified resolutions of the Board approving, authorizing and instructing PFPC Trust on a continuous basis, to deposit in the Book-Entry System all securities belonging to the Portfolios eligible for deposit therein and to utilize the Book-Entry System to the extent possible in connection with settlements of purchases and sales of securities by the Portfolios, and deliveries and returns of securities loaned, subject to repurchase agreements or used as collateral in connection with borrowings. PFPC Trust shall continue to perform such duties until it receives Written Instructions or Oral Instructions authorizing contrary actions. PFPC Trust shall administer the Book-Entry System as follows:
(i) With respect to securities of each Portfolio which are maintained in the Book-Entry System, the records of PFPC Trust shall identify by book-entry or otherwise those securities belonging to each Portfolio. PFPC Trust shall furnish to the Fund a detailed statement of the Property held for each Portfolio under this Agreement at least monthly and from time to time and upon written request.
(ii) Securities and any cash of each Portfolio deposited in the Book-Entry System will at all times be segregated from any assets and cash controlled by PFPC Trust in other than a fiduciary or custodian capacity but may be commingled with other assets held in such capacities. PFPC Trust and its sub-custodian, if any, will pay out money only upon receipt of securities and will deliver securities only upon the receipt of money.
(iii) All books and records maintained by PFPC Trust which relate to the Fund's participation in the Book-Entry System will be open to the inspection of Authorized Persons at all times during PFPC Trust's regular business hours, and PFPC Trust will furnish to the Fund all information in respect of the services rendered as it may require. PFPC Trust will also provide the Fund with such reports on its own system of internal control as the Fund may reasonably request from time to time.
Access to Site 3.05.1 Contractor may enter and leave the premises at all reasonable times without charge. Contractor and its employees may use the common areas and roadways of the premises where it is to perform the services together with all facilities, equipment, improvements, and services provided in connection with the premises for common use. This excludes parking for Contractor’s personnel. Contractor shall repair any damage caused by it or its employees as a result of its use of the common areas.
Access to NID 2.7.3.1 NewPhone may access the customer’s premises wiring by any of the following means and NewPhone shall not disturb the existing form of electrical protection and shall maintain the physical integrity of the NID:
2.7.3.1.1 BellSouth shall allow NewPhone to connect its Loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premises;
2.7.3.1.2 Where an adequate length of the customer’s premises wiring is present and environmental conditions permit, either Party may remove the customer premises wiring from the other Party’s NID and connect such wiring to that Party’s own NID;
2.7.3.1.3 Either Party may enter the subscriber access chamber or dual chamber NID enclosures for the purpose of extending a cross-connect or spliced jumper wire from the customer premises wiring through a suitable “punch-out” hole of such NID enclosures; or
2.7.3.1.4 NewPhone may request BellSouth to make other rearrangements to the customer premises wiring terminations or terminal enclosure on a time and materials cost basis.
2.7.3.2 In no case shall either Party remove or disconnect the other Party’s loop facilities from either Party’s NIDs, enclosures, or protectors unless the applicable Commission has expressly permitted the same and the disconnecting Party provides prior notice to the other Party. In such cases, it shall be the responsibility of the Party disconnecting loop facilities to leave undisturbed the existing form of electrical protection and to maintain the physical integrity of the NID. It will be NewPhone’s responsibility to ensure there is no safety hazard, and NewPhone will hold BellSouth harmless for any liability associated with the removal of the BellSouth Loop from the BellSouth NID. Furthermore, it shall be the responsibility of the disconnecting Party, once the other Party’s loop has been disconnected from the NID, to reconnect the disconnected loop to a nationally recognized testing laboratory listed station protector, which has been grounded as per Article 800 of the National Electrical Code. If no spare station protector exists in the NID, the disconnected loop must be appropriately cleared, capped and stored.
2.7.3.3 NewPhone shall not remove or disconnect ground wires from BellSouth’s NIDs, enclosures, or protectors.
2.7.3.4 NewPhone shall not remove or disconnect NID modules, protectors, or terminals from BellSouth’s NID enclosures.
2.7.3.5 Due to the wide variety of NID enclosures and outside plant environments, BellSouth will work with NewPhone to develop specific procedures to establish the most effective means of implementing this section if the procedures set forth herein do not apply to the NID in question.
DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer.
(b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.
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.
Book-Entry Systems The Depositary shall make arrangements for the acceptance of the ADSs into DTC. All ADSs held through DTC will be registered in the name of the nominee for DTC (currently “Cede & Co.”). As such, the nominee for DTC will be the only “Holder” of all ADSs held through DTC. Unless issued by the Depositary as Uncertificated ADSs, the ADSs registered in the name of Cede & Co. will be evidenced by one or more ADR(s) in the form of a “Balance Certificate,” which will provide that it represents the aggregate number of ADSs from time to time indicated in the records of the Depositary as being issued hereunder and that the aggregate number of ADSs represented thereby may from time to time be increased or decreased by making adjustments on such records of the Depositary and of DTC or its nominee as hereinafter provided. Citibank, N.A. (or such other entity as is appointed by DTC or its nominee) may hold the “Balance Certificate” as custodian for DTC. Each Beneficial Owner of ADSs held through DTC must rely upon the procedures of DTC and the DTC Participants to exercise or be entitled to any rights attributable to such ADSs. The DTC Participants shall for all purposes be deemed to have all requisite power and authority to act on behalf of the Beneficial Owners of the ADSs held in the DTC Participants’ respective accounts in DTC and the Depositary shall for all purposes be authorized to rely upon any instructions and information given to it by DTC Participants. So long as ADSs are held through DTC or unless otherwise required by law, ownership of beneficial interests in the ADSs registered in the name of the nominee for DTC will be shown on, and transfers of such ownership will be effected only through, records maintained by (i) DTC or its nominee (with respect to the interests of DTC Participants), or (ii) DTC Participants or their nominees (with respect to the interests of clients of DTC Participants). Any distributions made, and any notices given, by the Depositary to DTC under the terms of the Deposit Agreement shall (unless otherwise specified by the Depositary) satisfy the Depositary’s obligations under the Deposit Agreement to make such distributions, and give such notices, in respect of the ADSs held in DTC (including, for avoidance of doubt, to the DTC Participants holding the ADSs in their DTC accounts and to the Beneficial Owners of such ADSs).
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.
