BORDER GATEWAY PROTOCOL Sample Clauses

The Border Gateway Protocol (BGP) clause defines the rules and requirements for the use and management of BGP in network operations. It typically outlines responsibilities for configuring, maintaining, and securing BGP sessions between parties, and may specify standards for route advertisement, filtering, and incident response. This clause ensures reliable and secure routing of data between autonomous systems, helping to prevent misconfigurations or malicious activities that could disrupt network connectivity.
BORDER GATEWAY PROTOCOL. 14.1.1 The following BGP protocol protection functions (without limitation) should be implemented at the stage of project designing: bgp neighbor impersonation attack and resetting transmission control protocol; transmission control protocol session attack using internet control message protocol; bgp session theft attack; route "rocking"; route degradation; unauthorized route announcement; service rejection due to exhausted resources; 14.1.2 Implement secure BGP model including, but not limited to the following: iBGP should not contain synchronization (Internal BGP); disable «Fast external failover» function to prevent route change due to BGP neighbor temporary disruptions in sending «keepalives communication" packets; enable registering change in BGP neighbor status; use soft reconfiguration; use authentication; disable matching BGP versions to accelerate start process; block incoming route updates from fraudulent prefixes; use restriction on the maximum prefix number to avoid inflating Routing Table; use loopback interface for IBGP announcements; disable automatic summation prefix announcements; allow BGP neighbors establishing connection using only port TCP 179; use prefix lists to restrict announcing only selected prefixes.
View Source

Related to BORDER GATEWAY PROTOCOL

  • Network Interconnection Methods 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Network PHARMACY is a retail, mail order or specialty pharmacy that has a contract to accept our pharmacy allowance for prescription drugs and diabetic equipment or supplies covered under this plan. NETWORK PROVIDER is a provider that has entered into a contract with us or other Blue Cross and Blue Shield plans. For pediatric dental care services, network provider is a dentist that has entered into a contract with us or participates in the Dental Coast to Coast Network. For pediatric vision hardware services, a network provider is a provider that has entered into a contract with EyeMed, our vision care service manager.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

  • NON-NETWORK PROVIDER is a provider that has not entered into a contract with us or any other Blue Cross and Blue Shield plan. For pediatric dental care services, non-network provider is a dentist that has not entered into a contract with us or does not participate in the Dental Coast to Coast Network. For pediatric vision hardware services, a non-network provider is a provider that has not entered into a contract with EyeMed, our vision care service manager.