Search RFCs

RFC Editor

File formats:

Status:

DRAFT STANDARD

Obsoletes:

RFC 1771

Updated by:

RFC 4724,RFC 6286,RFC 6608,RFC 6793,RFC 7606,RFC 7607,RFC 7705,RFC 8212,RFC 8654,RFC 9072,RFC 9687,RFC 9774

Authors:

Y. Rekhter, Ed.
T. Li, Ed.
S. Hares, Ed.

Stream:

IETF

Source:

idr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4271

Discuss this RFC: Send questions or comments to the mailing listidr@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4271

Abstract

This document discusses the Border Gateway Protocol (BGP), which is aninter-Autonomous System routing protocol.

The primary function of a BGP speaking system is to exchange networkreachability information with other BGP systems. This networkreachability information includes information on the list ofAutonomous Systems (ASes) that reachability information traverses.This information is sufficient for constructing a graph of ASconnectivity for this reachability from which routing loops may bepruned, and, at the AS level, some policy decisions may be enforced.

BGP-4 provides a set of mechanisms for supporting ClasslessInter-Domain Routing (CIDR). These mechanismsinclude support for advertising a set of destinations as an IP prefix, andeliminating the concept of network "class" within BGP. BGP-4 alsointroduces mechanisms that allow aggregation of routes, includingaggregation of AS paths.

This document obsoletes RFC 1771. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.