Re: [homenet] “Hybrid Access for Broadband Networks” (WT-348)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 29 October 2014 14:24 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA061A00F9; Wed, 29 Oct 2014 07:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.567
X-Spam-Level: *
X-Spam-Status: No, score=1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, J_CHICKENPOX_84=0.6, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 wBoV0A7BDUUO; Wed, 29 Oct 2014 07:24:00 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB70E1A00EF; Wed, 29 Oct 2014 07:23:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9TENnnc025931; Wed, 29 Oct 2014 15:23:49 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 52A10204FB9; Wed, 29 Oct 2014 15:25:25 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3E537204F6B; Wed, 29 Oct 2014 15:25:25 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9TENMf4002872; Wed, 29 Oct 2014 15:23:48 +0100
Message-ID: <5450F85A.7000205@gmail.com>
Date: Wed, 29 Oct 2014 15:23:22 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Xueli <xueli@huawei.com>, Ted Lemon <Ted.Lemon@nominum.com>, "STARK, BARBARA H" <bs7652@att.com>
References: <20141021160652.24101.60334.idtracker@ietfa.amsl.com> <4BBD7952-84F7-40F9-9034-8DD7A1F2A05C@nominum.com> <2D09D61DDFA73D4C884805CC7865E61130EA59FC@GAALPA1MSGUSRBF.ITServices.sbc.com> <E8CCD261-8A5C-4249-AF65-468FB1441647@nominum.com> <01FE63842C181246BBE4CF183BD159B4490350AD@nkgeml504-mbx.china.huawei.com> <5447DB20.9080505@gmail.com> <01FE63842C181246BBE4CF183BD159B449036E28@nkgeml504-mbx.china.huawei.com>
In-Reply-To: <01FE63842C181246BBE4CF183BD159B449036E28@nkgeml504-mbx.china.huawei.com>
Content-Type: text/plain; charset="gbk"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/bapCHw5oVsRvc3-L0U_y73rVePQ
Cc: HOMENET Working Group <homenet@ietf.org>, "mif@ietf.org" <mif@ietf.org>
Subject: Re: [homenet] “Hybrid Access for Broadband Networks” (WT-348)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Oct 2014 14:24:03 -0000

Le 28/10/2014 05:10, Xueli a écrit :
> Hello Alex
>
> Thank you for your nice comment. The scenario here is for the fixed
> operators rather than the mobile phone for higher bandwidth. I make
> this clarification in the new version architecture draft as: ” Hosts
> in the customer site may connect to the Internet through the CPE, the
> 3G/4G network, or both.  In most cases the majority of the hosts
> connects to the Internet through the CPE only and will experience
> slow Internet access when the bandwidth provided by the fixed access
> network is fully utilized (e.g., the traffic over the fixed access
> network reached its maximum capacity or a pre-specified threshold set
> by the operator). So we are considering the scenario with CPE
> extension with multiple access networks.
>
> I would like to know additional information on the internet drafts
> you mentioned, do you mind to provide more information on this?

Sure, it is about these documents;

Flow Binding Support for Mobile IP
draft-ietf-mip4-multiple-tunnel-support-08.txt

Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support
RFC 6089

and this post:
https://www.ietf.org/mail-archive/web/mip4/current/msg03728.html

>
> Best Regards Li
>
>
> -----Original Message----- From: Alexandru Petrescu
> [mailto:alexandru.petrescu@gmail.com] Sent: Thursday, October 23,
> 2014 12:28 AM To: Xueli; Ted Lemon; STARK, BARBARA H Cc: HOMENET
> Working Group; mif@ietf.org Subject: Re: “Hybrid Access for Broadband
> Networks” (WT-348)
>
> Hello Xueli,
>
> Several people look at this problem as an IP problem.  Instead of
> considering a cellular+dsl combination in a homebox, they considered
> cellular+wifi on a smartphone.   But the goal was the same: augment
> the bandwidth perceived by the end user.
>
> In implementation it is however quite challenging.  The more tempting
> the expectations of augmenting bandwidth by simply adding network
> interfaces (as in adding RAM to a busy computer), the higher the
> desillusion when facing the challenges of implementation.
>
> Some consider it simply as a local computer policy problem (and hence
> no new communicaiton standards needed), but others consider that
> there is a need of a server in the infrastructure to which these
> interfaces would first connect (a sort of an 'anchor').
>
> If such a technology is developped, it will surely be useful for more
> than homenets - it will be useful for multi-interfaced smartphones,
> useful for mobile routers installed in vehicles, and more that I can
> not think of.
>
> Alex PS: there are a few IETF Internet Drafts about how would
> smartphones would use this, with Mobile IPv4 and Mobile IPv6
> extensions, but there are no widespread implementations.
>
> Le 22/10/2014 11:48, Xueli a écrit :
>> Hello
>>
>> Thanks Barbara to send this liaison out.
>>
>> Hybrid Access network is that Residential gateway (RG, or CPE) is
>> extended with more than two access lines
>>
>> (e.g. DSL + LTE) in order to provide higher bandwidth for the
>> customers. The scenario and architecture are shown as follows
>>
>> cid:image002.jpg@01CF9A07.BF8CD480
>>
>> Right now, we have two individual drafts, one for architecture and
>> requirements, and the other one is for an optional solution.
>>
>> The draft
>> (http://tools.ietf.org/html/draft-lhwxz-hybrid-access-network-architec
>>
>>
ture-00  ; ) proposes the architecture and gap analysis.
>>
>> The solution draft proposes one option for the solutions,
>> http://tools.ietf.org/html/draft-heileyli-gre-notifications-00
>>
>> We did not combine them as one draft, because we believe there may
>> be other candidates, and we would like to have further discussions
>> in the related groups and IETF.
>>
>> We used to present it in Homenet in Toronto.
>>
>> Now the authors have invited Orange to join this architecture
>> work. We will send out the new version of these drafts soon.
>>
>> We are glad to invite the experts for comments.
>>
>> Best Regards
>>
>> Li Xue on the co-authors behalf
>>
>> -----Original Message-----
>>
>> From: homenet [mailto:homenet-bounces@ietf.org] On Behalf Of Ted
>> Lemon
>>
>> Sent: Wednesday, October 22, 2014 3:05 AM
>>
>> To: STARK, BARBARA H
>>
>> Cc: HOMENET Working Group
>>
>> Subject: Re: [homenet] Fwd: New Liaison Statement, "Broadband
>> Forum Work on “Hybrid Access for Broadband Networks”(WT-348)"
>>
>> On Oct 21, 2014, at 2:55 PM, STARK, BARBARA H <bs7652@att.com>
>> wrote:
>>
>>> FYI. I made sure they were aware of IETF mif and homenet
>>> activities in this area. I intend to try to prevent having to
>>> track efforts that try to do the same thing in two different
>>> ways. But some of the BBF effort  may be focused on what can be
>>> done around "bonding" of multiple
>> interfaces that are under the control of a single service provider.
>> I don't see this in mif or homenet.
>>
>> Thanks.   I couldn't really tell what was being proposed from the
>> Liaison statement, so this information is helpful.
>>
>> _______________________________________________
>>
>> homenet mailing list
>>
>> homenet@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>>
>>
>> _______________________________________________ homenet mailing
>> list homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>