Registrar and Transfer Agent To maintain, at its expense, a registrar and transfer agent for the Stock.
Stock Plan Administration Service Provider The Company transfers the Optionee's Personal Information to Fidelity Stock Plan Services LLC, an independent service provider based in the United States, which assists the Company with the implementation, administration and management of the Plan (the “Stock Plan Administrator”). In the future, the Company may select a different Stock Plan Administrator and share the Optionee's Personal Information with another company that serves in a similar manner. The Stock Plan Administrator will open an account for the Optionee to receive and trade Shares acquired under the Plan. The Optionee will be asked to agree on separate terms and data processing practices with the Stock Plan Administrator, which is a condition to the Optionee’s ability to participate in the Plan.
Shareholder Account Maintenance (a) Maintain all shareholder records for each account in the Company.
(b) Issue customer statements on scheduled cycle, providing duplicate second and third party copies if required.
(c) Record shareholder account information changes.
(d) Maintain account documentation files for each shareholder.
Registrar and Paying Agent The Company shall maintain an office or agency where Notes may be presented for registration of transfer or for exchange ("Registrar") and an office or agency where Notes may be presented for payment ("Paying Agent"). The Registrar shall keep a register of the Notes and of their transfer and exchange. The Company may appoint one or more co-registrars and one or more additional paying agents. The term "
Stock Plan Administration Service Providers The Company transfers participant data to Xxxxxx Xxxxxxx, an independent service provider based in the United States, which assists the Company with the implementation, administration and management of the Plan. In the future, the Company may select a different service provider and share the Participant’s data with another company that serves in a similar manner. The Company’s service provider will open an account for the Participant to receive and trade Shares. The Participant will be asked to agree on separate terms and data processing practices with the service provider, which is a condition to the Participant’s ability to participate in the Plan.
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 <<<
Shareholder Services Transfer Agent or its agent will investigate all inquiries from Shareholders of a Fund relating to Shareholder accounts and will respond to all communications from Shareholders and others relating to its duties hereunder and such other correspondence as may from time to time be mutually agreed upon between Transfer Agent and a Fund. Transfer Agent shall provide each Fund with reports concerning Shareholder inquires and the responses thereto by Transfer Agent, in such form and at such times as are agreed to by the Fund and Transfer Agent.
Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
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.
