IETF Logo Mail Archive

Re: [curtis@ans.net: Re: BGP4 stuff: Local Preference Computation]

Curtis Villamizar <curtis@ans.net> Mon, 09 September 1996 17:51 UTC

Received: from ietf.org by ietf.org id aa02541; 9 Sep 96 13:51 EDT
Received: from cnri by ietf.org id aa02536; 9 Sep 96 13:51 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa10939; 9 Sep 96 13:51 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id NAA16734 for idr-outgoing; Mon, 9 Sep 1996 13:11:35 -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 NAA16728 for <bgp@merit.edu>; Mon, 9 Sep 1996 13:11:32 -0400 (EDT)
Received: by interlock.ans.net id AA01911 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Mon, 9 Sep 1996 13:11:31 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 9 Sep 1996 13:11:31 -0400
Message-Id: <199609091710.NAA29154@brookfield.ans.net>
To: "NITTMANN Michael (MSMail)" <MNittmann@shl.com>
Cc: "John G. Scudder" <jgs@ieng.com>, Yakov Rekhter <yakov@cisco.com>, "bgp@ans.net" <bgp@ans.net>
Reply-To: curtis@ans.net
Subject: Re: [curtis@ans.net: Re: BGP4 stuff: Local Preference Computation]
In-Reply-To: Your message of "Fri, 06 Sep 1996 08:38:13 MDT." <c=US%a=_%p=SHL%l=SHL/CANADAW/001B58E6@cocms1.calwdc.shl.com>
Date: Mon, 09 Sep 1996 13:09:58 -0400
Sender: ietf-archive-request@ietf.org
From: Curtis Villamizar <curtis@ans.net>
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

In message <c=US%a=_%p=SHL%l=SHL/CANADAW/001B58E6@cocms1.calwdc.shl.com>om>, "NITT
MANN Michael (MSMail)" writes:
> I like the table, but would like to change a little detail:
> 
> 			   Type of Connection
> 	Attribute	Internal	External
> 	---------	--------	--------
> 	ORIGIN		mandatory	mandatory
> 	AS_PATH	mandatory	mandatory
> 	NEXT_HOP	mandatory	mandatory
> 	MED		optional		mandatory   <<<<<<<<
> 	LOCAL_PREF	mandatory	forbidden
> 	ATOMIC_AGG	*		*
> 	AGGREGATOR	optional		optional
> 
> make the MED exchange for mutually set MEDs mandatory for the routes that 
> are concerned, i.e. if I am in AS 1 and peer with AS 2, all AS 2 routes 
> announced to me must carry the MED value assigned to them by AS 2 towards 
> me, AS 1, or -1 if there is no MED set.
> 
> Mike

Mike,

What you are saying doesn't make sense to me.  MED is non-transitive.
It is optional for EBGP.  It MAY be passed from EBGP into IBGP.  It is
NEVER passed from IBGP to EBGP.  It is perfectly legitimate to not
pass a MED at all in either IBGP or EBGP.

Curtis

v2.8.7 | Report a Bug | By Email