[bmwg] Comments on IGP Data Plane Conv Terminology

Al Morton <acmorton@att.com> Thu, 10 July 2003 02:51 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02971 for <bmwg-archive@lists.ietf.org>; Wed, 9 Jul 2003 22:51:34 -0400 (EDT)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRWP-0004eG-Fx; Wed, 09 Jul 2003 22:51:01 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRW3-0004dq-IK for bmwg@optimus.ietf.org; Wed, 09 Jul 2003 22:50:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02962 for <bmwg@ietf.org>; Wed, 9 Jul 2003 22:50:34 -0400 (EDT)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 19aRVz-0006Jj-00 for bmwg@ietf.org; Wed, 09 Jul 2003 22:50:35 -0400
Received: from ckmso1.att.com ([] helo=ckmso1.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 19aRVy-0006Jb-00 for bmwg@ietf.org; Wed, 09 Jul 2003 22:50:34 -0400
Received: from attrh3i.attrh.att.com ([]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h6A2nnMo017822 for <bmwg@ietf.org>; Wed, 9 Jul 2003 22:50:04 -0400
Received: from custsla.mt.att.com ( by attrh3i.attrh.att.com (6.5.032) id 3EF5D3D2007BA468 for bmwg@ietf.org; Wed, 9 Jul 2003 22:49:34 -0400
Received: from acmortonw.att.com ([]) by custsla.mt.att.com (8.10.2+Sun/8.10.2) with ESMTP id h6A320q06228 for <bmwg@ietf.org>; Wed, 9 Jul 2003 23:02:00 -0400 (EDT)
Message-Id: <>
X-Sender: acm@custsla.mt.att.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 09 Jul 2003 22:49:58 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [bmwg] Comments on IGP Data Plane Conv Terminology
Sender: bmwg-admin@ietf.org
Errors-To: bmwg-admin@ietf.org
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>


Here are some suggestions for the Terminology draft:

This text can be thinned-out by removing nearby redundancy.
For example, section 3.2 Protocol Convergence has almost identical
sentences in the Discussion and Issues sections.
Also, a single sentence under section 3 saying "All measurements
defined below are externally observable, unless noted."
reduces repetition.

It may help to change the names of the different convergence time
metrics to emphasize how they differ.  Consider:

3.4   Full Convergence Time ==> Rate-Derived Convergence Time

3.6   Average Convergence Time ==> Loss-Derived Convergence Time
(in this last one, it is a bit awkward to use a statistic in the name,
and we might find ourselves reporting the Average Average Convergence Time)

Also, it will help to add more rigor to the time interval definitions.
You need to define the measurement criteria for the interval start time
and end time.  For section 3.4, this might be:
The minimum time interval beginning at the start of a measurement sample
with less than the maximum forwarding rate, and ending at the
start of the first measurement interval that returns to maximum
forwarding rate following a route convergence event.
(certainly not the final text, but I think you'll get the idea)

You might consider re-defining the Route Convergence Event Slope
(and other slopes) as "Transition Time", too.  Slope implies a
Rise over Run format, and the slope may not be constant.

hope this helps,

bmwg mailing list