Re: [homenet] [mif] =?Windows-1252?Q?RE:__Fwd:_New_Liaison_Statement, _"Broadband_For?= um Work on “Hybrid Access for Broadband Networks” (WT-348)"

Alper Yegin <alper.yegin@yegin.org> Mon, 03 November 2014 17:51 UTC

Return-Path: <alper.yegin@yegin.org>
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 A6AA01A1BE4; Mon, 3 Nov 2014 09:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.299
X-Spam-Level:
X-Spam-Status: No, score=0.299 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=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 RcYffD8XcWQd; Mon, 3 Nov 2014 09:51:54 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79D0C1A6F38; Mon, 3 Nov 2014 09:51:51 -0800 (PST)
Received: from [192.168.2.49] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mreueus002) with ESMTP (Nemesis) id 0Md5N6-1XT8RL0lhS-00IDGh; Mon, 03 Nov 2014 18:51:13 +0100
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B1E229C3-838E-4B49-A944-DEE31057DE29"
From: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <01FE63842C181246BBE4CF183BD159B449036DFF@nkgeml504-mbx.china.huawei.com>
Date: Mon, 03 Nov 2014 19:50:58 +0200
Message-Id: <383C8250-658B-47B9-B836-052ADFD82E79@yegin.org>
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> <31246_1413972312_54478158_31246_662_1_81C77F07008CA24F9783A98CFD706F71142BD145@PEXCVZYM12.corporate.adroot.infra.ftgroup> <01FE63842C181246BBE4CF183BD159B449036DFF@nkgeml504-mbx.china.huawei.com>
To: Xueli <xueli@huawei.com>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:K1TwgwzCbgYVWv5LaoUJnAQftBjFakIwlRDz90gzyml tmKAF28Ka1SVuxm+QG5q0TtZU7m3qXjc+Jyz3Ya+OEupqGat6U iLf6CRc/in7KYS6jMTUALLo+zfrpzjxQJN+znncq0TLVcqiV1s 7txoLYJEFH781wcCgcSpZ9XRHAsX4KAEmHtWirVzU1GDhUc8YV vvSCUxAJmgx2tdTxpgZWp6+1byK+UQOqMnTxpeTogFqzYyfQPy 9VmZlmJzHfhwOsegGCndL99scHnHFvQr1ZYPEhXR4TaSe4YeoM NhYF0HNR+heWORvo1QtF2hFqwGP03fZTo9i7tkrldx95WX+I62 94egu0pt/DAoeSQ/ibtV3Rurs24E6p/rT6UrkW1sVK5pJsH1Nd 5wbRPf39C1x0A==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/h238kGJcUqz7dFnoc8QD1g-tExM
X-Mailman-Approved-At: Mon, 03 Nov 2014 23:46:12 -0800
Cc: "mif@ietf.org" <mif@ietf.org>, "pierrick.seite@orange.com" <pierrick.seite@orange.com>, Ted Lemon <Ted.Lemon@nominum.com>, "dmm@ietf.org" <dmm@ietf.org>, HOMENET Working Group <homenet@ietf.org>, "STARK, BARBARA H" <bs7652@att.com>
Subject: Re: [homenet] [mif] =?Windows-1252?Q?RE:__Fwd:_New_Liaison_Statement, _"Broadband_For?= um Work on “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: Mon, 03 Nov 2014 17:51:56 -0000

Hello Li,

Few comments on the lhwxz-hybrid-access draft:

- Even tough the driving use case involves heterogeneous access networks, the design can be used with homogeneous access networks as well. It'd be good to acknowledge that, so that the readers don't assume the applicability is limited to heterogeneous deployments only.

-  "Hosts in the customer site may connect to the Internet through the CPE, the 3G/4G network, or both. "

You mean, "CPE may be connected to the Internet through DSL, 3G/4G, or both"

- Figure 4 seems to refer to a case where the host is exposed to two different prefixes. Is this in scope for BBF? I though they wanted to limit the use case to the one that hides the "duality" from the host. I.e., host has single prefix/IP address.

- "Additionally, the available paths may have different characteristics in terms of bandwidth, delay, MTU, etc.

"cost" as well.

Alper




On Oct 28, 2014, at 5:59 AM, Xueli wrote:

> Hello Pierrick
>  
> First of all, thanks a lot for agree with the big picture depicture and architecture..
> I am fine to split the architecture considerations and solution design in two different documents.
> And I updated the architecture draft (No specific solution there) in the new version, I hope it makes sense for you.
> http://www.ietf.org/internet-drafts/draft-lhwxz-hybrid-access-network-architecture-01.txt
> Do you mind to share more about the solution about DMM proposal.
> Which exact issues it is really solving?
>  
> Best Regards
> Li
>  
> From: pierrick.seite@orange.com [mailto:pierrick.seite@orange.com] 
> Sent: Wednesday, October 22, 2014 6:05 PM
> To: Xueli; Ted Lemon; STARK, BARBARA H
> Cc: HOMENET Working Group; mif@ietf.org; dmm@ietf.org
> Subject: RE: [homenet] Fwd: New Liaison Statement, "Broadband Forum Work on “Hybrid Access for Broadband Networks” (WT-348)"
>  
> Hi Li,
>  
> Architecture considerations and solution design are two different things, which should not be addressed in the same I-D. People may agree with the big picture depicture and architecture but not agree with going on extensions to the GRE protocol to address the issue. BTW, I think that going for extensions to GRE header to address the hybrid access use-case is not the right way. Actually, IETF solutions already exist (RFC  4908 ) and, moreover, there is ongoing effort in DMM to update RFC 4908 to meet hybrid access requirements.  
>  
> BR,
> Pierrick  
>  
> De : Xueli [mailto:xueli@huawei.com] 
> Envoyé : mercredi 22 octobre 2014 11:48
> À : Ted Lemon; STARK, BARBARA H
> Cc : HOMENET Working Group; mif@ietf.org
> Objet : RE: [homenet] Fwd: New Liaison Statement, "Broadband Forum Work on “Hybrid Access for Broadband Networks” (WT-348)"
>  
> 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
> <image001.jpg>
>  
> 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-architecture-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
> _________________________________________________________________________________________________________________________
>  
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>  
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif