Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.txt
David Ward <dward@cisco.com> Sun, 24 July 2005 22:17 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dwomx-0003yb-0Y; Sun, 24 Jul 2005 18:17:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dwomv-0003yT-7L for rtg-bfd@megatron.ietf.org; Sun, 24 Jul 2005 18:17:37 -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 SAA29948 for <rtg-bfd@ietf.org>; Sun, 24 Jul 2005 18:17:34 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DwpHd-00082U-Kz for rtg-bfd@ietf.org; Sun, 24 Jul 2005 18:49:22 -0400
Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 24 Jul 2005 15:17:27 -0700
X-IronPort-AV: i="3.95,138,1120460400"; d="scan'208"; a="200269697:sNHT30339322"
Received: from cisco.com (cfcentral.cisco.com [64.101.210.32]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j6OMHO6p028120; Sun, 24 Jul 2005 15:17:24 -0700 (PDT)
Received: (from wardd@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id RAA18713; Sun, 24 Jul 2005 17:17:22 -0500 (CDT)
Date: Sun, 24 Jul 2005 17:17:22 -0500
From: David Ward <dward@cisco.com>
To: Suping Zhai <zhaisuping@huawei.com>
Message-ID: <20050724171722.G17755@cfcentral.cisco.com>
References: <0IK200GTU8U6H9@szxml01-in.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <0IK200GTU8U6H9@szxml01-in.huawei.com>; from zhaisuping@huawei.com on Sat, Jul 23, 2005 at 11:02:06AM +0800
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: bfd <rtg-bfd@ietf.org>, David Ward <dward@cisco.com>
Subject: 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
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
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. > 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
- I-D ACTION:draft-ietf-bfd-generic-00.txt Carlos Garcia Braschi
- Re: I-D ACTION:draft-ietf-bfd-generic-00.txt Suping Zhai
- I-D ACTION:draft-ietf-bfd-generic-00.txt Internet-Drafts
- Re: I-D ACTION:draft-ietf-bfd-generic-00.txt Suping Zhai
- Re: I-D ACTION:draft-ietf-bfd-generic-00.txt David Ward
- Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.txt Suping Zhai
- Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.txt David Ward
- Re: Re: Re: I-D ACTION:draft-ietf-bfd-generic-00.… Suping Zhai