Re: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02
Mingui Zhang <zhangmingui@huawei.com> Wed, 09 December 2015 02:54 UTC
Return-Path: <zhangmingui@huawei.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3247A1A883D for <dmm@ietfa.amsl.com>; Tue, 8 Dec 2015 18:54:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level:
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_36=0.6, J_CHICKENPOX_38=0.6, J_CHICKENPOX_65=0.6, 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 3jpYHemyEHh1 for <dmm@ietfa.amsl.com>; Tue, 8 Dec 2015 18:54:07 -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 D8AA31A883C for <dmm@ietf.org>; Tue, 8 Dec 2015 18:54:06 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CBI95320; Wed, 09 Dec 2015 02:54:02 +0000 (GMT)
Received: from lhreml704-cah.china.huawei.com (10.201.5.130) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 9 Dec 2015 02:54:01 +0000
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 9 Dec 2015 02:54:00 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.181]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Wed, 9 Dec 2015 10:53:57 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, "pierrick.seite@orange.com" <pierrick.seite@orange.com>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02
Thread-Index: AQHRLoMwh7LheBBZ806a1hp6MCrrrp66JIwAgAY4foCAAYCX0A==
Date: Wed, 09 Dec 2015 02:53:56 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E78725780C@nkgeml512-mbx.china.huawei.com>
References: <tencent_3D1069622110DFAF00D8DB64@qq.com> <CAKcc6Ae9McC_rrfv2mbvY1DdxO-Vj0exjjD0YPoPfD_sRi0c3A@mail.gmail.com> <56617290.40408@gmail.com> <19259_1449227196_566173BC_19259_8875_1_81C77F07008CA24F9783A98CFD706F7116126FB9@OPEXCLILM22.corporate.adroot.infra.ftgroup> <05C81A773E48DD49B181B04BA21A342A3865BC2777@HE113484.emea1.cds.t-internal.com>
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A3865BC2777@HE113484.emea1.cds.t-internal.com>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020203.566797CB.00C5, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.7.181, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: d89c1e2d4adf566b53bc33f8fb821271
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/hCAWAXISRNiOW9grVkkrs8GikY8>
Subject: Re: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2015 02:54:10 -0000
Hi, I am not alone who find Figure 1 is misleading. Lots of people around know 'DSL+LTE' is a peculiar use case of BBF WT-348. Now that the draft intends to provide a generic protocol extension for mobility management systems, please drop that use case. Looking at the structure of the doc, Figure 1 is obviously a good position to give a generic reference model rather than a specific example, not to mention a misleading one. In the text, " Flow-1,2 and 3 are distributed either on Tunnel-1 (over LTE) or Tunnel-2 (ober DSL), while Flow-4 is spread on both Tunnel-1 and 2. " s/ober/over/ So, this indicates the doc aims to support both per-flow and per-packet traffic distribution. This point could be explicitly stated. In the figure, s/Flow0=-4/ Flow-4 / I guess authors would produce an updated version to address the issues we've found. Thanks, Mingui > -----Original Message----- > From: Dirk.von-Hugo@telekom.de [mailto:Dirk.von-Hugo@telekom.de] > Sent: Tuesday, December 08, 2015 6:06 PM > To: pierrick.seite@orange.com; dmm@ietf.org > Cc: alexandre.petrescu@gmail.com > Subject: RE: [DMM] Call for adoption confirmation: > draft-seite-dmm-rg-multihoming-02 > > Hi Pierrick, > Thank you for the clarification! > May I recommend then to exchange also the multiple occurrences of RG in the > draft text by - why not MAG? > > Your approach which I think of as mainly opting towards future mobility > management systems with multiple connections (e.g. backhauling of > vehicular/nomadic access nodes or MRs) otherwise might be interpreted in a > misleading direction ... > > Having said this I also would appreciate to replace the expression 'hybrid' by > 'multi-link' or 'multi-connected'. For an BBF-related aggregated access bundling > often called 'hybrid access' (see e.g. BANANA activity) there are - as Mingui > already pointed out - other solution proposals available which consider in detail > the specific existing gaps. > > IMHO I would also opting to replace the use case DSL+LTE by a more general > one e.g. multiple wireless and cellular links as WiFi+LTE or LTE(provided by > operator x) + LTE(provided by operator y) or even LTE+future 5G air interface ... > ;-) > > Thanks a lot! > > Best Regards > Dirk > > -----Original Message----- > From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of > pierrick.seite@orange.com > Sent: Freitag, 4. Dezember 2015 12:07 > To: Alexandre Petrescu; dmm > Subject: Re: [DMM] Call for adoption confirmation: > draft-seite-dmm-rg-multihoming-02 > > Good point... moreover, "rg" means nothing here... > > > -----Message d'origine----- > > De : dmm [mailto:dmm-bounces@ietf.org] De la part de Alexandre > > Petrescu Envoyé : vendredi 4 décembre 2015 12:02 À : dmm Objet : Re: > > [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming- > > 02 > > > > Hi, > > > > I support adoption. > > > > One little note: the -rg- in filename makes think of Research Group. > > It would make sense to change the filename to avoid the use of -rg-, if it's not > too complicated. > > > > Alex > > > > Le 25/11/2015 17:22, Dapeng Liu a écrit : > > > Hello all, > > > > > > In IETF94, we initiated the call for adoption for the draft: > > > draft-seite-dmm-rg-multihoming-02 > > > <http://tools.ietf.org/html/draft-seite-dmm-rg-multihoming-02>: > > > http://tools.ietf.org/html/draft-seite-dmm-rg-multihoming-02 > > > Seems have got sufficient support during the meeting. We'd like to > > > confirm the call for adoption in the mailing list for 2 weeks. > > > Please send your opinion and comments to the list before December 9. > > > > > > > > > Thanks, > > > ------ > > > Best Regards, > > > Dapeng&Jouni > > > > > > > > > > > > > > > > > > -- > > > > > > ------ > > > Best Regards, > > > Dapeng Liu > > > > > > > > > _______________________________________________ > > > dmm mailing list > > > dmm@ietf.org > > > https://www.ietf.org/mailman/listinfo/dmm > > > > > > > _______________________________________________ > > dmm mailing list > > dmm@ietf.org > > https://www.ietf.org/mailman/listinfo/dmm > > ________________________________________________________________ > _________________________________________________________ > > 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. > > _______________________________________________ > dmm mailing list > dmm@ietf.org > https://www.ietf.org/mailman/listinfo/dmm
- [DMM] Call for adoption confirmation: draft-seite… Dapeng Liu
- Re: [DMM] Call for adoption confirmation: draft-s… Seil Jeon
- Re: [DMM] Call for adoption confirmation: draft-s… Mingui Zhang
- Re: [DMM] Call for adoption confirmation: draft-s… Jong-Hyouk Lee
- Re: [DMM] Call for adoption confirmation: draft-s… Dirk.von-Hugo
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Behcet Sarikaya
- Re: [DMM] Call for adoption confirmation: draft-s… Jouni Korhonen
- Re: [DMM] Call for adoption confirmation:draft-se… Z.W. Yan
- Re: [DMM] Call for adoption confirmation: draft-s… Moses, Danny
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Behcet Sarikaya
- Re: [DMM] Call for adoption confirmation: draft-s… Sri Gundavelli (sgundave)
- Re: [DMM] Call for adoption confirmation: draft-s… Behcet Sarikaya
- Re: [DMM] Call for adoption confirmation: draft-s… Jouni Korhonen
- Re: [DMM] Call for adoption confirmation: draft-s… Behcet Sarikaya
- Re: [DMM] Call for adoption confirmation: draft-s… Jouni Korhonen
- Re: [DMM] Call for adoption confirmation: draft-s… Lyle Bertz
- Re: [DMM] Call for adoption confirmation: draft-s… Sri Gundavelli (sgundave)
- Re: [DMM] Call for adoption confirmation: draft-s… Alper Yegin
- Re: [DMM] Call for adoption confirmation: draft-s… Muley, Praveen V (Praveen)
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Alexandre Petrescu
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Mingui Zhang
- Re: [DMM] Call for adoption confirmation: draft-s… Sri Gundavelli (sgundave)
- Re: [DMM] Call for adoption confirmation: draft-s… Dirk.von-Hugo
- Re: [DMM] Call for adoption confirmation: draft-s… Mingui Zhang
- Re: [DMM] Call for adoption confirmation: draft-s… Erunika
- Re: [DMM] Call for adoption confirmation: draft-s… Jouni
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Mingui Zhang
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Sri Gundavelli (sgundave)
- Re: [DMM] Call for adoption confirmation: draft-s… Suresh Krishnan
- Re: [DMM] Call for adoption confirmation: draft-s… pierrick.seite
- Re: [DMM] Call for adoption confirmation: draft-s… Muley, Praveen V (Praveen)
- Re: [DMM] Call for adoption confirmation: draft-s… Dapeng Liu