How Do I Get More Information? This Notice summarizes the Action, the terms of the Settlements, and your rights and options in connection with the Settlements. More details are in the Settlement Agreements, which are available for your review at xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx. The Settlement Website also has the Second Amended Complaint and other documents relating to the Settlements. You may also call toll-free 0-000-000-0000 or write the Claims Administrator at: Financial Aid Antitrust Settlements, c/o Claims Administrator, 0000 Xxxx Xxxxxx, Xxxxx 0000, Xxxxxxxxxxxx, XX 00000. To: Settlement Class Member Email Address From: Claims Administrator Subject: Notice of Proposed Class Action Settlement – Xxxxx, et al. x. Xxxxx University, et al. Please visit xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx for more information. • The Court has preliminarily approved proposed settlements (“Settlements”) with the following ten schools: Brown University, the University of Chicago, the Trustees of Columbia University in the City of New York, Trustees of Dartmouth College, Duke University, Emory University, Northwestern University, Xxxxxxx Xxxxx Xxxx University, Vanderbilt University, and Yale University (collectively the “Settling Universities”). • The Court has also preliminarily approved a class of students who attended one or more of the Settling Universities during certain time periods. This is referred to as the “Settlement Class,” which is defined in more detail below.
Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes
Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 ARTICLE VII BLV/BLVI TRAFFIC 16 7.1 Busy Line Verification 16 7.2 Busy Line Verification Interrupt 16 7.3 BLV/BLVI Traffic 16 7.4 BLV/BLVI Compensation 16
EDD Independent Subrecipient Reporting Requirements Effective January 1, 2001, the County of Orange is required to file in accordance with subdivision (a) of Section 6041A of the Internal Revenue Code for services received from a “service provider” to whom the County pays $600 or more or with whom the County enters into a contract for $600 or more within a single calendar year. The purpose of this reporting requirement is to increase child support collection by helping to locate parents who are delinquent in their child support obligations. The term “service provider” is defined in California Unemployment Insurance Code Section 1088.8, Subparagraph B.2 as “an individual who is not an employee of the service recipient for California purposes and who received compensation or executes a contract for services performed for that service recipient within or without the State.” The term is further defined by the California Employment Development Department to refer specifically to independent Subrecipients. An independent Subrecipient is defined as “an individual who is not an employee of the ... government entity for California purposes and who receives compensation or executes a contract for services performed for that ... government entity either in or outside of California.” The reporting requirement does not apply to corporations, general partnerships, limited liability partnerships, and limited liability companies. Additional information on this reporting requirement can be found at the California Employment Development Department web site located at xxxx://xxx.xxx.xx.xxx/Employer_Services.htm
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8 and Applicable Law, Verizon grants to Reconex a non-exclusive license to use Verizon OSS Information. 8.5.2 All Verizon OSS Information shall at all times remain the property of Verizon. Except as expressly stated in this Section 8, Reconex shall acquire no rights in or to any Verizon OSS Information. 8.5.2.1 The provisions of this Section 8.5.2 shall apply to all Verizon OSS Information, except (a) Reconex Usage Information, (b) CPNI of Reconex, and (c) CPNI of a Verizon Customer or a Reconex Customer, to the extent the Customer has authorized Reconex to use the Customer Information. 8.5.2.2 Verizon OSS Information may be accessed and used by Reconex only to provide Telecommunications Services to Reconex Customers. 8.5.2.3 Reconex shall treat Verizon OSS Information that is designated by Verizon, through written or electronic notice (including, but not limited to, through the Verizon OSS Services), as “Confidential” or “Proprietary” as Confidential Information of Verizon pursuant to Section 10 of the Agreement. 8.5.2.4 Except as expressly stated in this Section 8, this Agreement does not grant to Reconex any right or license to grant sublicenses to other persons, or permission to other persons (except Reconex’s employees, agents or contractors, in accordance with Section 8.5.2.5 below, to access, use or disclose Verizon OSS Information. 8.5.2.5 Reconex’s employees, agents and contractors may access, use and disclose Verizon OSS Information only to the extent necessary for Reconex’s access to, and use and disclosure of, Verizon OSS Information permitted by this Section 8. Any access to, or use or disclosure of, Verizon OSS Information by Reconex’s employees, agents or contractors, shall be subject to the provisions of this Agreement, including, but not limited to, Section 10 of the Agreement and Section 8.5.2.3 above. 8.5.2.6 Reconex’s license to use Verizon OSS Information shall expire upon the earliest of: (a) the time when the Verizon OSS Information is no longer needed by Reconex to provide Telecommunications Services to Reconex Customers; (b) termination of the license in accordance with this Section 8; or (c) expiration or termination of the Agreement. 8.5.2.7 All Verizon OSS Information received by Reconex shall be destroyed or returned by Reconex to Verizon, upon expiration, suspension or termination of the license to use such Verizon OSS Information. 8.5.3 Unless sooner terminated or suspended in accordance with the Agreement or this Section 8 (including, but not limited to, Section 2.2 of the Agreement and Section 8.6.1 below), Reconex’s access to Verizon OSS Information through Verizon OSS Services shall terminate upon the expiration or termination of the Agreement. 8.5.3.1 Verizon shall have the right (but not the obligation) to audit Reconex to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement with regard to Reconex’s access to, and use and disclosure of, Verizon OSS Information. 8.5.3.2 Without in any way limiting any other rights Verizon may have under the Agreement or Applicable Law, Verizon shall have the right (but not the obligation) to monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex pursuant to this Agreement, to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement, with regard to Reconex’s access to, and use and disclosure of, such Verizon OSS Information. The foregoing right shall include, but not be limited to, the right (but not the obligation) to electronically monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex through Verizon OSS Facilities. 8.5.3.3 Information obtained by Verizon pursuant to this Section 8.5.3.3 shall be treated by Verizon as Confidential Information of Reconex pursuant to Section 10 of the Agreement; provided that, Verizon shall have the right (but not the obligation) to use and disclose information obtained by Verizon pursuant to this Section 8.5.3.3 to enforce Verizon’s rights under the Agreement or Applicable Law.
LIFE COMPANY TO PROVIDE DOCUMENTS; INFORMATION ABOUT AVIF (a) LIFE COMPANY will provide to AVIF or its designated agent at least one (1) complete copy of all SEC registration statements, Account Prospectuses, reports, any preliminary and final voting instruction solicitation material, applications for exemptions, requests for no-action letters, and all amendments to any of the above, that relate to each Account or the Contracts, contemporaneously with the filing of such document with the SEC or other regulatory authorities. (b) LIFE COMPANY will provide to AVIF or its designated agent at least one (1) complete copy of each piece of sales literature or other promotional material in which AVIF or any of its affiliates is named, at least five (5) Business Days prior to its use or such shorter period as the Parties hereto may, from time to time, agree upon. No such material shall be used if AVIF or its designated agent objects to such use within five (5) Business Days after receipt of such material or such shorter period as the Parties hereto may, from time to time, agree upon. AVIF hereby designates INVESCO as the entity to receive such sales literature, until such time as AVIF appoints another designated agent by giving notice to LIFE COMPANY in the manner required by Section 9 hereof. (c) Neither LIFE COMPANY nor any of its affiliates, will give any information or make any representations or statements on behalf of or concerning AVIF or its affiliates in connection with the sale of the Contracts other than (i) the information or representations contained in the registration statement, including the AVIF Prospectus contained therein, relating to Shares, as such registration statement and AVIF Prospectus may be amended from time to time; or (ii) in reports or proxy materials for AVIF ; or (iii) in published reports for AVIF that are in the public domain and approved by AVIF for distribution; or (iv) in sales literature or other promotional material approved by AVIF , except with the express written permission of AVIF . (d) LIFE COMPANY shall adopt and implement procedures reasonably designed to ensure that information concerning AVIF and its affiliates that is intended for use only by brokers or agents selling the Contracts (i.e., information that is not intended for distribution to Participants) (“broker only materials”) is so used, and neither AVIF nor any of its affiliates shall be liable for any losses, damages or expenses relating to the improper use of such broker only materials. (e) For the purposes of this Section 4.5, the phrase “sales literature or other promotional material” includes, but is not limited to, advertisements (such as material published, or designed for use in, a newspaper, magazine, or other periodical, radio, television, telephone or tape recording, videotape display, signs or billboards, motion pictures, or other public media, (e.g., on-line networks such as the Internet or other electronic messages), sales literature (i.e., any written communication distributed or made generally available to customers or the public, including brochures, circulars, research reports, market letters, form letters, seminar texts, reprints or excerpts of any other advertisement, sales literature, or published article), educational or training materials or other communications distributed or made generally available to some or all agents or employees, registration statements, prospectuses, statements of additional information, shareholder reports, and proxy materials and any other material constituting sales literature or advertising under FINRA rules, the 1933 Act, or the 0000 Xxx.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.