The Accumulated IGP Metric Attribute for BGP, August 2014
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- P. Mohapatra
- idr (rtg)
Discuss this RFC: Send questions or comments to email@example.com
Routing protocols that have been designed to run within a single administrative domain (IGPs) generally do so by assigning a metric to each link and then choosing, as the installed path between two nodes, the path for which the total distance (sum of the metric of each link along the path) is minimized. BGP, designed to provide routing over a large number of independent administrative domains (autonomous systems), does not make its path-selection decisions through the use of a metric. It is generally recognized that any attempt to do so would incur significant scalability problems as well as inter-administration coordination problems. However, there are deployments in which a single administration runs several contiguous BGP networks. In such cases, it can be desirable, within that single administrative domain, for BGP to select paths based on a metric, just as an IGP would do. The purpose of this document is to provide a specification for doing so.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.