RE: [bmwg] dsmterm-07 at 57th IETF - Changes to Channel Capacity

["David Newman" <[e-mail]>]

Do you still need my input?

And what was the great rush to lose "channel capacity"? While I do not
object to the name change, your other coauthors might.  They should have had
a chance to weigh in.

dn

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]On Behalf Of
> Perser, Jerry
> Sent: Thursday, July 17, 2003 2:09 AM
> To: BMWG (E-mail)
> Subject: [bmwg] dsmterm-07 at 57th IETF - Changes to Channel Capacity
>
>
> Based on the comments at the BMWG meeting and a follow-up meeting, I have
> some proposed changes to dsmterm-07 term 'Channel Capacity'.  The new text
> is below.  The summary is:
>
> 1. Name change from 'Channel Capacity' to 'Maximum Lossless Forwarding
> Rate'.
>
> 2. The discussion (paragraph 2) discusses the effect of queing on ingress
> measurements; where this metric is a egress measurement and is
> not affected.
>
> 3. The discussion (paragraph 3) better states why you should
> measure Maximum
> Lossless Forwarding Rate first and how ths metric should be used in the
> methodology.
>
> Jerry.
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> 3.2.1 Maximum Lossless Forwarding Rate
>
>   Definition:
>     The number of packets per second that a device can be
>     observed to successfully transmit to the correct destination
>     interface in response to a specified offered load at which
>     none of the offered packets are dropped by the device.
>
>   Discussion:
>     Maximum lossless forwarding rate measures the packet rate at
>     the egress interface(s) of the DUT/SUT.  In contrast,
>     throughput as defined in RFC 1242 measures the frame rate at
>     the ingress interface(s) of the DUT/SUT.
>
>     Ingress-based measurements do not account for queuing of
>     the DUT/SUT.  Throughput numbers can be higher than Maximum
>     lossless forwarding rate because of queuing.  The difference
>     is dependent upon test duration, packet rate, and queue size.
>     Maximum lossless forwarding rate, as an egress measurement,
>     does take queuing into account.
>
>     Understanding Maximum lossless forwarding rate is a necessary
>     precursor to any measurement involving Traffic Control
>     Mechanisms.  The accompanying methodology document MUST take
>     into consideration Maximum lossless forwarding rate when
>     determining the expected forwarding vectors.  When the sum on
>     the expected forwarding vectors on an interface exceeds the
>     Maximum lossless forwarding rate, the interface's performance
>     will supersede the Traffic control mechanisms' performance.
>
>     This measurement differs from forwarding rate at maximum
>     offered load (FRMOL) [Ma98] in that Maximum lossless
>     forwarding rate is intolerant of loss.
>
>   Measurement units:
>     N-octet packets per second
>
>   See Also:
>     Throughput [Br91]
>     Forwarding Rate at Maximum Offered Load [Ma98]
>
>
> ___________________________________________________________
> Jerry Perser                         Spirent Communications
> Director of Test Methodology         SmartBits Division
> Phone: [phone]                  26750 Agoura Road
> Lab:   818.676.2337                  Calabasas, CA, 91302
> Cell:  818.292.6457                  Corp:  818.676.2300
>
>
> _______________________________________________
> bmwg mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/bmwg
>
>


_______________________________________________
bmwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/bmwg