Re: [bmwg] Comments on IGP Data Plane Conv Terminology

Scott Poretsky <> Thu, 10 July 2003 15:31 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id LAA07574 for <>; Thu, 10 Jul 2003 11:31:33 -0400 (EDT)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.20) id 19adNt-0001mW-Ry; Thu, 10 Jul 2003 11:31:01 -0400
Received: from ([] by with esmtp (Exim 4.20) id 19adNo-0001lr-0o for; Thu, 10 Jul 2003 11:30:56 -0400
Received: from ietf-mx ( []) by (8.9.1a/8.9.1a) with ESMTP id LAA07525 for <>; Thu, 10 Jul 2003 11:30:51 -0400 (EDT)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 19adNn-00041h-00 for; Thu, 10 Jul 2003 11:30:55 -0400
Received: from [] ( by ietf-mx with esmtp (Exim 4.12) id 19adNm-00041R-00 for; Thu, 10 Jul 2003 11:30:54 -0400
Received: from ([]) by (8.11.0/8.11.0) with ESMTP id h6AFSc324547; Thu, 10 Jul 2003 11:28:38 -0400 (EDT)
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 10 Jul 2003 11:30:42 -0400
To: Al Morton <>,
From: Scott Poretsky <>
Subject: Re: [bmwg] Comments on IGP Data Plane Conv Terminology
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: Benchmarking Methodology Working Group <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>


Great suggestions.  We will incorporate them all for the 01 version.


At 10:49 PM 7/9/2003 -0400, Al Morton wrote:
>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

bmwg mailing list