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

Okay, which seems to imply we should change the name of the draft, and work
on the into section some.... Any other places?

:-)

Russ

On Mon, 19 May 2003, Scott Poretsky wrote:

> 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
>
>

__________________________________
riw@cisco.com CCIE <>< Grace Alone

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