[Banana] BANANA BOF in Prague?

[Margaret Cullen <[e-mail]>]

Just FYI —

I have submitted a request for a WG Forming BANANA BOF in Prague with the information included below.  This information has also been added to the BOF Wiki.

Please let me know if you notice any errors or omissions, or if you have any questions or suggestions.

Thanks,
Margaret

BOF Name:  Bandwidth Aggregation for Network Access (BANANA)

Description:

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.

Agenda
- Agenda bash, scribe, minute taker [5min]
- Review of proposed charter text (see below) [10 mins]
- Charter discussion [45 mins]
- Questions: [30 mins]
    - Is the charter text clear and understandable?
    - Should the IETF do this work?
    - Are you willing to contribute (write, review, email, etc.)

Status: WG Forming 
Responsible AD: Suresh Krishnan 
BoF proponents: Margaret Cullen / Brian Trammel / Mingui Zhang
BoF chairs: Margaret Cullen / Brian Trammel 
Number of people expected to attend: 100 
Length of session (1, 1.5, 2, or 2.5 hours): 1.5 hours 
Conflicts to avoid (whole Areas and/or WGs): Internet area, Homenet, TRILL, MPTCP, QUIC

-     Mailing List: ​https://www.ietf.org/mailman/listinfo/banana
-     Draft charter: see below
-     Relevant drafts: [[BR]]
https://datatracker.ietf.org/doc/draft-leymann-banana-signalling
https://datatracker.ietf.org/doc/draft-leymann-banana-data-encap
https://datatracker.ietf.org/doc/draft-leymann-banana-integration
https://datatracker.ietf.org/doc/draft-leymann-banana-discard-load-rebalance
https://datatracker.ietf.org/doc/draft-leymann-banana-discard-timer
https://tools.ietf.org/html/draft-kanugovi-intarea-mams-protocol-04
https://tools.ietf.org/html/draft-zhu-intarea-mams-control-protocol-01


Proposed Charter Text and Milestones:

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
Apr 2018 Adopt WG draft for discovery/configuration mechanism
Apr 2018 Adopt WG draft for signalling proocol
Apr 2018 Adopt WG draft for tunnel encapsulation
Feb 2019 WGLC on discovery/configuration mechanism
Feb 2019 WGLC on signalling protocol
Feb 2019 WGLC on tunnel encapsulation
Aug 2019 Send discovery/configuration mechanism to the IESG
Aug 2019 Send signalling protocl to the IESG
Aug 2019 Send tunnel encapsulation to the IESG