From exim@www1.ietf.org Tue Feb 24 18:36:51 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17175 for ; Tue, 24 Feb 2004 18:36:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avm6D-0008Jv-0X for rtg-bfd-archive@odin.ietf.org; Tue, 24 Feb 2004 18:36:25 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1ONaOYr031977 for rtg-bfd-archive@odin.ietf.org; Tue, 24 Feb 2004 18:36:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avm6C-0008Jg-RY for rtg-bfd-web-archive@optimus.ietf.org; Tue, 24 Feb 2004 18:36:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17169 for ; Tue, 24 Feb 2004 18:36:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Avm69-00071V-00 for rtg-bfd-web-archive@ietf.org; Tue, 24 Feb 2004 18:36:21 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avm5E-0006xC-00 for rtg-bfd-web-archive@ietf.org; Tue, 24 Feb 2004 18:35:25 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Avm4z-0006sV-00 for rtg-bfd-web-archive@ietf.org; Tue, 24 Feb 2004 18:35:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avm4t-0008GX-0K; Tue, 24 Feb 2004 18:35:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avm4E-0008Fa-JC for rtg-bfd@optimus.ietf.org; Tue, 24 Feb 2004 18:34:22 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17115 for ; Tue, 24 Feb 2004 18:34:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Avm4B-0006rW-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 18:34:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avm3E-0006nh-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 18:33:21 -0500 Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1Avm2w-0006je-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 18:33:02 -0500 Received: from [147.28.0.62] (helo=127.0.0.1) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1Avm2w-000FyD-JV for rtg-bfd@ietf.org; Tue, 24 Feb 2004 23:33:02 +0000 Date: Tue, 24 Feb 2004 15:32:05 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.62i) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <135163083661.20040224153205@psg.com> To: rtg-bfd@ietf.org Subject: Re: BFD and eBGP In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: rtg-bfd-admin@ietf.org Errors-To: rtg-bfd-admin@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: RTG Area: Bidirectional Forwarding Detection DT List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,RCVD_NUMERIC_HELO autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Did this one get dropped? -- Alex http://www.psg.com/~zinin/ Friday, January 23, 2004, 1:30:14 AM, Pekka Savola wrote: > Hi, > As I proposed BFD for static routes, it struck me (now that we > suffered a small outage due to eBGP timeout :-) that eBGP would profit > *enermously* from BFD. You usually don't run other routing protocols > on such links, so if the physical link doesn't provide link-state > notifications, you're pretty much down to very long BGP timeouts if > the link fails. > Something to add to the draft-katz-ward-bfd-v4v6-1hop-00.txt document, > only describing non-multihop case? (It's pretty trivial as well, > because you don't even have to figure which addresses to use between > the BGP session endpoints..) From exim@www1.ietf.org Wed Feb 25 01:00:09 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29222 for ; Wed, 25 Feb 2004 01:00:09 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs55-0005ZC-Vz for rtg-bfd-archive@odin.ietf.org; Wed, 25 Feb 2004 00:59:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1P5xdKB021391 for rtg-bfd-archive@odin.ietf.org; Wed, 25 Feb 2004 00:59:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs55-0005Yw-JJ for rtg-bfd-web-archive@optimus.ietf.org; Wed, 25 Feb 2004 00:59:39 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29185 for ; Wed, 25 Feb 2004 00:59:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Avs52-0007kM-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:59:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avs4D-0007ek-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:58:45 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Avs3U-0007Ym-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:58:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs3V-0005Us-6E; Wed, 25 Feb 2004 00:58:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avo53-00082d-Mr for rtg-bfd@optimus.ietf.org; Tue, 24 Feb 2004 20:43:21 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21585 for ; Tue, 24 Feb 2004 20:43:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Avo51-00025C-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 20:43:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avo4C-00021Q-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 20:42:29 -0500 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx with esmtp (Exim 4.12) id 1Avo3W-0001t3-00 for rtg-bfd@ietf.org; Tue, 24 Feb 2004 20:41:46 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 24 Feb 2004 17:38:00 -0800 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1P1fDT4020162; Tue, 24 Feb 2004 20:41:14 -0500 (EST) Received: from tnadeauw2k02 (che-vpn-cluster-1-26.cisco.com [10.86.240.26]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGH37761; Tue, 24 Feb 2004 20:41:13 -0500 (EST) Reply-To: From: "Thomas D. Nadeau" To: , Cc: "'zafar ali'" , "'David Ward'" , "'Alex Zinin'" Subject: BFD MIB Date: Tue, 24 Feb 2004 20:41:00 -0500 Organization: Cisco Systems, inc. Message-ID: <004e01c3fb40$70ba1d70$6b01a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 7bit Sender: rtg-bfd-admin@ietf.org Errors-To: rtg-bfd-admin@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: RTG Area: Bidirectional Forwarding Detection DT List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Zafar and I put together a MIB module that can be used to manage BFD. Comments/suggestions on the draft are welcome. The draft can be found here: http://www.ietf.org/internet-drafts/draft-nadeau-bfd-mib-00.txt --Tom From exim@www1.ietf.org Wed Feb 25 01:46:03 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29227 for ; Wed, 25 Feb 2004 01:00:09 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs56-0005ZU-Gn for rtg-bfd-archive@odin.ietf.org; Wed, 25 Feb 2004 00:59:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1P5xe7q021410 for rtg-bfd-archive@odin.ietf.org; Wed, 25 Feb 2004 00:59:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs56-0005ZD-7h for rtg-bfd-web-archive@optimus.ietf.org; Wed, 25 Feb 2004 00:59:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29188 for ; Wed, 25 Feb 2004 00:59:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Avs53-0007kR-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:59:37 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Avs4D-0007es-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:58:46 -0500 Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Avs3U-0007Yn-00 for rtg-bfd-web-archive@ietf.org; Wed, 25 Feb 2004 00:58:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Avs3U-0005Uj-VU; Wed, 25 Feb 2004 00:58:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnkJN-0005hF-V4 for rtg-bfd@optimus.ietf.org; Mon, 02 Feb 2004 15:04:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05543 for ; Mon, 2 Feb 2004 15:04:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnkJK-0003Gu-00 for rtg-bfd@ietf.org; Mon, 02 Feb 2004 15:04:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnkIR-0003CJ-00 for rtg-bfd@ietf.org; Mon, 02 Feb 2004 15:03:51 -0500 Received: from [169.144.2.221] (helo=uspitsmsgrtr01.pit.comms.marconi.com) by ietf-mx with esmtp (Exim 4.12) id 1AnkHZ-00031d-00; Mon, 02 Feb 2004 15:02:57 -0500 Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Feb 2004 15:02:27 -0500 Message-ID: <39469E08BD83D411A3D900204840EC55FB71BD@vie-msgusr-01.dc.fore.com> From: "Naidu, Venkata" To: "'vach.kompella@alcatel.com'" , l2vpn@ietf.org Cc: "'rtg-bfd@ietf.org'" Subject: RE: VPLS full-mesh issues Date: Mon, 2 Feb 2004 15:02:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: rtg-bfd-admin@ietf.org Errors-To: rtg-bfd-admin@ietf.org X-BeenThere: rtg-bfd@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: RTG Area: Bidirectional Forwarding Detection DT List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Vach, [ CC'ing to RTG-BFD list, because I found this related ] -> Question 1: important issue worthy of our cycles, or not? Yes. It is an important issue to consider. -> Question 2: "discover" connectivity issues or "discover and repair"? In my opinion, this fully-connected and strongly-connected graph synchrony is required by many protocols (mostly for routing protocols) - not just VPLS. If known, communication complexity (number of message overhead) can be reduced by using well established distributed algorithms (in asynchronous problem space). For now, VPLS can have some provisioning to discover connectivity issues in full-mesh topology. But, in general, a separate protocol like http://www.ietf.org/internet-drafts/draft-katz-ward-bfd-v4v6-1hop-00.txt is good to start with. If BFD can figure out the link bi-directional connectivity, any higher-level protocol knowing the full-mesh diameter can compute which of the links went down by flooding, leader-election or BFS spanning tree methods. Venkata.