Visual RFC.
ALL RFCs / RFC 4271
Read the RFC ↗
RFC 4271 / PROTOCOL MECHANISMS

Select routes using policy and reachability

04

BGP’s decision process separates received routes, a selected local route, and exported routes.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 9.1 ↗
RFC 4271 · § 9.1EXAMPLE
3 / 3
Select routes using policy and reachabilityBGP’s decision process separates received routes, a selected local route, and exported routes.Adj-RIBs-Inreceived candidatesResolvable NEXT_HOP?nopolicy / tie breaksLoc-RIB → export policyunusable excludedPolicy preference is not a globally shortest geographic path
03
Install in Loc-RIB and apply export policy for Adj-RIBs-Out.

Install in Loc-RIB and apply export policy for Adj-RIBs-Out.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

NEXT_HOP must be resolvable for a route to be usable.

  • NEXT_HOP must be resolvable for a route to be usable.
  • Degree of preference and tie breaking are not equivalent to globally choosing the geographically shortest route.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Establish a BGP session
  2. Advertise and withdraw prefixes
  3. Use AS paths to detect loops
  4. Select routes using policy and reachability
  5. Handle failures without assuming route truth
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗