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

Xueli <xueli@huawei.com> Tue, 28 October 2014 03:59 UTC

Return-Path: <xueli@huawei.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 09F871A044F; Mon, 27 Oct 2014 20:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Rxvv5tGbmDIu; Mon, 27 Oct 2014 20:59:26 -0700 (PDT)
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 EAC3C1A001E; Mon, 27 Oct 2014 20:59:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKZ80023; Tue, 28 Oct 2014 03:59:23 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 28 Oct 2014 03:59:21 +0000
Received: from NKGEML504-MBX.china.huawei.com ([169.254.7.168]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Tue, 28 Oct 2014 11:59:14 +0800
From: Xueli <xueli@huawei.com>
To: "pierrick.seite@orange.com" <pierrick.seite@orange.com>, Ted Lemon <Ted.Lemon@nominum.com>, "STARK, BARBARA H" <bs7652@att.com>
Thread-Topic: [homenet] Fwd: New Liaison Statement, "Broadband Forum Work on “Hybrid Access for Broadband Networks” (WT-348)"
Thread-Index: AQHP7WIcOm96HPXJ7U2H19EDbAXxJpw7zesggAASlkCACQpR4A==
Date: Tue, 28 Oct 2014 03:59:14 +0000
Message-ID: <01FE63842C181246BBE4CF183BD159B449036DFF@nkgeml504-mbx.china.huawei.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> <31246_1413972312_54478158_31246_662_1_81C77F07008CA24F9783A98CFD706F71142BD145@PEXCVZYM12.corporate.adroot.infra.ftgroup>
In-Reply-To: <31246_1413972312_54478158_31246_662_1_81C77F07008CA24F9783A98CFD706F71142BD145@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.97.86]
Content-Type: multipart/related; boundary="_004_01FE63842C181246BBE4CF183BD159B449036DFFnkgeml504mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/8r1iFw8ZMXZ9GlRLKOUZePBEqyM
Cc: HOMENET Working Group <homenet@ietf.org>, "mif@ietf.org" <mif@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
Subject: [homenet] =?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: Tue, 28 Oct 2014 03:59:30 -0000

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

[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-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<mailto: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<mailto: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.