Re: [bmwg] Call for adoption: draft-balarajah-bmwg-ngfw-performance

"Brian Monkman" <bmonkman@netsecopen.org> Thu, 25 October 2018 13:30 UTC

Return-Path: <bmonkman@netsecopen.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE47130E58 for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2018 06:30:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netsecopen-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6KEW61orA3H for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2018 06:30:15 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAE54130E5C for <bmwg@ietf.org>; Thu, 25 Oct 2018 06:30:09 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id d14-v6so9803627qto.4 for <bmwg@ietf.org>; Thu, 25 Oct 2018 06:30:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netsecopen-org.20150623.gappssmtp.com; s=20150623; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=0nJeQz5azwS5YT9G0sOVffqGjpxanuLg2uAIib0bpks=; b=yEF7Z39HNV9dLmE0MhoBnePssgV8sxhDnBLVV2QVNlzo72flhGMOI+0HRA/LuB7f7J An9nMh+BpdhKsG3H0iwkD6LSuI48CryqgoyMJy9oey7Qfu5EnLXu5zbigljDhaK4ufMy 2JBnJHRyn1EO8nSldfXqbv+IwAG5hH9UcD6wXFGt/0iyhzj129jgOJD336MbXRGobvdN o5d7HC9DQILWnyJqUNz9kZn8lxR8cXmvzpvjDEoVZZrvynVtaSUpsjxTbrPNgTNpjK3G 1BjC7EbYrms8Szh0TVEhxb0UVV/GmoHI/sZN//Arhy3m5/K8XxpeUf58fPVZODQ2Ahhs KDFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=0nJeQz5azwS5YT9G0sOVffqGjpxanuLg2uAIib0bpks=; b=IdfEka2v4oBHuhaXWxWmIjr+w9ju7A08DNTlCu6gtPIGCZV5lnH+R8B1Fe4hs4VY3d BqVNPktWNo7qs90onWUdbE7n/OpzFGhHbLW5PKJsvZc8SmXQUUrK9y/w88jOI3FAYxyp 3yhuDFE1mjdi2ZZxOJ2udApuqtguciknPnHXtEEBN6d7Eb1ztShVqqijU/G14JSYtsKP h93uu1nme1Zu89DZ3n3l2/OGVi6fo4pKu0hDOpxaSr7pJKIfsZaL5KHgUCP4jbJn7/hu VZ1p6v7V90cyswoA7xeYoV654vD/6BO9L7TmVXjO+VWuatxh9F0gXV9NNHqRRRubWT8c /AwQ==
X-Gm-Message-State: AGRZ1gLMX84DVWruhbna+jTgqE2d+/5CqzEnQZ1n3f2wX6rceUUc6siF ozqyp1o3NhzJP2lDj2IMBwoofA==
X-Google-Smtp-Source: AJdET5c8DbZTGv0WnfBgDcBD/7KR0+BsE/ovBGbkaSKChXmtVx3rvFY4Q6FGuZFzEAgjeAIKe3BtrA==
X-Received: by 2002:a0c:9384:: with SMTP id f4mr1525020qvf.239.1540474208656; Thu, 25 Oct 2018 06:30:08 -0700 (PDT)
Received: from BrianPC (c-98-235-201-224.hsd1.pa.comcast.net. [98.235.201.224]) by smtp.gmail.com with ESMTPSA id k188-v6sm3160182qkb.3.2018.10.25.06.30.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Oct 2018 06:30:07 -0700 (PDT)
From: Brian Monkman <bmonkman@netsecopen.org>
To: "'MORTON, ALFRED C (AL)'" <acm@research.att.com>, bmwg@ietf.org
References: <4D7F4AD313D3FC43A053B309F97543CF557A38BD@njmtexg5.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF557A38BD@njmtexg5.research.att.com>
Date: Thu, 25 Oct 2018 09:30:03 -0400
Message-ID: <000501d46c66$d6f39a60$84dacf20$@netsecopen.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQL6aEN143tNWjkPlzryAxnrGrmZlKLj+85g
Content-Language: en-ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/lOaI91nczsAk4dhj8Pihci3af2o>
Subject: Re: [bmwg] Call for adoption: draft-balarajah-bmwg-ngfw-performance
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 13:30:18 -0000

Al,

My comments are inline below.

Brian

-----Original Message-----
From: bmwg <bmwg-bounces@ietf.org> On Behalf Of MORTON, ALFRED C (AL)
Sent: October 21, 2018 2:42 PM
To: bmwg@ietf.org
Subject: Re: [bmwg] Call for adoption: draft-balarajah-bmwg-ngfw-performance

BMWG,

As we consider this draft, I have the following administrative questions to
discuss.

Al
bmwg co-chair

Benchmarking Methodology Working Group                      B. Balarajah
Internet-Draft                                           C. Rossenhoevel
Intended status: Informational                                  EANTC AG
Expires: January 3, 2019                                    July 2, 2018
[acm]
Admin questions: 
Will this draft Update or Replace or make Obsolete RFC3511?

[bpm] We view this as somewhat separate from RFC3511. Most of RFC3511 is
still valid when it comes to basic network firewalls. This proposed draft is
meant to go well beyond that by addressing the needs to NGFWs. Since basic
firewalling technologies are still in active use RFC3511 is still valid.

The WG should be clear about this aspect, it can't be omitted IMO.
(question, is any part of 3511 referenced here?) Will this work benefit from
Early SEC-DIR review?
WIll this work benefit from early APPS-DIR review? (especially HTTPS/browser
aspects) Will this work benefit from TSV-AREA review? (TCP aspects, other
transport...)

[bpm] May people were involved in the development of this proposal, with a
very wide scope of knowledge and expertise. Folks form security product
vendors, test labs and test tool vendors. I don't think having other areas
review this wold be of benefit if it is going to lengthen the review
process. 

> -----Original Message-----
> From: MORTON, ALFRED C (AL)
> Sent: Sunday, October 21, 2018 2:39 PM
> To: bmwg@ietf.org
> Subject: Call for adoption: draft-balarajah-bmwg-ngfw-performance
> 
> BMWG,
> 
> At our three meetings so far this year, the BMWG reviewed a version of 
> the Internet Draft on
> 
> Benchmarking Methodology for Network Security Device Performance
>    
> https://tools.ietf.org/html/draft-balarajah-bmwg-ngfw-performance-05
> 
> The BMWG has already adopted a milestone on our charter:
> 
> Aug 2018 	Methodology for Next-Gen Firewall Benchmarking to IESG
Review
> (in retrospect, this milestone was quite aspirational!)
> 
> This message, therefore, starts a call for adoption on:
> 
> Benchmarking Methodology for Network Security Device Performance
>    
> https://tools.ietf.org/html/draft-balarajah-bmwg-ngfw-performance-05
> 
> to run until Friday, November 9, 2018.
> 
> Please reply to bmwg@ietf.org indicating:
> 
> (1) whether you support the adoption of the draft
>    as the basis document for the existing milestone
> 
> (2) whether you commit to reviewing the WG document if adopted
> 
> 
> thanks for your consideration of the draft, and regards,
> 
> Al
> bmwg co-chair

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