[bmwg] Draft Liaison to IEEE 802.1 on DCB proposal
Al Morton <acmorton@att.com> Mon, 12 April 2010 16:10 UTC
Return-Path: <acmorton@att.com>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFC653A6A9A for <bmwg@core3.amsl.com>; Mon, 12 Apr 2010 09:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.03
X-Spam-Level:
X-Spam-Status: No, score=-104.03 tagged_above=-999 required=5 tests=[AWL=-0.834, BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrJLXtMEKEYk for <bmwg@core3.amsl.com>; Mon, 12 Apr 2010 09:10:30 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with ESMTP id 502203A6A6C for <bmwg@ietf.org>; Mon, 12 Apr 2010 09:09:32 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-4.tower-120.messagelabs.com!1271088565!47315380!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 27365 invoked from network); 12 Apr 2010 16:09:26 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-4.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Apr 2010 16:09:26 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3CG9ano010675 for <bmwg@ietf.org>; Mon, 12 Apr 2010 12:09:37 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o3CG9XTd010586 for <bmwg@ietf.org>; Mon, 12 Apr 2010 12:09:33 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.3/8.14.3) with ESMTP id o3CG9Kop028748 for <bmwg@ietf.org>; Mon, 12 Apr 2010 12:09:20 -0400
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.3/8.14.4) with ESMTP id o3CG9FCJ028321 for <bmwg@ietf.org>; Mon, 12 Apr 2010 12:09:15 -0400
Message-Id: <201004121609.o3CG9FCJ028321@alpd052.aldc.att.com>
Received: from acmt.att.com (dyp004254dys.mt.att.com[135.16.251.229](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20100412160915gw100b8j3me>; Mon, 12 Apr 2010 16:09:15 +0000
X-Originating-IP: [135.16.251.229]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 12 Apr 2010 12:08:18 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Dan Romascanu <dromasca@avaya.com>, Eric Gray <eric.gray@ericsson.com>
Subject: [bmwg] Draft Liaison to IEEE 802.1 on DCB proposal
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Apr 2010 16:10:32 -0000
BMWG, The first draft Liaison to IEEE 802.1 describing the proposal to update RFCs 2544 and 2889 to address the Per-Flow Control capabilities of IEEE 802.1Qbb is below. Thanks to David Newman and Eric Gray (IETF Liaison Manager for 802.1) for suggested text and/or background info shared off-list. Comments by April 26, 2010, on the bmwg-list, please. Al bmwg chair --------------------------------------------------------------- To: IEEE 802.1 Tony Jeffrey, WG Chair tony@jeffree.co.uk and Pat Thaler, DCB TG Chair pthaler@broadcom.com From: IETF-BMWG Al Morton, WG Chair acmorton@att.com For Action/Comment Deadline: August 1, 2010 Title: Proposal to update RFCs 2544 and 2889 to address the Per-Flow Control capabilities of IEEE 802.1Qbb The purpose of this Liaison is to inform you of a new work proposal in the Benchmarking Methodology Working Group (BMWG) of the IETF, and seek your comments. BMWG is considering adding a charter work item to update several of our fundamental RFCs, described in detail in the memo by D.Newman and T.Player: http://tools.ietf.org/html/draft-player-dcb-benchmarking-01 In this proposal, there is an intersection between IETF benchmarking practice and new IEEE standardization work. Benchmarks for Ethernet switch performance based on RFCs 1242, 2285, 2544 and 2889 are recognized as industry standards. The terminology and methodology described in these memos has been in widespread use by test equipment vendors, networking device manufacturers, enterprises and service providers for more than a decade. Some concepts in these RFCs 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). Since devices that implement these new congestion-management specifications should never drop frames, and since the metric of throughput distinguishes between non-zero and zero drop rates, no throughput measurement is possible using the existing methodology. There are related cases where other existing metrics can be extended or replaced. The Internet-Draft seeks to recognize the importance of these new IEEE specifications in the context of data center switch benchmarking. The draft seeks to extend rather than replace existing industry standard practices for benchmarking switch performance characteristics in the lab, and it does so by defining new terms and metrics relevant to recent IEEE work on data center bridging. The charter of BMWG strictly limits our work to laboratory characterization. Therefore, live network performance testing, manageability, MIB module development, and other operational/functional testing is beyond our scope. http://www.ietf.org/dyn/wg/charter/bmwg-charter Before considering this work proposal further, we seek your comments on: - whether there is overlapping work planned in 802.1 - whether a liaison relationship could be beneficial to complete this work - the proposal details, as currently described sincerely, Al Morton bmwg chair
- [bmwg] Draft Liaison to IEEE 802.1 on DCB proposal Al Morton
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… Romascanu, Dan (Dan)
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… Al Morton
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… Romascanu, Dan (Dan)
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… David Newman
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… Romascanu, Dan (Dan)
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… dnewman
- Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB pro… Al Morton