[bmwg] RFC 8238 on Data Center Benchmarking Terminology

rfc-editor@rfc-editor.org Wed, 30 August 2017 22:17 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 D7CEB132C2F; Wed, 30 Aug 2017 15:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 JBSsjRnByf_X; Wed, 30 Aug 2017 15:17:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A636132A80; Wed, 30 Aug 2017 15:17:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BEDCFB81090; Wed, 30 Aug 2017 15:17:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bmwg@ietf.org
Message-Id: <20170830221707.BEDCFB81090@rfc-editor.org>
Date: Wed, 30 Aug 2017 15:17:07 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/bl1VuwpxRXBPqtJAnxpBJjW0_Y4>
Subject: [bmwg] RFC 8238 on Data Center Benchmarking Terminology
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Aug 2017 22:17:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8238

        Title:      Data Center Benchmarking Terminology 
        Author:     L. Avramov,
                    J. Rapp
        Status:     Informational
        Stream:     IETF
        Date:       August 2017
        Mailbox:    lucien.avramov@gmail.com, 
                    jhrapp@gmail.com
        Pages:      20
        Characters: 39128
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bmwg-dcbench-terminology-19.txt

        URL:        https://www.rfc-editor.org/info/rfc8238

        DOI:        10.17487/RFC8238

The purposes of this informational document are to establish
definitions and describe measurement techniques for data center
benchmarking, as well as to introduce new terminology applicable to
performance evaluations of data center network equipment.  This
document establishes the important concepts for benchmarking network
switches and routers in the data center and is a prerequisite for the
test methodology document (RFC 8239).  Many of these terms and
methods may be applicable to network equipment beyond the scope of
this document as the technologies originally applied in the data
center are deployed elsewhere.

This document is a product of the Benchmarking Methodology Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC