Re: [nemo] NEMO WG Agenda

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sun, 18 March 2007 13:13 UTC

Return-path: <nemo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSvCv-0007jX-3f; Sun, 18 Mar 2007 09:13:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSvCs-0007hk-Vp for nemo@ietf.org; Sun, 18 Mar 2007 09:13:54 -0400
Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HSvCo-0000jU-Ku for nemo@ietf.org; Sun, 18 Mar 2007 09:13:54 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1174223630!22952193!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 22167 invoked from network); 18 Mar 2007 13:13:50 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-14.tower-119.messagelabs.com with SMTP; 18 Mar 2007 13:13:50 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2IDDjYf009431; Sun, 18 Mar 2007 06:13:49 -0700 (MST)
Received: from [10.129.40.16] ([10.129.40.16]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2IDDhFt020933; Sun, 18 Mar 2007 08:13:44 -0500 (CDT)
Message-ID: <45FD3B07.8080305@gmail.com>
Date: Sun, 18 Mar 2007 14:13:43 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: [nemo] NEMO WG Agenda
References: <20070318015512.1cb8d182.thierry.ernst@inria.fr>
In-Reply-To: <20070318015512.1cb8d182.thierry.ernst@inria.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: ml-nemo <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

Thierry Ernst wrote:
> Dear all,
> 
> Here is the NEMO WG agenda as of today. 
> 
> We have 2 times 1-hour slot. The 1st hour is devoted to WG status
> updates and the use case requirements as required by the new charter
> under set up, whereas the 2nd slot is devoted to the RO issues met in
> the MANEMO context.
> 
> However, note that:
> 1. the session on the Aeronautic use case might be compromised.

That would be a pitty.  RO with non-MIP6 and gentle BGP for in-plane 
prefix.  And we've seen a lot of discussion on multi-homing and how it 
can work.  The aeronautic industry requirements may lead to meaningful 
immediate solutions for the neverending quest of future Internet 
architectures.

> 2. we have not yet collected any input for the Personal Mobile Router
> use case.

In MANEMO space we have a MANEMO Configuration Problems draft that talks 
about PMR use-case and how it can match egress-egress MANEMO scenario. 
It was submitted late, won't show up in I-D Repository during Prague. 
Until then it can be found here:

                     http://tinyurl.com/2z6lnz
(or until it shows on mobileip.jp/MANEMO or on network-mobility.org)

Alex

>  
> 
> NEMO WG meeting Agenda, IETF68 March 18-23 2007 Prague
> Chairs: TJ Kniveton & Thierry Ernst
> 
> ===
> NEMO WG page: http://www.ietf.org/html.charters/nemo-charter.html
> NEMO Additional Page: http://www.mobilenetworks.org/nemo/
> NEMO Status Page: http://tools.ietf.org/wg/nemo/
> ===
> 
> TUESDAY, March 20, 2007 
> 1740-1840 Afternoon Session III & 1850-1950 Afternoon Session IV
> 
> 1740-1840 Afternoon Session III 
> 1. Welcome, agenda bashing ....................................... 05 mins
>    Chairs 
> 
> 2. WG documents status  .......................................... 10 mins
>    Chairs
> 
>    http://tools.ietf.org/wg/nemo/
> 
> 3. WG rechartering status ........................................ 10 mins
>    Chairs
> 
> 4. Aviation Industry Requirements ................................ 15 mins
>    ???? Terry Davis & William Ivancic
> 
>     Multi-Domained, Multi-Homed Mobile Networks
>     http://www.ietf.org/internet-drafts/draft-ivancic-mobile-platforms-problem-00.txt
> 
>     Aviation Global Internet Operations Requirements          
>     http://www.ietf.org/internet-drafts/draft-davis-aviationreq-00.txt
>   
> 5. Automotive Industry Requirements .............................. 20 mins
>    Roberto Baldessari
> 
>    C2C-C Consortium Requirements for Usage of NEMO in VANETs"
>    http://www.ietf.org/internet-drafts/draft-baldessari-c2ccc-nemo-req-00.txt
> 
> 
> 1850-1950 Afternoon Session IV
> 7. NEMO RO Issues & Requirements in the MANEMO Scenario
>    Wakikawa & Thubert & Boot & Clausen
> 
>    Analysis of MANET and NEMO
>    http://www.ietf.org/internet-drafts/draft-boot-manet-nemo-analysis-00.txt
>    
>    MANEMO Problem Statement
>    http://www.ietf.org/internet-drafts/draft-wakikawa-manemo-problem-statement-00.txt
> 
>    NEMO Route Optimisation Problem Statement
>    http://www.ietf.org/internet-drafts/draft-clausen-nemo-ro-problem-statement-01.txt
> 
>    FYI only 
>    ========
>       Solution drafts that might be useful to read
>       -- draft-thubert-tree-discovery-04.txt
>       -- draft-thubert-nemo-reverse-routing-header-07.txt
>       -- draft-thubert-nina-00.txt
>       -- draft-petrescu-manemo-nano-00.txt
> 
>       For more information on MANEMO
>       -- http://www.mobileip.jp/MANEMO/MANEMO.html
>       -- http://www.mobileip.jp/MANEMO/IETF68.html
>    ========
> 
> 
> -- version 2007-03-17
> 
> 
> Thierry.
> 
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________