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

"MORTON, ALFRED C (AL)" <acm@research.att.com> Thu, 25 October 2018 14:48 UTC

Return-Path: <acm@research.att.com>
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 1584C130E69 for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2018 07:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level:
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 gpzJPH3Se5aP for <bmwg@ietfa.amsl.com>; Thu, 25 Oct 2018 07:48:06 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07F73130E5A for <bmwg@ietf.org>; Thu, 25 Oct 2018 07:48:05 -0700 (PDT)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w9PEm2Bf018115; Thu, 25 Oct 2018 10:48:04 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049458.ppops.net-00191d01. with ESMTP id 2nbexc22h6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 25 Oct 2018 10:48:01 -0400
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id w9PEltOe087472; Thu, 25 Oct 2018 09:47:56 -0500
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [135.46.181.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id w9PElpH1087346; Thu, 25 Oct 2018 09:47:51 -0500
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [127.0.0.1]) by zlp30494.vci.att.com (Service) with ESMTP id 672CC40004A1; Thu, 25 Oct 2018 14:47:51 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30494.vci.att.com (Service) with ESMTP id 48D9F40004A2; Thu, 25 Oct 2018 14:47:51 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id w9PElpbQ001163; Thu, 25 Oct 2018 09:47:51 -0500
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id w9PElgLw000392; Thu, 25 Oct 2018 09:47:42 -0500
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-blue.research.att.com (Postfix) with ESMTP id DCE58F1C76; Thu, 25 Oct 2018 10:47:41 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0415.000; Thu, 25 Oct 2018 10:46:57 -0400
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: Brian Monkman <bmonkman@netsecopen.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] Call for adoption: draft-balarajah-bmwg-ngfw-performance
Thread-Index: AdRpbQmISVir3THXT3m9iQjUgXW92gAAGu6gAMa554AABgdyEA==
Date: Thu, 25 Oct 2018 14:46:55 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF557A7FF8@njmtexg5.research.att.com>
References: <4D7F4AD313D3FC43A053B309F97543CF557A38BD@njmtexg5.research.att.com> <000501d46c66$d6f39a60$84dacf20$@netsecopen.org>
In-Reply-To: <000501d46c66$d6f39a60$84dacf20$@netsecopen.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [69.141.203.172]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-25_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810250125
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/moVC0RwAZQ46OoGJvpIYy76jvrk>
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 14:48:08 -0000

Thanks for the clarification on RFC3511, Brian,
and sharing your view on the review process.

Although requesting early review is an exception,
this would take place after adoption and before
WG consensus, so it should not lengthen the process
unnecessarily. We would receive reviews from these
Directorate teams anyway, during IETF Last Call, and 
this may be more efficient (ideally).

It also occurs to me that we had some interest from the
opsec WG - I will cross-post the call for adoption there.

Al
bmwg co-chair

> -----Original Message-----
> From: Brian Monkman [mailto:bmonkman@netsecopen.org]
> Sent: Thursday, October 25, 2018 9:30 AM
> To: MORTON, ALFRED C (AL) <acm@research.att.com>; bmwg@ietf.org
> Subject: RE: [bmwg] Call for adoption: draft-balarajah-bmwg-ngfw-
> performance
> 
> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_draft-2Dbalarajah-2Dbmwg-2Dngfw-2Dperformance-
> 2D05&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=_6cen3Hn-
> e_hOm0BhY7aIpA58dd19Z9qGQsr8-
> 6zYMI&m=SnQDPuXNkU4lpz0K_xDQPKNQZ8LfDDYIHf55M9-
> 0gEM&s=k9ra4_IYee8XZHNoEVpIs4VzmBJv4I_94p1o5CKmkqk&e=
> >
> > 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_draft-2Dbalarajah-2Dbmwg-2Dngfw-2Dperformance-
> 2D05&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=_6cen3Hn-
> e_hOm0BhY7aIpA58dd19Z9qGQsr8-
> 6zYMI&m=SnQDPuXNkU4lpz0K_xDQPKNQZ8LfDDYIHf55M9-
> 0gEM&s=k9ra4_IYee8XZHNoEVpIs4VzmBJv4I_94p1o5CKmkqk&e=
> >
> > 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_bmwg&d=DwICAg&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=_6cen3Hn-e_hOm0BhY7aIpA58dd19Z9qGQsr8-
> 6zYMI&m=SnQDPuXNkU4lpz0K_xDQPKNQZ8LfDDYIHf55M9-
> 0gEM&s=ZoAskSYmre8HJxrixoOVquJ1WJZ7GSPcWxsi4C5-aNM&e=