[bmwg] Draft text for Re-Chartering

"MORTON, ALFRED C (AL)" <acmorton@att.com> Sun, 29 October 2017 15:21 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 49D4813F560; Sun, 29 Oct 2017 08:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ObORRZHeakIT; Sun, 29 Oct 2017 08:21:25 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 F415313F569; Sun, 29 Oct 2017 08:21:21 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id v9TFEnhq022670; Sun, 29 Oct 2017 11:21:20 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049297.ppops.net-00191d01. with ESMTP id 2dvpm80dhr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 29 Oct 2017 11:21:20 -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 v9TFLIxb093880; Sun, 29 Oct 2017 10:21:19 -0500
Received: from dalint01.pst.cso.att.com (dalint01.pst.cso.att.com [135.31.133.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id v9TFLFvs093835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 29 Oct 2017 10:21:16 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by dalint01.pst.cso.att.com (RSA Interceptor); Sun, 29 Oct 2017 15:04:15 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 v9TF4ELX007002; Sun, 29 Oct 2017 10:04:14 -0500
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v9TF47uc006646; Sun, 29 Oct 2017 10:04:11 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-azure.research.att.com (Postfix) with ESMTP id 0DA8DE10A0; Sun, 29 Oct 2017 11:04:08 -0400 (EDT)
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; Sun, 29 Oct 2017 11:04:07 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>
CC: "bmwg-ads@ietf.org" <bmwg-ads@ietf.org>
Thread-Topic: Draft text for Re-Chartering
Thread-Index: AdNQxUrbng5SqNP0TuWo2gqShAGGsA==
Date: Sun, 29 Oct 2017 15:04:06 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF490202BB@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.28.170.142]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-29_09:, , 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710290218
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/xE7YzPe7j61x-bgzUX9ETdYU53E>
Subject: [bmwg] 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: Sun, 29 Oct 2017 15:21:26 -0000

BMWG,

As discussed during our session in Prague, we have
nearly completed all our milestones and (recognizing
the number of new proposals we are tracking) it is time
to re-charter.

Below, please find the revised Charter text in Draft form.
Review will commence now through our session at IETF-100.

Also, it is time to determine which proposals have WG support
at the same time we re-charter, and we will add milestones
for those. Other proposals may need further consideration
as part of our on-going work. 

In any case, our session at IETF-100 will offer time for
the new charter review and discussion of new work proposals. 

So, please help the working group by participating
in discussions on the list and during the session!

for the co-chairs,
Al



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

  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:
...
  Dec 2017 - Methodology for SDV Controller Benchmarking to IESG Review
  Dec 2017 - Terminology for SDV Controller Benchmarking to IESG Review