Re: document layout for singlehop, multihop and generic
Suping Zhai <zhaisuping@huawei.com> Tue, 25 October 2005 11:21 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUMs0-0001pZ-6D; Tue, 25 Oct 2005 07:21:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUMry-0001oI-Lx for rtg-bfd@megatron.ietf.org; Tue, 25 Oct 2005 07:21:30 -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 HAA07539 for <rtg-bfd@ietf.org>; Tue, 25 Oct 2005 07:21:16 -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 1EUN4u-0006lH-AV for rtg-bfd@ietf.org; Tue, 25 Oct 2005 07:34:53 -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 <0IOW00LZPY3C3L@szxga02-in.huawei.com> for rtg-bfd@ietf.org; Tue, 25 Oct 2005 19:18:49 +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 <0IOW00DBVY3CPC@szxga02-in.huawei.com> for rtg-bfd@ietf.org; Tue, 25 Oct 2005 19:18:48 +0800 (CST)
Received: from z11024 ([10.110.100.87]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IOW00EVHY34T2@szxml02-in.huawei.com>; Tue, 25 Oct 2005 19:18:40 +0800 (CST)
Date: Tue, 25 Oct 2005 19:10:56 +0800
From: Suping Zhai <zhaisuping@huawei.com>
To: Pekka Savola <pekkas@netcore.fi>, bfd <rtg-bfd@ietf.org>
Message-id: <0IOW00EVJY34T2@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: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc:
Subject: Re: document layout for singlehop, multihop and generic
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
Hi Pekka, I have the same feeling with you. In fact before last 63th meeting, including me and you, some other people provide the alike concern. Based on the your suggestions I propose further that the following separation be considered in the upcoming meeting, and to have a logical assignment for various documents: 1) First bfd-generic-01 is a common guidance for all the bfd draft, for the generic purpose, 2) Second bfd-multihop-xx, bfd-v4v6-1hop-xx, bfd-mpls-xx separately describe the specific deployment of BFD in various situations if the generic document doesn't cover; 3) Last the protocol specific descriptions e.g. OSFP/ISIS/BGP(IBGP and EBGP)/RIPv2 with BFD are given out in detail, including the bootstrap methods, interactions etc in the very specific environment. Since that almost all documents have been in a relative stable state, it's not very difficult to seperate the existing draft according to the above rules. Hope that BFD work group will produce a set of sensible documents for the vendors or operators to follow. Best Regards, Suping >Hi, > >I'm still puzzled by the coverage of various documents: > > 1) bfd-multihop-03: about 3 pages of very generic (non-protocol >specific) guidance on multihop BFD sessions. > > 2) bfd-v4v6-1hop-04: the first 4.5 pages are very generic single-hop >BGP guidance (applicable to any single hop BFD application), the next >4 pages detail a number of OSPF/IS-IS details for single-hop cases > > 3) bfd-generic-01: about 5 pages of generic BFD guidance (not >specific to either single or multihop). > >This seems like patchwork. IMHO, a more logical separation might be >having everything generic (either single or multihop) in one document >and moving the protocol-specific details out of v2v6-1hop to a >separate BFD+OSPF/ISIS document. > >-- >Pekka Savola "You each name yourselves king, yet the >Netcore Oy kingdom bleeds." >Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
- Re: document layout for singlehop, multihop and g… Suping Zhai
- document layout for singlehop, multihop and gener… Pekka Savola
- Re: document layout for singlehop, multihop and g… Thomas D. Nadeau
- RE: document layout for singlehop, multihop and g… Zafar Ali (zali)
- Re: document layout for singlehop, multihop and g… David Ward
- RE: document layout for singlehop, multihop and g… Peter Arberg
- RE: document layout for singlehop, multihop and g… richard.spencer
- RE: document layout for singlehop, multihop and g… Peter Arberg