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

<N.Leymann@telekom.de> Tue, 18 July 2017 14:12 UTC

Return-Path: <N.Leymann@telekom.de>
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 C70411317C3 for <banana@ietfa.amsl.com>; Tue, 18 Jul 2017 07:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 yipL4oR2q-Bh for <banana@ietfa.amsl.com>; Tue, 18 Jul 2017 07:12:15 -0700 (PDT)
Received: from mailout33.telekom.de (MAILOUT33.telekom.de [80.149.113.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C069131B64 for <banana@ietf.org>; Tue, 18 Jul 2017 07:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1500387134; x=1531923134; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ykQdnL5EsoIojvDWG90c7C3nMMfJUIobz82yKNKWZXs=; b=TDDvUxc5e2DTJz7es/CXnzwhHtTJi8rjVWpJCkVdfpFtRqmjhHAMW7Zx wwvVYaUgT1Yw4xVDhnFLxchv7aOGeIERv5u7Mr6PtVSyW83Y62ffcNQ5m Q5FHea1M4+BJg3br+0E0KuJHOWRRUYgWHC31wCvskHSBhN11K4gVP70ED j2wxuu8qGlGVwPeie7hdvtAM5HQAHjOnxELzuSlAh06MR4eo0lf9InYR1 VcJf6LA71RpGoejx17zERGXg7FTflRlI9P2zFa3LVr7WauzgIutPadJcO yzkXlSpxNX5R0lFxF7maDleq3AqezCOSlm5U9Xi+kFLvtFdxESgtY/ewq A==;
Received: from q4de8psa04t.blf.telekom.de ([10.151.13.130]) by MAILOUT31.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2017 16:12:11 +0200
X-IronPort-AV: E=Sophos;i="5.40,378,1496095200"; d="scan'208";a="702786582"
Received: from he105662.emea1.cds.t-internal.com ([10.169.119.58]) by Q4DE8PSA04V.blf.telekom.de with ESMTP/TLS/AES256-SHA; 18 Jul 2017 16:12:11 +0200
Received: from HE105662.EMEA1.cds.t-internal.com (10.169.119.58) by HE105662.emea1.cds.t-internal.com (10.169.119.58) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 18 Jul 2017 16:12:10 +0200
Received: from HE105662.EMEA1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4]) by HE105662.emea1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4%26]) with mapi id 15.00.1263.000; Tue, 18 Jul 2017 16:12:10 +0200
From: N.Leymann@telekom.de
To: ddolson@sandvine.com, pierre.pfister@darou.fr, david.i.allan@ericsson.com
CC: jim@rfc1035.com, banana@ietf.org
Thread-Topic: [Banana] How many links can be BANANA'd together?
Thread-Index: AdL/tXauEol5v0YGSwSpIScYAk8fmAAI2FiAAAf2s8D//2XXgIAAHvYA///XBhA=
Date: Tue, 18 Jul 2017 14:12:10 +0000
Message-ID: <a9ca8b12c03d4036baf9938308153ff1@HE105662.emea1.cds.t-internal.com>
References: <E8355113905631478EFF04F5AA706E98A9066BBD@wtl-exchp-2.sandvine.com> <9E2FF6E3-383A-4836-827E-B38F9FB78C02@rfc1035.com> <E6C17D2345AC7A45B7D054D407AA205C68ED2D16@eusaamb105.ericsson.se>, <05C2ACEB-0711-4E5A-8A06-C3578B5EF931@darou.fr> <20170718134340.5140562.37503.24048@sandvine.com>
In-Reply-To: <20170718134340.5140562.37503.24048@sandvine.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.176.211.138]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/e6hi4PUo6AJEcPkD9LeH772knvo>
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 14:12:18 -0000

Hi,

I think there are "banana-like" deployments out there, using two links. But I agree that there is no reason to limit banana to two.

Regards

Nic

-----Ursprüngliche Nachricht-----
Von: Banana [mailto:banana-bounces@ietf.org] Im Auftrag von Dave Dolson
Gesendet: Dienstag, 18. Juli 2017 15:44
An: Pierre Pfister; David Allan I
Cc: Jim Reid; banana@ietf.org
Betreff: Re: [Banana] How many links can be BANANA'd together?

Let me state it another way: I think it should be possible to utilize N BANANA tunnels, where N may exceed 2.

I don't recall which draft or email I read that assumed 2.


David Dolson
Sandvine
  Original Message
From: Pierre Pfister
Sent: Tuesday, July 18, 2017 1:52 PM
To: David Allan I
Cc: Jim Reid; Dave Dolson; banana@ietf.org
Subject: Re: [Banana] How many links can be BANANA'd together?


One single interface/link can also be used to provide multiple ways to access the network (e.g. in case of network multi-homing).
This distinction between interface and "Provisioning Domains" has been defined in [rfc7556].

A BANANA box should be able to aggregate traffic between multiple Provisioning Domains (PvDs) regardless whether those PvDs are on distinct interfaces or not.

- Pierre

> Le 18 juil. 2017 à 13:32, David Allan I <david.i.allan@ericsson.com> a écrit :
>
> The discussion is conflating a few concepts....
>
> We have physical interfaces, which can be subdivided for the purpose of accessing the internet or specific closed user groups or VPNs a.k.a. slices.
>
> A BANANA function (not box) would serve for access to a slice where access was available on multiple interfaces. If my CPE wanted to do bandwidth aggregation to more than one slice, more than one function instance would be required.
>
> Cheers
> Dave
>
> -----Original Message-----
> From: Banana [mailto:banana-bounces@ietf.org] On Behalf Of Jim Reid
> Sent: Tuesday, July 18, 2017 1:17 PM
> To: Dave Dolson <ddolson@sandvine.com>
> Cc: banana@ietf.org
> Subject: Re: [Banana] How many links can be BANANA'd together?
>
>
>> 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.
>
> _______________________________________________
> Banana mailing list
> Banana@ietf.org
> https://www.ietf.org/mailman/listinfo/banana
>
> _______________________________________________
> Banana mailing list
> Banana@ietf.org
> https://www.ietf.org/mailman/listinfo/banana

_______________________________________________
Banana mailing list
Banana@ietf.org
https://www.ietf.org/mailman/listinfo/banana