[bmwg] Fwd: New Version Notification for draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt

bhuvaneswaran.vengainathan@veryxtech.com Mon, 02 October 2017 16:30 UTC

Return-Path: <bhuvaneswaran.vengainathan@veryxtech.com>
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 920EA13234B for <bmwg@ietfa.amsl.com>; Mon, 2 Oct 2017 09:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 K5BHLhpeDg9v for <bmwg@ietfa.amsl.com>; Mon, 2 Oct 2017 09:30:01 -0700 (PDT)
Received: from smtpout4.netcore.co.in (smout464.nsmailserv.com [202.162.238.64]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AA4E13263F for <bmwg@ietf.org>; Mon, 2 Oct 2017 09:30:01 -0700 (PDT)
Received: from smtpin5.netcore.co.in (unknown [192.168.2.96]) by cf3.netcore.co.in (Postfix) with ESMTP id 137281200C3; Mon, 2 Oct 2017 21:59:47 +0530 (IST)
Received: from cloudmail14.netcore.co.in (cloudmail12.netcore.co.in [202.162.231.3]) by smtpin5.netcore.co.in (Postfix) with ESMTP id C362D57D5E; Mon, 2 Oct 2017 21:59:50 +0530 (IST)
Mime-Version: 1.0
Date: Mon, 02 Oct 2017 16:29:51 +0000
Content-Type: multipart/alternative; boundary="----=_Part_652_491088771.1506961791"
Message-ID: <b551c4756efb65cb01a67b46c438aedc@cloudmail14.netcore.co.in>
X-Mailer: AfterLogic webmail client
From: bhuvaneswaran.vengainathan@veryxtech.com
To: "bmwg@ietf.org" <bmwg@ietf.org>
Cc: "Sarah B" <sbanks@encrypted.net>, "MORTON, ALFRED C (AL)" <acmorton@att.com>
In-Reply-To: <150696083474.28744.11512922472398306447.idtracker@ietfa.amsl.com>
References: <150696083474.28744.11512922472398306447.idtracker@ietfa.amsl.com>
X-Priority: 3 (Normal)
X-SMTP30-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: C362D57D5E.A66DE
X-SMTP30-MailScanner: Found to be clean
X-MailScanner-From: bhuvaneswaran.vengainathan@veryxtech.com
X-Cloudmilter-Processed: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/2ZDeoE9nZMmponr5osfmKhJC6H8>
Subject: [bmwg] Fwd: New Version Notification for draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt
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: Mon, 02 Oct 2017 16:30:05 -0000

Hi All,
A new version of SDN controller benchmarking terminology and methodology drafts have been submitted into IETF.
The following are the draft changes:
1. Addressed Al's comment on Asynchronous Message Processing Rate benchmark test about loss-free and maximum message processing rate.
2. Reworded Test Iterations/Duration to Trails/Trail Duration.

Note: The 3x3 matrix in terminology draft still remain the same.
Thanks,
Bhuvan

---- Original Message ----
 From: internet-drafts@ietf.org
 To: Vishwas Manral , Sarah Banks , Bhuvaneswaran Vengainathan , Anton Basil , Mark Tassinari 
 Sent: Mon, Oct 2, 2017, 09:44 PM
 Subject: New Version Notification for draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt
A new version of I-D, draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt
has been successfully submitted by Bhuvaneswaran Vengainathan and posted to the
IETF repository.

Name:      draft-ietf-bmwg-sdn-controller-benchmark-meth
Revision:   05
Title:      Benchmarking Methodology for SDN Controller Performance
Document date:   2017-10-01
Group:      bmwg
Pages:      53
URL:            https://www.ietf.org/internet-drafts/draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt (https://www.ietf.org/internet-drafts/draft-ietf-bmwg-sdn-controller-benchmark-meth-05.txt)
Status:         https://datatracker.ietf.org/doc/draft-ietf-bmwg-sdn-controller-benchmark-meth/ (https://datatracker.ietf.org/doc/draft-ietf-bmwg-sdn-controller-benchmark-meth/)
Htmlized:       https://tools.ietf.org/html/draft-ietf-bmwg-sdn-controller-benchmark-meth-05 (https://tools.ietf.org/html/draft-ietf-bmwg-sdn-controller-benchmark-meth-05)
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-sdn-controller-benchmark-meth-05 (https://datatracker.ietf.org/doc/html/draft-ietf-bmwg-sdn-controller-benchmark-meth-05)
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-bmwg-sdn-controller-benchmark-meth-05 (https://www.ietf.org/rfcdiff?url2=draft-ietf-bmwg-sdn-controller-benchmark-meth-05)

Abstract:
This document defines the methodologies for benchmarking control
plane performance of SDN controllers. Terminology related to
benchmarking SDN controllers is described in the companion
terminology document. SDN controllers have been implemented with
many varying designs in order to achieve their intended network
functionality. Hence, the authors have taken the approach of
considering an SDN controller as a black box, defining the
methodology in a manner that is agnostic to protocols and network
services supported by controllers. The intent of this document is to
provide a standard mechanism to measure the performance of all
controller implementations.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

DISCLAIMER: Privileged and/or Confidential information may be
contained in this message. If you are not the addressee of this message,
you may not copy, use or deliver this message to anyone. In such
event,you should destroy the message and kindly notify the sender by
reply e-mail.
It is understood that opinions or conclusions that do not relate to the
official business of the company are neither given nor endorsed by the
company.