Re: [Banana] How many links can be BANANA'd together?

Jim Reid <jim@rfc1035.com> Tue, 18 July 2017 11:16 UTC

Return-Path: <jim@rfc1035.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 3CAB1131471 for <banana@ietfa.amsl.com>; Tue, 18 Jul 2017 04:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 17Jc7IiLcfjT for <banana@ietfa.amsl.com>; Tue, 18 Jul 2017 04:16:38 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DEC12EB99 for <banana@ietf.org>; Tue, 18 Jul 2017 04:16:38 -0700 (PDT)
Received: from dhcp-8e9b.meeting.ietf.org (dhcp-8e9b.meeting.ietf.org [31.133.142.155]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 2C9F52421527; Tue, 18 Jul 2017 11:16:36 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <E8355113905631478EFF04F5AA706E98A9066BBD@wtl-exchp-2.sandvine.com>
Date: Tue, 18 Jul 2017 12:16:35 +0100
Cc: "banana@ietf.org" <banana@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E2FF6E3-383A-4836-827E-B38F9FB78C02@rfc1035.com>
References: <E8355113905631478EFF04F5AA706E98A9066BBD@wtl-exchp-2.sandvine.com>
To: Dave Dolson <ddolson@sandvine.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/D4L-1iuqISCxxtOdkBwFGD20PDg>
Subject: Re: [Banana] How many links can be BANANA'd together?
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 18 Jul 2017 11:16:39 -0000

> On 18 Jul 2017, at 12:04, Dave Dolson <ddolson@sandvine.com> wrote:
> 
> In contrast, I think some BANANA documents have explicitly referred to 2 slices.

[citation needed]

AFAICT the banana WG has just about got a charter done and there are no other documents yet.

I think a 5G pipe would be one "path" for a banana device -- handwave! -- alongside wi-fi, DSL or whatever. And if that 5G pipe uses up to 8 network slices, that'll be implementation detail for the 5G provider which is invisible to the banana device. It seems the internal workings of the 5G infrastructure is not going to be exposed to the end user devices that access it. YMMV.