Re: [bmwg] WG Last Call: OSPF convergence benchmarking

Scott Poretsky <sporetsky@avici.com> Tue, 20 May 2003 14:29 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 KAA15542 for <bmwg-archive@odin.ietf.org>; Tue, 20 May 2003 10:29:50 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KDxIn03617 for bmwg-archive@odin.ietf.org; Tue, 20 May 2003 09:59:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KDwWB03579; Tue, 20 May 2003 09:58:32 -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 h4KDvuB03534 for <bmwg@optimus.ietf.org>; Tue, 20 May 2003 09:57:56 -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 KAA15501 for <bmwg@ietf.org>; Tue, 20 May 2003 10:27:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I87d-0005f1-00 for bmwg@ietf.org; Tue, 20 May 2003 10:29:45 -0400
Received: from [12.38.212.174] (helo=mailhost.avici.com) by ietf-mx with esmtp (Exim 4.12) id 19I87c-0005eu-00 for bmwg@ietf.org; Tue, 20 May 2003 10:29:44 -0400
Received: from sporetsky-lt.avici.com ([10.2.103.34]) by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id h4KEUHhh021133; Tue, 20 May 2003 10:30:17 -0400
Message-Id: <5.0.2.1.2.20030519194303.0279eec0@pop.avici.com>
X-Sender: sporetsky@pop.avici.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 19 May 2003 19:47:19 -0400
To: Russ White <riw@cisco.com>
From: Scott Poretsky <sporetsky@avici.com>
Subject: Re: [bmwg] WG Last Call: OSPF convergence benchmarking
Cc: Kevin Dubray <kdubray@juniper.net>, bmwg@ietf.org
In-Reply-To: <Pine.WNT.4.55.0305171133490.1392@russpc>
References: <5.0.2.1.2.20030517080557.0278cf40@pop.avici.com> <5.0.2.1.2.20030517080557.0278cf40@pop.avici.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>

Russ,

Since the test cases in this methodology can be used for inter-area, 
intra-area, and a mix, I recommend that no restrictions are placed upon the 
methodologies.  This would mean that the draft explicitly states it can be 
used for all the types of OSPF routes.  You can then write another draft 
for test cases specific to inter-area and a mix.

Scott

At 11:36 AM 5/17/2003 -0400, Russ White wrote:

>I agree that many of these same tests could be used for intraarea
>measurements, but I also think there are unique tests that could be run for
>intraarea and external route issues. I would like to see the intraarea and
>external issues in a seperate draft, which refers to this draft as ways to
>measure the more common elements of OSPF performance.
>
>Thoughts?
>
>:-)
>
>Russ
>
>
>
>On Sat, 17 May 2003, Scott Poretsky wrote:
>
> > I support draft-ietf-bmwg-ospfconv-intraarea-04.txt be given to the Area
> > Directors for consideration in progressing the draft to an Informational
> > RFC.  I have one question for the authors- why do these methodologies apply
> > to only OSPF intraarea routes?  It seems that these same control plane
> > convergence methodologies can be applied for OSPF inter-area routes and a
> > mix of inter-area and intra-area routes, which is the practical scenario.
> >
> > Scott
> >
> > At 05:28 PM 5/7/2003 -0400, Kevin Dubray wrote:
> > >BMWG'ers:
> > >
> > >A WG Last Call period for the Internet-Drafts regarding
> > >OSPF convergence benchmarking terminology, methodology, and
> > >benchmark applicability,
> > >
> > >    <draft-ietf-bmwg-ospfconv-term-03.txt>,
> > >    <draft-ietf-bmwg-ospfconv-intraarea-04.txt>,
> > >    <draft-ietf-bmwg-ospfconv-applicability-02.txt>
> > >
> > >will be open from 7 May 2003 until 17 May 2003.
> > >
> > >These I-Ds contain modifications based on feedback from the previous
> > >WG Last Call.
> > >
> > >Please weigh in on whether or not you feel each individual draft
> > >should not be given to the Area Directors for consideration in
> > >progressing the draft to an Informational RFC.  Send your comments
> > >to this list or kdubray@juniper.net.
> > >
> > >
> > >URLs for the Internet-Drafts are:
> > >
> > >http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-term-03.txt
> > >http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-intraarea- 
> 04.txt
> > >http://www.ietf.org/internet-drafts/draft-ietf-bmwg-ospfconv-applicabil 
> ity-02.txt
> > >
> > >
> > >
> > >_______________________________________________
> > >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
> >
>
>__________________________________
>riw@cisco.com CCIE <>< Grace Alone
>
>_______________________________________________
>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