Re: [GROW] [Idr] draft-ietf-grow-diverse-bgp-path-dist ignore IGP metric

Robert Raszuk <raszuk@cisco.com> Sun, 27 March 2011 21:02 UTC

Return-Path: <raszuk@cisco.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C2193A693C; Sun, 27 Mar 2011 14:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1YnIus1EfeN; Sun, 27 Mar 2011 14:02:36 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id D3F0B3A693B; Sun, 27 Mar 2011 14:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=raszuk@cisco.com; l=1047; q=dns/txt; s=iport; t=1301259854; x=1302469454; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=OLuFJ/In2n1ONeZnQtyubNQxuz4o7Q7y76O7kur6MHM=; b=M6rTkAKlwK4nNCCflyfio/muypQLQB/obcOR3WV8kFq8W053vmdmDHVi ZaZesOCwx12yAiuY3dhAnuuigyTvio4MQPoBedgZ1wmiCemftmkYCBkcY arsKLb1V8N0/pbo2PWansATuaZLpszK6vyV7jnaUt8UscvuaCgf5ZCgxm o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACOlj02rRDoH/2dsb2JhbAClUXeIa5xHgm8OAZd3hWkEjHeDVA
X-IronPort-AV: E=Sophos;i="4.63,251,1299456000"; d="scan'208";a="325449711"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by sj-iport-2.cisco.com with ESMTP; 27 Mar 2011 21:04:14 +0000
Received: from [10.21.104.107] (sjc-vpnasa1-107.cisco.com [10.21.104.107]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2RL4CsZ031294; Sun, 27 Mar 2011 21:04:13 GMT
Message-ID: <4D8FA64C.4030607@cisco.com>
Date: Sun, 27 Mar 2011 23:04:12 +0200
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Jakob Heitz <jakob.heitz@ericsson.com>
References: <7309FCBCAE981B43ABBE69B31C8D21390E3F5BECAB@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21390E3F5BECAB@EUSAACMS0701.eamcs.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF IDR <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] draft-ietf-grow-diverse-bgp-path-dist ignore IGP metric
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 21:02:37 -0000

Jakob,

> If you ignore IGP metric, you may choose the wrong bestpath.

This is to be used when RRs are control plane devices somewhere in the 
middle of the network. In case of hierarchical network such RRs would be 
in the core area.

If you have RRs in each POP either at the pop to core boundary or within 
the POP you do not need to use this at all.

Moreover if you have two sessions to any of the RRs this is also not 
needed.

For more discussions on next hop IGP metric influence of BGP best path 
decision I would recommend to take a look at this work:

http://tools.ietf.org/html/draft-raszuk-bgp-optimal-route-reflection-01

Thx,
R.


> Suppose 3 paths, 2 RR planes.
> Suppose RR clusters in POPs all over the country.
> One RR cluster may not choose its closest path at all.
> It could choose 2 paths far away when there is one
> path closer.
>
> --
> Jakob Heitz.
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>