Replace stale routes inside the boundaries
03Adj-RIB-Out is the set of routes a speaker advertises to a particular peer, subject to outbound policy. Beginning and ending markers let the receiver find a saved route whose withdrawal it missed.
B finishes its complete re-advertisement and sends EoRR. A immediately purges B, retaining fresh A/C plus untouched X/V. No TCP session reset is part of this example.
Source for this drawing: RFC 7313 · Read RFC section 4 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
Before either a locally initiated or requested refresh, the sender MUST send BoRR. After completing the entire Adj-RIB-Out re-advertisement it MUST send EoRR.
- Before either a locally initiated or requested refresh, the sender MUST send BoRR. After completing the entire Adj-RIB-Out re-advertisement it MUST send EoRR.
- The entire Adj-RIB-Out means the entries at the start of this refresh, including reachability and unreachability information. If an entry changes, only the modified entry needs advertising.
- On BoRR, the receiver MUST mark all routes from that peer for that AFI/SAFI stale. Subsequent advertisements replace corresponding stale routes; other peers and families stay separate.
- On EoRR, the receiver MUST immediately remove routes from that peer still stale for that AFI/SAFI. Purged routes MAY be logged. This can change routing; keeping the BGP session up does not promise unchanged forwarding.
RFC7313 §4. Route letters stand for fictional documentation prefixes: A=192.0.2.0/24, B=198.51.100.0/24, C=203.0.113.0/24. Table is the received view, not the global Internet routing table.
Read the RFC section ↗