Re: [bmwg] Draft Liaison to IEEE 802.1 on DCB proposal

["Romascanu, Dan (Dan)" <[e-mail]>]

Looks good, editorial comments in-line. 

Dan
 

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On 
> Behalf Of Al Morton
> Sent: Monday, April 12, 2010 7:08 PM
> To: [e-mail]
> Cc: Romascanu, Dan (Dan); Eric Gray
> Subject: [bmwg] Draft Liaison to IEEE 802.1 on DCB proposal
> 
> 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 [e-mail] and Pat Thaler, DCB 
> TG Chair [e-mail]
> From: IETF-BMWG
> Al Morton, WG Chair [e-mail]
> 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 

I do not really know what a 'fundamental RFC' is so I suggest to strike
this out or use a more clear term. 

> 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 

s/has been/have 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.

s/is beyond/are beyond/

> 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

It would be useful to specify what liaison we are asking about -
probably between the BMWG and the IEEE 802.1 (?)

>   - the proposal details, as currently described
> 
> sincerely,
> Al Morton
> bmwg chair
> 
> 
> _______________________________________________
> bmwg mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bmwg
>