IETF Logo Mail Archive

Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft

"Ilya Varlashkin" <Ilya.Varlashkin@de.easynet.net> Thu, 23 July 2009 12:02 UTC

Return-Path: <Ilya.Varlashkin@de.easynet.net>
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37A583A6968 for <idr@core3.amsl.com>; Thu, 23 Jul 2009 05:02:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 N81t9hq5NSEf for <idr@core3.amsl.com>; Thu, 23 Jul 2009 05:02:41 -0700 (PDT)
Received: from softy.de.easynet.net (softy.de.easynet.net [194.163.250.97]) by core3.amsl.com (Postfix) with ESMTP id 66EC63A6856 for <idr@ietf.org>; Thu, 23 Jul 2009 05:02:41 -0700 (PDT)
Received: from fe01kgham.de.easynet.net ([194.163.250.17] helo=fe01kgham.adoffice.local.de.easynet.net) by softy.de.easynet.net with esmtp (Exim 4.63) (envelope-from <Ilya.Varlashkin@de.easynet.net>) id 1MTwza-0002CR-HU; Thu, 23 Jul 2009 14:01:46 +0200
Received: from ex01kgham.adoffice.local.de.easynet.net ([10.43.3.3]) by fe01kgham.adoffice.local.de.easynet.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 14:01:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 23 Jul 2009 14:01:45 +0200
Message-ID: <D12350C326DF61448B1AE6B46C453F0E25BDE0@ex01kgham.adoffice.local.de.easynet.net>
In-Reply-To: <4A683F5E.906@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: AW: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft
thread-index: AcoLgsL6YtDig1zUSJSaYltxKDBXLgABgiSA
References: <200907230422.n6N4MgYa021490@harbor.orleans.occnc.com> <4A680D87.80501@cisco.com> <D12350C326DF61448B1AE6B46C453F0E25BDD8@ex01kgham.adoffice.local.de.easynet.net> <4A683F5E.906@cisco.com>
From: Ilya Varlashkin <Ilya.Varlashkin@de.easynet.net>
To: raszuk@cisco.com
X-OriginalArrivalTime: 23 Jul 2009 12:01:46.0794 (UTC) FILETIME=[5A5ED8A0:01CA0B8D]
Cc: idr List <idr@ietf.org>
Subject: Re: [Idr] draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2009 12:02:42 -0000

> -----Ursprüngliche Nachricht-----
> Are you really recommending that each application (one of them being
> BGP) which may use underlying transport of LSPs to 
> continuously perform it's own OAM check over such LSPs ?
> 

Not exactly. There are two things BGP could potentially do: 

- first it could consult local forwarding plane to check whether next-hop info has been installed there.

- second, in some cases BGP could rely on OAM (e.g. BFD) for verifying next-hop availability. It may sound as not very scaleable, it could be used for example to check availability of critical exit points such as major IXP or uplinks. 

Cheers,
iLya

v2.23.0 | Report a Bug | By Email