Re: [Banana] Updated Charter

"Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com> Sun, 01 October 2017 12:22 UTC

Return-Path: <wim.henderickx@nokia.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 7266A1342DC for <banana@ietfa.amsl.com>; Sun, 1 Oct 2017 05:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 pNc-E0pEzrVC for <banana@ietfa.amsl.com>; Sun, 1 Oct 2017 05:22:08 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0101.outbound.protection.outlook.com [104.47.2.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D710132C2A for <banana@ietf.org>; Sun, 1 Oct 2017 05:22:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GEPmyuCRYvhlxxYOpwwwIhxOWP/q2IV44D4fuL2aNMw=; b=M7AmedDVVukMF7IiORkFmGSYs9X6KcKlZVheic2tPkRgOP+JEGRRc1Ql2gCQHnPFj/lPT1NOqEaCNyFYXEDIi6ctzy3VJe9yMnHN1xcllXyhoubcqOnXEc2sc1NJWvaXx0JBdJNDnpbB72Y7oOVfnx36BGlyRgtvXEWUeTf3GlQ=
Received: from AM2PR07MB0961.eurprd07.prod.outlook.com (10.162.37.144) by AM2PR07MB0963.eurprd07.prod.outlook.com (10.162.37.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.77.5; Sun, 1 Oct 2017 12:22:04 +0000
Received: from AM2PR07MB0961.eurprd07.prod.outlook.com ([fe80::4c8a:b7d0:b947:7695]) by AM2PR07MB0961.eurprd07.prod.outlook.com ([fe80::4c8a:b7d0:b947:7695%13]) with mapi id 15.20.0077.016; Sun, 1 Oct 2017 12:22:04 +0000
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
To: Margaret Wasserman <margaretw42@gmail.com>
CC: David Allan I <david.i.allan@ericsson.com>, "banana@ietf.org" <banana@ietf.org>
Thread-Topic: [Banana] Updated Charter
Thread-Index: AQHTNjUUCas+7o82rUq73xEcR/2cT6LGAFWAgAAEGwCAAAR9AIAAnZYAgAD2voCAB1YbgA==
Date: Sun, 01 Oct 2017 12:22:04 +0000
Message-ID: <58424B72-403C-4C81-A60B-C8E3747A8124@nokia.com>
References: <2F845727-395A-4FDD-9E6D-41734E22F9BD@gmail.com> <a7717b292b2f4ece916410f98dc38cb4@rew09926dag03b.domain1.systemhost.net> <BEBED891-9A4B-421F-BD80-606D20FB803B@gmail.com> <E6C17D2345AC7A45B7D054D407AA205C68F6B38A@eusaamb105.ericsson.se> <E8628CC1-A63B-422C-AF18-3A16AF3F9223@gmail.com> <E6C17D2345AC7A45B7D054D407AA205C68F6B49C@eusaamb105.ericsson.se> <B420FF35-A139-45EB-AE64-A330B58A5E28@nokia.com> <0C6764E0-B414-4F0A-A04C-B9CC9E5DFABB@gmail.com>
In-Reply-To: <0C6764E0-B414-4F0A-A04C-B9CC9E5DFABB@gmail.com>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.28.0.170926
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wim.henderickx@nokia.com;
x-originating-ip: [2a02:1810:350a:9600:c410:417f:a2:405e]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0963; 6:5I3jA0Kj/SLpboX4pw0v/Vpp2K7IXuKQaeaCIrlFp7TEm7/uGmoD6sJs3nq+8FuF7GTVkqZUz0jBOeDP2aI1rhMQW9eo1Dbr54bzSOFbDyKbCrhK7655+fVL15P+EfgSxEA7KZAF00t0hWts/2n5h3wGlHvE03wvLRZx9DqQ6AopxEcq/y5/nvUjBwMiqIEm5X3D1wmxd4dIpvFCnmkltYF+obnfgQuQ5fUJNrmHbbAwMZ4bWCwO0SWSzaqMZ6uilxrEAJjvgtGyTNe2kVI2cZyLh+FQPUiyf/Oow8gSanFUdVcuaL9IdiWpLG/ElJRBbWF138+Cpx0YPGKA4JOTnA==; 5:xZdOWjlQsBZ/9aSLj1PP20FRxZWSBeLxYL+idOXKXsHj1U6UPKns+qfdXMhj7zjFy41t/Ymw5mQ73LNYwg+UHhlSqjeIGqAvUSckJWADxklZ/2tTtUigjSAH7WxLWg2YTBwEhRo3faD1oNmm1btwww==; 24:9n3ncSzfs/IgIzZENOd9snGPwYjt8gTvRWCNRYsfHx309QBmO4/6+HWld3vUkRJRKYkI8KKvNPsBNpe+2U8l6lVwehRWHUyPRHOKu89+00M=; 7:ccCjcdCH4mZuHO6PljRwNNHmF530BlGV53/VX/Yy/uJw1lVT5eYor62xW/nM7wnb0vKlS/9c10RUMHpO6+QDpmbADWxFCWqQ/S/nFDBcnH/T/zO7Kmtgj7Wr16PBaPEXpHoUM9dLzVmPA1Vm7bYJ402V1JLyfzsN9tqIJnzlQ3x/UCG+MHNFgwhhUrVkQI7O8Ry9lndJ/fOH55lQESqorM1ZdP/rb18J2g8rEZEkhFs=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: cf558aea-f98c-4555-d15a-08d508c70688
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254152)(48565401081)(2017052603199)(201703131423075)(201703031133081)(201702281549075); SRVR:AM2PR07MB0963;
x-ms-traffictypediagnostic: AM2PR07MB0963:
x-exchange-antispam-report-test: UriScan:(37575265505322)(146908506813832)(278428928389397)(82608151540597)(788757137089)(211936372134217)(175275609761927)(119230021023882);
x-microsoft-antispam-prvs: <AM2PR07MB0963AC4B7FA2922F4579237F837C0@AM2PR07MB0963.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(10201501046)(93006095)(93001095)(920507026)(6055026)(6041248)(20161123560025)(20161123555025)(20161123558100)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB0963; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB0963;
x-forefront-prvs: 0447DB1C71
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(346002)(39860400002)(24454002)(51444003)(13464003)(377454003)(199003)(189002)(1411001)(6306002)(966005)(86362001)(5003630100001)(97736004)(6916009)(410100003)(101416001)(106356001)(7736002)(6512007)(34040400001)(3280700002)(3660700001)(316002)(2900100001)(6506006)(33656002)(58126008)(54906003)(5250100002)(83716003)(14454004)(5890100001)(53546010)(93886005)(36756003)(83506001)(478600001)(81156014)(5660300001)(39060400002)(105586002)(6486002)(4326008)(229853002)(15650500001)(305945005)(81166006)(2950100002)(6246003)(8676002)(53936002)(50986999)(189998001)(6436002)(76176999)(102836003)(2906002)(25786009)(8936002)(68736007)(6116002)(54356999)(82746002)(99286003); DIR:OUT; SFP:1102; SCL:1; SRVR:AM2PR07MB0963; H:AM2PR07MB0961.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C14283AA3BE2C4E89DC64C071294729@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2017 12:22:04.3155 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0963
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/6TD-FnKaBhmSewLYDSaTsDElUNk>
Subject: Re: [Banana] Updated Charter
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: Sun, 01 Oct 2017 12:22:11 -0000

Margeret, will look at the proposed charter again but I am traveling non-stop these days so sorry for my delayed responses. This is idd an improvement afais.
The main issue is that there is a set of protocols that could benefit from the banana work and hence I suggested the information model as a target. The reason is to allow the different protocols to adopt the banana behvior in their work. At least this was my view on how we could move forward.

On 26/09/2017, 22:20, "Margaret Wasserman" <margaretw42@gmail.com> wrote:

    Hi Wim,
    
    I have removed the word signaling in the most recently distributed version, as proposed by Dave Allan below.  Does that address your concern, as well?
    
    Would people also find it clearer if we used the term protocol(s) or mechanism(s) or something similar where we are currently using the word "solutions"?  I think that word may mean different things to different people.
    
    Margaret
    
    Sent from my iPhone
    
    > On Sep 26, 2017, at 1:36 AM, Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com> wrote:
    > 
    > My 2 cents on this and I believe this is where a lot of controversy is coming from, is why would we not charter Banana as a WG which is defining an information model that is required to execute banana. So banana defines which information needs to be exchanged and what the banana entities do with it to perform banana
    > As such the actual protocol works can be done in different WG(s) and we can leverage existing work as Sri was pointing out.
    > 
    > Would this work for people? My 2 cents, just a try to help.
    > 
    > On 25/09/2017, 22:13, "Banana on behalf of David Allan I" <banana-bounces@ietf.org on behalf of david.i.allan@ericsson.com> wrote:
    > 
    >    I'd probably be happier losing signaling. IMO it is an overloaded term...
    > 
    >    "specify protocol(s) that can be used..." 
    > 
    >    WDYT?
    >    Dave
    > 
    >    -----Original Message-----
    >    From: Margaret Cullen [mailto:margaretw42@gmail.com] 
    >    Sent: Monday, September 25, 2017 12:57 PM
    >    To: David Allan I <david.i.allan@ericsson.com>
    >    Cc: banana@ietf.org
    >    Subject: Re: [Banana] Updated Charter
    > 
    > 
    >    Good point, Dave!
    > 
    >    I am a little concerned about the overuse of the term “mechanism”, though (since I define Bandwidth Aggregation mechanisms in the text).  So how about just changing “protocol” to “protocol(s)"?:
    > 
    >    OLD:
    > 
    >        Select or specify a signalling protocol that can be used to send 
    >        control information between BANANA Boxes, including:
    > 
    >    NEW:
    > 
    >        Select or specify signaling protocol(s) that can be used to send 
    >        control information between BANANA Boxes, including:
    > 
    >    Or is theres something more that you were trying to capture by changing from “protocols” to “mechanisms”?
    > 
    >    In addition to what you mentioned, this might allow us to reuse an existing protocol to do part of this job, even if that protocol could not be extended to cover everything we need for BANANA.
    > 
    >    Margaret
    > 
    > 
    > 
    > 
    > 
    >> On Sep 25, 2017, at 3:42 PM, David Allan I <david.i.allan@ericsson.com> wrote:
    >> 
    >> HI Margaret
    >> 
    >> An aspect that concerns me for a while is the notion that there will be a single signaling protocol to satisfy a laundry list of requirements. On first blush this seems to suggest a solution is already in the wings that needs the laundry list, or that we will end up with  a bloated superset god protocol. Neither of which is IMO a totally desirable outcome.
    >> 
    >> Easiest fix for me would be to replace “a signaling protocol” with “mechanisms”.
    >> 
    >> Cheers
    >> Dave
    >> 
    >> From: Banana [mailto:banana-bounces@ietf.org] On Behalf Of Margaret 
    >> Cullen
    >> Sent: Monday, September 25, 2017 12:33 PM
    >> To: philip.eardley@bt.com
    >> Cc: banana@ietf.org
    >> Subject: Re: [Banana] Updated Charter
    >> 
    >> 
    >> No problem, Philip.  I have included the latest text below.  This does not yet include the changes I am currently discussing with Dave Sinicrope.
    >> 
    >> Margaret
    >> 
    >> 
    >> Charter: BANdwidth Aggregation for Network Access WG
    >> 
    >> 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.
    >> 
    >> Bandwidth 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, VPNs, 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 mechanisms (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 or at the remote end, and mechanisms for those components to find each other, exchange signalling information, and direct traffic to each other.   We refer to the functional components at each end as the Local and Remote “BANANA Boxes”, and we refer to the mechanisms they use to direct traffic to each other as “Bandwidth Aggregation mechanisms”.  
    >> 
    >> [Note:  Despite our use of the term “Boxes”, it should be understood 
    >> that a “BANANA Box” might be a software component running on a piece 
    >> of hardware with another primary purpose (e.g. a CPE router).]
    >> 
    >> The Bandwidth Aggregation solutions developed in this group will work 
    >> in true multi-provider scenarios (i.e. they will not depend on all of 
    >> the aggregated links being provided by a single Internet access 
    >> provider nor by a group of cooperating providers).  Any protocols 
    >> defined by this group will be IP-based, link-layer-independent 
    >> solutions, and they will be designed to work across NATs and other middle boxes, as needed.
    >> 
    >> The BANANA WG is chartered to complete the following  work items:
    >>    • Informally document/discuss BANANA problem statement and usage scenarios in a non-archival document (e.g. Wiki, Google Doc, etc.)
    >>    • Determine how Local and Remote BANANA Boxes find each other (i.e. describe how BANANA boxes will be provisioned/configured.)
    >>    • Select or specify a signalling protocol that can be used to send control information between BANANA Boxes, including:
    >>    • IP Prefixes of access  links
    >>    • Information about link status and properties (including congestion)
    >>    • Information needed by the Bandwidth Aggregation mechanism(s) in use
    >>    • Determining which flows are/are not eligible for Bandwidth Aggregation
    >>    • Select (and extend, if necessary) a tunneling encapsulation for sending traffic between BANANA Boxes.
    >> 
    >> When applicable, the BANANA WG will use existing IETF protocols, or extensions to existing IETF protocols, as the basis for the work items listed above.  When an existing protocol is used, the WG deliverable will be a document describing the use of that protocol for Bandwidth Aggregation and/or a set of options or extensions to an existing IETF protocol to make it useful for Bandwidth Aggregation.
    >> 
    >> The BANANA WG will also work with other IETF WGs (and other SDOs, as requested) that define additional Bandwidth Aggregation mechanisms (if any)  to ensure that the protocols defined by the BANANA WG will meet the needs of those additional mechanisms.
    >> 
    >> Milestones
    >>    • Apr 2018 Adopt WG draft for provisioning/configuration mechanism
    >>    • Apr 2018 Adopt WG draft for signaling protocol
    >>    • Apr 2018 Adopt WG draft(s) for tunnel encapsulation(s)
    >>    • Feb 2019 WGLC on provisioning/configuration mechanism
    >>    • Feb 2019 WGLC on signaling protocol
    >>    • Feb 2019 WGLC on tunnel encapsulation(s)
    >>    • Aug 2019 Send provisioning/configuration mechanism to the IESG
    >>    • Aug 2019 Send signalling protocol to the IESG
    >>    • Aug 2019 Send tunnel encapsulation(s) to the IESG
    >> 
    >> On Sep 25, 2017, at 12:37 PM, <philip.eardley@bt.com> <philip.eardley@bt.com> wrote:
    >> 
    >> Margaret,
    >> Please could you post the text on the mailing list, as our firewall 
    >> blocks google docs Thanks!
    >> phil
    >> 
    >> From: Banana [mailto:banana-bounces@ietf.org] On Behalf Of Margaret 
    >> Cullen
    >> Sent: 22 September 2017 20:19
    >> To: banana@ietf.org
    >> Subject: [Banana] Updated Charter
    >> 
    >> I have updated the charter text in an attempt to reflect all of the feedback to date.  You can find the new version here:
    >> https://docs.google.com/document/d/1byOJ_To6eL1ZBxKSYpTafQbngTBiNwxaK7
    >> ReIsld9Ek/edit
    >> 
    >> Thoughts?  Comments?
    >> 
    >> Do folks think this is ready to send to the IESG?  Or are there other changes that it would make it clearer or better?
    >> 
    >> Margaret
    > 
    >    _______________________________________________
    >    Banana mailing list
    >    Banana@ietf.org
    >    https://www.ietf.org/mailman/listinfo/banana
    > 
    >