Re: Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.txt

Suping Zhai <zhaisuping@huawei.com> Mon, 25 July 2005 04:10 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwuIt-0005Tj-4v; Mon, 25 Jul 2005 00:10:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwuIs-0005TZ-8W for rtg-bfd@megatron.ietf.org; Mon, 25 Jul 2005 00:10:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20654 for <rtg-bfd@ietf.org>; Mon, 25 Jul 2005 00:10:54 -0400 (EDT)
Received: from szxga02-in.huawei.com ([61.144.161.54] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dwune-0000j1-1a for rtg-bfd@ietf.org; Mon, 25 Jul 2005 00:42:46 -0400
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IK6003M517XO2@szxga02-in.huawei.com> for rtg-bfd@ietf.org; Mon, 25 Jul 2005 12:16:46 +0800 (CST)
Received: from szxml02-in ([172.24.1.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IK60007A17XDH@szxga02-in.huawei.com> for rtg-bfd@ietf.org; Mon, 25 Jul 2005 12:16:45 +0800 (CST)
Received: from z11024 ([10.110.100.95]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IK600CRL17R34@szxml02-in.huawei.com>; Mon, 25 Jul 2005 12:16:40 +0800 (CST)
Date: Mon, 25 Jul 2005 12:10:56 +0800
From: Suping Zhai <zhaisuping@huawei.com>
To: David Ward <dward@cisco.com>, bfd <rtg-bfd@ietf.org>
Message-id: <0IK600CRM17S34@szxml02-in.huawei.com>
Organization: huawei
MIME-version: 1.0
X-Mailer: Foxmail 4.2 [cn]
Content-type: text/plain; charset="GB2312"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.txt
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: zhaisuping@huawei.com
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

David,
Please see the inline below.
>Suping -
>
>On Sat, Jul 23, 2005 at 11:02:06AM +0800, Suping Zhai wrote:
>....snip..
>
>> >
>> >
>> >I don't see how this is possible. BFD checks the forwarding plane created
>> >by other applications. Those applications are requesting from BFD the 
>> >fast notification of a failure. Since BFD doesn't setup the forwarding plane,
>> >it should bootstrap itself. 
>> 
>> 
>> First, I mean that the time parameters is negotiated by the BFD session, not supplied by the applicatons.
>
>
>The time parameters should be defined by config. Either via template, by the
>bootstrapping app, etc. I don't think I see an issue but, I might be still
> missing your point.

Yes, the time paramters are defined by config. But in the BFD session, time parameters could be changed during the negotiation. Perhaps it's more clear to add some description like "....and BFD provides the **parameters negotiation** and the session state, of which the most interesting transitions are to and from the Up state." --That's my point.

Suping

>
>
>> Second, what does it mean by the last line above---"since BFD doesn't setup the forwarding plane, it should bootstrap ***itself***"???
>
>
>It should be negative ... "should NOT bootstrap itself." Sorry for the 
>confusion.
>
>-DWard