Re: [Banana] diff (banana load distribution, next-hop selection of multipath)

Margaret Cullen <margaretw42@gmail.com> Sat, 04 February 2017 18:06 UTC

Return-Path: <margaretw42@gmail.com>
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 B56A1129617 for <banana@ietfa.amsl.com>; Sat, 4 Feb 2017 10:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PHZUFhzkPo7l for <banana@ietfa.amsl.com>; Sat, 4 Feb 2017 10:06:22 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 1D32E129471 for <banana@ietf.org>; Sat, 4 Feb 2017 10:06:22 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id k15so74047262qtg.3 for <banana@ietf.org>; Sat, 04 Feb 2017 10:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=drvBY/EGtuiyZBWb5eI7bdvb67+PSFGqAPpso8c420k=; b=nwPQhEc1TEoJNN5tv3z/hw8BCAAbBimRG2OgXIffnW9JzWvzKByJlia9YeIqsHrZLM 3iXTa5wLPg9vrFFMvXtTlzV++J04ZxaZhj/I686b/Xs7x+rQ1Zjblb6rh2SjTxUqCFHA 7b0ZuGMvhxe3qoKz4bgXJB9tARglXmgs6USvdoIMVGHKGqueM9lZOkG7PbNiJBDDmHB9 njszG6vjwXHbPEaCMir+NPhKqrPSzT5b/yf8+dmtDdMkk1x0A8APmenhDUp294FG4j9U XfRsB97wyVt4HDJjCkLF4n7gp2ovE3f2bUCX7kYuCz0szRkPXXklgG3ZoOCQ8bzKdlIA VU7Q==
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=drvBY/EGtuiyZBWb5eI7bdvb67+PSFGqAPpso8c420k=; b=pXRo/k0O+LkhvvzBCvuTzWoH9pKkv4Ak1AsNhn5fK0fadwLl5voiADKyJzlikaWPKt XaRnzwajVQ9JG/aJSOa014zxoiSSh61tAdQak+0vGrNAtutL4XFiduMj67YDDzRsFtZ2 Ub/m5w2kvN6X37Wm+7NS9jSZG6cP4jLLTOMxBmiD/Lsp5PV/PnZa7XhA65l9L6ap9wWj roh0y0ZXb/u9rugxO0F6O5CXSo5ZzRLF3qMkPXIED/j3GMD65M1gBFMi30VKuPsIRymL 6a8fNxWdixZ1eOQfP2vpPt4XvRau0xIzzGD7vhP58Yi2YQgTlLigS8uRIFQgY5YqHWig NDYQ==
X-Gm-Message-State: AMke39nBe2fNPWgeS769tpW8JNIjI1JhfQ5VprEfdqo4IK3tIahtaLojXm0kjVsgTggaaw==
X-Received: by 10.200.34.155 with SMTP id f27mr2554591qta.129.1486231580795; Sat, 04 Feb 2017 10:06:20 -0800 (PST)
Received: from ?IPv6:2607:fb90:682b:13b6:cc9:144e:7870:10e9? ([2607:fb90:682b:13b6:cc9:144e:7870:10e9]) by smtp.gmail.com with ESMTPSA id h40sm28215964qtb.6.2017.02.04.10.06.19 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 04 Feb 2017 10:06:20 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Margaret Cullen <margaretw42@gmail.com>
In-Reply-To: <209d92ca-32c4-0f79-bfda-74b469390df1@isi.edu>
Date: Sat, 04 Feb 2017 13:06:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A53E1F28-AF2E-465B-93FE-5D75AD81593B@gmail.com>
References: <4552F0907735844E9204A62BBDD325E7A6386E6A@NKGEML515-MBX.china.huawei.com> <C328BFD1-A2B7-4E95-956A-D553A8167922@gmail.com> <f5bc7430-45dd-c5a6-d376-9d349d40a373@isi.edu> <6F657BB7-A556-4428-B3FE-015F7EC92A61@gmail.com> <209d92ca-32c4-0f79-bfda-74b469390df1@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/kNNSYUJjQ7ycEUEO3TIqevhUtS8>
Cc: Mingui Zhang <zhangmingui@huawei.com>, "banana@ietf.org" <banana@ietf.org>
Subject: Re: [Banana] diff (banana load distribution, next-hop selection of multipath)
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: Sat, 04 Feb 2017 18:06:23 -0000

> On 2/4/2017 9:49 AM, Margaret Cullen wrote:
>> Hi Joe,
>> ,,,
>> There are all sorts of devices that are routers AND include other sorts of traffic shaping or loadsharing.  There are even some routers deployed today that can share a single flow across multiple access links, recombining the traffic in a provider network.   However, there is no standard that I am aware of for doing this, so both ends need to be provided by a single vendor.
> 
> OK, so this would be about picking a standard for coordinating the
> endpoints, tunneling with sequence numbers, and (maybe) the "ECMP"
> sharing alg.

Picking/developing one (or more) standard(s), yes.  A few different solutions have been proposed, and we quickly reviewed them during the BOF.  The two major classes of solution under discussion on the BANANA list have been bonded tunnels (with packet resequencing and flow control at the bonded tunnel endpoints), or something MPTCP Proxy-based (some with various extensions for handling UDP/QUIC traffic).

Because there are significant trade-offs between these two types of solutions that make them applicable for different scenarios, it is possible that we might end up deciding that it makes sense to standardize one of each class.  Or, maybe one of them can be improved to become the preferred solution for all scenarios.  I don’t think we know how that will come out yet.

> I'm just trying to scope the problem. Right now, it looks a lot like it
> might also include trying to use multiple heterogeneous links without a
> cooperating party upstream where the traffic merges, which is quite a
> different problem.

No, that has been tried in the past with very poor results.

> IMO, it'd be useful to be clear about that scope.

Thanks!  I will try to make this clearer in the problem statement.

Margaret