Re: draft-suping-bfd-mpls-fecmismatch-00 questions

"Thomas D. Nadeau" <tnadeau@cisco.com> Sat, 26 February 2005 14:16 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03087; Sat, 26 Feb 2005 09:16:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D52kU-0004Fc-Ed; Sat, 26 Feb 2005 09:16:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D52jU-0002Vj-6v; Sat, 26 Feb 2005 09:15:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D52jS-0002T9-9M for rtg-bfd@megatron.ietf.org; Sat, 26 Feb 2005 09:15:46 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03065 for <rtg-bfd@ietf.org>; Sat, 26 Feb 2005 09:15:44 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D52jm-0004Ev-SY for rtg-bfd@ietf.org; Sat, 26 Feb 2005 09:16:08 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 26 Feb 2005 07:30:40 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.90,118,1107734400"; d="scan'208"; a="229555369:sNHT24597580"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1QEFPuC027203; Sat, 26 Feb 2005 06:15:26 -0800 (PST)
Received: from [192.168.1.100] (che-vpn-cluster-1-214.cisco.com [10.86.240.214]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APK50411; Sat, 26 Feb 2005 09:15:26 -0500 (EST)
In-Reply-To: <0ICH00M6UWPNRF@szxml02-in.huawei.com>
References: <0ICH00M6UWPNRF@szxml02-in.huawei.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <82b48ee320e24671ca27050d4b5cc86a@cisco.com>
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Date: Sat, 26 Feb 2005 09:15:25 -0500
To: zhaisuping@huawei.com
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: draft-suping-bfd-mpls-fecmismatch-00 questions
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

On Feb 25, 2005, at 8:41 PM, zhaisuping wrote:

> Hi, all
> The purpose of FEC filter in BFD is to detect the consistence of
> the control plane and data plane. So that in the MPLS network, just
> running the BFD session(LSP-Ping is not needed) is enough for the
> defect detection. Or else such tools as LSP-Ping is needed because
> the BFD session can't detect the inconsistence of the control plane
> and data plane.

	There are cases where BFD/MPLS will work and return
a positive result, but the LSP is actually broken.
If you run LSP ping, this will certainly detect (and report) the
failure.  This is why a combination of both tools is necessary.
BFD with or without your FEC filter will not solve all of the
problems alone.

	--Tom


> In the section 2 of the draft, there is description of the
> problem the draft want to solve.
>>> Wouldn't LSP-Ping (or VCCV) be a more appropriate place to do this
>>> filter verification?
>
>
>>
>> LSP-Ping does a verification on the FEC itself, so a filter would add
>> nothing.
>>
>> VCCV is not a protocol.  Just a little sideband for sending IP packets
>> down a pseudowire so that you can run LSP-Ping, BFD, etc. between the
>> two ends.
>>
>> ....George
>>
>> ====================================================================== 
>> ==
>> George Swallow             Cisco Systems                  (978)  
>> 936-1398
>>                           1414 Massachusetts Avenue
>>                           Boxborough, MA 01719
>