IETF Logo Mail Archive

Re: [Banana] diff (banana load distribution, next-hop selection of multipath)

Mingui Zhang <zhangmingui@huawei.com> Sat, 04 February 2017 08:50 UTC

Return-Path: <zhangmingui@huawei.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 6635912946A for <banana@ietfa.amsl.com>; Sat, 4 Feb 2017 00:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.42
X-Spam-Level:
X-Spam-Status: No, score=-7.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-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 j7vECDH8aNri for <banana@ietfa.amsl.com>; Sat, 4 Feb 2017 00:50:55 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F1B0127058 for <banana@ietf.org>; Sat, 4 Feb 2017 00:50:54 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CZZ74928; Sat, 04 Feb 2017 08:50:52 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sat, 4 Feb 2017 08:50:52 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Sat, 4 Feb 2017 16:50:02 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Banana] diff (banana load distribution, next-hop selection of multipath)
Thread-Index: AdJdA2lYXkbqbDOFQbGKAFgQ1qTtuQg7pqqAAAH84AAALb23UP//jfQA//91VwA=
Date: Sat, 04 Feb 2017 08:51:17 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7A63A1D7D@NKGEML515-MBX.china.huawei.com>
References: <4552F0907735844E9204A62BBDD325E7A6386E6A@NKGEML515-MBX.china.huawei.com> <C328BFD1-A2B7-4E95-956A-D553A8167922@gmail.com> <f5bc7430-45dd-c5a6-d376-9d349d40a373@isi.edu> <4552F0907735844E9204A62BBDD325E7A63A1C49@NKGEML515-MBX.china.huawei.com> <99F04B22-01AC-476C-A15A-1696B686A953@isi.edu>
In-Reply-To: <99F04B22-01AC-476C-A15A-1696B686A953@isi.edu>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.146.93]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.589595ED.018B, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: f49f829f0acb312289d3bab283f73fdd
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/jtm9IU4OX4QGtsUVpDERSPwmtCU>
Cc: Margaret Cullen <margaretw42@gmail.com>, "banana@ietf.org" <banana@ietf.org>
Subject: Re: [Banana] diff (banana load distribution, next-hop selection of multipath)
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 04 Feb 2017 08:50:56 -0000

Hi Joe,

But channel bonding is not applicable to heterogeneous links (wired & wireless). It's not applicable to tunnels which are built up on multi-hop paths either. 

So, according to my understanding the goal is to sequence incoming packets and distribute them onto multiple paths (heterogeneous yet multi-hops) in a per-packet manner and then restore their order according to their sequence number. 

Thanks,
Mingui

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Saturday, February 04, 2017 3:48 PM
> To: Mingui Zhang
> Cc: Margaret Cullen; banana@ietf.org
> Subject: Re: [Banana] diff (banana load distribution, next-hop selection of
> multipath)
> 
> 
> 
> > On Feb 3, 2017, at 10:51 PM, Mingui Zhang <zhangmingui@huawei.com> wrote:
> >
> > Hi Joe, all,
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Saturday, February 04, 2017 12:46 AM
> >> To: Margaret Cullen; Mingui Zhang
> >> Cc: banana@ietf.org
> >> Subject: Re: [Banana] diff (banana load distribution, next-hop
> >> selection of
> >> multipath)
> >>
> >> Hi, all,
> >>
> >> So am I to understand that the "problem statement" is:
> >>
> >>    - given two cooperating devices, how to manage a set of bonded
> >> links between them?
> >>
> >> Isn't that what routers already do?
> >
> > There is one key difference. What is routers nowadays doing is per-flow load
> balancing using hashing rather than flow splitting across this set of bonded links
> and then reordering.
> 
> True for many commercial routers but channel bonding isn't new.
> 
> I'm asking what the goal here is - new channel bonding algs? Thats IRTF space.
> What's left?
> 
> Joe
> 
> 
> >
> > Thanks,
> > Mingui
> >
> >>
> >> (yes, I know that I've glossed over the fact that these "links" might
> >> be tunnels - because we have dozens of ways of doing that already)
> >>
> >> Joe

v2.23.0 | Report a Bug | By Email