IETF Logo Mail Archive

Re: document layout for singlehop, multihop and generic

David Ward <dward@cisco.com> Tue, 25 October 2005 20:45 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVg4-0006ui-EX; Tue, 25 Oct 2005 16:45:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVg2-0006q5-Cr for rtg-bfd@megatron.ietf.org; Tue, 25 Oct 2005 16:45: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 QAA07218 for <rtg-bfd@ietf.org>; Tue, 25 Oct 2005 16:45:30 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVt2-0007Z6-5L for rtg-bfd@ietf.org; Tue, 25 Oct 2005 16:59:13 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 25 Oct 2005 13:45:31 -0700
X-IronPort-AV: i="3.97,250,1125903600"; d="scan'208"; a="356606044:sNHT2850249352"
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9PKjS94021367; Tue, 25 Oct 2005 13:45:29 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 13:45:27 -0700
Received: from [128.107.9.48] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 13:45:26 -0700
User-Agent: Microsoft-Entourage/10.1.6.040913.0
Date: Tue, 25 Oct 2005 15:45:36 -0500
From: David Ward <dward@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>, rtg-bfd@ietf.org, David Ward <dward@cisco.com>, Jeffrey Haas <jhaas@nexthop.com>
Message-ID: <BF8403A0.13B87%dward@cisco.com>
In-Reply-To: <Pine.LNX.4.64.0510251311450.20898@netcore.fi>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 25 Oct 2005 20:45:26.0971 (UTC) FILETIME=[079120B0:01C5D9A5]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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
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

We covered this at the last several WG meetings. The issue is: reorganizing
the docs w/o changing the content vs getting the docs to spec ... The WG
agreed to get the docs to full standard.

-DWard


On 10/25/05 5:22 AM, "Pekka Savola" <pekkas@netcore.fi> wrote:

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

v2.23.0 | Report a Bug | By Email