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

David Ward <dward@cisco.com> Fri, 22 July 2005 20:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw47S-0007s9-OE; Fri, 22 Jul 2005 16:27:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw47S-0007s4-1p for rtg-bfd@megatron.ietf.org; Fri, 22 Jul 2005 16:27:42 -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 QAA24092 for <rtg-bfd@ietf.org>; Fri, 22 Jul 2005 16:27:39 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw4bk-00072k-RY for rtg-bfd@ietf.org; Fri, 22 Jul 2005 16:59:01 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-5.cisco.com with ESMTP; 22 Jul 2005 13:27:26 -0700
X-IronPort-AV: i="3.95,135,1120460400"; d="scan'208"; a="200065429:sNHT35368074"
Received: from cisco.com (cfcentral.cisco.com [64.101.210.32]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j6MKRGul025665; Fri, 22 Jul 2005 13:27:16 -0700 (PDT)
Received: (from wardd@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id PAA13327; Fri, 22 Jul 2005 15:27:17 -0500 (CDT)
Date: Fri, 22 Jul 2005 15:27:17 -0500
From: David Ward <dward@cisco.com>
To: Suping Zhai <zhaisuping@huawei.com>
Message-ID: <20050722152717.N9707@cfcentral.cisco.com>
References: <0IJY00KCRIBYTN@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: <0IJY00KCRIBYTN@szxml01-in.huawei.com>; from zhaisuping@huawei.com on Thu, Jul 21, 2005 at 10:36:48AM +0800
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: bfd <rtg-bfd@ietf.org>, Carlos Garcia Braschi <cgbraschi@gmail.com>
Subject: 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

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.

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. 

-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
> >>