Re: [bmwg] Re-Charter Text for review
"Fernando Calabria (fcalabri)" <fcalabri@cisco.com> Mon, 28 April 2014 13:30 UTC
Return-Path: <fcalabri@cisco.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5882A1A09E6 for <bmwg@ietfa.amsl.com>; Mon, 28 Apr 2014 06:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 8mA49tBnuM3O for <bmwg@ietfa.amsl.com>; Mon, 28 Apr 2014 06:30:43 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id CEBF41A0795 for <bmwg@ietf.org>; Mon, 28 Apr 2014 06:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7125; q=dns/txt; s=iport; t=1398691842; x=1399901442; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=nUc6C5uS8EHzl/4xQpOt1CklEounQQNSYiloYkb9ow4=; b=Apb8nPZLP1xLvxr0ATbNXhYY6JCij2ZDOf1x4uE3p9Lb9zzFq5MBlpjl arVrnJIMWZS5Is5nsCvFD5/RYz3TkX3rq0JTSi7dpDPCjfkoA84HZwAvR tGMzw7bmcJVSch3OucqY2eD22ksotRiDG/4HAcgWONUkJF9BITazVilrB 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFALJXXlOtJA2H/2dsb2JhbABPBwODBk9XvS6HOYEVFnSCJQEBAQQBAQE3MQMXBgEIEQQBAR8JLgsUCQoEARIUiC0NyXMTBI19BCUIGx0LhCgEmQySXoMxgWlC
X-IronPort-AV: E=Sophos;i="4.97,944,1389744000"; d="scan'208";a="320908977"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP; 28 Apr 2014 13:30:36 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3SDUZX7002968 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 13:30:35 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.55]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Mon, 28 Apr 2014 08:30:35 -0500
From: "Fernando Calabria (fcalabri)" <fcalabri@cisco.com>
To: Barry Constantine <Barry.Constantine@jdsu.com>, "MORTON, ALFRED C (AL)" <acmorton@att.com>, "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] Re-Charter Text for review
Thread-Index: AQHPYuYI+sFq4e5XzUOeDhY19DyGBg==
Date: Mon, 28 Apr 2014 13:30:35 +0000
Message-ID: <CF83D031.1663F%fcalabri@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [64.102.130.150]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9C170C8FFD1D144BBA7F5BDCBF1146D8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/bmwg/VMkdRAWFMJ_wOordB7uCIaPZKdQ
Subject: Re: [bmwg] Re-Charter Text for review
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 28 Apr 2014 13:30:45 -0000
+1 On 4/28/14, 9:07 AM, "Barry Constantine" <Barry.Constantine@jdsu.com> wrote: >Hi Al, > >I think the charter is well written and with topics that are very >relevant. > >Thank you, >Barry Constantine > >JDSU Network and Service Enablement >Principal Member Technical Staff >301-325-7069 > >-----Original Message----- >From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of MORTON, ALFRED C >(AL) >Sent: Thursday, April 24, 2014 1:21 PM >To: bmwg@ietf.org >Subject: [bmwg] Re-Charter Text for review > >BMWG, > >Over the last year, we've developed this set of paragraphs for specific >work items one at a time. Now it's time for one last look (by May 2) and >then we declare consensus and move to the next step (unless the wheels >come-off). Reply with your comments on the text below. > >Al and Sarah, >bmwg co-chairs > >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >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. > >Each recommendation will describe the class of equipment, 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 terminology 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 detailed >description of the task, as listed below. > >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 discussion regarding the >advancement of measurements designed to provide insight on the >capabilities and operation of inter-networking technology implementations. > >The BMWG will communicate with the operations community through >organizations such as NANOG, RIPE, and APRICOT. > >In addition to its current work items, the BMWG is explicitly tasked to >develop benchmarks and methodologies for the following technologies: > >Traffic Management: Develop the methods to characterize the capacity of >traffic management features in network devices, such as classification, >policing, shaping, and active queue management. Existing terminology will >be used where appropriate. Configured operation will be verified as a >part of the methodology. The goal is a methodology to assess the maximum >forwarding performance that a network device can sustain without dropping >or impairing packets, or compromising the accuracy of multiple instances >of traffic management functions. This is the benchmark for comparison >between devices. Another goal is to devise methods that utilize flows >with congestion-aware transport as part of the traffic load and still >produce repeatable results in the isolated test environment. > >IPv6 Neighbor Discovery: Large address space in IPv6 subnets presents >several networking challenges, as described in RFC 6583. Indexes to >describe the performance of network devices, such as the number of >reachable devices on a sub-network, are useful benchmarks to the >operations community. The working group will develop the necessary >terminology and methodologies to measure such benchmarks. > >In-Service Software Upgrade: Develop new methods and benchmarks to >characterize the upgrade of network devices while in-service, considering >both data and control plane operations and impacts. >These devices are generally expected to maintain control plane session >integrity, including routing connections. Quantification of Upgrade >impact will include packet loss measurement, and other forms of recovery >behavior will be noted accordingly. The work will produce a definition of >ISSU, which will help refine the scope. Liaisons will be established as >needed. > >Data Center Benchmarking: This work will define additional terms, >benchmarks, and methods applicable to data center performance >evaluations. >This includes data center specific congestion scenarios, switch buffer >analysis, microburst, head of line blocking, while also using a wide mix >of traffic conditions. Some aspects from BMWG's past work are not >meaningful when testing switches that implement new IEEE specifications >in the area of data center bridging. For example, throughput as defined >in RFC 1242 cannot be measured when testing devices that implement three >new IEEE specifications: priority-based flow control (802.1Qbb); priority >groups (802.1Qaz); and congestion notification (802.1Qau). >This work will update RFC1242, RFC2544, RFC2889 (and other key RFCs), and >exchange Liaisons with relevant SDOs, especially at WG Last Call. > >VNF and related Infrastructure Benchmarking: Benchmarking Methodologies >have reliably characterized many physical devices. This work item extends >and enhances the methods to virtual network functions (VNF) and their >unique supporting infrastructure. First, the new task space will be >considered to ensure that common issues are recognized from the start. >Benchmarks for platform capacity and performance characteristics of >virtual routers, switches, and related components will follow, including >comparisons between physical and virtual network functions. > >_______________________________________________ >bmwg mailing list >bmwg@ietf.org >https://www.ietf.org/mailman/listinfo/bmwg > >_______________________________________________ >bmwg mailing list >bmwg@ietf.org >https://www.ietf.org/mailman/listinfo/bmwg
- [bmwg] Re-Charter Text for review MORTON, ALFRED C (AL)
- Re: [bmwg] Re-Charter Text for review Barry Constantine
- Re: [bmwg] Re-Charter Text for review Fernando Calabria (fcalabri)
- Re: [bmwg] Re-Charter Text for review ramki Krishnan
- Re: [bmwg] Re-Charter Text for review MORTON, ALFRED C (AL)
- Re: [bmwg] Re-Charter Text for review joel jaeggli