# Bracket route refresh updates so peers can reconcile stale state > Use RFC 7313 — Enhanced Route Refresh Capability for BGP-4 to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/bracket-route-refresh-updates-so-peers-can-reconcile-stale-state/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:16:38+00:00 - Modified: 2026-08-27T12:36:16+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Explainer - DSE priority: Advisory - Topics: IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use RFC 7313 — Enhanced Route Refresh Capability for 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 7313 — Enhanced Route Refresh Capability for 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 Frame this document as a source-led configuration and assurance check: Bracket route refresh updates so peers can reconcile stale state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [RFC 7313 — Enhanced Route Refresh Capability for BGP-4](https://www.rfc-editor.org/rfc/rfc7313.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements: - Enhanced route-refresh procedures apply to a peer only after that peer has advertised the Enhanced Route Refresh Capability. The research record locates this support at Section 4 (Operation), capability precondition. - The refreshing speaker must send Begin-of-RIB-Refresh before re-advertisement and End-of-RIB-Refresh after completing the entire affected Adj-RIB-Out. The research record locates this support at Section 4 (Operation), sender procedure. - On Begin-of-RIB-Refresh, the receiver marks that peer’s AFI/SAFI routes stale; refreshed routes replace them, and End-of-RIB-Refresh removes any that remain stale. The research record locates this support at Section 4 (Operation), receiver procedure. Keep the evidence boundary at these traced claims. They support a review of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains; they do not support conclusions outside the source’s stated conditions. ## 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 Section 4 (Operation), capability precondition, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section 4 (Operation), sender procedure, which observable configuration, record, or test can confirm applicability here? - For source statement 3 at Section 4 (Operation), receiver procedure, 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. Anchor the review in the cited section and keep observation separate from interpretation. 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. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Keep the source locations Section 4 (Operation), capability precondition; Section 4 (Operation), sender procedure; Section 4 (Operation), receiver procedure adjacent to the sanitized artifacts used for comparison. Prefer configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, with enough identity and timing data for an independent recheck. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [RFC 7313 — Enhanced Route Refresh Capability for BGP-4](https://www.rfc-editor.org/rfc/rfc7313.html) — RFC Editor / Internet Engineering Task Force ## Primary reference - Name: RFC 7313 — Enhanced Route Refresh Capability for BGP-4 - Authority: www.rfc-editor.org - URL: https://www.rfc-editor.org/rfc/rfc7313.html - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Bracket route refresh updates so peers can reconcile stale state,” DSE Security, https://update.dsesecurity.com/updates/bracket-route-refresh-updates-so-peers-can-reconcile-stale-state/ 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.