Re: [Banana] Reaching Consensus on Problem Statement

Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch> Fri, 03 February 2017 16:54 UTC

Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: banana@ietfa.amsl.com
Delivered-To: banana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49924129692 for <banana@ietfa.amsl.com>; Fri, 3 Feb 2017 08:54:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] 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 VLpW3kWdNLOt for <banana@ietfa.amsl.com>; Fri, 3 Feb 2017 08:54:27 -0800 (PST)
Received: from virgo02.ee.ethz.ch (virgo02.ee.ethz.ch [129.132.72.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39B8E129669 for <banana@ietf.org>; Fri, 3 Feb 2017 08:54:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virgo02.ee.ethz.ch (Postfix) with ESMTP id 3vFNJ171hCz15Ly5; Fri, 3 Feb 2017 17:54:25 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at virgo02.ee.ethz.ch
Received: from virgo02.ee.ethz.ch ([127.0.0.1]) by localhost (virgo02.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yLgnfNIPixq; Fri, 3 Feb 2017 17:54:25 +0100 (CET)
X-MtScore: NO score=0
Received: from [192.168.178.33] (p5DEC295F.dip0.t-ipconnect.de [93.236.41.95]) by virgo02.ee.ethz.ch (Postfix) with ESMTPSA; Fri, 3 Feb 2017 17:54:25 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <C4D4B9D7-3509-40CA-954E-67ECB18FC0CC@gmail.com>
Date: Fri, 03 Feb 2017 17:54:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <71AA8F00-D4D5-4265-BE54-3260B2A00BA4@tik.ee.ethz.ch>
References: <EE162993-F96F-458A-846C-D722EEF7A3B8@gmail.com> <BBB875EC-629F-4B43-B528-11F5299BFE71@tik.ee.ethz.ch> <C4D4B9D7-3509-40CA-954E-67ECB18FC0CC@gmail.com>
To: Margaret Cullen <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/ihCS_4dGgSjmmHY6reODjym4-Lg>
Cc: banana@ietf.org
Subject: Re: [Banana] Reaching Consensus on Problem Statement
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Bandwidth Aggregation for interNet Access: Discussion of bandwidth aggregation solutions based on IETF technologies." <banana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/banana>, <mailto:banana-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/banana/>
List-Post: <mailto:banana@ietf.org>
List-Help: <mailto:banana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/banana>, <mailto:banana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 16:54:28 -0000

Hi,

I do agree, but…


> Am 03.02.2017 um 16:57 schrieb Margaret Cullen <margaretw42@gmail.com>:
> 
> Hi Mirja,
> 
>> Also having an agreement for the problem is of course the first step. Howeve,r my understanding from the BoF was that there are already quite a bunch of people working on different solutions. So what’s really needed is agreement on the solution (and if there is one for all or different things or multiple solutions  are needed). Only if there is a first proposal for one (or more?) protocol(s) that this group would work on, it makes sense to think about chartering.
> 
> I agree that we also need to reach consensus, as a group, on how to move forward on one or more solutions, but I don’t think we can move forward on solutions until we have:
> 
> - Consensus that we have a well-understood problem statement, and

I had the feeling there was already a good understanding of the problem in the BoF.

> - Consensus that we think the problem is something it would be useful for the IETF to work on.

This depends on the solution rather than the problem…

Mirja


> 
> Once we have agreement on those things, we can discuss whether it makes sense to standardize only a single solution to this problem, or whether the trade-offs between different solutions mean that more than one solution may be needed for different deployment scenarios.
> 
> Does that make sense?
> 
> Margaret
>