[bmwg] RFC 8455 on Terminology for Benchmarking Software-Defined Networking (SDN) Controller Performance
rfc-editor@rfc-editor.org Tue, 30 October 2018 23:01 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 D3110130E0F; Tue, 30 Oct 2018 16:01:40 -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=unavailable 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 UPgSq5fphJIC; Tue, 30 Oct 2018 16:01:39 -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 6388812D4F0; Tue, 30 Oct 2018 16:01:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 777D5B810B2; Tue, 30 Oct 2018 16:01:16 -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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181030230116.777D5B810B2@rfc-editor.org>
Date: Tue, 30 Oct 2018 16:01:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/ReQteZgW8R_ljGnvYa0ZNC9PnOc>
Subject: [bmwg] RFC 8455 on Terminology for Benchmarking Software-Defined Networking (SDN) Controller Performance
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: Tue, 30 Oct 2018 23:01:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8455
Title: Terminology for Benchmarking Software-Defined
Networking (SDN) Controller Performance
Author: V. Bhuvaneswaran,
A. Basil,
M. Tassinari,
V. Manral,
S. Banks
Status: Informational
Stream: IETF
Date: October 2018
Mailbox: bhuvaneswaran.vengainathan@veryxtech.com,
anton.basil@veryxtech.com,
mark.tassinari@hpe.com,
vishwas.manral@gmail.com,
sbanks@encrypted.net
Pages: 23
Characters: 46339
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bmwg-sdn-controller-benchmark-term-10.txt
URL: https://www.rfc-editor.org/info/rfc8455
DOI: 10.17487/RFC8455
This document defines terminology for benchmarking a Software-Defined
Networking (SDN) controller's control-plane performance. It extends
the terminology already defined in RFC 7426 for the purpose of
benchmarking SDN Controllers. The terms provided in this document
help to benchmark an SDN Controller's performance independently of
the controller's supported protocols and/or network services.
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