IETF Logo Mail Archive

Re: [bmwg] New version of SDN Controller Benchmarking drafts notification

Warren Kumari <warren@kumari.net> Tue, 27 February 2018 18:37 UTC

Return-Path: <warren@kumari.net>
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 6F46912D7F0 for <bmwg@ietfa.amsl.com>; Tue, 27 Feb 2018 10:37:23 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 jBQt1vDZjaf9 for <bmwg@ietfa.amsl.com>; Tue, 27 Feb 2018 10:37:21 -0800 (PST)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F7C112D875 for <bmwg@ietf.org>; Tue, 27 Feb 2018 10:37:08 -0800 (PST)
Received: by mail-wr0-x22d.google.com with SMTP id w77so25884386wrc.6 for <bmwg@ietf.org>; Tue, 27 Feb 2018 10:37:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WLsIl2ReOYsndDtpwtiRdf+q36z8H30AbSWenImJIEk=; b=kZmn1g6EfyPoSIjr4mtewLOqmC7tIRpsX5BsJ4hEQG9YIRKN+mpPJaS3LFILsYtdOq GnDrSXhHrwCEppmttdvRsQSbo5G6fmgqsbGIRTUuHiqARFNmbDDQqliHwRUhDqHm2MnU ntL23OfEh+uFxnzcGcA1M80pT2VNx1ZksBrf/D14RYbBlBmmgWVlHheEskSiXHfcDVEQ ysyMrYHwVFV8GHs/fStaSg44j+yYs4yX08zalcotsQP0yIw3zTdcy62V9EXG7UQE7vyC h8GS+tb78rnlrDCk5diz1m3HTPM4r4TwoUToIJYujUBhwqkiJJb3LmRwpboTVRo43rT4 5fRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WLsIl2ReOYsndDtpwtiRdf+q36z8H30AbSWenImJIEk=; b=RdqsUkmMUsdNm3VuhZ4mHxLXeTJBudXBtAXPI9g6QdMAWgcl2GuoiX9xV/wrgkDU3V U030r485qx0V9n511ApPvlWJYPj1TzTMMoTn45nzz+FEn8x+tbu5TVRqtYPWLSrEcSG1 sdFWhnY7svSwfiSIYUtVmcBCb7krft+RjgjdTK7UbmVsGV548Em/DFwbxJVT83ODcfMk hWn4TmpWm3PrpVqiit2YE0enp/iw+tCKuId8VAfUsJi788YrnbouTgeVg9nH30/owGsO qR0h51lhX01ZbcWwloYB5MBCTG44F92SMrb/YfZH2vz37daJI/6d4A059w1qLIRHXho4 Te0w==
X-Gm-Message-State: APf1xPB4GHfyeSD9tdW8zy6eAEVBPogTj8cHVFR+SOpBfW/PINA+tw5v E5Qxhw7x+9AgdGxpv6CI3iexuo4B3bQ4HvMheYX7Sw==
X-Google-Smtp-Source: AH8x226PvpF+vbDku6kp1N8tEptwD7ygcow35+98ZkAxfy6GHqlA7eE2lGDzH1n4qbu9lR9eW2el/WE3HvhzcwGkcZQ=
X-Received: by 10.223.134.42 with SMTP id 39mr14177331wrv.10.1519756626427; Tue, 27 Feb 2018 10:37:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.152.235 with HTTP; Tue, 27 Feb 2018 10:36:25 -0800 (PST)
In-Reply-To: <97b042c7c37a05c480d03c26e50b6c8d@cloudmail14.netcore.co.in>
References: <151760684081.17028.12836598632315025128@ietfa.amsl.com> <97b042c7c37a05c480d03c26e50b6c8d@cloudmail14.netcore.co.in>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 27 Feb 2018 13:36:25 -0500
Message-ID: <CAHw9_iLAhuP+-nUQomUxazSd7UOu10OfLFczg_Qe7PaT=yx=1A@mail.gmail.com>
To: bhuvaneswaran.vengainathan@veryxtech.com
Cc: bmwg@ietf.org, "MORTON, ALFRED C (AL)" <acmorton@att.com>, draft-ietf-bmwg-sdn-controller-benchmark-term.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/Bm0F6Bxq0g5_gUCWyPqKbyV0u1k>
Subject: Re: [bmwg] New version of SDN Controller Benchmarking drafts notification
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: Tue, 27 Feb 2018 18:37:23 -0000

Thank you for making these changes - I'll kick off the IESG Eval and
put them on the telechat.

Unfortunately, because a number of ADs are stepping down (and because
we are close to IETF101) the next telechat is quite full, as is the
following one (2018-04-05), and so I'm planning on putting this on the
2018-04-19 telechat. This is ~7 weeks out - sorry.

W



On Mon, Feb 26, 2018 at 10:52 AM,
<bhuvaneswaran.vengainathan@veryxtech.com> wrote:
> We would  like to thank Al and all DIRs for taking time to review and share
> insightful comments on both the drafts.
>
> We have submitted  new version of SDN controller benchmarking drafts into
> IETF, addressing the review comments received during IESG last call
> - draft-ietf-bmwg-sdn-controller-benchmark-term-09
> - draft-ietf-bmwg-sdn-controller-benchmark-meth-08
>
> Key changes to the  terminology draft:
>
> 1. Fixed Nits
> 2. Updated the draft first paragraph to reference RFC 8174 in addition to
> RFC 2119
> 3. Added definitions for Southbound Interface and Leaf-Spine Topology
>
> Key changes to the  methodology draft:
> 1. Fixed Nits & references
> 2. Updated the draft first paragraph to reference RFC 8174 in addition to
> RFC 2119
> 3. Added Variance Measurement for all the tests.
> 4. Updated the Test Setup Diagram to reflect Leaf Spine Topology
> 5. Updated test objectives for Reactive & Proactive Path Provisioning Rate
> tests to reflect the rate measurement
>
> @Al, Please let us know for any  further actions on the drafts.
>
> Thank you,
> Bhuvan
>
> 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.



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf

v2.23.0 | Report a Bug | By Email