[bmwg] IGP/Data-plane convergence proposal
Al Morton <acmorton@att.com> Wed, 23 April 2003 20:22 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 QAA05153 for <bmwg-archive@lists.ietf.org>; Wed, 23 Apr 2003 16:22:20 -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 h3NKON827735; Wed, 23 Apr 2003 16:24:24 -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 h3NKN6827694 for <bmwg@optimus.ietf.org>; Wed, 23 Apr 2003 16:23:06 -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 QAA05129 for <bmwg@ietf.org>; Wed, 23 Apr 2003 16:20:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 198QlL-00078q-00 for bmwg@ietf.org; Wed, 23 Apr 2003 16:22:39 -0400
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 198QlK-00078h-00 for bmwg@ietf.org; Wed, 23 Apr 2003 16:22:38 -0400
Received: from hogpa.mt.att.com ([135.16.74.2]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h3NKMTii011394 for <bmwg@ietf.org>; Wed, 23 Apr 2003 16:22:29 -0400 (EDT)
Received: from acmortonw.att.com by hogpa.mt.att.com (8.8.8p2+Sun/ATTEMS-1.4.1 sol2) id QAA17011; Wed, 23 Apr 2003 16:22:27 -0400 (EDT)
Message-Id: <5.2.1.1.0.20030423161811.05337100@hogpa.mt.att.com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [bmwg] IGP/Data-plane convergence proposal
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>
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] IGP/Data-plane convergence proposal Al Morton
- RE: [bmwg] IGP/Data-plane convergence proposal Shankar Rao
- Re: [bmwg] IGP/Data-plane convergence proposal Scott Bradner
- RE: [bmwg] IGP/Data-plane convergence proposal Tony DeLaRosa