Scribd
Upload
53 views5 pages

BGP Bandwidth Community

The document defines an extended community that can carry the bandwidth of a link to enable ingress routers to do unequal cost load balancing. It is already implemented by some vendors but not standardized. The motivation is that when an EBGP peer is dually connected to provider edge routers with different bandwidth links, the bandwidth value in the extended community allows the ingress router to do 2:1 load balancing based on the link capacities. The format uses an optional non-transitive extended community type with the AS number and bandwidth in bytes/sec. It is restricted to cases where IBGP multipath is safely supported.

Uploaded by

Srdjan Milenkovic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
53 views5 pages

BGP Bandwidth Community

The document defines an extended community that can carry the bandwidth of a link to enable ingress routers to do unequal cost load balancing. It is already implemented by some vendors but not standardized. The motivation is that when an EBGP peer is dually connected to provider edge routers with different bandwidth links, the bandwidth value in the extended community allows the ingress router to do 2:1 load balancing based on the link capacities. The format uses an optional non-transitive extended community type with the AS number and bandwidth in bytes/sec. It is restricted to cases where IBGP multipath is safely supported.

Uploaded by

Srdjan Milenkovic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

BGP Link Bandwidth

Extended Community
draft-rfernando-idr-link-bandwidth-00

Pradosh Mohapatra <[email protected]>,


Rex Fernando <[email protected]>

Acknowledgements: Yakov Rekhter, Srihari Sangli, Dan Tappan

IETF 74, March 2009, San Francisco, USA


1

Basic Idea
 Define an extended community to carry the
DMZ links bandwidth (or an associated
weight) to enable ingress routers to do
unequal cost load balancing
 Already implemented by multiple vendors;
not standardized (hence potential for
interoperability issues)

Motivation
 CE1 is one-hop EBGP
neighbor dually connected
to PE2 and PE3 (links with
different bandwidths)
 When PE2 & PE3 send
received prefixes from CE1
to IBGP mesh, they include
the bandwidth in an
extended community
 PE1 does unequal cost
load balancing based on
the bandwidth values (e.g.
2:1 in this case)

AS 1
PE2

bw=500

CE1
bw=250

PE1
PE3

Format & Usage


 Optional non-transitive
 Type high=0x40, low=0x04
 AS# in next two octets (AS_TRANS
in case of 4-byte ASes)
 Bandwidth in bytes/sec in next four
octets (IEEE floating point format)
 Restricted to cases where IBGP
multipath can safely be used

1 octet
0x40

1 octet
0x04

2 octets

AS#

2 octets

bandwidth (IEEE
floating pt format)

4 octets

 IGP cost to nexthop should be same or


use of tunneling for unequal cost

Document Status
 Comments are welcome
 We would like the draft to be WG draft

You might also like