Re: [nemo] New versions of charter

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Mon, 15 May 2006 21:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffl5F-0005aD-4F; Mon, 15 May 2006 17:58:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffl5D-0005a1-QE for nemo@ietf.org; Mon, 15 May 2006 17:58:31 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffl5D-0007Om-Fj for nemo@ietf.org; Mon, 15 May 2006 17:58:31 -0400
Received: from [10.1.201.8] ([10.1.201.8]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 15 May 2006 14:58:29 -0700
Message-ID: <4468F985.6070108@azairenet.com>
Date: Mon, 15 May 2006 14:58:29 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: "T.J. Kniveton" <tj@kniveton.com>
Subject: Re: [nemo] New versions of charter
References: <EE44BD57-7721-4111-BEAB-837F3D13FDFB@kniveton.com>
In-Reply-To: <EE44BD57-7721-4111-BEAB-837F3D13FDFB@kniveton.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 May 2006 21:58:29.0456 (UTC) FILETIME=[B32CC500:01C6786A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: ml-nemo WG <nemo@ietf.org>
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Errors-To: nemo-bounces@ietf.org

hi TJ,

my understanding was that there will also be a general
purpose route optimization solution. and this solution
would not depend on geographically distributed HAs.
this is not mentioned anywhere in the charter. the
charter only talks about "Analysis of the Solution
Space for Route Optimization".

> The working group has work items to describe a basic solution for
> network mobility in IPv6-only networks, and to design a mechanism to
> allow mixed IPv4/IPv6 networks, carrying signalling messages that
> describe both IPv4 and IPv6 addresses and mobile network prefixes. The
> latter task is shared with the Mobile IPv6 working group, addressed by
> a joint design team.

this is just DS-MIPv6 (with appropriate extensions for
IPv4 mobile network prefixes), right? nothing more.

Vijay

T.J. Kniveton wrote:
> I have posted a new version of the proposed charter (on the web page) to 
> replace the April 30 version. Some of the changes include:
> 
> - Added some text about v6, v4 and v4/v6 solution distinctions.
> - Added some additional text throughout the tasks/nontasks
> - Added editing and typo fixes as suggested
> - Other suggested changes
> 
> One remaining comment which I have not addressed yet:
> 
> James Kempf wrote:
>> I am very much in favor of making WG charters very specific. It helps 
>> to avoid ambiguity about what the WG is intending to accomplish, and 
>> also helps focus the energy of the WG and avoid having it become 
>> distracted by other proposals that tend to pop up, until the 
>> originally promised work is completed. Therefore, I would recommend 
>> that the charter include a bulleted list with three items 
>> corresponding to each of these new drafts, with each item giving a 
>> concise but complete description of what the promised draft is 
>> intended to accomplish. If there are existing individual drafts that 
>> cover these, the descriptions can be based on the individual drafts. 
>> Also, it might be helpful to be more specific about the goals and 
>> their timing. Rather than just a single goal, have a list that 
>> correspond to the process: 00 WG draft selected by this time, WG last 
>> call by this time, submission to IESG by this time.
> 
> (Some help would be appreciated with this one). I think we still have to 
> adjust the milestones a bit more to make sure everything is explicitly 
> spelled out. I have tried to make the charter as concrete as possible, 
> while still short enough to be manageable/readable. I would like the 
> next revision to focus on the milestones.
> 
> Can people please read this over and make comments/suggestions, with 
> proposed text changes? That would be helpful.
> 
> Thanks,
> TJ
> 
>