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

Advertise and withdraw prefixes

02

UPDATE messages carry withdrawals, path attributes, and reachable prefixes.

Related RFCs and changes

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

DIAGRAM§ 4.3 ↗
RFC 4271 · § 4.3EXAMPLE
3 / 3
Advertise and withdraw prefixesUPDATE messages carry withdrawals, path attributes, and reachable prefixes.UPDATE: 192.0.2.0/24 + attributesAccepted reachability from peerWithdraw: 192.0.2.0/24A withdrawal removes reachability; it is not an infinite metric
03
Withdraw the prefix when that reachability is removed.

Withdraw the prefix when that reachability is removed.

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

NLRI describes prefixes, not a flat list of individual hosts.

  • NLRI describes prefixes, not a flat list of individual hosts.
  • Withdrawal removes advertised reachability; it is not a route advertisement with an arbitrary very large metric.
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 ↗