Hi, As Julien pointed out, we have a checkpoint planned for IETF#85. After two meeting cycles we should be clear which documents will be the basis (can be a combination of multiple, not just one) for requirements & analysis. That should give us enough time & background to realized whether concrete protocol extensions are needed and what they roughly are. New goals for possible new solutions (i.e. extensions to some protocol, not necessarily just mobility protocols) will be added as a part of charter goals update.
- Jouni On Dec 15, 2011, at 2:35 AM, [email protected] wrote: > > Hi Julien > > Thank you for correcting me > > Cheers > Luowen > > > > Julien Laganier <[email protected]> > 发件人: [email protected] > 2011-12-15 01:28 > > 收件人 > [email protected] > 抄送 > jouni korhonen <[email protected]>, [email protected] > 主题 > Re: [MEXT] 答复: The first proposal for the DMM charter > > > > > > Luowen, > > 2011/12/14 <[email protected]> > > > > > > Hi jouni: > > > > I have a quick question about 'Goals and Milestones'. > > > > As it is stated 'If limitations are identified as part of the above > > deliverable, specify extensions to existing protocols that removes these > > limitations within a distributed mobility management environment.' which > > means, I guess, a solution will be created for remove these limitations and > > a RFC will be needed. > > > > So why the 'Goals and Milestones' misses this part? Or does it mean the > > solution for remove these limitaions is also included in the I-D 'Best > > practices and Gap Analysis' ? > > It's not missing, it is covered as part of this milestone: > > Nov 2012 - Evaluate the need for additional working group document(s) > for extensions to fill the identified gaps. > > --julien > _______________________________________________ > MEXT mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mext > > _______________________________________________ MEXT mailing list [email protected] https://www.ietf.org/mailman/listinfo/mext
