Network Presence Clause Samples

Network Presence. In the event that AMS fails to use commercially reasonable efforts to maintain the network presence of the IETF in the cited areas in accordance with guidelines established in accordance with section 3C.1.a of the SOW, AMS shall credit ISOC the amount set forth in the SLA Schedule. SLA 57: Trouble Ticketing Service. In the event that AMS fails to perform the infrastructure and clerical services set forth in Section 3C 1.d and 3C.2.b of the SOW, AMS shall credit ISOC the amount set forth in the SLA Schedule. SLA 58: Capacity of 50,000 messages per hour. In the event that AMS fails to provide the capacity for the IETF mailing lists to handle 50,000 messages per hour as set forth in Section 3C 3.c of the SOW, AMS shall credit ISOC the amount set forth in the SLA Schedule. SLA 59: Ability to host Mailing Lists. In the event that AMS is unable to host all of the active IETF mailing lists as set forth in Section 3C 3.c of the SOW, AMS shall credit ISOC the amount set forth in the SLA Schedule. SLA 60: Maintenance of Web-based mailing lists. In the event that Web-based mailing lists are not available for at least 99.5% of the time measured on a monthly basis as set forth in Section 3C 3.c of the SOW, AMS shall credit ISOC the amount set forth in the SLA Schedule. Availability shall be measured in the same manner as set forth in SLA 55. SLA 61: Implementation of Spam Filtering. In the event that AMS fails to use commercially reasonably spam filtering measures, including, at a minimum, those spam filtering
View SourceView Similar (2)
Network Presence. Contractor shall provide a reliable and resilient network presence for the website and the following technical services: i. co-location, providing at least two (2) independent sites (separate power grids and widely separate geographic locations) capable of serving 100+ Mb/sec of data (i.e., located on different subnets and/or with different service providers), designed for scalable access and resistance to denial of service attacks. ii. secure name service [RFC 4035 and references], iii. routing, iv. transit, v. monitoring & security, vi. provisioning core services such as rsync and FTP, and
View SourceView Similar (2)
Network Presence. In the event that Contractor fails to use commercially reasonable efforts to maintain the network presence of the IETF in the cited areas in accordance with guidelines established in accordance with Section II.C.1.a of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 57: Trouble Ticketing Service. In the event that Contractor fails to provide the trouble ticketing services and perform the customer support services as set forth Section III.C.4 of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 58: Capacity of 50,000 messages per hour. In the event that Contractor fails to provide the capacity for the IETF mailing lists as set forth in Section III.C.1.c.i of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 59: Ability to host Mailing Lists. In the event that Contractor is unable to host all of the active IETF mailing lists as set forth in Section III.C.1.c.ii of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 60: Maintenance of Web-based mailing lists. In the event that Web-based mailing lists as set forth in Section III.C.1.c.iii of the SOW are not available for at least 99.5% of the time measured on a monthly basis, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. Availability shall be measured in the same manner as set forth in SLA 56. SLA 61: Implementation of Spam Filtering. In the event that Contractor fails to use commercially reasonably spam filtering measures as set forth in Section III.C.1.c.vii of the SOW, including, at a minimum, those spam filtering measures equivalent to the measures Contractor takes to protect its own internal and external mailing lists, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 62: Dual Redundant Systems. In the event that Contractor fails to provide dual redundant systems as set forth in Section III.C.1.c.v of the SOW of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 63: Instant Messaging Service. In the event that Contractor fails to maintain an instant messaging service that provides for chat sessions for meetings as set forth in Section III.C.1.e of the SOW, Contractor shall credit IETF LLC the amount set forth in the SLA Schedule. SLA 64: Subdomain Support. In the event that Contractor fails to provide DNS authorization and DNS support for IETF subdomains in accor...
View Source
Network Presence. The Vendor shall provide a reliable and resilient network presence for the website and the following technical services: (i) co-location, providing at least two (2) independent sites (separate power grids and separate geographic locations) capable of serving 10+ Mb/sec of data (i.e., located on different subnets and/or with different service providers), (ii) secure name service [RFC 4035 and references], (iii) routing, (iv) transit, (v) monitoring & security, (vi) provisioning core services such as rsync and FTP, and (vii) cooperation and coordination with mirror sites. The Vendor is required to provide in its offer the network and infrastructure measurements and Service Level Agreements it is prepared to deliver and maintain.
View Source
Network Presence. The Vendor shall provide a reliable and resilient network presence for the website and the following technical services: (i) co-location, (ii) secure name service [RFC 4035 and references], (iii) routing, (iv) transit, (v) monitoring & security, (vi) provisioning core services such as rsync and FTP, and (vii) cooperation and coordination with mirror sites. The Vendor is required to provide in its offer the network and infrastructure measurements and Service Level Agreements it is prepared to deliver and maintain.
View Source

Related to Network Presence

  • Network Management 56.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement. 56.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink. 56.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers. 56.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied. 56.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service. 56.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users. 56.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • WASHINGTON’S ELECTRONIC BUSINESS SOLUTION (WEBS). Contractor represents and warrants that Contractor is registered in Washington’s Electronic Business Solution (WEBS), Washington’s contract registration system and that, all of Contractor’s information therein is current and accurate and that throughout the term of this Contract, Contractor shall maintain an accurate profile in WEBS.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Cellular Telephone Executive shall receive reimbursement for reasonable expenses associated with Executive's use of a cellular telephone in performing his services.