BGP4 stuff: Local Preference Computation

Cristina Radulescu-Banu <cristina@midnight.com> Wed, 04 September 1996 20:23 UTC

Received: from ietf.org by ietf.org id aa07650; 4 Sep 96 16:23 EDT
Received: from cnri by ietf.org id aa07646; 4 Sep 96 16:23 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa15623; 4 Sep 96 16:23 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id PAA03261 for idr-outgoing; Wed, 4 Sep 1996 15:31:53 -0400 (EDT)
Received: from interlock.ans.net (interlock.ans.net [147.225.5.5]) by merit.edu (8.7.5/merit-2.0) with SMTP id PAA03256 for <bgp@merit.edu>; Wed, 4 Sep 1996 15:31:49 -0400 (EDT)
Received: by interlock.ans.net id AA15312 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Wed, 4 Sep 1996 15:31:48 -0400
Received: by interlock.ans.net (Internal Mail Agent-2); Wed, 4 Sep 1996 15:31:48 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Wed, 4 Sep 1996 15:31:48 -0400
Date: Wed, 4 Sep 1996 15:34:29 -0400
Message-Id: <199609041934.PAA00467@rasarit.midnight.com>
Sender: ietf-archive-request@ietf.org
From: Cristina Radulescu-Banu <cristina@midnight.com>
To: bgp@ans.net
Cc: rwoundy@vnet.ibm.com, jgs@ieng.com
Subject: BGP4 stuff: Local Preference Computation
Reply-To: Cristina Radelescu-Banu 617/890-1001 <cristina@midnight.com>
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

	I have some problems in implementing BGP4, and if you could
clarify some of them , this would be great.

	I understood that LOCAL_PREF is used as degree of preference only for
the BGP4 speakers located in the SAME Autonomous System. The Degree of
Preference is something totally different, it is used both for the BGP
Peers in the same and in the neighbor AS (it can use in its
computation the LOCAL_PREF, that's true), and one of the devices I
tested computes the Degree of Prefence with formula:

	TotalASPolicyWeight+ PeerWeight + DefaultWeight

where DefaultWeight = the weight added to each route when computing 
the degree of preference for the route (LOCAL_PREF)-if you have
any-because it's an discretionary attribute-, and
if you consider it because it was received from a peer in the
same AS)
	You can assign weight to each AS in the AS_PATH => this way you have the
TotalASPolicyWeight; 

PeerWeight = the weight that is added to all routes received from the specified peer
 
	For me this is pretty clear, to take in account 
the AS and the Peer when you compute the Deegre of Preference.

	After the router has done the computation for this Degree of
Preference, the Local Pref  assigned to the route take the value of
the Degree of preference already computed. If an internal peer
received that route, it may or may not
take as Local Pref the LOCAL_PREF already received (it can compute
another Degree of Pref based on this Local Pref); If an external peer
received it, it ignores it and does the Degree of Pref computation for
the route again, without taking in account any Local Pref.

	Yes, sometimes the Local Pref can be computed (if the internal
peer choose this)but the one which is computed is always the DEGREE OF
PREFERENCE, which is different form Local Pref.

This is totally different from what I saw in the messages
exchanged, about the Local Pref Computation, which I think should be
the Degree of Preference Computation; what is the right thing to be?

	Thanks in advance,

	Cristina 
-- 


...............................................................................
Cristina Radulescu-Banu : Midnight Networks 200 Fifth Avenue Waltham MA 02154
cristina@midnight.com  : Vox 617/890-1001 Fax 0028 The Best in Network Software
	
	 There wouldn't be wolves if there wouldn't be sheep.

			  - Romanian proverb