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

Suping Zhai <zhaisuping@huawei.com> Sat, 23 July 2005 03:01 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwAGo-0004qf-Ri; Fri, 22 Jul 2005 23:01:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwAGo-0004qa-1g for rtg-bfd@megatron.ietf.org; Fri, 22 Jul 2005 23:01:46 -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 XAA02409 for <rtg-bfd@ietf.org>; Fri, 22 Jul 2005 23:01:43 -0400 (EDT)
Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DwAl9-0003og-Oa for rtg-bfd@ietf.org; Fri, 22 Jul 2005 23:33:08 -0400
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IK200BPA8JQUC@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 23 Jul 2005 11:04:38 +0800 (CST)
Received: from szxml01-in ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IK200BY58JQRF@szxga03-in.huawei.com> for rtg-bfd@ietf.org; Sat, 23 Jul 2005 11:04:38 +0800 (CST)
Received: from z11024 ([10.110.100.95]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IK200GTT8U6H9@szxml01-in.huawei.com>; Sat, 23 Jul 2005 11:10:54 +0800 (CST)
Date: Sat, 23 Jul 2005 11:02:06 +0800
From: Suping Zhai <zhaisuping@huawei.com>
To: David Ward <dward@cisco.com>, bfd <rtg-bfd@ietf.org>
Message-id: <0IK200GTU8U6H9@szxml01-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: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
Cc:
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
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

Dear David,
Some clarification inline, please see below.
>All -
>
>We have left the 1-hop (w/ IGP examples) and generic draft as agreed at
>the last two WG meetings. There is no real benefit (as discussed) to mentioning
>each and every app that could bootstrap a BFD session, we would never 
>standardize the doc as new ones are creeping up every day. Since the 
>base spec and 1-hop are in LC (again as agreed by the WG), I recommend
>we don't reopen this can of worms.

Geting together all the applications together is just a idea, perhaps it is difficult to realize:)  No problem.
>
>more down below. 
>
>On Thu, Jul 21, 2005 at 10:36:48AM +0800, Suping Zhai wrote:
>> Hi Carlos,
>> I am sympathy with you regarding this generic draft. 
>> And more I think that it's better if all the BFD related applications including IGP, BGP, MPLS and static routes can go together into one draft.
>> 
>> And another note, in this draft section 2, it reads as followings,
>>    The service interface with BFD is straightforward.  The application
>>    supplies session parameters (neighbor address, time parameters,
>>    protocol options), and BFD provides the session state, of which the
>>    most interesting transitions are to and from the Up state.  The
>>    application is expected to bootstrap the BFD session, as BFD has no
>>    discovery mechanism.
>> 
>> 
>> Perhaps, the session paramters of time parameters is the responsiblity of BFD session its self, not supplied by application.
>
>
>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.
Second, what does it mean by the last line above---"since BFD doesn't setup the forwarding plane, it should bootstrap ***itself***"???

Suping
>
>-DWard
>
>> 
>> I dont' what's opinions?
>> 
>> Regards,
>> suping
>> >Hi,
>> >
>> >Reading the generic document, I now have a doubt: shouldn't mentions
>> >to OSPF and IS-IS in the 1-hop draft go in a separate "IGP application
>> >document" or "OSPF / ISIS application document"? Most of the content
>> >is not related to the 1hop functionality but rather with BFD-protocol
>> >interactions, including Graceful restart.
>> >
>> >Or perhaps, as another example in the generic draft?
>> >
>> >For example, the Graceful restart mentioned in the 1hop draft, is
>> >probably applicable to all protocols that have Graceful restart (as
>> >BGP), not only to IGPs.
>> >
>> >I know it is a non negligible amount of editorial work, but will
>> >probably lay out a clear structure for the BFD standards... that, with
>> >the count already up to more than four drafts for BFD, may be a good
>> >thing. (or not, it probably depends).
>> >
>> >Regards,
>> >Carlos.
>> >
>> >2005/7/16, rtg-bfd-request@ietf.org <rtg-bfd-request@ietf.org>:
>> >> Date: Fri, 15 Jul 2005 15:50:02 -0400
>> >> From: Internet-Drafts@ietf.org
>> >> Subject: I-D ACTION:draft-ietf-bfd-generic-00.txt
>> >> To: i-d-announce@ietf.org
>> >> Cc: rtg-bfd@ietf.org
>> >> Message-ID: <E1DtWCA-0001vE-Uf@newodin.ietf.org>
>> >> Content-Type: text/plain; charset="us-ascii"
>> >> 
>> >> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> >> This draft is a work item of the Bidirectional Forwarding Detection Working Group of the IETF.
>> >> 
>> >>         Title           : Generic Application of BFD
>> >>         Author(s)       : D. Katz, D. Ward
>> >>         Filename        : draft-ietf-bfd-generic-00.txt
>> >>         Pages           : 7
>> >>         Date            : 2005-7-15
>> >> 
>> >>    This document describes the generic application of the Bidirectional
>> >>    Forwarding Detection (BFD) protocol in environments not specifically
>> >>    documented in other specifications.  Comments on this draft should be
>> >>    directed to rtg-bfd@ietf.org.
>> >> 
>> >> A URL for this Internet-Draft is:
>> >> http://www.ietf.org/internet-drafts/draft-ietf-bfd-generic-00.txt
>> >> 
>> >> To remove yourself from the I-D Announcement list, send a message to
>> >> i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.
>> >> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>> >> to change your subscription settings.
>> >> 
>> >> 
>> >> Internet-Drafts are also available by anonymous FTP. Login with the username
>> >> "anonymous" and a password of your e-mail address. After logging in,
>> >> type "cd internet-drafts" and then
>> >>         "get draft-ietf-bfd-generic-00.txt".
>> >> 
>> >> A list of Internet-Drafts directories can be found in
>> >> http://www.ietf.org/shadow.html
>> >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> >>