Re: Equal-cost path

Yasuhiro Ohara <yasu@SFC.WIDE.AD.JP> Tue, 12 April 2005 23:01 UTC

Received: from grape.ease.lsoft.com (grape.ease.lsoft.com [209.119.1.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21877 for <ospf-archive@LISTS.IETF.ORG>; Tue, 12 Apr 2005 19:01:15 -0400 (EDT)
Received: from PEACH.EASE.LSOFT.COM (209.119.1.45) by grape.ease.lsoft.com (LSMTP for OpenVMS v1.1b) with SMTP id <11.00564F4F@grape.ease.lsoft.com>; Tue, 12 Apr 2005 19:01:17 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.3) with spool id 66274097 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 12 Apr 2005 19:01:17 -0400
Received: from 203.178.143.91 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0l) with TCP; Tue, 12 Apr 2005 19:01:13 -0500
Received: from localhost (p16006-ipad46hodogaya.kanagawa.ocn.ne.jp [60.33.95.6]) by plant.sfc.wide.ad.jp (Postfix) with ESMTP id 4DEF41B66A; Wed, 13 Apr 2005 08:01:10 +0900 (JST)
References: <OF126B0677.37EA48FE-ONC2256FDF.003D24CD@ecitele.com> <20050412154007.R19808@kummer.juniper.net>
X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <20050413.080109.01294295.yasu@sfc.wide.ad.jp>
Date: Wed, 13 Apr 2005 08:01:09 +0900
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Yasuhiro Ohara <yasu@SFC.WIDE.AD.JP>
Subject: Re: Equal-cost path
Comments: To: kireeti@JUNIPER.NET
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <20050412154007.R19808@kummer.juniper.net>
Precedence: list
Content-Transfer-Encoding: 7bit

Ahahaha,
what are you talking about Kireeti !? ;p)

The correct answer would be "It's an implementation specific issue".

One should recognize ECMP as a property of OSPF (dijkstra) algorithm,
rather than a feature. It means "you can use either path as far as
those paths are equal cost". Which path to use actually is totally left
to the calculating router. Whichever the path is selected by the router
whole OSPF domain will work fine (in terms of issue regarding routing loops).

OSPF does not specify which path (out of ECMP) should be used/preferred,
it's totally left to a implementor.

regards,
yasu

From: Kireeti Kompella <kireeti@JUNIPER.NET>
Subject: Re: Equal-cost path
Date: Tue, 12 Apr 2005 15:40:29 -0700

> On Sun, 10 Apr 2005, Ilan Bercovich wrote:
> 
> > When not using "equal-cost multipath",
> > Which equal-cost path should be selected?
> 
> The one that's more equal than the rest.
> 
> Kireeti.
> -------
>