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

Julien Laganier <julien.ietf@gmail.com> Wed, 14 December 2011 17:28 UTC

Return-Path: <julien.ietf@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 90F051F0C63 for <mext@ietfa.amsl.com>; Wed, 14 Dec 2011 09:28:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.177
X-Spam-Level:
X-Spam-Status: No, score=-1.177 tagged_above=-999 required=5 tests=[AWL=-2.423, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_GB2312=1.345]
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 FOOlel--KkXJ for <mext@ietfa.amsl.com>; Wed, 14 Dec 2011 09:28:08 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 28A351F0C61 for <mext@ietf.org>; Wed, 14 Dec 2011 09:28:08 -0800 (PST)
Received: by pbdd12 with SMTP id d12so1010277pbd.31 for <mext@ietf.org>; Wed, 14 Dec 2011 09:28:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=AuGvrryOPKUiOUUeZiGE8liGNByL+FvF0g07u/GZJLs=; b=RcFQR6hKsu5XyTeqCA7Ldd69OhMU4hAxN13QIC44R/F64Hl4Tunew/KNpO5zBhI349 VEO31d/PKLt/oZgBLxWtEF9DV5TilxKEIbPuimeVkvyyVCTczvvqX8FBEkTmFGZMm932 +qOzOWXNmTuRiJAGcMaYzVd+Ol1pNP5IjhVLc=
MIME-Version: 1.0
Received: by 10.68.74.10 with SMTP id p10mr4583550pbv.3.1323883687817; Wed, 14 Dec 2011 09:28:07 -0800 (PST)
Received: by 10.142.102.10 with HTTP; Wed, 14 Dec 2011 09:28:07 -0800 (PST)
In-Reply-To: <OF4079AAAC.D7E49201-ON48257966.00330B17-48257966.0034287F@zte.com.cn>
References: <8CAD2158-A0AC-4767-9DDC-857536E26DC6@gmail.com> <OF4079AAAC.D7E49201-ON48257966.00330B17-48257966.0034287F@zte.com.cn>
Date: Wed, 14 Dec 2011 09:28:07 -0800
Message-ID: <CAE_dhjuwkPmYfrY+bD7rvUEhsnU6r4vCmgGswoYxansxbwS68w@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: luo.wen@zte.com.cn
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: jouni korhonen <jouni.nospam@gmail.com>, mext@ietf.org
Subject: Re: [MEXT] =?gb2312?b?tPC4tDogIFRoZSBmaXJzdCBwcm9wb3NhbCBmb3IgdGhl?= =?gb2312?b?IERNTSBjaGFydGVy?=
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: Wed, 14 Dec 2011 17:28:08 -0000

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