Re: [Banana] Charter Text w/Milestones
Jordan Melzer <Jordan.Melzer@telus.com> Tue, 04 April 2017 20:05 UTC
Return-Path: <Jordan.Melzer@telus.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 558241294E6 for <banana@ietfa.amsl.com>; Tue, 4 Apr 2017 13:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.122
X-Spam-Level:
X-Spam-Status: No, score=-4.122 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=fail (1024-bit key) reason="fail (message has been altered)" header.from=Jordan.Melzer@telus.com header.d=telus.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 uVYAY-a5Rqtt for <banana@ietfa.amsl.com>; Tue, 4 Apr 2017 13:05:49 -0700 (PDT)
Received: from orkaan.nssi.telus.com (orkaan.nssi.telus.com [208.38.59.78]) by ietfa.amsl.com (Postfix) with ESMTP id 62CB81294F7 for <banana@ietf.org>; Tue, 4 Apr 2017 13:05:38 -0700 (PDT)
DomainKey-Signature: s=orkaan.nssi; d=telus.com; c=nofws; q=dns; h=X-IronPort-Anti-Spam-Filtered: X-IronPort-Anti-Spam-Result:X-IronPort-AV:Received: Received:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader:x-originating-ip: Content-Type:Content-Transfer-Encoding:MIME-Version: Return-Path; b=HDB40iwT/aKxROJ4m6gbg1uRUvBUg45//mElD2TVEYeTpEQCYf6OQoNg lwnCtgOnqJJVhPBEcaYaljhojvigLLNOTQcb3jGSQRoGh3xTOi2bIDIys ggUi3aM49sVslRVSVY4QzX+kw5dGLPAU3yLfYdwMm5SIlVTlkPBdLQkk+ E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2DEAQAz++NY/5Fjso5cGQEBAQEBAQEBAQEBBwEBAQEBgw9FURCBCweNbpFblVOCDh8LgkKCbEoCg0M/GAECAQEBAQEBAWsohRUBAQEBAgEBAVEUBwsFBwQCAQgNBAQBASgHJwsUCQgCBAENBQgTiWsIAQQJr28mikEBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBQkBhkSDZoEJijkFkCiMRZJHggaIe4ZEhhiCRIsZHziBBSUWIFaEWR2BY3UBiA0BgQwBAQE
X-IronPort-AV: E=Sophos;i="5.36,275,1486425600"; d="scan'208";a="630520792"
Received: from unknown (HELO WP40080.corp.ads) ([142.178.99.145]) by orkaan-o.nssi.telus.com with ESMTP/TLS/AES128-SHA; 04 Apr 2017 20:05:33 +0000
Received: from BTWP000355.corp.ads (142.174.108.65) by WP40080.corp.ads (142.178.99.145) with Microsoft SMTP Server (TLS) id 8.3.348.2; Tue, 4 Apr 2017 14:05:33 -0600
Received: from BTWP000357.corp.ads (142.174.108.67) by BTWP000355.corp.ads (142.174.108.65) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 4 Apr 2017 13:05:31 -0700
Received: from BTWP000357.corp.ads ([fe80::3d29:ad33:93d3:ea45]) by BTWP000357.corp.ads ([fe80::3d29:ad33:93d3:ea45%14]) with mapi id 15.00.1236.000; Tue, 4 Apr 2017 13:05:31 -0700
From: Jordan Melzer <Jordan.Melzer@telus.com>
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, David Allan I <david.i.allan@ericsson.com>, Margaret Cullen <margaretw42@gmail.com>, "banana@ietf.org" <banana@ietf.org>
CC: Mirja Kuehlewind <ietf@kuehlewind.net>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Banana] Charter Text w/Milestones
Thread-Index: AQHSqXEH9+MOZQ3wckS9wmvp5XEkV6GuJOyAgAfnnAD//5TTsA==
Date: Tue, 04 Apr 2017 20:05:31 +0000
Message-ID: <6eb47203c5f447d3bd3dd1e8c38d0f5c@BTWP000357.corp.ads>
References: <96A7BC33-FB64-487A-A60D-7AB8504C9DDF@gmail.com> <E6C17D2345AC7A45B7D054D407AA205C68D24314@eusaamb105.ericsson.se> <D5093953.266331%sgundave@cisco.com>
In-Reply-To: <D5093953.266331%sgundave@cisco.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [142.63.7.97]
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/SDSjNUcqzGij210gS7HaL9bkdHs>
Subject: Re: [Banana] Charter Text w/Milestones
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, 04 Apr 2017 20:05:52 -0000
I would like to see the group develop a path bonding mechanism that works for arbitrary collections of links (like MPTCP) and allows arbitrary protocols to run across them (unlike MPTCP). I believe this implies flow control but not retransmission. There may be some other considerations -- eg packet size, perhaps some policy concerns around what link gets used first / by what. There are a number of uses for arbitrary link bonding, some of which would apply only to a network segment but not the endpoints and others which would involve one or both endpoints. If it's possible to make a protocol that could be used in any of these ways that would be great. Like every other group doing a multipath something, I think this group should briefly put together requirements and then define a solution that meets them. Where BANANA is different from some of the others is that it would be building a general multi-path solution. If you feel there already is one or a potential to do one without creating any new messages, say so -- certainly an informational RFC explaining how to do something with existing tools is easier to do than making a new protocol. If not, it does sound possible to build -- some of the current solutions are very close -- feel free to suggest a method. Though I am not sure that this is the group consensus, I believe the reason there is a new group for this is that no other protocol / group has nailed any path collection, any protocol multipathing. If we're able to agree on what that really is and another IETF group can solve it -- great. We knock off early for beers. Jordan -----Original Message----- From: Banana [mailto:banana-bounces@ietf.org] On Behalf Of Sri Gundavelli (sgundave) Sent: April 4, 2017 02:56 PM To: David Allan I; Margaret Cullen; banana@ietf.org Cc: Mirja Kuehlewind; Suresh Krishnan Subject: Re: [Banana] Charter Text w/Milestones > So before progressing, I think more effort needs to be put into >demonstrating that there is a common problem to be solved that is any >more than configuration of what I believe to be a boutique use case. Agree with Dave. I am not understanding what this group intends to develop. I am all for bringing new features/addressing gaps in protocol specific groups such as MPTCP/DMM ..etc. Sri On 3/30/17, 11:12 AM, "Banana on behalf of David Allan I" <banana-bounces@ietf.org on behalf of david.i.allan@ericsson.com> wrote: >HI > >I have to admit I have a few problems with this.... > >First, two items in the interest of full disclosure, > >1) I'm focused on the converged operator case where this is likely to >be a managed service, and my comments are a result of viewing the >problem through that lens. As such, operators already have tools to do >a chunk of this (e.g. policy and configuration) which they will simply >extend as necessary vs. deploy new protocols. > >2) I have a leadership position in Broadband Forum where we have been >working this space for some time. We expect to do further work as part >of efforts to add fixed access/hybrid access directly to a 5G core. >This is to satisfy the aspirations of a number of European carriers of >have both wireless and wireline offerings and wish to converge them. >This is a project we are initiating in cooperation with 3GPP with >deliverables to be complete for release 16(YE 2018), and I would expect >this to address a chunk of the wishlist in the charter independently of any BANANA efforts. >My reasons for thinking this outlined above, the bootstrapping and >configuration I would expect to be achieved by augmenting already >specified and deployed tools. > >IF this were to go forward I would want to see the necessary functions >decomposed, and separate out initial bootstrapping of the service from >steady state operation. A toolbox of protocols that could be >individually adopted would serve the industry better than a god >protocol. That being said, if bootstrapping and initial configuration >is taken off the table as not of use to my constituency, I am highly >skeptical that the steady state operation of any of a number of >solutions can be genericized to be common to the set of approaches >currently on the table... Off the top of my head I would characterize the steady state functions as: > - routing to an off path proxy <-- property of the individual protocol >solution > - flow control <-- property of the individual protocol solution, e.g. >TCP can be dealt with differently than UDP, differently than something >like QUIC > - maintaining ordering guarantees <-- property of the individual >protocol solution > - fault detection <-- COULD be separate OAM, or bundled into the >individual solution's flow control, ergo part of the specific solution.... > >So before progressing, I think more effort needs to be put into >demonstrating that there is a common problem to be solved that is any >more than configuration of what I believe to be a boutique use case. > >I hope this helps >Dave > > > >-----Original Message----- >From: Banana [mailto:banana-bounces@ietf.org] On Behalf Of Margaret >Cullen >Sent: Thursday, March 30, 2017 11:10 AM >To: banana@ietf.org >Cc: Mirja Kuehlewind <ietf@kuehlewind.net>; Suresh Krishnan ><suresh.krishnan@ericsson.com> >Subject: [Banana] Charter Text w/Milestones > >Here is the (wordsmithed) charter text from last night. I have also >added milestones. > >At this point, the text attempts to be neutral about the subject of >whether there will be an MPTCP encapsulation (presumably done in the >MPTCP WG) or not. We might want to update the text based on the >outcome of today¹s MPTCP meeting if there is any clear conclusion. > >Thoughts? Comments? > >Any feedback will be appreciated! > >Margaret > >The BANdwidth Aggregation for Network Access (BANANA) Working Group is >chartered to develop solution(s) to support dynamic path selection on a >per-packet basis in networks that have more than one point of >attachment to the Internet. > >Bandwith Aggregation consists of splitting local traffic across >multiple Internet links on a per-packet basis, including the ability to >split a single flow across multiple links when necessary. > >It is the goal of this WG to produce a Bandwidth Aggregation solution >that will provide the following benefits: > >- Higher Per-Flow Bandwidth: Many Internet links available to homes > and small offices (DSL, Cable, LTE, Satellite, etc.) have relatively > low bandwidth. Users may wish to run applications (such as > streaming video, or content up/downloads) that require (or could > benefit from) more bandwidth for a single traffic flow than is > available on any of the local links. A Bandwidth Aggregation > solution could supply the needed bandwidth by splitting a single > traffic flow across multiple Internet links. > >- Reduced Cost: Traffic sharing on a per-packet basis allows the full > bandwidth of the lowest-cost link to be used first, only using a > higher-cost link when the lowest-cost link is full. > >- Increased Reliability: When one Internet link goes down, ongoing > application flows can be moved to another link, preventing service > disruption. > >Proposed BANANA solutions use different approaches (e.g. tunnels, >proxies, etc.) to split and recombine traffic, but at an abstract >level, they involve a local (hardware or software) component on the >multi-access network, a remote component within the Internet, and >mechanisms for those components to find each other, exchange signalling >information, and direct traffic to each other. We refer to these >functional components as the Local and Remote "BANANA Boxes", and we >refer to the method they use to direct traffic to each other as a "BANANA Encapsulation". > >The Bandwidth Aggregation solutions developed in this group will work >whether the attached links are provided by a single Internet Service >Provider or multiple Providers. > >The BANANA WG will have the following work items: > >- Determine how Local and Remote BANANA Boxes find each other. > >- Specify a signalling protocol that can be used to send configuration > and control information between BANANA boxes, including: > - IP Prefixes of local links > - Information about link properties & status > - Information needed by the encapsulations > >- Select (and extend, if necessary) an existing tunneling > encapsulation for sending traffic between BANANA Boxes. > >- Work with other IETF WGs defining BANANA encapsulations > (if any) to ensure that the discovery mechanism and signalling > protocol will meet their needs. > >BANANA Boxes will determine if a specific flow is eligible for Bandwith >Aggregation. If a flow is not eligible, it will not be split across >multiple attached links. > >For this initial charter, we will focus on how Local BANANA Boxes >communicate with Remote BANANA Boxes. We will not address the topic of >cooperation between multiple Local BANANA Boxes. > >MILESTONES >(Assumes WG Chartering by May 2017) >Dec 2017 Adopt WG draft for discovery/configuration mechanism Dec 2017 >Adopt WG draft for signalling proocol Dec 2017 Adopt WG draft for >tunnel encapsulation Oct 2018 WGLC on discovery/configuration mechanism >Oct 2018 WGLC on signalling protocol Oct 2018 WGLC on tunnel >encapsulation Apr >2019 Send discovery/configuration mechanism to the IESG Apr 2019 Send >signalling protocl to the IESG Apr 2019 Send tunnel encapsulation to >the IESG > >_______________________________________________ >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
- Re: [Banana] Charter Text w/Milestones Juliusz Chroboczek
- Re: [Banana] Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] Charter Text w/Milestones Juliusz Chroboczek
- Re: [Banana] Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] Charter Text w/Milestones Juliusz Chroboczek
- Re: [Banana] Charter Text w/Milestones Flinck, Hannu (Nokia - FI/Espoo)
- Re: [Banana] Charter Margaret Wasserman
- Re: [Banana] Charter N.Leymann
- Re: [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones Flinck, Hannu (Nokia - FI/Espoo)
- [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones Dave Dolson
- Re: [Banana] Charter Text w/Milestones philip.eardley
- Re: [Banana] Charter Text w/Milestones Dave Dolson
- Re: [Banana] Charter Text w/Milestones Jordan Melzer
- Re: [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones Margaret Cullen
- Re: [Banana] Charter Text w/Milestones David Allan I
- Re: [Banana] Charter Text w/Milestones Jordan Melzer
- Re: [Banana] Charter Text w/Milestones David Allan I
- Re: [Banana] Charter Text w/Milestones Mirja Kuehlewind (IETF)
- Re: [Banana] Charter Text w/Milestones David Allan I
- Re: [Banana] [ALU] Re: Charter Text w/Milestones Muley, Praveen (Nokia - US/Mountain View)
- Re: [Banana] [ALU] Re: Charter Text w/Milestones Zhangmingui (Martin)
- Re: [Banana] [ALU] Re: Charter Text w/Milestones Philipp S. Tiesel
- Re: [Banana] [ALU] Re: Charter Text w/Milestones Muley, Praveen (Nokia - US/Mountain View)
- Re: [Banana] Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] [ALU] Re: Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] Charter Text w/Milestones Jordan Melzer
- Re: [Banana] Charter Text w/Milestones Sri Gundavelli (sgundave)
- Re: [Banana] [ALU] Re: Charter Text w/Milestones pierrick.seite
- Re: [Banana] Charter Text w/Milestones Juliusz Chroboczek
- Re: [Banana] Charter Text w/Milestones Flinck, Hannu (Nokia - FI/Espoo)
- Re: [Banana] Charter Text w/Milestones Juliusz Chroboczek
- Re: [Banana] Charter Text w/Milestones Flinck, Hannu (Nokia - FI/Espoo)
- Re: [Banana] Charter Text w/Milestones Jordan Melzer
- Re: [Banana] Charter Text w/Milestones Margaret Wasserman
- Re: [Banana] Charter Text w/Milestones Brian Trammell (IETF)
- Re: [Banana] Charter Text w/Milestones Alexandre Petrescu
- Re: [Banana] Charter Alexandre Petrescu
- Re: [Banana] Charter Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [Banana] Charter Muley, Praveen (Nokia - US/Mountain View)
- Re: [Banana] Charter mrcullen42
- Re: [Banana] Charter mrcullen42
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [Banana] Charter Zhangmingui (Martin)
- Re: [Banana] Charter Brian Trammell (IETF)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Muley, Praveen (Nokia - US/Mountain View)
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter David Allan I
- Re: [Banana] Charter Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Zhangmingui (Martin)
- Re: [Banana] Charter Suresh Krishnan
- Re: [Banana] Charter HeidemannC
- Re: [Banana] Charter N.Leymann
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Tommy Pauly
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Wasserman
- Re: [Banana] Charter Margaret Wasserman
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter philip.eardley
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter David Sinicrope
- Re: [Banana] Charter Florin Baboescu
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Suresh Krishnan
- Re: [Banana] Charter Zhangmingui (Martin)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter David Sinicrope
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Joerg Deutschmann
- Re: [Banana] Charter N.Leymann
- Re: [Banana] Charter Mirja Kühlewind
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter Sri Gundavelli (sgundave)
- Re: [Banana] Charter David Sinicrope
- Re: [Banana] Charter Margaret Cullen
- Re: [Banana] Charter David Sinicrope