# Apply BGP path selection before advertising a chosen route > Use RFC 4271 — A Border Gateway Protocol 4 (BGP-4) to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/apply-bgp-path-selection-before-advertising-a-chosen-route/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:16:41+00:00 - Modified: 2026-08-27T12:36:16+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Playbook - DSE priority: Advisory - Topics: IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use RFC 4271 — A Border Gateway Protocol 4 (BGP-4) to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of RFC 4271 — A Border Gateway Protocol 4 (BGP-4) ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Keep this document to one review outcome: Apply BGP path selection before advertising a chosen route. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [RFC 4271 — A Border Gateway Protocol 4 (BGP-4)](https://www.rfc-editor.org/rfc/rfc4271.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements: - BGP first assigns each feasible received route a policy-derived preference, then selects one best route per destination for the Loc-RIB. The research record locates this support at Sections 9.1.1 (Phase 1) and 9.1.2 (Phase 2). - A route with an unresolvable NEXT_HOP is excluded from selection, and the chosen route is re-evaluated when next-hop reachability or IGP cost changes. The research record locates this support at Section 9.1.2 (Phase 2: Route Selection). - Only after selection does Phase 3 apply per-peer export policy and place eligible routes in each Adj-RIB-Out for advertisement. The research record locates this support at Section 9.1.3 (Phase 3: Route Dissemination). Only the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match. ## What the source does not establish This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints. ## Applicability questions - For source statement 1 at Sections 9.1.1 (Phase 1) and 9.1.2 (Phase 2), which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section 9.1.2 (Phase 2: Route Selection), which observable configuration, record, or test can confirm applicability here? - For source statement 3 at Section 9.1.3 (Phase 3: Route Dissemination), which observable configuration, record, or test can confirm applicability here? - Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population? - Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability? - Who owns the decision, and which observation requires stopping, escalation, or rollback? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Build a reproducible chain from Sections 9.1.1 (Phase 1) and 9.1.2 (Phase 2); Section 9.1.2 (Phase 2: Route Selection); Section 9.1.3 (Phase 3: Route Dissemination) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier. Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee. ## Official references - [RFC 4271 — A Border Gateway Protocol 4 (BGP-4)](https://www.rfc-editor.org/rfc/rfc4271.html) — RFC Editor / Internet Engineering Task Force ## Primary reference - Name: RFC 4271 — A Border Gateway Protocol 4 (BGP-4) - Authority: www.rfc-editor.org - URL: https://www.rfc-editor.org/rfc/rfc4271.html - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Apply BGP path selection before advertising a chosen route,” DSE Security, https://update.dsesecurity.com/updates/apply-bgp-path-selection-before-advertising-a-chosen-route/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.