Re: BGP-4 changes

Yakov Rekhter <yakov@cisco.com> Fri, 30 August 1996 14:47 UTC

Received: from ietf.org by ietf.org id aa23406; 30 Aug 96 10:47 EDT
Received: from cnri by ietf.org id aa23400; 30 Aug 96 10:47 EDT
Received: from merit.edu by CNRI.Reston.VA.US id aa07856; 30 Aug 96 10:47 EDT
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id KAA27623 for idr-outgoing; Fri, 30 Aug 1996 10:11:19 -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 KAA27618 for <bgp@merit.edu>; Fri, 30 Aug 1996 10:11:16 -0400 (EDT)
Received: by interlock.ans.net id AA12354 (InterLock SMTP Gateway 3.0 for bgp@ans.net); Fri, 30 Aug 1996 10:11:14 -0400
Received: by interlock.ans.net (Internal Mail Agent-1); Fri, 30 Aug 1996 10:11:14 -0400
Message-Id: <199608301414.HAA29855@hubbub.cisco.com>
To: Rich Woundy <rwoundy@vnet.ibm.com>
Cc: bgp@ans.net
Subject: Re: BGP-4 changes
In-Reply-To: Your message of "Thu, 29 Aug 96 16:03:39 EDT." <199608292012.NAA20093@hubbub.cisco.com>
Date: Fri, 30 Aug 96 07:11:11 PDT
Sender: ietf-archive-request@ietf.org
From: Yakov Rekhter <yakov@cisco.com>
X-Orig-Sender: owner-idr@merit.edu
Precedence: bulk

Rich,

>  >1. Add to 5.1.4 the following:
> 
>  >  MULTI_EXIT_DISC shall not be considered when comparing routes received fr
om
>  >  different neighboring ASs.
> 
>  I agree with your intent, but this is too easy to misinterpret.  For
>  example, suppose a router has three routes for a prefix, with the same
>  local preference: one from AS X w/MED 5, one from AS X w/MED 10, and one
>  from AS Y w/MED 15.  I think the consensus is that the router should not
>  compare the MED values 5 and 10 from AS X with the MED value 15 from
>  AS Y.  On the other hand, we should also make it clear that as part of
>  MED comparison, the route from AS Y w/MED 15 should be preferred over
>  the route from AS X w/MED 10 -- otherwise, you can get routing loops.

Comparing MEDs on routes coming from different ASs is not very
meaningful, as MED is intended to reflect IGP distance within a
particular neighboring AS, and one shouldn't expect that IGP distances
would be comparable across all neighboring ASs.

Thus while I certainly agree with your statement that "the router
should not compare the MED values 5 and 10 from AS X with the MED value
15 from AS Y", I don't think that "the route from AS Y w/MED 15 should
be preferred over the route from AS X w/MED 10" (as it compares
uncomparable things).

Yakov.