MPS LOGO/PUBLICITY No Contractor shall use the MPS Logo in its literature or issue a press release about the subject of this Contract without prior written notice to and written approval of MPS’s Executive Director of Communications & Outreach.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)
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.
Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting
Press Releases The Company agrees that it will not issue press releases or engage in any other publicity, without the Representative’s prior written consent (not to be unreasonably withheld), for a period of twenty-five (25) days after the Closing Date. Notwithstanding the foregoing, in no event shall the Company be prohibited from issuing any press releases or engaging in any other publicity required by law, except that including the name of any Underwriter therein shall require the prior written consent of such Underwriter.
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.
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. EXHIBIT B 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 six schools: Brown University, the University of Chicago, the Trustees of Columbia University in the City of New York, Duke University, Emory 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.
Joint Press Release If requested by a party, the parties shall issue a joint press release announcing the execution of this Agreement in substantially the form(s) mutually agreed upon by the parties.
DNSSEC Registry Operator shall sign its TLD zone files implementing Domain Name System Security Extensions (“DNSSEC”). During the Term, Registry Operator shall comply with RFCs 4033, 4034, 4035, 4509 and their successors, and follow the best practices described in RFC 4641 and its successors. If Registry Operator implements Hashed Authenticated Denial of Existence for DNS Security Extensions, it shall comply with RFC 5155 and its successors. Registry Operator shall accept public-‐key material from child domain names in a secure manner according to industry best practices. Registry shall also publish in its website the DNSSEC Practice Statements (DPS) describing critical security controls and procedures for key material storage, access and usage for its own keys and secure acceptance of registrants’ public-‐key material. Registry Operator shall publish its DPS following the format described in XXX 0000.
