{"id":24922,"date":"2026-10-11T10:26:48","date_gmt":"2026-10-11T10:26:48","guid":{"rendered":"https:\/\/atalnetworks.com\/?p=24922"},"modified":"2026-10-11T10:28:59","modified_gmt":"2026-10-11T10:28:59","slug":"bgp-communities-for-multi-provider-networks","status":"publish","type":"post","link":"https:\/\/atalnetworks.com\/fr\/bgp-communities-for-multi-provider-networks\/","title":{"rendered":"BGP Communities for Multi-Provider Networks: A Traffic-Policy Guide"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">BGP communities attach policy information to route announcements. A provider can use documented values to adjust route preference, limit advertisements, or apply other agreed actions. They help us influence routing, but they do not give us control over every network along a path.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Using <a href=\"https:\/\/atalnetworks.com\/how-asn-and-bgp-planning-affect-dedicated-server-deployments\/\">BGP<\/a> communities for traffic engineering starts with three questions: which traffic direction needs to change, which network must act, and which documented control supports that goal?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This guide helps you prepare those requirements for <a href=\"https:\/\/atalnetworks.com\/\">Atal Networks<\/a>, compare provider policies, and test changes before relying on them.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Match the Routing Goal to the Right Control<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A multi-provider design gives us alternative connections. Routing policy determines how we use them.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Our objective<\/b><\/th>\n<th><b>Control to assess<\/b><\/th>\n<th><b>Detail to confirm<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Choose a connection for outbound traffic<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Our import policy and local preference<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Available routes and policy order<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Influence traffic arriving through a provider<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Provider local-preference community<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Supported values and alternative paths<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Limit advertisements to selected neighbors<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Selective export community<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Targets, exceptions, and precedence<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Make an advertised path less attractive<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Targeted AS-path prepending<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Scope and which ASN the provider repeats<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Drain traffic before maintenance<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Graceful-shutdown support<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Receiver behavior and backup capacity<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Discard traffic during an incident<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Authorized blackhole service<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Activation, prefix rules, and removal<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Treat this table as a planning checklist. Confirm each feature for the actual service, location, session, and address family.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">1. Understand the Information a BGP Community Carries<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A community labels a BGP route. It does not label each packet or reserve bandwidth.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We can attach several communities to an announcement. A receiving router then applies policies that match those values.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Two uses matter most:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Informational communities<\/b><span style=\"font-weight: 400;\"> describe a route, such as its entry location or whether the provider learned it from a customer or peer.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Action communities<\/b><span style=\"font-weight: 400;\"> request a documented change, such as lowering preference or suppressing an advertisement.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">An informational tag can help us choose an outbound route. An action tag on our own prefix can influence how a provider handles traffic toward us.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The value itself does not create a custom action. The receiving network must support a matching policy.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">2. Compare Community Formats and Provider Definitions<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Standard, extended, and large communities describe different encodings. Provider-defined describes meaning.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Format<\/b><\/th>\n<th><b>Size per value<\/b><\/th>\n<th><b>Common use<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Standard<\/span><\/td>\n<td><span style=\"font-weight: 400;\">32 bits<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Two 16-bit fields commonly displayed as A:B<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Extended<\/span><\/td>\n<td><span style=\"font-weight: 400;\">64 bits under RFC 4360<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Typed policy information, including route targets<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Large<\/span><\/td>\n<td><span style=\"font-weight: 400;\">96 bits<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Three 32-bit fields displayed as A:B:C<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Large communities allow a full four-octet ASN in the administrator field. A network with a four-octet ASN can still use standard communities through a documented numbering scheme, but that full ASN cannot fit in a 16-bit field. [1][2][3]<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Read the Meaning, Scope, and Exceptions<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">For every value, record the requested action, eligible session, target neighbors, geographic scope, and address-family support.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Also check how the provider handles conflicting communities. The order in which values appear does not establish policy priority.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Router behavior matters too. Confirm whether the session sends the required community types and whether a policy adds to or replaces existing values. Do not assume identical defaults across platforms.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Providers may remove action communities after processing them. A tag does not need to remain visible across the Internet for the intended action to have occurred.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">3. Separate Our Local Preference From the Provider\u2019s<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Traffic direction causes many routing-policy mistakes. Always name the network whose inbound or outbound traffic we mean.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Our Local Preference Influences Our Outbound Traffic<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Suppose we receive a route through Providers A and B. Our import policy can assign a higher local preference to A\u2019s route, making it preferred within our AS when other eligibility conditions permit.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This controls our route choice for traffic leaving our network. It does not directly choose the return path.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">LOCAL_PREF stays within an AS under ordinary external BGP operation. We cannot send our preferred value to an unrelated provider and expect it to adopt that value. [4]<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Provider Communities Can Influence Traffic Toward Us<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A provider may accept a community that lowers its local preference for our announced prefix.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That can make another eligible route more attractive inside the provider\u2019s network. The result depends on the available alternatives and the provider\u2019s policy.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, lowering a route below another customer route differs from lowering it below routes learned from peers. Ask which preference class the community selects.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Remote networks still make their own choices. A provider accepting our community does not guarantee a particular global traffic split.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Prepending and MED Have Different Limits<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">AS-path prepending makes a path appear longer. It may influence a network that considers path length after higher-priority decisions, but it may do nothing when local preference already decides the outcome.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">MED can express a preferred entry point under applicable comparison rules. Do not treat it as a universal control across unrelated providers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We should choose the mechanism that matches the routing problem, then measure the result. Adding more prepends without checking the selected path can leave the original problem unchanged. [5]<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">4. Plan Selective Route Advertisement<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Selective export communities can ask a provider to advertise a prefix to some neighbors and withhold it from others.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Possible targets include peers, customers, transit providers, individual ASNs, or route-server clients. Each provider defines the available groups.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An instruction to stop advertising to one direct neighbor does not guarantee that the neighbor\u2019s ASN disappears from every possible Internet path.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Distinguish NO_EXPORT From NO_ADVERTISE<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">These standard communities have different boundaries:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>NO_EXPORT:<\/b><span style=\"font-weight: 400;\"> Do not advertise the route beyond the BGP confederation boundary. For a standalone AS, that means its AS boundary.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>NO_ADVERTISE:<\/b><span style=\"font-weight: 400;\"> Do not advertise the route to any BGP peer. [1]<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Provider-specific commands such as \u201cdo not announce to this upstream\u201d offer a different scope.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Before restricting exports, check which backup routes remain. Suppressing the only usable advertisement can remove reachability rather than improve a path.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Check Rule Precedence<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">An allow instruction may override a broader suppress instruction, or the reverse. Follow the provider\u2019s documented order.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">NTT, for example, publishes precedence rules for overlapping customer communities. GTT states that certain prepend communities affect peering partners but not customers. These differences make copying a policy between providers unreliable. [6][7]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For exchange connections, distinguish the route server from the forwarding path. A route server normally exchanges routing information without carrying the resulting user traffic.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">5. Map Regional and Upstream Policies<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">\u201cPrefer this location\u201d and \u201cadvertise only from this location\u201d are different requests.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The first may leave other paths available with lower preference. The second may remove advertisements that would otherwise provide a fallback.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A regional tag also uses the provider\u2019s definition of a region. It does not guarantee that every packet remains within that geography or establish data residency.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">A Two-Provider Planning Example<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Consider this fictional network:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Customer: AS64496.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provider A: AS64497.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provider B: AS64498.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Example prefix: 192.0.2.0\/24.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">These values serve documentation only. Do not announce this prefix on the public Internet.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Our goal is to influence selected inbound traffic toward A while retaining B as a backup.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We first confirm that B offers a suitable preference-reduction community. Then we check whether B can learn an eligible alternative path through A and whether that path has enough capacity.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We apply B\u2019s documented action to the intended announcement and inspect B\u2019s route choice. External observations and traffic measurements show whether the change achieves our goal.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Finally, we test loss of A and restoration of A. A policy that works during normal operation may behave differently after a failure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Use the actual provider\u2019s documented value during deployment. A label such as PROVIDER_B_BACKUP_ACTION is only a planning placeholder.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Keep Maintenance and Incident Controls Separate<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The graceful-shutdown community, 65535:0, supports planned traffic draining when the receiving network implements the relevant policy and usable alternatives exist. It does not promise interruption-free maintenance. [8]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The BLACKHOLE community, 65535:666, requests discard behavior under an agreed service. Confirm authorization, accepted prefix lengths, and scope before use. Blackholing drops legitimate traffic along with unwanted traffic; it differs from attack scrubbing. [9]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Ask whether incident handling can override location or export restrictions.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">6. Check IPv4 and IPv6 Independently<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A successful IPv4 test does not prove that IPv6 behaves the same way.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Confirm community support, route filters, session configuration, and next-hop reachability for each address family. Large communities are not specific to IPv6.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Prefix acceptance also needs separate checks. Many networks filter ordinary IPv4 routes longer than \/24 and IPv6 routes longer than \/48, but these are common practices rather than universal guarantees. Confirm your providers\u2019 current policies and test visibility. [10]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Blackhole services may accept host routes under separate rules. Do not assume those exceptions apply to normal advertisements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Also examine aggregates and more-specific routes. Packet forwarding uses the longest matching prefix, so a more-specific route can change the result even when the aggregate has a different preference.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">7. Confirm ASN and Prefix Prerequisites<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Community policy only matters after a provider accepts the route.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Identify the intended origin ASN, any different session ASN, and your authority to announce each prefix. Confirm the provider\u2019s authorization and onboarding requirements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An IP lease or ASN arrangement does not automatically establish announcement rights through every upstream.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For independent public multihoming, confirm a suitable public ASN and prefix arrangement. Review our <\/span><a href=\"https:\/\/atalnetworks.com\/lease-ipv4-ipv6-asn\/\"><span style=\"font-weight: 400;\">IPv4, IPv6, and ASN services<\/span><\/a><span style=\"font-weight: 400;\"> as part of that discussion.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Prepare these details:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Authorized IPv4 and IPv6 prefixes.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Required IRR route, route6, or AS-set records.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default, partial, or full routing needs.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router capacity and maximum-prefix limits.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session addresses and authentication requirements.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Handoff locations, port capacity, and traffic commitments.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Operational contacts and change ownership.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Two providers may still share facilities or physical paths. Review failure independence and the capacity remaining after one connection stops.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">8. Check RPKI and Filtering Before Policy Changes<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A correct community does not repair an unauthorized or rejected announcement.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Check Origin Authorization<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A Route Origin Authorization, or ROA, states which ASN may originate a prefix and can specify an allowed maximum length.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">RPKI origin checks produce three main states:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>State<\/b><\/th>\n<th><b>Meaning<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Valid<\/span><\/td>\n<td><span style=\"font-weight: 400;\">At least one applicable authorization matches the route\u2019s origin and length<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Invalid<\/span><\/td>\n<td><span style=\"font-weight: 400;\">An authorization covers the prefix, but none matches the route<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">NotFound<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No applicable authorization covers the prefix<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">NotFound and Invalid are different states. Provider handling depends on its routing policy. RPKI origin checks do not authenticate community values or the complete AS path. [11]<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Check the intended origin and prefix lengths before changing advertisements. Avoid expanding a ROA\u2019s maximum length simply to accommodate an unplanned more-specific route.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Check Both Prefix and Community Filters<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Confirm IRR filters, accepted lengths, authorized origins, and session limits.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Use export policies that permit only intended prefixes. At policy boundaries, reject or remove unauthorized action tags and protect internal-only controls.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Also check whether adding a community removes existing values. An accidental replacement can erase a required export restriction or maintenance signal.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">9. Test the Action, the Traffic, and the Rollback<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A routing change needs evidence at more than one point.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Capture a Baseline<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Record the prefix, address family, selected paths, existing communities, traffic by interface, packet loss, latency, and available alternatives.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Save the previous policy and define success before making the change.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Confirm Each Stage<\/span><\/h3>\n<table>\n<thead>\n<tr>\n<th><b>Test<\/b><\/th>\n<th><b>Evidence to collect<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Route acceptance<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Provider\u2019s received-route view<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Community delivery<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Our export attributes and provider receipt<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Policy execution<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Provider route selection or export behavior<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Traffic result<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Interface counters, flow data, and active probes<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Failover<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Behavior after the preferred path stops<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Restoration<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Behavior after the path returns<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Looking glasses and route collectors provide useful external views, but they do not see every route or source network. Use several viewpoints relevant to your users.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A visible community proves that a tag reached an observation point, not that a particular policy executed. Conversely, a provider may process a tag and remove it before exporting the route.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Keep the Initial Change Limited<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Start in a lab, then use an authorized prefix or a controlled production scope. Change one policy objective at a time.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Use the platform\u2019s supported method to re-evaluate policy. Check IPv4 and IPv6, and allow for the network\u2019s observed convergence behavior rather than promising a fixed recovery time.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Prepare the Reversal<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Keep exact rollback steps, out-of-band access, and an operator responsible for restoring service. Use confirmed commits or equivalent safeguards where the platform supports them.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Set rollback triggers for lost reachability, excessive packet loss, overloaded backup capacity, or an unexpected path.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">After reversal, check both route visibility and traffic. Restoring configuration text alone does not prove that the service has recovered.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">10. Bring Your Routing Requirements to Atal Networks<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">A useful provider discussion starts with the outcome you need.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Share your ASN, authorized prefixes, upstream design, target markets, deployment locations, traffic volumes, and recovery requirements with us.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Describe the direction clearly. \u201cPrefer Provider A for traffic leaving our network\u201d requires a different discussion from \u201creduce traffic entering through Provider B.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Use this checklist before committing to a deployment:<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><b>Requirement<\/b><\/th>\n<th><b>Request confirmation<\/b><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Community support<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Current catalogue, formats, and revision date<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Scope<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Supported services, locations, sessions, and address families<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Preference<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Available levels and their relationship to other route classes<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Export controls<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Neighbor groups, regional actions, and exceptions<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Conflicts<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rule precedence and unsupported combinations<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Third-party tags<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pass-through, stripping, or translation behavior<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Route acceptance<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Authorization, IRR, RPKI, and prefix-length requirements<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Operations<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Testing visibility, change process, and support ownership<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Commercial terms<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Setup requirements, charges, commitments, and fallback capacity<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Keep unanswered items marked as unconfirmed. Do not substitute another carrier\u2019s community list for deployment-specific documentation.<\/span><\/p>\n<p><b>Discuss your ASN, prefixes, upstream design, target markets, and routing-policy requirements with Atal Networks.<\/b><\/p>\n<h2><span style=\"font-weight: 400;\">Frequently Asked Questions<\/span><\/h2>\n<h3><span style=\"font-weight: 400;\">Can BGP communities control traffic across every provider?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No. A community requests an action from a network that recognizes and permits it. Other networks apply their own policies. Confirm the scope with each provider and measure the resulting traffic paths.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Does local preference control inbound or outbound traffic?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Local preference influences route choice inside the AS that sets it. Our local preference helps choose our outbound path. A community that changes a provider\u2019s local preference can influence that provider\u2019s traffic toward us.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Can a four-octet ASN use standard communities?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Yes, through a suitable documented numbering scheme. The full four-octet ASN cannot fit in the conventional 16-bit administrator field of a standard community. Large communities provide three 32-bit fields.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Does NO_EXPORT stop every BGP advertisement?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No. NO_EXPORT restricts advertisement beyond the BGP confederation boundary, which is the AS boundary for a standalone AS. NO_ADVERTISE prevents advertisement to any BGP peer.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Can a community override an RPKI-invalid route?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Do not assume so. A provider may reject the route before the requested action matters. Correct the origin authorization or announcement problem and confirm the provider\u2019s acceptance policy.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Does a regional community keep all traffic inside that region?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">No. It controls the documented routing action within the provider\u2019s scope. Other networks and physical links can take different paths. Regional advertisements do not establish data residency by themselves.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Can Atal Networks pass upstream communities unchanged?<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Confirm that requirement for the proposed deployment. We need to establish the service, upstream policy, supported community types, and any filtering or translation before relying on pass-through behavior.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Technical References<\/span><\/h2>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc1997.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 1997: BGP Communities<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc4360.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 4360: BGP Extended Communities<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8092.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 8092: BGP Large Communities<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc4271.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 4271: BGP-4<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/blog.cloudflare.com\/prepends-considered-harmful\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Cloudflare: Communities and AS-path prepending<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.gin.ntt.net\/support-center\/policies-procedures\/routing\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">NTT routing policies<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.gtt.net\/services\/managed-networking\/internet\/ip-transit\/bgp-communities\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">GTT community documentation<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc8326.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 8326: Graceful BGP Session Shutdown<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc7999.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 7999: BLACKHOLE Community<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc7454.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 7454: BGP Operations and Security<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc6811.html\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">RFC 6811: BGP Prefix Origin Checks<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>BGP communities attach policy information to route announcements. A provider can use documented values to adjust route preference, limit advertisements, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":24923,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-24922","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-enterprise-grade-server"],"acf":[],"_links":{"self":[{"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/posts\/24922","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/comments?post=24922"}],"version-history":[{"count":3,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/posts\/24922\/revisions"}],"predecessor-version":[{"id":24926,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/posts\/24922\/revisions\/24926"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/media\/24923"}],"wp:attachment":[{"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/media?parent=24922"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/categories?post=24922"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/atalnetworks.com\/fr\/wp-json\/wp\/v2\/tags?post=24922"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}