document layout for singlehop, multihop and generic

Pekka Savola <pekkas@netcore.fi> Tue, 25 October 2005 10:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EULwc-0006pB-QJ; Tue, 25 Oct 2005 06:22:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EULwa-0006nn-RI for rtg-bfd@megatron.ietf.org; Tue, 25 Oct 2005 06:22:12 -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 GAA04999 for <rtg-bfd@ietf.org>; Tue, 25 Oct 2005 06:21:57 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUM9W-0005L3-KI for rtg-bfd@ietf.org; Tue, 25 Oct 2005 06:35:35 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j9PAM2T21260 for <rtg-bfd@ietf.org>; Tue, 25 Oct 2005 13:22:02 +0300
Date: Tue, 25 Oct 2005 13:22:02 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: rtg-bfd@ietf.org
Message-ID: <Pine.LNX.4.64.0510251311450.20898@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: document layout for singlehop, multihop and generic
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

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