[nemo] Charter proposal..

"T.J. Kniveton" <tj@kniveton.com> Fri, 03 November 2006 05:47 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gfru6-0006qg-Ss; Fri, 03 Nov 2006 00:47:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gfru6-0006qU-It for nemo@ietf.org; Fri, 03 Nov 2006 00:47:46 -0500
Received: from h-74-0-36-190.snfccasy.covad.net ([74.0.36.190] helo=multihop.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gfru0-0002ME-7e for nemo@ietf.org; Fri, 03 Nov 2006 00:47:44 -0500
Received: by deimos.multihop.net (Postfix, from userid 1013) id EF25C8ABACE; Thu, 2 Nov 2006 21:47:19 -0800 (PST)
X-Spam-Score: -4.2
X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on deimos.multihop.net
X-Spam-Level:
X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.6
Received: from [192.168.4.16] (wideload-eth.tehama.multihop.net [192.168.4.16]) by deimos.multihop.net (Postfix) with ESMTP id DEC7B8AB9A0 for <nemo@ietf.org>; Thu, 2 Nov 2006 21:47:16 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <353E5B3B-6091-423E-B276-CF39F2818E07@kniveton.com>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: ml-nemo WG <nemo@ietf.org>
From: "T.J. Kniveton" <tj@kniveton.com>
Date: Thu, 02 Nov 2006 21:47:15 -0800
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [nemo] Charter proposal..
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 folks,

After the latest discussion on the list, I weighed some of our  
options, and then we had a pow-wow between the NEMO chairs, and the  
Area Director. We've come up with a more tightly-constrained charter,  
with goals that I believe are achievable.

http://www.mobilenetworks.org/nemo/charter2_5.txt

This charter focuses on route optimization for two scenarios:  
automotive and aeronautical. Initially, we will gather the  
requirements into documents, and then work on solutions based on that.

The infrastructure-based / distributed home agent type of solution is  
not spelled out in the charter, because I don't want to bias the type  
of solution we can use. However, based on the documents I've seen  
from Will Ivancic, Terry Davis, and their compatriots, that may be a  
good place to start. We need to refine those documents and their  
input into a good requirements doc. I will work with those groups to  
come up with that document.

The automotive industry working on NEMO solutions is primarily  
located in Japan and Europe. They seem to be in the early stages of  
figuring out how to interact with the IETF, so it may take some extra  
communication with them to be able to import meaningful requirements  
data from them. Thierry will work with those groups on that document.

As was mentioned on the list, it's not my goal to have to change the  
charter document very frequently, since it's a long process. However,  
if we do discover some important deployment scenarios that aren't  
covered under these concrete examples, we can definitely investigate  
updating the charter.

Thanks for your patience and see you all soon in San Diego.

TJ