BGP Community Tags for Routing Propagation Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In data center environments, customers require stringent performance, reliability, and security for network connectivity, which is not adequately met by public Internet connections, necessitating dedicated physical network links and controlled routing information propagation between client and provider networks.
Innovation Solution
The use of BGP community tags to manage the distribution of routing information between client and provider networks connected via dedicated physical connections, allowing customers to control the propagation scope of their routing information within the provider network by including tag field values in routing protocol messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If routing information is propagated throughout the entire provider network, then network connectivity and resource accessibility are improved, but network security and isolation are worsened
Solution Approach 1:
The provider network is segmented into multiple regions or areas, and routing information propagation is controlled at this segmented level. The BGP community tags enable selective propagation of routing information to specific regions, allowing the network to be divided into secure zones while maintaining connectivity where needed.
Solution Approach 2:
Different regions of the provider network are assigned different propagation characteristics based on local requirements. By using BGP community tags, each region can receive routing information appropriate to its location and security requirements, creating local quality differences in routing behavior across the network.
2Reliability
If dedicated physical network links are established between client and provider networks, then network reliability and security are improved, but device complexity and configuration requirements are worsened
Solution Approach 1:
BGP community tags serve as an intermediary mechanism that simplifies the configuration of dedicated physical network links. Instead of requiring complex direct configuration between client and provider networks, the community tags act as a mediating layer that encodes propagation preferences, making the dedicated link configuration more manageable while maintaining reliability.
3Object-affected harmful factors
If routing information is limited to specific regions, then network isolation and security are improved, but network versatility and resource accessibility are worsened
Solution Approach 1:
The routing information propagation is made dynamic through BGP community tags that can be assigned and modified based on changing network requirements. This allows the isolation boundaries to be dynamically adjusted, enabling the network to adapt between more isolated and more connected states as business needs change.
Solution Approach 2:
The propagation scope of routing information is controlled by changing parameters in BGP community tags. By modifying these tag parameters, the network can adjust the geographical or logical scope of routing information propagation, allowing flexible control over the balance between isolation and accessibility.
Data Source
AI summary
A system includes a provider network and a client network connected via a dedicated physical connection. The client network and the provider network exchange routing information using routing protocol messages, such as border gateway protocol (BGP) update messages exchanged during a BGP session. A provider network includes tag field values in outgoing routing protocol messages that indicate a portion of the provider network wherein resources of the provider network associated with a corresponding route are located. The client network may use the tag field value to determine whether to add the route to a routing table of the client network. A client network may also include tag field values in outgoing routing protocol messages to a provider network. The tag field values may indicate what portions of the provider network are to receive the routes from the client network. For example a tag field value may indicate that a route is to be propagated within a limited portion of the provider network.