IETF Logo Mail Archive

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

Robert Raszuk <raszuk@cisco.com> Thu, 23 July 2009 10:46 UTC

Return-Path: <raszuk@cisco.com>
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 90D5E3A696D for <idr@core3.amsl.com>; Thu, 23 Jul 2009 03:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.167
X-Spam-Level:
X-Spam-Status: No, score=-6.167 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Y4ucxTzD6upl for <idr@core3.amsl.com>; Thu, 23 Jul 2009 03:46:41 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id C38873A693B for <idr@ietf.org>; Thu, 23 Jul 2009 03:46:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAEjcZ0qrR7PD/2dsb2JhbAC3I4EUCAGHCJB/BYQN
X-IronPort-AV: E=Sophos;i="4.43,253,1246838400"; d="scan'208";a="352362444"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 23 Jul 2009 10:45:54 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6NAjs1R002142; Thu, 23 Jul 2009 03:45:54 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n6NAjs8C029040; Thu, 23 Jul 2009 10:45:54 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 03:45:54 -0700
Received: from [10.21.148.11] ([10.21.148.11]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 03:45:53 -0700
Message-ID: <4A683F5E.906@cisco.com>
Date: Thu, 23 Jul 2009 03:45:50 -0700
From: Robert Raszuk <raszuk@cisco.com>
Organization: Cisco Systems
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Ilya Varlashkin <Ilya.Varlashkin@de.easynet.net>
References: <200907230422.n6N4MgYa021490@harbor.orleans.occnc.com> <4A680D87.80501@cisco.com> <D12350C326DF61448B1AE6B46C453F0E25BDD8@ex01kgham.adoffice.local.de.easynet.net>
In-Reply-To: <D12350C326DF61448B1AE6B46C453F0E25BDD8@ex01kgham.adoffice.local.de.easynet.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 23 Jul 2009 10:45:54.0103 (UTC) FILETIME=[C0C15470:01CA0B82]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2118; t=1248345954; x=1249209954; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=raszuk@cisco.com; z=From:=20Robert=20Raszuk=20<raszuk@cisco.com> |Subject:=20Re=3A=20AW=3A=20[Idr]=20draft-asati-idr-bgp-bes tpath-selection-criteria=20as=0A=20IDR=20WG=09draft |Sender:=20; bh=GwiNmgMdlZ6jkiQHoXacIcnkOLKS39D4Uet8vIIab+s=; b=GgF7gsPNSuLzIOjSgz3kAtX4jvpEtwhDwm/3VvKcUJYGE+Klp+6YBcdHhB THzjOW8sfIu9nztLYJEkjDIYICQ1dwPYlXSiVzCuIOi0ecsEblFZXIuK9p6E U9fRQU7t/6;
Authentication-Results: sj-dkim-3; header.From=raszuk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
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
Reply-To: raszuk@cisco.com
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 10:46:42 -0000

Ilya,

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 ?

I really think it is a data plane OAM thing which should be done in full 
abstraction to routing protocols or label distribution protocols before 
such LSP is inserted in RIB as a means to reach destination XYZ.

Cheers,
R.

>> -----Ursprüngliche Nachricht-----
>> Von: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] Im 
>> Auftrag von Robert Raszuk
>> Gesendet: Donnerstag, 23. Juli 2009 09:13
>> An: curtis@occnc.com
>> Cc: idr List
>> Betreff: Re: [Idr] 
>> draft-asati-idr-bgp-bestpath-selection-criteria as IDR WG draft
>>
>> Hi Curtis,
>>
>> I think your assessment of the draft is right. The original 
>> issue has been raised by the problem of considering next hop 
>> as valid and reachable IP reachability wise without any 
>> correlation with MPLS LSP to such next hop which was a must 
>> and a prerequisite for some applications to work.
>>
>> In my opinion this is a valid problem, but this is not a BGP issue.
>>
>> Underlying transport (for example MPLS LDP or MPLS-TE) should 
>> only expose valid and reachable LSPs to it's RIB so when BGP 
> 
> Robert,
> 
> in some scenarios (e.g Inter-AS MPLS stuff) labels are distributed by BGP itself. Also, LDP may have received all correct info from the neighbors, but failed to install it into forwarding plane (either due to hardware failure or a software bug). Having experienced this with routers from two different manufacturers, I believe it would be really benefical if BGP could perform a bit more extended checks rather than just looking into control plane. I understand that issue is more of "local type" (e.g. hardware failure) rather than protocol itself, but considering reality (bugs do happen and hardware does fail) it's very desirable that BGP specs at least encourage implementors to make more effort in validating next-hop. And this is why I believe IDR is correct WG for this draft.
> 
> Cheers,
> iLya
>

v2.23.0 | Report a Bug | By Email