Benchmarking Methodology (bmwg)

Kevin Dubray | 3 Apr 2008 17:49

Re: Work item proposal: extending firewallbenchmarkingmethodology and terminology

In which dimensions are the overlap, Scott?  AccStress seems to want to 
describe coexisting applications (breadth?) in a generic manner; the 
extension proposed seems to increase depth in specific context.

I think the effort has merit; I would like to see a I-D (or at least a 
possible table of contents) to better reconcile possible overlap.. 
(whether AccStress, IPsec, etc.)

-Kevin

Scott Poretsky wrote:
>
> This proposal as written seems to have quite a bit of overlap with the 
> existing Accelerated Stress work item.
>
> Scott
>
> -----Original Message-----
> From: bmwg-bounces <at> ietf.org [mailto:bmwg-bounces <at> ietf.org] On Behalf 
> Of Eyal Manor
> Sent: Thursday, April 03, 2008 5:26 AM
> To: bmwg <at> ietf.org
> Subject: [bmwg] Work item proposal: extending firewall 
> benchmarkingmethodology and terminology
>
> Dear BMWG members,
>
> I would like to have the group's feedback on the following proposal, with
> the goal of adding it to the BMWG charter. We would like to extend RFC 
> 2647

(Continue reading)

headers

Scott Poretsky | 3 Apr 2008 22:55

Re: Work item proposal: extending firewallbenchmarkingmethodology and terminology

Excerpts provided here.  Scott
-------------

  	            Methodology for Benchmarking 
              Accelerated Stress with Operational Security 
             <draft-ietf-bmwg-acc-bench-meth-opsec-00.txt>

   ABSTRACT
   Routers in an operational network are simultaneously configured with 
   multiple protocols and security policies while forwarding traffic and

   being managed.  To accurately benchmark a router for deployment it is

   necessary that the router be tested in these simultaneous operational

   conditions, which is known as Stress Testing.  This document provides

   the Methodology for performing Stress Benchmarking of networking 
   devices when subjected to instability as described in [7].  
   Descriptions of test topology, benchmarks and reporting format are 
   provided in addition to procedures for conducting various test cases.

   This methodology is based upon the accelerated stress methodology 
   guidelines [6] and is to be used with the companion terminology 
   document [4].

    4.1 Restart Under Load
        Objective
        The purpose of this test is to benchmark the performance of the
DUT

(Continue reading)

headers

Eyal Manor | 6 Apr 2008 09:47

Re: Work item proposal: extendingfirewallbenchmarkingmethodology and terminology

Hello Scott,

This suggested proposal and the Accelerated work item have different goals:

As I understand the "Accelerated Stress" work item, it comes to benchmarks
the stability of routers in different scenarios under load of multiple
routing protocols, interface flapping, routes flapping, management
operations, etc'

Our suggested proposal comes to extend existing Firewall performance
benchmarking RFCs (2647 and 3511). We aim to define the criterions of
benchmarking the performance of "next generation" firewalls that provide
IDS/IPS capabilities, deep inspection, enhanced DoS mitigation, and UTM
features such as Anti Virus, Anti Spam, and Web Filtering.

The main motivation is to benchmark the performance of these features, and
less to "stress" the Firewall. 

If you still see an overlap between these two, I'll be happy to continue
discussing about that with you together with the group of people that work
on this new suggestion.

/Eyal. 

-----Original Message-----
From: bmwg-bounces <at> ietf.org [mailto:bmwg-bounces <at> ietf.org] On Behalf Of
Scott Poretsky
Sent: Thursday, April 03, 2008 11:56 PM
To: Kevin Dubray; bmwg <at> ietf.org
Subject: Re: [bmwg] Work item proposal:

(Continue reading)