Re: [Banana] Reaching Consensus on Problem Statement

Brian Trammell <ietf@trammell.ch> Fri, 03 February 2017 10:11 UTC

Return-Path: <ietf@trammell.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 60352128AB0 for <banana@ietfa.amsl.com>; Fri, 3 Feb 2017 02:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 c6L0vjCLdS-R for <banana@ietfa.amsl.com>; Fri, 3 Feb 2017 02:11:03 -0800 (PST)
Received: from trammell.ch (unknown [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 825FA127078 for <banana@ietf.org>; Fri, 3 Feb 2017 02:11:02 -0800 (PST)
Received: from [IPv6:2001:470:26:9c2:d879:3fbb:be92:133f] (unknown [IPv6:2001:470:26:9c2:d879:3fbb:be92:133f]) by trammell.ch (Postfix) with ESMTPSA id DFFDE1A0237; Fri, 3 Feb 2017 11:11:01 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A3D6A495-88DD-40A7-BD2D-8C6CBCC5B697"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <EE162993-F96F-458A-846C-D722EEF7A3B8@gmail.com>
Date: Fri, 03 Feb 2017 11:11:01 +0100
Message-Id: <CDC5B9AE-3F25-4C74-ACE7-A7A8060A84A9@trammell.ch>
References: <EE162993-F96F-458A-846C-D722EEF7A3B8@gmail.com>
To: Margaret Cullen <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/4y2qTcUd4beUe-bM5SsPszj0nnE>
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 10:11:04 -0000

hi Margaret,

Thanks a lot for pulling this together -- this, I think, concisely and accurately reflects the intersection of the problem spaces discussed in the BoF that we should explore further.

Cheers,

Brian (no hats)

> On 02 Feb 2017, at 17:48, Margaret Cullen <margaretw42@gmail.com> wrote:
> 
> At the BANANA BOF in November, we did not seem to have clear consensus on a concise problem statement.  So, I’d like to try to reach consensus on a problem statement on this list, in the hopes that we can (finally!) move forward towards work on solutions.   To that end, I’ve been working with multiple people over the past few weeks to come up with a concise problem statement for our expanded BANANA effort (as represented at the BOF), and I have determined that the main aspects of the problem we are trying to solve are:
> 
> (1) Unmanaged networks (i.e. homes or small offices) often have more than one point of attachment to the Internet (DSL, Cable, LTE, etc).  We call these networks “multi-access networks”.  In multi-access networks, it is desirable to utilize the bandwidth of all attached networks to increase performance.  We call this “bandwidth aggregation”.
> 
> (2) An unmanaged multi-access network may have multiple links from a single provider (e.g. DSL/LTE, or two LTE links), or multiple links from different providers (e.g. Cable & LTE, or DSL and LTE from different providers).   We need a solution that will work in both cases, without requiring cooperation between multiple providers.  Therefore, our solution needs to work with existing IP address assignment, ingress filtering, and reverse path routing mechanisms.
> 
> (3) In these environments, the available paths to the Internet may change over time due to changing conditions and/or service outages.  It would be desirable for all existing sessions to continue using the remaining link(s) when a link becomes unavailable or unreliable.  We call this “failover”.  [Note:  This is especially true when you consider the possibility that, using this mechanism, people could increase the bandwidth available wherever they are by routinely using their smart phones as Wifi access points accessible to their home or office CPE, PCs or laptops.]
> 
> (4) Homes and small offices tend to have few simultaneous sessions active at any given time, and may often have only one large, relatively long-lived session in use for an online game or media download.  Despite the fact that only one session may be active, end-users would still benefit from increased bandwidth and reliability for that single session.  It is therefore important to support bandwidth aggregation and failover for a single session (i.e. a single TCP connection or UDP flow).  This is a key point that distinguishes the BANANA problem from other flow-based load sharing and site multihoming problems.
> 
> Thoughts?  Comments?  Do you think this problem statement is clear and understandable?  If not, in what way is it unclear?  All comments from major rewrites to word-smithing are welcome!
> 
> I’ll wait a week for feedback, then I’ll update this problem statement based on any comments I have received from this list.  After that, I will make a formal consensus call on the list, in the hope of confirming that we have consensus, among ourselves at least, regarding the problem we are trying to solve.
> 
> Margaret
> 
> 
> _______________________________________________
> Banana mailing list
> Banana@ietf.org
> https://www.ietf.org/mailman/listinfo/banana