RE: [bmwg] IGP/Data-plane convergence proposal

"Shankar Rao" <srao@qmail.qwest.net> Mon, 28 April 2003 13:38 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00507 for <bmwg-archive@lists.ietf.org>; Mon, 28 Apr 2003 09:38:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SDg4811035; Mon, 28 Apr 2003 09:42:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3PHqi814634 for <bmwg@optimus.ietf.org>; Fri, 25 Apr 2003 13:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16563 for <bmwg@ietf.org>; Fri, 25 Apr 2003 13:49:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1997Ly-0002So-00 for bmwg@ietf.org; Fri, 25 Apr 2003 13:51:18 -0400
Received: from uswgne22.uswest.com ([204.26.87.76]) by ietf-mx with esmtp (Exim 4.12) id 1997Lx-0002Sk-00 for bmwg@ietf.org; Fri, 25 Apr 2003 13:51:17 -0400
Received: from egate-ne7.uswc.uswest.com (mailgate.uswc.uswest.com [151.117.69.18]) by uswgne22.uswest.com (8.xx.x/8.xx.x) with ESMTP id h3PHoui1007463; Fri, 25 Apr 2003 12:50:57 -0500 (CDT)
Received: from denntex012.qwest.net (localhost [127.0.0.1]) by egate-ne7.uswc.uswest.com (8.12.8/8.12.8) with ESMTP id h3PHou2j003424; Fri, 25 Apr 2003 12:50:56 -0500 (CDT)
Received: from srao (srao.zone0.qintra.com [10.0.84.152]) by denntex012.qwest.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2656.59) id HJ9ZL770; Fri, 25 Apr 2003 11:50:56 -0600
Reply-To: srao@qwest.com
From: Shankar Rao <srao@qmail.qwest.net>
To: bmwg@ietf.org
Cc: acmorton@att.com
Subject: RE: [bmwg] IGP/Data-plane convergence proposal
Date: Fri, 25 Apr 2003 11:50:53 -0600
Organization: Qwest
Message-ID: <015401c30b53$3718d030$9854000a@srao>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <5.0.2.1.2.20030425132600.02e83b60@pop.avici.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

I support this effort, and recommend that this BMWG undertake this work
as a WG deliverable. 

As as service provider, we find this work to be directly applicable and
relevant to measuring key availability parameters of carrier networks.

Shankar.

>X-Sender: acm1@hogpa.mt.att.com (Unverified)
>X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
>Date: Wed, 23 Apr 2003 16:22:25 -0400
>To: <bmwg@ietf.org>
>From: Al Morton <acmorton@att.com>
>Subject: [bmwg] IGP/Data-plane convergence proposal
>Sender: bmwg-admin@ietf.org
>X-BeenThere: bmwg@ietf.org
>X-Mailman-Version: 2.0.12
>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>
>X-Avici-MailScanner: Not scanned: please contact your Internet E-Mail
>Service Provider for details
>X-Avici-MailScanner-SpamCheck: not spam, SpamAssassin (score=-9.3,
>         required 5, AWL, BAYES_20)
>
>BMWG,
>
>Now that we have made significant progress toward completing the OSPF 
>Convergence I-Ds, it has been proposed that the BMWG support a new work

>item relative to 3 individually-submitted I-Ds, titled:
>
>"Benchmarking Applicability for IGP Route Convergence" 
>http://www.ietf.org/internet-drafts/draft-poretsky-igp-convergence-app-
>00.txt
>"Terminology for Benchmarking IGP Convergence"
>http://www.ietf.org/internet-drafts/draft-poretsky-igp-convergence-term
-00.txt
>"Benchmarking Methodology for IGP Convergence"
>http://www.ietf.org/internet-drafts/draft-poretsky-igp-convergence-meth
-00.txt
>
>
>Goal:
>
>If undertaken by the WG, the objective is to produce applicability, 
>terminology, and methodology drafts that specify the benchmarking of 
>IGP convergence in routers and systems under test.  Route convergence 
>is assessed by active measurements of packet transfer, called data 
>plane measurements to distinguish them from measurements of the control

>plane.
>
>Scope:
>
>The focus of this effort is to benchmark the route convergence of 
>Routers running a link state IGP such as OSPF or ISIS.  Other routing 
>protocols are outside the scope of this effort.
>
>Motivation:
>
>Service Providers seek minimal IGP Convergence time, and that time is a

>key metric of system/network design and router design. Network 
>convergence time may be improved through deployment of fast converging 
>routers.
>
>Network users consider packet loss a key service quality metric. 
>Intervals of high packet loss are externally observable events having 
>direct impact on their application performance. IGP Route Convergence 
>time is a Direct Measure of Quality (DMOQ) when benchmarking the data 
>plane's ability to support continuous flows.
>
>For these reasons it is important to develop a standard methodology and

>terminology for benchmarking router IGP convergence that measures 
>performance in the data plane. The applicability document describes all

>of the factors that influence a convergence measurement, and how a 
>purely black box test can be designed to account for them.
>
>Schedule:
>
>If you wish to offer your thoughts as to whether the BMWG should or 
>should not undertake the effort as a WG deliverable, please email your 
>comments to this list or acmorton@att.com no later than 21 May 03.
>
>_______________________________________________
>bmwg mailing list
>bmwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/bmwg


_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg