Network Connections Clause Samples

Network Connections. The user agrees that they will be responsible for providing, maintaining, and supporting a connection to the ▇▇▇.▇▇▇ system via the Internet. The system administrator will be responsible for providing, maintaining, and supporting the ▇▇▇.▇▇▇ system and its connection to the Internet

Network Connections. 3.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users and/or utilize the other Party’s facilities for a transiting function, each Party, at a minimum, will: 3.1.1 Route such traffic via direct network facilities to either a) each others access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see section 3.2.2 for exclusions); or b) another mutually agreed upon point. 3.1.1.1 Specific facility arrangements required to interconnect the Parties’ networks shall be negotiated by the Parties’. Where the LEC providing FX-NXX service, also operates as a CLEC within SBC ILEC exchange, and whose switch is located in the SBC ILEC exchange; the existing interconnection facility between the parties’ within the SBC ILEC exchange may be considered as an option for interconnection, provided a separate and distinct portion of this existing facility can be established as further defined below in section 3.5. 3.1.1.2 For FX-NXX service, the interconnection facilities and trunks between the Parties’ networks shall only be used for traffic exchanged between the Parties’. No Third Party traffic shall be routed over these facilities, except where ICG is unable to interconnect with Rural/Independent Telecommunications Carriers (or any other “exempted” carriers). Notwithstanding this exception, ICG will exert reasonable effort to interconnect with such Carriers. 3.1.2 Route such traffic to the other Party utilizing a Third Party incumbent LECs facilities and/or utilizing another Third Party Telecommunications Carrier’s facilities with whom the Party already has an agreement for exchanging like traffic. The Parties acknowledge and agree that this option may not be implemented without the written agreement of the Third Party incumbent LEC and/or Telecommunications Carrier as well as the mutual consent of each of the Parties. The Parties further agree that in order for this option to be considered, it is the responsibility of the originating Party to obtain the required written permission from the Third Party incumbent LEC and/or Telecommunications Carrier. 3.2 The Parties acknowledge and agree that when traffic destined for an SBC ILEC tandem exceeds a DS1’s amount of traffic and/or that it is more efficient to connect via direct End Office connections, ICG shall establish a direct End Office trunk group and provide transp...

Network Connections. 4.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users, each Party, at a minimum, will: 4.1.1 Route such traffic via direct network facilities to either a) each others access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see Section 4.2.2 for exclusions); or b) another mutually agreed upon point.

Network Connections. If a network connection is established between ▇▇▇▇▇ Fargo and the computing environment(s) used by Vendor or Vendor Personnel to perform the Program Development Services, Vendor agrees, for itself and all Vendor Personnel, to (1) allow ▇▇▇▇▇ Fargo to perform network assessments of such computing environment(s) based on a mutually-agreed schedule, and (2) maintain an alert status regarding the security of such computing environments, including without limitation all vulnerabilities and security patches or corrective actions, by subscribing to an industry-recognized service, such as CERT or CIAC. Vendor understands that, should a ▇▇▇▇▇ Fargo assessment reveal inappropriate or inadequate security based on the pre-defined requirements for security, ▇▇▇▇▇ Fargo may, in addition to other remedies it may have, remove access by Vendor Personnel to the ▇▇▇▇▇ Fargo network until Vendor Personnel satisfactorily comply with the security requirements defined.

Network Connections. 4.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users, each Party, at a minimum, will: 4.1.1 Route such traffic via direct network facilities to either a) each other’s access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see Section 4.2.2 for exclusions); or b) another mutually agreed upon point. . 4.1.1.1 For FX-NXX service, the interconnection facilities and trunks between the Parties’ networks shall only be used for traffic exchanged between the Parties’. No Third Party traffic shall be routed over these facilities. 4.2 Except as otherwise provided in this Agreement, the Parties understand and agree that either Party, upon ten (10) days notice to the other Party where regulatory environment permits, may block any traffic that is improperly routed over any trunk groups and/or which is routed outside of the mutual agreement of the Parties. 4.3 AT&T-21STATE shall not compensate any Third Party Incumbent Carrier and/or Telecommunications Carrier for Local, EAS, Toll, IXC or any other traffic that is inappropriately routed to AT&T-21STATE (as reflected in the LERG). Any compensation due AT&T-21STATE for such misrouted traffic shall be paid by ILEC, unless otherwise agreed to in writing by both Parties. The appropriateness of such routing and the correct AT&T-21STATE serving tandems are reflected by AT&T-21STATE in the LERG. This also includes traffic that is destined to End Offices that do not subtend AT&T-21STATE tandem. 4.4 Within thirty (30) days from the Effective Date of this Agreement, the Parties agree to have met and developed joint planning and forecasting responsibilities which are applicable to services described in this Agreement, if necessary. Either Party may delay processing the other Party’s service orders should the Parties not perform obligations as specified in this Section. Such responsibilities shall include but are not limited to the following: 4.4.1 The Parties will establish periodic reviews of network and technology plans and will notify one another no later than six (6) months in advance of changes that would impact either Party’s provision of services. 4.4.2 The Parties will furnish to each other, information that provides for state-wide annual forecasts of order activity, in-service quantity forecasts, and facility/demand forecasts. 4.4.3 The Parties will develop join...

Network Connections a. No device shall be connected to a Cingular Wireless network, including LANs and switching elements, without the knowledge of, and permission from, the network's administrator. b. Persons using remote, e.g., in-dial, ISDN, wireless or other public switched network access shall be individually identified and authenticated by an independent dedicated access control device such as a network access controller. The remote authentication process must utilize a dynamic password, such as a token card. This requirement may be met independently by the Contractor or Supplier's Employees and Subcontractors, or by utilization of a Cingular Wireless system or network access device provided for such purposes. c. Internet (including VPN), extranet, or other direct network access arrangements shall be approved by the Cingular Wireless Corporate Security Team prior to implementation. ------------------------------------------------------------------------------- Revision 1: June 5, 2001 35 [CINGULAR WIRELESS LOGO] SECTION 1: SECTION 2: ------------------------------------------------------------------------------- 400-200-TR - SECURITY REQUIREMENTS FOR PURCHASED OR EXTERNALLY DEVELOPED COMPUTER SYSTEMS, APPLICATIONS AND SOFTWARE ------------------------------------------------------------------------------- Approval shall be obtained through the use of a waiver as described earlier in this document. d. Remote access connections to Cingular Wireless internal networks are prohibited unless special arrangements are approved by the Cingular Wireless Corporate Security Team well in advance of the needed access. This includes any provision for remote application or system support, development, and/or other miscellaneous access. Types of remote access may include but are not limited to direct connections or Internet based connections. Approval shall be obtained through the use of a waiver as described earlier in this document. e. Cingular Wireless's internal IP networks may make use of internal firewalls to form IP partitions. The supplier shall document the compatibility of their product with firewalls for IP networks and that documentation shall be submitted to Cingular Wireless for approval prior to execution of the Agreement. Examples of incompatibility include the use of port or socket negotiation for communication, e.g. rpc's and portmapper. f. Use of UDP shall be avoided where possible. g. Any and all traffic traversing a remote access link to a Cingular Wireless internal...

Network Connections. 1. UMD, at its sole cost and expense, will provide the County with a i. Ten-Gigabit Ethernet port, owned by UMD, to the County-owned networking equipment located in the NOC. The County shall have at all times full control of the port, which may be used and changed as determined by the County. Additionally, at no cost to the County, UMD shall provide the County with: a. MAX Layer 3 IP routing which shall include the following: i. Layer 2 Ethernet services; ii. A One-Gigabit Layer 2 VLAN to Amazon Web Services (“AWS”) via the MAX AWS Direct Connect Service; and, iii. Access to Internet2 as well as other Layer 3 routes on the MAX network. County is responsible for fees charged by Internet2 and other organizations to access their infrastructure. 2. Primary internet service to the County is not offered by UMD as part of this MOU. If the County desires connections to services other than those described in subsection C.1 above, then the County will pay for such services, and corresponding connections to obtain such services. The County will be required to pay for any connection or service fees charged to the County by any service providers for the County to obtain services from such providers. 3. UMD shall not be liable to the County for any non-UMD activity associated with the County’s Amazon and Cloud user accounts for the AWS connection through AWS Direct Connect.

Network Connections. InterCept will connect the Terminals to -shared -------------------- transaction networks on behalf of the Customer. InterCept will comply with all network operating system regulations and maintain communications with the network for transaction authorization purposes. InterCept will forward all transaction requests from each Terminal to the appropriate shared network for authorization. InterCept will monitor and log all transaction requests regardless of disposition for reporting and balancing purposes.

Network Connections. As part of this Master Services Agreement, Customer may be required to connect to NeuStar’s system. (a) Customer may only use the network connection to NeuStar’s systems (“Network Connection”) for the specific lawful business purposes outlined in this Master Services Agreement, or in any applicable Service Agreements or Addenda. (b) Customer shall not use the Network Connection or its equipment or systems in a way that interferes in any way with or adversely affects the use of the NeuStar network by NeuStar or any other authorized third party user of the NeuStar network. (c) Upon prior written notice by NeuStar, Customer shall promptly remove any interference or service obstruction that may be caused by hardware, software or connectivity, owned by or under the control of Customer or any of its representatives, agents or contractors. If Customer fails to remove any interference or service obstruction in a reasonably timely manner, NeuStar may take any and all reasonable steps necessary to remedy the interference or service obstruction, at Customer’s expense, with no liability to NeuStar. Additionally, if the interference or service obstruction creates an emergency or urgent situation, NeuStar may take any and all reasonable steps necessary to remedy the interference or service obstruction, at Customer’s expense, with no liability to NeuStar. (d) Each party shall take all reasonable precautions not to disturb or interfere with the other party’s services or property, unless such disturbance or interference is deemed to be necessary for control of the use of NeuStar’s network and the party is notified in advance. (e) Customer will allow only authorized employees or agents to access the Network Connection. Customer shall be solely responsible for ensuring that such employees or agents are not security risks. (f) Each party will adhere to generally accepted industry best practices relating to network security and data privacy as they relate to the Network Connection and shall be solely responsible for the selection, implementation, and maintenance of security procedures and policies that are sufficient to ensure that (a) such party’s use of the Network Connection (and Customer’s use of NeuStar-owned equipment) is secure, including protected from viruses and other malicious code or attacks, and is used only for authorized purposes, and (b) such party’s business records and data are protected against improper access, use, loss alteration or destruction.