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

Mingui Zhang <[email protected]>
Newsgroups gmane.ietf.mip6
Message-ID <4552F0907735844E9204A62BBDD325E78725780C__31742.2942411669$1449629667$gmane$org@nkgeml512-mbx.china.huawei.com>
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: [email protected] [mailto:[email protected]]
> Sent: Tuesday, December 08, 2015 6:06 PM
> To: [email protected]; [email protected]
> Cc: [email protected]
> 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:[email protected]] On Behalf Of
> [email protected]
> 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:[email protected]] 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
> > > [email protected]
> > > https://www.ietf.org/mailman/listinfo/dmm
> > >
> >
> > _______________________________________________
> > dmm mailing list
> > [email protected]
> > 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/dmm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.