[MEXT] 答复: Re: 答复: Re: 答复: The first proposal for the DMM charter

luo.wen@zte.com.cn Fri, 16 December 2011 00:41 UTC

Return-Path: <luo.wen@zte.com.cn>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B5921F8448; Thu, 15 Dec 2011 16:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -90.375
X-Spam-Level:
X-Spam-Status: No, score=-90.375 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQmSTv5cj5Ow; Thu, 15 Dec 2011 16:41:31 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDAA21F8481; Thu, 15 Dec 2011 16:41:29 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 566902761818882; Fri, 16 Dec 2011 08:24:31 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 59129.5383578916; Fri, 16 Dec 2011 08:41:01 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id pBG0fCK6017207; Fri, 16 Dec 2011 08:41:12 +0800 (GMT-8) (envelope-from luo.wen@zte.com.cn)
In-Reply-To: <4E37A011-7BA2-4B39-8AF5-8311E362A649@gmail.com>
To: jouni korhonen <jouni.nospam@gmail.com>
MIME-Version: 1.0
X-KeepSent: A57D4A0F:E141F511-48257968:00038DC2; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFA57D4A0F.E141F511-ON48257968.00038DC2-48257968.0003C47E@zte.com.cn>
From: luo.wen@zte.com.cn
Date: Fri, 16 Dec 2011 08:41:02 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-12-16 08:41:12, Serialize complete at 2011-12-16 08:41:12
Content-Type: multipart/alternative; boundary="=_alternative 0003C47948257968_="
X-MAIL: mse02.zte.com.cn pBG0fCK6017207
Cc: Julien Laganier <julien.ietf@gmail.com>, mext-bounces@ietf.org, mext@ietf.org
Subject: [MEXT] 答复: Re: 答复: Re: 答复: The first proposal for the DMM charter
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 00:41:32 -0000

Hi jouni:

     Thank you for the reply. 

Cheers
Luowen




jouni korhonen <jouni.nospam@gmail.com> 
发件人:  mext-bounces@ietf.org
2011-12-15 16:17

收件人
luo.wen@zte.com.cn
抄送
Julien Laganier <julien.ietf@gmail.com>, mext@ietf.org
主题
Re: [MEXT] 答复: Re:  答复:  The first proposal for the DMM charter







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, luo.wen@zte.com.cn wrote:

> 
> Hi Julien 
> 
> Thank you for correcting me 
> 
> Cheers 
> Luowen 
> 
> 
> 
> Julien Laganier <julien.ietf@gmail.com> 
> 发件人:  mext-bounces@ietf.org
> 2011-12-15 01:28
> 
> 收件人
> luo.wen@zte.com.cn
> 抄送
> jouni korhonen <jouni.nospam@gmail.com>, mext@ietf.org
> 主题
> Re: [MEXT] 答复:  The first proposal for the DMM charter
> 
> 
> 
> 
> 
> Luowen,
> 
> 2011/12/14 <luo.wen@zte.com.cn>
> >
> >
> > 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
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
> 
> 

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext