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

jouni korhonen <jouni.nospam@gmail.com> Thu, 15 December 2011 08:17 UTC

Return-Path: <jouni.nospam@gmail.com>
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 9812A11E808C for <mext@ietfa.amsl.com>; Thu, 15 Dec 2011 00:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level:
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=-1.451, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
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 5D1qlNDc-TZS for <mext@ietfa.amsl.com>; Thu, 15 Dec 2011 00:17:25 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D09E11E8089 for <mext@ietf.org>; Thu, 15 Dec 2011 00:17:25 -0800 (PST)
Received: by laah2 with SMTP id h2so902342laa.31 for <mext@ietf.org>; Thu, 15 Dec 2011 00:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=6A9ZRezn+IdbmBPaa2xptZbEoLrpfFC+81Mv+tUDkhU=; b=qt00GfQq+H1I5Z+yFa/Sw6t5mMSQfpRzsfFvdkJ+GIb0MfKKMv+kFikDpGqRb61iGp ZFwbWfUxJ8drDu1jj0c0iI1/Psz/uQtKC9JNBFy9TD/whIsZu1ayH+OEeoYPMUMKa3Rt 1Xov0xZ+v2otIfzDvOgdjwivu9MEPGllpn53c=
Received: by 10.152.144.136 with SMTP id sm8mr1610392lab.33.1323937044307; Thu, 15 Dec 2011 00:17:24 -0800 (PST)
Received: from a88-112-207-66.elisa-laajakaista.fi (a88-112-207-66.elisa-laajakaista.fi. [88.112.207.66]) by mx.google.com with ESMTPS id hy5sm1619742lab.4.2011.12.15.00.17.21 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Dec 2011 00:17:21 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="GB2312"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <OFED49F6F5.B9C35824-ON48257967.0002F383-48257967.00033B14@zte.com.cn>
Date: Thu, 15 Dec 2011 10:17:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E37A011-7BA2-4B39-8AF5-8311E362A649@gmail.com>
References: <OFED49F6F5.B9C35824-ON48257967.0002F383-48257967.00033B14@zte.com.cn>
To: luo.wen@zte.com.cn
X-Mailer: Apple Mail (2.1084)
Cc: Julien Laganier <julien.ietf@gmail.com>, mext@ietf.org
Subject: Re: [MEXT] 答复: 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: Thu, 15 Dec 2011 08:17:26 -0000

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
> 
>