Re: [bmwg] Spencer Dawkins' No Objection on draft-ietf-bmwg-dcbench-methodology-13: (with COMMENT)

Lucien Avramov <lucienav@google.com> Tue, 20 June 2017 20:44 UTC

Return-Path: <lucienav@google.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 629DA131640 for <bmwg@ietfa.amsl.com>; Tue, 20 Jun 2017 13:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 9S_dMwx_BnCN for <bmwg@ietfa.amsl.com>; Tue, 20 Jun 2017 13:44:13 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (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 3F74113163B for <bmwg@ietf.org>; Tue, 20 Jun 2017 13:44:13 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id 83so74700847pfr.0 for <bmwg@ietf.org>; Tue, 20 Jun 2017 13:44:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sYPLNeovXoK5sQO/WMLEihf/M7dAit2ShTsdBOX9QF8=; b=DBemqhqqtY6UWIsyKjwL/4sv2TWWM5UHSTv5alRJV2YyCyy10WPs4J2H6FiM/6fwXg wusSj2fr5O7Xx9d10cB/44Ri0a2dYihSnHuO+WCtDRTd+/4nyL5vdAJRzHFcEvEekhRe 37L9wxq+OfOLWiVo9Zzj9nuJXs+2InGF1YRFiOsrUov3gSX5DI7NY0vVwXYvAbbuDH0o 54aC7DSblUsNpz0NxFDeTLbjwHBbv2p25TAY3tjbgVKNRHoZPjjYewOZ9WKbqW8c6Do5 sflCfZxUd8RBwgpn73gRuzvQ1eKbZsoh7K8VxLW+aZ93lt5V54lKZe7x+doap7EoTgFH Lbqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sYPLNeovXoK5sQO/WMLEihf/M7dAit2ShTsdBOX9QF8=; b=AgUpnNxO9BuW8/0GkgoJ4qDoVGJOBhpBCnAPYRHPYm5vykBOdq4Bls1fu8HD6c+iQX vzxAUZqphHKdbRKV3/NVDZp6okJqjvtozgmU/yO/7Mqb0jw4IgJYRBOeI3qUD8ZU295t q1CW1e2aGGh4HXj5Z4+diQWup88Be32TwgMu1d19QiGRfQvXiQZXfq3zd3IpSRumApzP KTQzJVq0OkLOHCnmNeEEe0EEhz9oAYIzAMbfLgnrSZQyB+1LL0gyTw9A/1wDLlVDlqKT oHTOQZIpo0+XESqipGd9++JVvL3ndPg/kv7f5otXlyY6itfdPMQqnGaOY2BDTwQVp83b xlIw==
X-Gm-Message-State: AKS2vOyvdGYrCMlt+P2OukRN+EIyXqyHYW9BQ9K+PGHxvj1V1TP1vwI9 rKF+dwlQ4ly+yEZ1
X-Received: by 10.99.126.67 with SMTP id o3mr33136628pgn.36.1497991452637; Tue, 20 Jun 2017 13:44:12 -0700 (PDT)
Received: from ?IPv6:2620::100e:fd00:55db:f4b:7d01:12b2? ([2620:0:100e:fd00:55db:f4b:7d01:12b2]) by smtp.gmail.com with ESMTPSA id k11sm30043913pfj.48.2017.06.20.13.44.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jun 2017 13:44:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Lucien Avramov <lucienav@google.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <8BA949EB-B14A-49BA-992F-34180343FB92@gmail.com>
Date: Tue, 20 Jun 2017 13:44:11 -0700
Cc: The IESG <iesg@ietf.org>, draft-ietf-bmwg-dcbench-methodology@ietf.org, Sarah Banks <sbanks@encrypted.net>, bmwg-chairs@ietf.org, bmwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1FF3AD3-2249-45DB-8A93-32DEA3D5E503@google.com>
References: <149799053504.24974.8498552938277597302.idtracker@ietfa.amsl.com> <8BA949EB-B14A-49BA-992F-34180343FB92@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/1HvrlMIDii7KilZpcBZghDK0UvM>
Subject: Re: [bmwg] Spencer Dawkins' No Objection on draft-ietf-bmwg-dcbench-methodology-13: (with COMMENT)
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, 20 Jun 2017 20:44:16 -0000

> 
> Definitely agreed, will place a statement in both documents today to explain what datacenter switches are at time of writing. 
> 
> Thank you,
> Lucien
> 
>> On Jun 20, 2017, at 13:28, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
>> 
>> Spencer Dawkins has entered the following ballot position for
>> draft-ietf-bmwg-dcbench-methodology-13: No Objection
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-bmwg-dcbench-methodology/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> (I'm making the same comment on draft-ietf-bmwg-dcbench-terminology and
>> draft-ietf-bmwg-dcbench-methodology)
>> 
>> I'm looking at the ballot positions on draft-ietf-bmwg-dcbench-terminology and
>> draft-ietf-bmwg-dcbench-methodology that assert these documents aren't specific
>> to "data centers". That wouldn't surprise me, but I'm not seeing a definition
>> of "data center" in either document - did I miss it?
>> 
>> I suspect that the authors have specific technical characteristics in mind,
>> that happen to map onto what data centers look like today, but may not in the
>> future ("RFCs last forever"). Is it possible to tease those characteristics out?
>> 
>> (Full disclosure: my first working group in the IETF could have been called
>> "TCP over cellular links", but it turned out that when we said "cellular
>> links", we meant "low-speed links with high loss rates and asymmetric
>> bandwidth". "Cellular links" in the late 1990s didn't have the same
>> characteristics that "cellular links" have in 2017, but there are other link
>> types with those characteristics, so the documents ended up being useful in
>> places like CORE. I'm not suggesting anything like a restructure of the
>> document(s), only that they be clear about how future readers would know
>> whether they should be reading them in 2027)
>> 
>>