Re: load-sharing/load-balancing 2 T1s (fwd)
Tony Li <tli@cisco.com> Sat, 09 March 1996 18:13 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11540;
9 Mar 96 13:13 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11536;
9 Mar 96 13:13 EST
Received: from p-o.ans.net by CNRI.Reston.VA.US id aa07652; 9 Mar 96 13:13 EST
Received: by p-o.ans.net id AA41094
(5.65c/IDA-1.4.4 for bgp-outgoing); Sat, 9 Mar 1996 17:40:59 GMT
Date: Sat, 9 Mar 1996 09:40:46 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Li <tli@cisco.com>
Message-Id: <199603091740.JAA13576@greatdane.cisco.com>
To: bgp@ans.net
Cc: bgp@ans.net
In-Reply-To: <199603081951.LAA00866@greatdane.cisco.com> (message from Ravi
Chandra on Fri, 08 Mar 1996 11:51:16 -0800)
Subject: Re: load-sharing/load-balancing 2 T1s (fwd)
X-Orig-Sender: bgp-owner@ans.net
Precedence: bulk
Reply-To: bgp@ans.net
Why does BGP pick only one route when it has several options? 90% historical reasons. In the general case, it was very difficult with BGP3 to select multiple paths and not lie about the AS path. Such lies have the obvious bad consequence. ;-( More sophisticated behavior is obviously possible. But requires more CPU cycles. ;-) Tony
- Re: load-sharing/load-balancing 2 T1s (fwd) Tony Li
- Re: load-sharing/load-balancing 2 T1s (fwd) Tony Li
- Re: load-sharing/load-balancing 2 T1s (fwd) bmanning
- Re: load-sharing/load-balancing 2 T1s (fwd) Erik Sherk
- Re: load-sharing/load-balancing 2 T1s (fwd) Paul Traina
- Re: load-sharing/load-balancing 2 T1s (fwd) David Whipple
- Re: load-sharing/load-balancing 2 T1s (fwd) Ravi Chandra
- Re: load-sharing/load-balancing 2 T1s (fwd) Paul Traina