[bmwg] Revised Draft Text for Re-Chartering

"MORTON, ALFRED C (AL)" <acmorton@att.com> Thu, 01 March 2018 15:17 UTC

Return-Path: <acmorton@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 C582B12D94E for <bmwg@ietfa.amsl.com>; Thu, 1 Mar 2018 07:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 jkePA2yaR8vZ for <bmwg@ietfa.amsl.com>; Thu, 1 Mar 2018 07:17:20 -0800 (PST)
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 D255A12D7E5 for <bmwg@ietf.org>; Thu, 1 Mar 2018 07:17:19 -0800 (PST)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id w21FH7Fm042393 for <bmwg@ietf.org>; Thu, 1 Mar 2018 10:17:14 -0500
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049463.ppops.net-00191d01. with ESMTP id 2gej2xb1ta-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <bmwg@ietf.org>; Thu, 01 Mar 2018 10:17:09 -0500
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 w21FDB5o125513 for <bmwg@ietf.org>; Thu, 1 Mar 2018 09:13:12 -0600
Received: from zlp30493.vci.att.com (zlp30493.vci.att.com [135.46.181.176]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id w21FD7qI125422 for <bmwg@ietf.org>; Thu, 1 Mar 2018 09:13:07 -0600
Received: from zlp30493.vci.att.com (zlp30493.vci.att.com [127.0.0.1]) by zlp30493.vci.att.com (Service) with ESMTP id 0574A4000497 for <bmwg@ietf.org>; Thu, 1 Mar 2018 15:13:07 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30493.vci.att.com (Service) with ESMTP id DD9D2400048F for <bmwg@ietf.org>; Thu, 1 Mar 2018 15:13:06 +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 w21FD62R023407 for <bmwg@ietf.org>; Thu, 1 Mar 2018 09:13:06 -0600
Received: from mail-bd.research.att.com (mail-bd.research.att.com [135.197.255.68]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id w21FCxnh023005 for <bmwg@ietf.org>; Thu, 1 Mar 2018 09:13:00 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-bd.research.att.com (Postfix) with ESMTP id 0EC0BE565D for <bmwg@ietf.org>; Thu, 1 Mar 2018 10:12:59 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0361.001; Thu, 1 Mar 2018 10:12:58 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: Revised Draft Text for Re-Chartering
Thread-Index: AdOxb2rKXpi1VX+tRZuJhTfFaQDwzg==
Date: Thu, 1 Mar 2018 15:12:57 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF490BD78B@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [195.238.226.2]
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.10432:, , definitions=2018-03-01_08:, , 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=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803010190
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/3g13ODStfbq3H1TrRIwrRTIb0Ao>
Subject: [bmwg] Revised Draft Text for Re-Chartering
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Mar 2018 15:17:22 -0000

BMWG,

We have slightly revised text to review during our 
Virtual Interim Meeting today (the first draft text
was sent to bmwg-list in October, 2017).
I'll summarize the changes during the meeting.

regards,
Al
bmwg-co-chair

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

BMWG - Benchmarking Methodology Working Group

Description of Working Group:

  The Benchmarking Methodology Working Group (BMWG) will continue to
  produce a series of recommendations concerning the key performance
  characteristics of internetworking technologies, or benchmarks for
  network devices, systems, and services. Taking a view of networking
  divided into planes, the scope of work includes benchmarks for the
  management, control, and forwarding planes. 

  The scope of BMWG has been extended to develop methods for
  virtual network functions (VNF) and their unique supporting 
  infrastructure (such as SDN Controllers and vSwitches). 
  Benchmarks for platform capacity and performance characteristics 
  of virtual routers, firewalls (and other security functions), 
  signaling control gateways, and other forms of gateways are included.  
  The benchmarks will foster comparisons between physical and virtual 
  network functions, and also cover unique features of  
  Network Function Virtualization systems. Also, with the emergence
  of virtualized test systems, specifications for test system
  calibration are also in-scope.

  Each recommendation will describe the class of network function, system, 
  or service being addressed; discuss the performance characteristics that
  are pertinent to that class; clearly identify a set of metrics that aid
  in the description of those characteristics; specify the methodologies
  required to collect said metrics; and lastly, present the requirements
  for the common, unambiguous reporting of benchmarking results.

  The set of relevant benchmarks will be developed with input from the
  community of users (e.g., network operators and testing organizations)
  and from those affected by the benchmarks when they are published
  (networking and test equipment manufacturers). When possible, the
  benchmarks and other terminologies will be developed jointly with
  organizations that are willing to share their expertise. Joint review
  requirements for a specific work area will be included in the
  description of the task.

  To better distinguish the BMWG from other measurement initiatives in the
  IETF, the scope of the BMWG is limited to the characterization of
  implementations of various internetworking technologies
  using controlled stimuli in a laboratory environment. Said differently,
  the BMWG does not attempt to produce benchmarks for live, operational
  networks. Moreover, the benchmarks produced by this WG shall strive to
  be vendor independent or otherwise have universal applicability to a
  given technology class.

  Because the demands of a particular technology may vary from deployment
  to deployment, a specific non-goal of the Working Group is to define
  acceptance criteria or performance requirements.

  An ongoing task is to provide a forum for development and
  advancement of measurements which provide insight on the
  capabilities and operation of implementations of inter-networking 
  technology. Ideally, BMWG should communicate with the operations 
  community through organizations such as NANOG, RIPE, and APRICOT.

 
Goals and Milestones: (preliminary list, we have an active draft for all topics)

  Dec 2018 - Methodology for Next-Gen Firewall Benchmarking to IESG Review
  Dec 2018 - Update to RFC2544 Back-to-back Frame Benchmarking to IESG Review
  Dec 2019 - Methodology for EVPN Benchmarking to IESG Review
  Dec 2019 - Considerations for Benchmarking Network Virtualization Platforms 
             to IESG Review
  Dec 2019 - Draft on Network Service Layer Abstract Models applied to 
             Benchmarking to IESG Review
  Dec 2019 - Draft on Automated VNF Benchmarking to IESG Review