Re: [DMM] Call for adoption confirmation: draft-seite-dmm-rg-multihoming-02

Jouni <jouni.nospam@gmail.com> Wed, 09 December 2015 05:04 UTC

Return-Path: <jouni.nospam@gmail.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 903701ACD25 for <dmm@ietfa.amsl.com>; Tue, 8 Dec 2015 21:04:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_36=0.6, J_CHICKENPOX_38=0.6, J_CHICKENPOX_65=0.6, SPF_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 2FWCLKt_zrg6 for <dmm@ietfa.amsl.com>; Tue, 8 Dec 2015 21:04:41 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C4A91ACD2F for <dmm@ietf.org>; Tue, 8 Dec 2015 21:04:41 -0800 (PST)
Received: by pacdm15 with SMTP id dm15so23584145pac.3 for <dmm@ietf.org>; Tue, 08 Dec 2015 21:04:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CvekuJFInT4PgOmTCuTEaJlu3pDnntVAkVxsckgJH5M=; b=eNlzx9wtiYueD1fHTfhbS6powyVPud7tKrXJOlZoGaR8xbiArQFawwr4znynXC+bXz IRFT1f7xTnBbDGIjPLrY8TrVc7aT2CE/HuohZkGMdidJdSaEBpJm4A+b6f3uQDFwRPAY iwT35RrYSsbxSQGcwhi1kUcR/xp7Y+J/6XUZZNzF08J087ix9B0CMuuZQpKrAUh8Gkm+ C29Gor3G5B4GXMvmRqLuYRVCdEJrfSomfuhG+CaJkN5Wm7hihPh7BUeOUieGqjBtB6HQ nDD++lY17yYxZMMb0vnsFa0BqFNWYrIN34z5mZaHmrNuzxEAw9Kyi0tFQuw2gBjZZ/zG Cq4w==
X-Received: by 10.66.222.202 with SMTP id qo10mr5235750pac.27.1449637481211; Tue, 08 Dec 2015 21:04:41 -0800 (PST)
Received: from ?IPv6:2601:647:4204:228b:ed4c:e356:8bcf:a740? ([2601:647:4204:228b:ed4c:e356:8bcf:a740]) by smtp.gmail.com with ESMTPSA id f13sm8121783pfj.35.2015.12.08.21.04.39 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 08 Dec 2015 21:04:40 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <4552F0907735844E9204A62BBDD325E78725780C@nkgeml512-mbx.china.huawei.com>
Date: Tue, 08 Dec 2015 21:04:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4EA8935-C2A0-40B6-AA7C-B940B3CFC20A@gmail.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> <4552F0907735844E9204A62BBDD325E78725780C@nkgeml512-mbx.china.huawei.com>
To: Mingui Zhang <zhangmingui@huawei.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/gEiIGnpY9j86HywaNiuQxLmrXps>
Cc: "dmm@ietf.org" <dmm@ietf.org>
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 05:04:44 -0000

> On 08 Dec 2015, at 18:53, Mingui Zhang <zhangmingui@huawei.com> wrote:
> 
> 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. 

I do not see why giving an example which happens to depict access technologies such as LTE and DSL would be somehow exclusive to some specific SDO. 

- Jouni

> 
> 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 mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm