Xxxxxxx Xxxxxxx/Market Abuse Laws You acknowledge that, depending on your country or broker’s country, or the country in which Common Stock is listed, you may be subject to xxxxxxx xxxxxxx restrictions and/or market abuse laws in applicable jurisdictions, which may affect your ability to accept, acquire, sell or attempt to sell, or otherwise dispose of the shares of Common Stock, rights to shares of Common Stock (e.g., RSUs) or rights linked to the value of Common Stock, during such times as you are considered to have “inside information” regarding the Company (as defined by the laws or regulations in applicable jurisdictions, including the United States and your country). Local xxxxxxx xxxxxxx laws and regulations may prohibit the cancellation or amendment of orders you placed before possessing inside information. Furthermore, you may be prohibited from (i) disclosing insider information to any third party, including fellow employees and (ii) “tipping” third parties or causing them to otherwise buy or sell securities. Any restrictions under these laws or regulations are separate from and in addition to any restrictions that may be imposed under any applicable Company xxxxxxx xxxxxxx policy. You acknowledge that it is your responsibility to comply with any applicable restrictions, and you should speak to your personal advisor on this matter.
LICENSE HOLDER CONTACT INFORMATION This notice is being provided for information purposes. It does not create an obligation for you to use the broker’s services. Please acknowledge receipt of this notice below and retain a copy for your records.
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.
Xxxxxxx Xxxxxxx Restrictions/Market Abuse Laws The Participant acknowledges that, depending on his or her country, the broker’s country, or the country in which the Shares are listed, the Participant may be subject to xxxxxxx xxxxxxx restrictions and/or market abuse laws in applicable jurisdictions, which may affect his or her ability to accept, acquire, sell, or attempt to sell or otherwise dispose of Shares or rights to Shares (e.g., Restricted Share Units), or rights linked to the value of Shares, during such times as he or she is considered to have “inside information” regarding the Company (as defined by applicable laws or regulations in the applicable jurisdictions, including the United States and the Participant’s country). Local xxxxxxx xxxxxxx laws and regulations may prohibit the cancellation or amendment of orders the Participant placed before possessing inside information. Furthermore, the Participant may be prohibited from (i) disclosing the inside information to any third party, including fellow employees (other than on a “need to know” basis) and (ii) “tipping” third parties or causing them to otherwise buy or sell securities. Any restrictions under these laws or regulations are separate from and in addition to any restrictions that may be imposed under any applicable Company xxxxxxx xxxxxxx policy. The Participant acknowledges that it is his or her responsibility to comply with any applicable restrictions, and the Participant should consult his or her personal advisor on this matter.
Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.
XXXXXXXX ANTI-KICKBACK ACT (a) The Sub-Recipient hereby agrees that, unless exempt under Federal law, it will incorporate or cause to be incorporated into any contract for construction work, or modification thereof, the following clause:
i. Contractor. The contractor shall comply with 18 U.S.C. § 874, 40 U.S.C. § 3145, and the requirements of 29 C.F.R. pt. 3 as may be applicable, which are incorporated by reference into this contract.
Project Administration Designation Pursuant to Paragraph (B) of Rule 164-1-21 of the Administrative Code, the Recipient shall designate its Chief Executive Officer, Chief Fiscal Officer and Project Manager in Appendix B of this Agreement. Changes in these designations must be made in writing.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning):
1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises.
2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated.
3. If capacity exists, provide "side-door" porting through the switch.
4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch).
2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases.
2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
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.