Re: [bmwg] [Technical Errata Reported] RFC8239 (6768)

[Warren Kumari <[e-mail]>]

Dear BMWG,

While trying to clean up my mailbox for the end of year, I realized that
this Errata had slipped through the cracks -- I believe that it is correct
and should be marked as "Verified", but would like another set of eyes (or
two!).

Please review and let me know...
W

On Wed, Dec 1, 2021 at 3:44 AM RFC Errata System <[e-mail]>
wrote:

> The following errata report has been submitted for RFC8239,
> "Data Center Benchmarking Methodology".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6768
>
> --------------------------------------
> Type: Technical
> Reported by: Leonard Yu <[e-mail]>
>
> Section: 3.2
>
> Original Text
> -------------
> 3) Measure maximum port pair buffer sizes.
>
>       o  First iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port 2 and port 3, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
>       o  Second iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port 4 and port 5, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
>       o  Last iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port N-3 and port N-2, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
> Corrected Text
> --------------
> 3) Measure maximum port pair buffer sizes.
>
>       o  First iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port 1 and port 2, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
>       o  Second iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port 3 and port 4, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
>       o  Last iteration: Ingress port 1 sending line rate to egress
>          port 2, ingress port 3 sending line rate to egress port 4, etc.
>          Ingress port N-1 and port N will oversubscribe, at 1% of line
>          rate, egress port N-3 and port N-2, respectively.  Measure the
>          buffer size value by multiplying the number of extra frames
>          sent by the frame size for each egress port.
>
> Notes
> -----
> The oversubscribed ports are a pair of ingress and egress ports. The
> oversubscribed ports in the texts describing the first are port 2 & 3,
> which are incorrect, should be port 1 & 2. The oversubscribed ports in the
> texts describing the second are port 4 & 5, which are incorrect, should be
> port 3 & 4.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8239 (draft-ietf-bmwg-dcbench-methodology-18)
> --------------------------------------
> Title               : Data Center Benchmarking Methodology
> Publication Date    : August 2017
> Author(s)           : L. Avramov, J. Rapp
> Category            : INFORMATIONAL
> Source              : Benchmarking Methodology
> Area                : Operations and Management
> Stream              : IETF
> Verifying Party     : IESG
>


-- 
The computing scientist’s main challenge is not to get confused by the
complexities of his own making.
  -- E. W. Dijkstra