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

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 01 December 2021 08:44 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59EA3A0813 for <bmwg@ietfa.amsl.com>; Wed, 1 Dec 2021 00:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mCakc4vMWBU9 for <bmwg@ietfa.amsl.com>; Wed, 1 Dec 2021 00:44:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D377B3A0814 for <bmwg@ietf.org>; Wed, 1 Dec 2021 00:44:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 8A530E54AE; Wed, 1 Dec 2021 00:44:12 -0800 (PST)
To: lucien.avramov@gmail.com, jhrapp@gmail.com, warren@kumari.net, rwilton@cisco.com, acmorton@att.com, sbanks@encrypted.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: hyu@xenanetworks.com, bmwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20211201084412.8A530E54AE@rfc-editor.org>
Date: Wed, 01 Dec 2021 00:44:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/Q_lbbIZ68zP5DtK1igrXxmsS34M>
Subject: [bmwg] [Technical Errata Reported] RFC8239 (6768)
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 01 Dec 2021 08:44:18 -0000

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 <hyu@xenanetworks.com>

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