From mailman-admin@ietf.org  Fri Jan  9 12:56:07 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18411
	for <nemo-archive@lists.ietf.org>; Fri, 9 Jan 2004 12:56:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af0rE-0005i6-Gm
	for nemo-archive@lists.ietf.org; Fri, 09 Jan 2004 12:55:40 -0500
Date: Fri, 09 Jan 2004 12:55:40 -0500
Message-ID: <20040109175540.9164.63273.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: nemo-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, nemo-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for nemo-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
nemo@ietf.org                            koepih    
https://www1.ietf.org/mailman/options/nemo/nemo-archive%40lists.ietf.org


From exim@www1.ietf.org  Fri Jan  9 13:22:48 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21529
	for <nemo-archive@odin.ietf.org>; Fri, 9 Jan 2004 13:22:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af1H3-0000v0-Lh
	for nemo-archive@odin.ietf.org; Fri, 09 Jan 2004 13:22:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i09IMLMR003524
	for nemo-archive@odin.ietf.org; Fri, 9 Jan 2004 13:22:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af1H3-0000ul-Fb
	for nemo-web-archive@optimus.ietf.org; Fri, 09 Jan 2004 13:22:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21352
	for <nemo-web-archive@ietf.org>; Fri, 9 Jan 2004 13:22:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1H1-0007mr-00
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 13:22:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af0tQ-0005Qo-00
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 12:57:57 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af0jr-0003jS-01
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 12:48:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af0jr-0005My-OQ
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 12:48:03 -0500
Date: Fri, 09 Jan 2004 12:48:03 -0500
Message-ID: <20040109174803.9164.67590.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: nemo-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, nemo-request@ietf.org) containing just the word
'help' in the message body, and an email message will be sent to you
with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for nemo-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
nemo@ietf.org                            dawauv    
https://www1.ietf.org/mailman/options/nemo/nemo-web-archive%40ietf.org



From nemo-admin@ietf.org  Fri Jan  9 15:25:43 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09456
	for <nemo-archive@lists.ietf.org>; Fri, 9 Jan 2004 15:25:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3Bp-0004MK-42; Fri, 09 Jan 2004 15:25:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3B2-0004EJ-Hg
	for nemo@optimus.ietf.org; Fri, 09 Jan 2004 15:24:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08553
	for <nemo@ietf.org>; Fri, 9 Jan 2004 15:24:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3B0-0007iO-00
	for nemo@ietf.org; Fri, 09 Jan 2004 15:24:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af2ac-0001gT-00
	for nemo@ietf.org; Fri, 09 Jan 2004 14:46:39 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1rZ-00006A-00
	for nemo@ietf.org; Fri, 09 Jan 2004 14:00:05 -0500
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i09IxtDc003764
	for <nemo@ietf.org>; Fri, 9 Jan 2004 11:59:55 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i09IxiiN006838
	for <nemo@ietf.org>; Fri, 9 Jan 2004 12:59:49 -0600
Received: from motorola.com (test9.crm.mot.com [10.161.201.219])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 6A5EE85272C
	for <nemo@ietf.org>; Fri,  9 Jan 2004 19:59:44 +0100 (CET)
Message-ID: <3FFEFA20.2080601@motorola.com>
Date: Fri, 09 Jan 2004 19:59:44 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nemo@ietf.org
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [nemo] New version of draft on NEMO threats
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi all,

We've just submitted a new version of draft-petrescu-nemo-threats-01.txt 
to the I-D editor and hope it will show on the NEMO WG list soon.  Until 
then one can find it at:

http://www.mobilenetworks.org/nemo/drafts/draft-petrescu-nemo-threats-01.txt

In this new version we have added more detail about the described 
threats (included packet formats and how and what IPsec headers protect) 
all at the same time by narrowing the focus explicitely on the NEMO base 
protocol as it is in draft-ietf-nemo-basic-support-02.txt and avoiding 
as much as possible description of threats of Mobile IPv6 or other 
Internet generic threats.

Seongho Cho provided significant comments that we acknowledge.

We solicit and welcome further comments and discussion on Threats for 
NEMO, thank you,

Alex




From exim@www1.ietf.org  Fri Jan  9 15:37:04 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12549
	for <nemo-archive@odin.ietf.org>; Fri, 9 Jan 2004 15:37:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3Mw-0005Xu-GK
	for nemo-archive@odin.ietf.org; Fri, 09 Jan 2004 15:36:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i09KaYjK021312
	for nemo-archive@odin.ietf.org; Fri, 9 Jan 2004 15:36:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3Mu-0005Xf-U5
	for nemo-web-archive@optimus.ietf.org; Fri, 09 Jan 2004 15:36:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12234
	for <nemo-web-archive@ietf.org>; Fri, 9 Jan 2004 15:36:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3Mt-0002wG-00
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 15:36:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af3Il-0001kx-00
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 15:32:18 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3Bx-0000Gx-00
	for nemo-web-archive@ietf.org; Fri, 09 Jan 2004 15:25:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3Bp-0004MK-42; Fri, 09 Jan 2004 15:25:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Af3B2-0004EJ-Hg
	for nemo@optimus.ietf.org; Fri, 09 Jan 2004 15:24:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08553
	for <nemo@ietf.org>; Fri, 9 Jan 2004 15:24:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af3B0-0007iO-00
	for nemo@ietf.org; Fri, 09 Jan 2004 15:24:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Af2ac-0001gT-00
	for nemo@ietf.org; Fri, 09 Jan 2004 14:46:39 -0500
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Af1rZ-00006A-00
	for nemo@ietf.org; Fri, 09 Jan 2004 14:00:05 -0500
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate8.mot.com (Motorola/Motgate3) with ESMTP id i09IxtDc003764
	for <nemo@ietf.org>; Fri, 9 Jan 2004 11:59:55 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id i09IxiiN006838
	for <nemo@ietf.org>; Fri, 9 Jan 2004 12:59:49 -0600
Received: from motorola.com (test9.crm.mot.com [10.161.201.219])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 6A5EE85272C
	for <nemo@ietf.org>; Fri,  9 Jan 2004 19:59:44 +0100 (CET)
Message-ID: <3FFEFA20.2080601@motorola.com>
Date: Fri, 09 Jan 2004 19:59:44 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: nemo@ietf.org
X-Enigmail-Version: 0.72.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [nemo] New version of draft on NEMO threats
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,

We've just submitted a new version of draft-petrescu-nemo-threats-01.txt 
to the I-D editor and hope it will show on the NEMO WG list soon.  Until 
then one can find it at:

http://www.mobilenetworks.org/nemo/drafts/draft-petrescu-nemo-threats-01.txt

In this new version we have added more detail about the described 
threats (included packet formats and how and what IPsec headers protect) 
all at the same time by narrowing the focus explicitely on the NEMO base 
protocol as it is in draft-ietf-nemo-basic-support-02.txt and avoiding 
as much as possible description of threats of Mobile IPv6 or other 
Internet generic threats.

Seongho Cho provided significant comments that we acknowledge.

We solicit and welcome further comments and discussion on Threats for 
NEMO, thank you,

Alex





From nemo-admin@ietf.org  Tue Jan 13 09:46:34 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14708
	for <nemo-archive@lists.ietf.org>; Tue, 13 Jan 2004 09:46:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPnt-0007vI-8s; Tue, 13 Jan 2004 09:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPmx-0007jC-98
	for nemo@optimus.ietf.org; Tue, 13 Jan 2004 09:45:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14577
	for <nemo@ietf.org>; Tue, 13 Jan 2004 09:45:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPmj-0002Od-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:44:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPkv-0002Hz-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:42:58 -0500
Received: from roura.ac.upc.es ([147.83.33.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPjz-0002B7-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:41:59 -0500
Received: from rogent.ac.upc.es (rogent.ac.upc.es [147.83.31.7])
	by roura.ac.upc.es (8.12.8/8.12.8) with ESMTP id i0DEfR7J019237
	for <nemo@ietf.org>; Tue, 13 Jan 2004 15:41:27 +0100 (MET)
Received: (from ew2004@localhost)
	by rogent.ac.upc.es (8.12.8/8.12.8) id i0DEfQ5L006858
	for nemo@ietf.org; Tue, 13 Jan 2004 15:41:26 +0100 (MET)
Date: Tue, 13 Jan 2004 15:41:26 +0100
From: Conferencia ew2004 <ew2004@ac.upc.es>
To: nemo@ietf.org
Message-ID: <20040113144126.GA6850@ac.upc.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=FROM_ENDS_IN_NUMS autolearn=no 
	version=2.60
Subject: [nemo] EW2004 Call For Participation
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>

Dear Colleague,

Please accept our apologies if you receive multiple copies of this
e-mail.

You are cordially invited to attend The 5th European Wireless
Conference (EW2004) Mobile and Wireless Systems beyond 3G to be held in
Barcelona, Spain in February 24-27, 2004.

All the details about the conference can be found at:
http://www.ac.upc.es/EW2004

(look at links: "Conference Program", "Tutorials"
and "Conference and tutorial Registration")

Looking forward to see you in Barcelona,
	EW2004 organizing committee.



From exim@www1.ietf.org  Tue Jan 13 09:51:01 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15066
	for <nemo-archive@odin.ietf.org>; Tue, 13 Jan 2004 09:51:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPsH-0008Lx-7p
	for nemo-archive@odin.ietf.org; Tue, 13 Jan 2004 09:50:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DEoXKN032103
	for nemo-archive@odin.ietf.org; Tue, 13 Jan 2004 09:50:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPsH-0008Li-2e
	for nemo-web-archive@optimus.ietf.org; Tue, 13 Jan 2004 09:50:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14994
	for <nemo-web-archive@ietf.org>; Tue, 13 Jan 2004 09:50:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPsF-00036X-00
	for nemo-web-archive@ietf.org; Tue, 13 Jan 2004 09:50:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPpy-0002ky-00
	for nemo-web-archive@ietf.org; Tue, 13 Jan 2004 09:48:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPny-0002SJ-00
	for nemo-web-archive@ietf.org; Tue, 13 Jan 2004 09:46:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPnt-0007vI-8s; Tue, 13 Jan 2004 09:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AgPmx-0007jC-98
	for nemo@optimus.ietf.org; Tue, 13 Jan 2004 09:45:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14577
	for <nemo@ietf.org>; Tue, 13 Jan 2004 09:45:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPmj-0002Od-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:44:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AgPkv-0002Hz-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:42:58 -0500
Received: from roura.ac.upc.es ([147.83.33.10])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AgPjz-0002B7-00
	for nemo@ietf.org; Tue, 13 Jan 2004 09:41:59 -0500
Received: from rogent.ac.upc.es (rogent.ac.upc.es [147.83.31.7])
	by roura.ac.upc.es (8.12.8/8.12.8) with ESMTP id i0DEfR7J019237
	for <nemo@ietf.org>; Tue, 13 Jan 2004 15:41:27 +0100 (MET)
Received: (from ew2004@localhost)
	by rogent.ac.upc.es (8.12.8/8.12.8) id i0DEfQ5L006858
	for nemo@ietf.org; Tue, 13 Jan 2004 15:41:26 +0100 (MET)
Date: Tue, 13 Jan 2004 15:41:26 +0100
From: Conferencia ew2004 <ew2004@ac.upc.es>
To: nemo@ietf.org
Message-ID: <20040113144126.GA6850@ac.upc.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: [nemo] EW2004 Call For Participation
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS 
	autolearn=no version=2.60

Dear Colleague,

Please accept our apologies if you receive multiple copies of this
e-mail.

You are cordially invited to attend The 5th European Wireless
Conference (EW2004) Mobile and Wireless Systems beyond 3G to be held in
Barcelona, Spain in February 24-27, 2004.

All the details about the conference can be found at:
http://www.ac.upc.es/EW2004

(look at links: "Conference Program", "Tutorials"
and "Conference and tutorial Registration")

Looking forward to see you in Barcelona,
	EW2004 organizing committee.




From nemo-admin@ietf.org  Thu Jan 15 20:53:51 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13094
	for <nemo-archive@lists.ietf.org>; Thu, 15 Jan 2004 20:53:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJ9U-0001tN-JA; Thu, 15 Jan 2004 20:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJ8j-0001sD-Rd
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 20:51:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13025
	for <nemo@ietf.org>; Thu, 15 Jan 2004 20:51:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJ8h-0003Ib-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:51:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhJ7f-0003Fl-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:50:08 -0500
Received: from [202.20.142.13] (helo=ns.sait.samsung.co.kr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJ74-0003BX-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:49:30 -0500
Received: from ns.sait.samsung.co.kr (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id DAA7F1F36F; Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP;
      Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Received: from LocalHost (unknown [75.2.47.234])
	by ns.sait.samsung.co.kr (Postfix) with ESMTP
	id:254F21F347; Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Reply-To: <jhch@sait.samsung.co.kr>
From: "Jung-Hoon Cheon" <jhch@sait.samsung.co.kr>
To: <nemo@ietf.org>
Cc: <hscho@mmlab.snu.ac.kr>, <eun@mmlab.snu.ac.kr>
Date: Fri, 16 Jan 2004 10:48:56 +0900
Organization: Samsung AIT
Message-ID: <000001c3dbd2$e76e81a0$ea2f024b@LocalHost>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200401152109.QAA28426@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network.
The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.





From exim@www1.ietf.org  Thu Jan 15 20:54:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13119
	for <nemo-archive@odin.ietf.org>; Thu, 15 Jan 2004 20:54:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJBJ-0001zm-9p
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 20:53:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G1rrqP007666
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 20:53:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJBJ-0001zZ-60
	for nemo-web-archive@optimus.ietf.org; Thu, 15 Jan 2004 20:53:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13092
	for <nemo-web-archive@ietf.org>; Thu, 15 Jan 2004 20:53:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJBG-0003PS-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 20:53:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhJAN-0003Nv-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 20:52:55 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJ9Z-0003M3-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 20:52:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJ9U-0001tN-JA; Thu, 15 Jan 2004 20:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhJ8j-0001sD-Rd
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 20:51:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13025
	for <nemo@ietf.org>; Thu, 15 Jan 2004 20:51:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJ8h-0003Ib-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:51:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhJ7f-0003Fl-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:50:08 -0500
Received: from [202.20.142.13] (helo=ns.sait.samsung.co.kr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhJ74-0003BX-00
	for nemo@ietf.org; Thu, 15 Jan 2004 20:49:30 -0500
Received: from ns.sait.samsung.co.kr (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id DAA7F1F36F; Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP;
      Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Received: from LocalHost (unknown [75.2.47.234])
	by ns.sait.samsung.co.kr (Postfix) with ESMTP
	id:254F21F347; Fri, 16 Jan 2004 10:48:56 +0900 (KST)
Reply-To: <jhch@sait.samsung.co.kr>
From: "Jung-Hoon Cheon" <jhch@sait.samsung.co.kr>
To: <nemo@ietf.org>
Cc: <hscho@mmlab.snu.ac.kr>, <eun@mmlab.snu.ac.kr>
Date: Fri, 16 Jan 2004 10:48:56 +0900
Organization: Samsung AIT
Message-ID: <000001c3dbd2$e76e81a0$ea2f024b@LocalHost>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200401152109.QAA28426@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network.
The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.






From nemo-admin@ietf.org  Thu Jan 15 22:14:31 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14816
	for <nemo-archive@lists.ietf.org>; Thu, 15 Jan 2004 22:14:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKQr-0005Lz-Oq; Thu, 15 Jan 2004 22:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKQn-0005Lb-Fe
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 22:13:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14813
	for <nemo@ietf.org>; Thu, 15 Jan 2004 22:13:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKQk-0006DT-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:13:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhKPo-0006Bz-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:12:57 -0500
Received: from mmlab.snu.ac.kr ([147.46.114.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKPV-0006AN-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:12:38 -0500
Received: from cydream (bijou.snu.ac.kr [147.46.114.131])
	by mmlab.snu.ac.kr (8.11.6/8.11.6) with ESMTP id i0G3Caw21445;
	Fri, 16 Jan 2004 12:12:36 +0900 (KST)
	(envelope-from hscho@mmlab.snu.ac.kr)
Message-Id: <200401160312.i0G3Caw21445@mmlab.snu.ac.kr>
From: "Hosik Cho" <hscho@mmlab.snu.ac.kr>
To: <jhch@sait.samsung.co.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Date: Fri, 16 Jan 2004 12:12:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPb0up6W2edmFWdSbSYwZ8o64jymAAAIW/A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <000001c3dbd2$e76e81a0$ea2f024b@LocalHost>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age.
(In our draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we need.)

The age of each child MR is re-calculated when if receives a RA message from
its parent MR. If the received age, i.e. the parent MR's age, is bigger than
its age, the child MR re-assigns its age to (received age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network.
The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.






From exim@www1.ietf.org  Thu Jan 15 22:16:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14875
	for <nemo-archive@odin.ietf.org>; Thu, 15 Jan 2004 22:16:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKSh-0005TD-Fb
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 22:15:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G3Ftm5021021
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 22:15:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKSh-0005Sy-Bh
	for nemo-web-archive@optimus.ietf.org; Thu, 15 Jan 2004 22:15:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14864
	for <nemo-web-archive@ietf.org>; Thu, 15 Jan 2004 22:15:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKSe-0006IP-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:15:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhKRl-0006GX-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:14:57 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKQr-0006ER-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:14:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKQr-0005Lz-Oq; Thu, 15 Jan 2004 22:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhKQn-0005Lb-Fe
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 22:13:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14813
	for <nemo@ietf.org>; Thu, 15 Jan 2004 22:13:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKQk-0006DT-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:13:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhKPo-0006Bz-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:12:57 -0500
Received: from mmlab.snu.ac.kr ([147.46.114.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhKPV-0006AN-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:12:38 -0500
Received: from cydream (bijou.snu.ac.kr [147.46.114.131])
	by mmlab.snu.ac.kr (8.11.6/8.11.6) with ESMTP id i0G3Caw21445;
	Fri, 16 Jan 2004 12:12:36 +0900 (KST)
	(envelope-from hscho@mmlab.snu.ac.kr)
Message-Id: <200401160312.i0G3Caw21445@mmlab.snu.ac.kr>
From: "Hosik Cho" <hscho@mmlab.snu.ac.kr>
To: <jhch@sait.samsung.co.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Date: Fri, 16 Jan 2004 12:12:46 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPb0up6W2edmFWdSbSYwZ8o64jymAAAIW/A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <000001c3dbd2$e76e81a0$ea2f024b@LocalHost>
Content-Transfer-Encoding: 7bit
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age.
(In our draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we need.)

The age of each child MR is re-calculated when if receives a RA message from
its parent MR. If the received age, i.e. the parent MR's age, is bigger than
its age, the child MR re-assigns its age to (received age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network.
The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.







From nemo-admin@ietf.org  Thu Jan 15 22:57:42 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15613
	for <nemo-archive@lists.ietf.org>; Thu, 15 Jan 2004 22:57:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL6S-0006t4-Pq; Thu, 15 Jan 2004 22:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL5e-0006sQ-HH
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 22:56:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15595
	for <nemo@ietf.org>; Thu, 15 Jan 2004 22:56:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL5O-0007YI-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:55:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhL4V-0007X0-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:55:00 -0500
Received: from [202.20.142.13] (helo=ns.sait.samsung.co.kr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL3j-0007ST-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:54:11 -0500
Received: from ns.sait.samsung.co.kr (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 9821F1F35F; Fri, 16 Jan 2004 12:53:39 +0900 (KST)
Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP;
      Fri, 16 Jan 2004 12:53:39 +0900 (KST)
Received: from LocalHost (unknown [75.2.47.234])
	by ns.sait.samsung.co.kr (Postfix) with ESMTP
	id:CE7191F381; Fri, 16 Jan 2004 12:53:38 +0900 (KST)
Reply-To: <jhch@sait.samsung.co.kr>
From: "Jung-Hoon Cheon" <jhch@sait.samsung.co.kr>
To: "'Hosik Cho'" <hscho@mmlab.snu.ac.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Date: Fri, 16 Jan 2004 12:53:39 +0900
Organization: Samsung AIT
Message-ID: <000201c3dbe4$537f8b80$ea2f024b@LocalHost>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <200401160312.i0G3Caw21445@mmlab.snu.ac.kr>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi. Hosik and all,

If MR2 and MR3 arrive at foreign network almost simultaneously

and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
before sending RA message, 

at this time, how can the MR2 determine MR1 with its parent MR?

  AR
   |
 MR1
   |
 MR2
   |
 MR3

As my understanding, every MR update its position according to other
MR's age, 
whenever receiving RA message.

It's not easy to solve this problem.

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Hosik Cho
Sent: Friday, January 16, 2004 12:13 PM
To: jhch@sait.samsung.co.kr
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt


Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know 
> its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age. (In our
draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we
need.)

The age of each child MR is re-calculated when if receives a RA message
from its parent MR. If the received age, i.e. the parent MR's age, is
bigger than its age, the child MR re-assigns its age to (received
age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network. The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.










From exim@www1.ietf.org  Thu Jan 15 22:59:22 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15656
	for <nemo-archive@odin.ietf.org>; Thu, 15 Jan 2004 22:59:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL8J-00070C-NT
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 22:58:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G3wtOP026910
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 22:58:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL8J-0006zx-Hk
	for nemo-web-archive@optimus.ietf.org; Thu, 15 Jan 2004 22:58:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15652
	for <nemo-web-archive@ietf.org>; Thu, 15 Jan 2004 22:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL8G-0007dk-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:58:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhL7L-0007cO-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:57:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL6e-0007b2-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 22:57:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL6S-0006t4-Pq; Thu, 15 Jan 2004 22:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhL5e-0006sQ-HH
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 22:56:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15595
	for <nemo@ietf.org>; Thu, 15 Jan 2004 22:56:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL5O-0007YI-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:55:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhL4V-0007X0-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:55:00 -0500
Received: from [202.20.142.13] (helo=ns.sait.samsung.co.kr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhL3j-0007ST-00
	for nemo@ietf.org; Thu, 15 Jan 2004 22:54:11 -0500
Received: from ns.sait.samsung.co.kr (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 9821F1F35F; Fri, 16 Jan 2004 12:53:39 +0900 (KST)
Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP;
      Fri, 16 Jan 2004 12:53:39 +0900 (KST)
Received: from LocalHost (unknown [75.2.47.234])
	by ns.sait.samsung.co.kr (Postfix) with ESMTP
	id:CE7191F381; Fri, 16 Jan 2004 12:53:38 +0900 (KST)
Reply-To: <jhch@sait.samsung.co.kr>
From: "Jung-Hoon Cheon" <jhch@sait.samsung.co.kr>
To: "'Hosik Cho'" <hscho@mmlab.snu.ac.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Date: Fri, 16 Jan 2004 12:53:39 +0900
Organization: Samsung AIT
Message-ID: <000201c3dbe4$537f8b80$ea2f024b@LocalHost>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <200401160312.i0G3Caw21445@mmlab.snu.ac.kr>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi. Hosik and all,

If MR2 and MR3 arrive at foreign network almost simultaneously

and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
before sending RA message, 

at this time, how can the MR2 determine MR1 with its parent MR?

  AR
   |
 MR1
   |
 MR2
   |
 MR3

As my understanding, every MR update its position according to other
MR's age, 
whenever receiving RA message.

It's not easy to solve this problem.

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Hosik Cho
Sent: Friday, January 16, 2004 12:13 PM
To: jhch@sait.samsung.co.kr
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt


Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know 
> its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age. (In our
draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we
need.)

The age of each child MR is re-calculated when if receives a RA message
from its parent MR. If the received age, i.e. the parent MR's age, is
bigger than its age, the child MR re-assigns its age to (received
age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network. The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.











From nemo-admin@ietf.org  Thu Jan 15 23:32:32 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16331
	for <nemo-archive@lists.ietf.org>; Thu, 15 Jan 2004 23:32:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLeM-0008I4-2m; Thu, 15 Jan 2004 23:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLeL-0008Hq-B5
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 23:32:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16312
	for <nemo@ietf.org>; Thu, 15 Jan 2004 23:31:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLeJ-0000u8-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:31:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhLdJ-0000rv-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:30:58 -0500
Received: from mmlab.snu.ac.kr ([147.46.114.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLck-0000qM-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:30:22 -0500
Received: from cydream (bijou.snu.ac.kr [147.46.114.131])
	by mmlab.snu.ac.kr (8.11.6/8.11.6) with ESMTP id i0G4UKw22924;
	Fri, 16 Jan 2004 13:30:20 +0900 (KST)
	(envelope-from hscho@mmlab.snu.ac.kr)
Message-Id: <200401160430.i0G4UKw22924@mmlab.snu.ac.kr>
From: "Hosik Cho" <hscho@mmlab.snu.ac.kr>
To: <jhch@sait.samsung.co.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Date: Fri, 16 Jan 2004 13:30:31 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPb5Nw1EJg3LOAUQru2GD2pIW63XQAAfMFw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <000201c3dbe4$537f8b80$ea2f024b@LocalHost>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi Jung-Hoon,

> If MR2 and MR3 arrive at foreign network almost simultaneously
> and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
> before sending RA message, at this time, how can the MR2 determine MR1
with its parent MR?

Only access routers can have the maximum age 7.

When MR2 and MR3 enter into the network, the ages of MR are initially zero.
And MR2 can receive two RAs from MR1(age=6) and MR3(age=0).
So MR2(age=0) accepts the RA from MR1(age=6) and sets its age to 5.

Regards,
Hosik

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Jung-Hoon Cheon
Sent: Friday, January 16, 2004 12:54 PM
To: 'Hosik Cho'
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi. Hosik and all,

If MR2 and MR3 arrive at foreign network almost simultaneously

and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
before sending RA message, 

at this time, how can the MR2 determine MR1 with its parent MR?

  AR
   |
 MR1
   |
 MR2
   |
 MR3

As my understanding, every MR update its position according to other
MR's age, 
whenever receiving RA message.

It's not easy to solve this problem.

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Hosik Cho
Sent: Friday, January 16, 2004 12:13 PM
To: jhch@sait.samsung.co.kr
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt


Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know 
> its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age. (In our
draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we
need.)

The age of each child MR is re-calculated when if receives a RA message
from its parent MR. If the received age, i.e. the parent MR's age, is
bigger than its age, the child MR re-assigns its age to (received
age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network. The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.












From exim@www1.ietf.org  Thu Jan 15 23:34:24 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16363
	for <nemo-archive@odin.ietf.org>; Thu, 15 Jan 2004 23:34:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLgC-0008Ny-Ds
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 23:33:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G4Xue4032230
	for nemo-archive@odin.ietf.org; Thu, 15 Jan 2004 23:33:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLgC-0008Nl-9O
	for nemo-web-archive@optimus.ietf.org; Thu, 15 Jan 2004 23:33:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16353
	for <nemo-web-archive@ietf.org>; Thu, 15 Jan 2004 23:33:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLgA-0000xq-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 23:33:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhLfB-0000w6-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 23:32:54 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLeN-0000ug-00
	for nemo-web-archive@ietf.org; Thu, 15 Jan 2004 23:32:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLeM-0008I4-2m; Thu, 15 Jan 2004 23:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhLeL-0008Hq-B5
	for nemo@optimus.ietf.org; Thu, 15 Jan 2004 23:32:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16312
	for <nemo@ietf.org>; Thu, 15 Jan 2004 23:31:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLeJ-0000u8-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:31:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhLdJ-0000rv-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:30:58 -0500
Received: from mmlab.snu.ac.kr ([147.46.114.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhLck-0000qM-00
	for nemo@ietf.org; Thu, 15 Jan 2004 23:30:22 -0500
Received: from cydream (bijou.snu.ac.kr [147.46.114.131])
	by mmlab.snu.ac.kr (8.11.6/8.11.6) with ESMTP id i0G4UKw22924;
	Fri, 16 Jan 2004 13:30:20 +0900 (KST)
	(envelope-from hscho@mmlab.snu.ac.kr)
Message-Id: <200401160430.i0G4UKw22924@mmlab.snu.ac.kr>
From: "Hosik Cho" <hscho@mmlab.snu.ac.kr>
To: <jhch@sait.samsung.co.kr>
Cc: <eun@mmlab.snu.ac.kr>, <nemo@ietf.org>
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt
Date: Fri, 16 Jan 2004 13:30:31 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPb5Nw1EJg3LOAUQru2GD2pIW63XQAAfMFw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <000201c3dbe4$537f8b80$ea2f024b@LocalHost>
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Jung-Hoon,

> If MR2 and MR3 arrive at foreign network almost simultaneously
> and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
> before sending RA message, at this time, how can the MR2 determine MR1
with its parent MR?

Only access routers can have the maximum age 7.

When MR2 and MR3 enter into the network, the ages of MR are initially zero.
And MR2 can receive two RAs from MR1(age=6) and MR3(age=0).
So MR2(age=0) accepts the RA from MR1(age=6) and sets its age to 5.

Regards,
Hosik

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Jung-Hoon Cheon
Sent: Friday, January 16, 2004 12:54 PM
To: 'Hosik Cho'
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: RE: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi. Hosik and all,

If MR2 and MR3 arrive at foreign network almost simultaneously

and MR2 receives two RA message from the both MR1(age=6) and MR3(age=7)
before sending RA message, 

at this time, how can the MR2 determine MR1 with its parent MR?

  AR
   |
 MR1
   |
 MR2
   |
 MR3

As my understanding, every MR update its position according to other
MR's age, 
whenever receiving RA message.

It's not easy to solve this problem.

-----Original Message-----
From: nemo-admin@ietf.org [mailto:nemo-admin@ietf.org] On Behalf Of
Hosik Cho
Sent: Friday, January 16, 2004 12:13 PM
To: jhch@sait.samsung.co.kr
Cc: eun@mmlab.snu.ac.kr; nemo@ietf.org
Subject: [nemo] RE: I-D ACTION:draft-cho-nemo-hmra-00.txt


Hi Jung-Hoon,

Thank you for your interest in our draft.

> How can MR know its age?
> I think that before comparing its age with other age, MR should know 
> its
age.

Every mobile router has the initial value of zero.
Every access router has the initial value of the maximum age. (In our
draft, the field size for AGE is three bits, so the maximum age is
defined 7. But this value of maximum age may be extended later, if we
need.)

The age of each child MR is re-calculated when if receives a RA message
from its parent MR. If the received age, i.e. the parent MR's age, is
bigger than its age, the child MR re-assigns its age to (received
age)-1.

Regards,
Hosik


-----Original Message-----
From: Jung-Hoon Cheon [mailto:jhch@sait.samsung.co.kr] 
Sent: Friday, January 16, 2004 10:49 AM
To: nemo@ietf.org
Cc: hscho@mmlab.snu.ac.kr; eun@mmlab.snu.ac.kr
Subject: RE: I-D ACTION:draft-cho-nemo-hmra-00.txt

Hi...Hosik and Eunkyung.

your solution is very applicable for nested networks.
if MRs know their correct age, MRs can manage a hierarchy within overall
mobile network. The MR sends a RA message including its age. 
Also,  knows its current position from received RA message.

I have a question.
How can MR know its age?
I think that before comparing its age with other age, MR should know its
age.

Sincerely.

Jung-Hoon

-----Original Message-----
From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org]
On Behalf Of Internet-Drafts@ietf.org
Sent: Friday, January 16, 2004 6:10 AM
To: IETF-Announce:
Subject: I-D ACTION:draft-cho-nemo-hmra-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Hierarchical Mobile Router Advertisement for
nested mobile networks
	Author(s)	: H. Cho
	Filename	: draft-cho-nemo-hmra-00.txt
	Pages		: 7
	Date		: 2004-1-15
	
This document describes needs for hierarchical mobile router
     advertisement for nested mobile networks. When ingress and egress
     interfaces of a Mobile Router are both wireless, the MR cannot
     distinguish the Router Advertisement of the parent MR from the RA
     of the child MR. To maintain hierarchical information of wireless
     nested mobile networks, RA message needs to be extended to deliver
     additional information for hierarchy.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-cho-nemo-hmra-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the
message.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
	"get draft-cho-nemo-hmra-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-cho-nemo-hmra-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.













From nemo-admin@ietf.org  Mon Jan 19 08:24:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15724
	for <nemo-archive@lists.ietf.org>; Mon, 19 Jan 2004 08:24:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiZNr-00011T-Dg; Mon, 19 Jan 2004 08:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiYTJ-000746-Nf
	for nemo@optimus.ietf.org; Mon, 19 Jan 2004 07:25:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14161
	for <nemo@ietf.org>; Mon, 19 Jan 2004 07:25:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYTE-0000u1-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:25:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiYR0-0000kA-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:23:15 -0500
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYNa-0000WY-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:19:42 -0500
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 19 Jan 2004 13:19:30 +0100
Received: from xbe-lon-312.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id i0JCIPYU015821
	for <nemo@ietf.org>; Mon, 19 Jan 2004 13:18:25 +0100 (MET)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 19 Jan 2004 12:18:45 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 12:18:43 -0000
Message-ID: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
Thread-Topic: Make  usages draft a WG DOC
Thread-Index: AcPehZ0UPAO79hMfTxasqZEZQEZ/kw==
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: <nemo@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 12:18:45.0156 (UTC) FILETIME=[623B8E40:01C3DE86]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [nemo] Make  usages draft a WG DOC
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Hi;

During last meeting, we voted that the usages document should be a WG
document but needed more work and maybe more content. An advice was
voiced that since at the moment the draft is about the organization of
the home network, it should be renamed (which it will be anyway as a WG
doc).=20

So I'm posting this to ask you all to discuss areas where revisions and
additions are needed. It's time to discuss this now if we want the
modifications ready by IETF deadline. Ideas?

Pascal




From exim@www1.ietf.org  Mon Jan 19 08:33:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16097
	for <nemo-archive@odin.ietf.org>; Mon, 19 Jan 2004 08:33:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiZWd-0001oj-Te
	for nemo-archive@odin.ietf.org; Mon, 19 Jan 2004 08:33:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0JDX75P006985
	for nemo-archive@odin.ietf.org; Mon, 19 Jan 2004 08:33:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiZWd-0001oa-Pc
	for nemo-web-archive@optimus.ietf.org; Mon, 19 Jan 2004 08:33:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16054
	for <nemo-web-archive@ietf.org>; Mon, 19 Jan 2004 08:33:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiZWX-0004C2-00
	for nemo-web-archive@ietf.org; Mon, 19 Jan 2004 08:33:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiZQz-0003xW-00
	for nemo-web-archive@ietf.org; Mon, 19 Jan 2004 08:27:19 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiZP2-0003m3-00
	for nemo-web-archive@ietf.org; Mon, 19 Jan 2004 08:25:16 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AiZOd-0007eX-PP
	for nemo-web-archive@ietf.org; Mon, 19 Jan 2004 08:24:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiZNr-00011T-Dg; Mon, 19 Jan 2004 08:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AiYTJ-000746-Nf
	for nemo@optimus.ietf.org; Mon, 19 Jan 2004 07:25:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14161
	for <nemo@ietf.org>; Mon, 19 Jan 2004 07:25:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYTE-0000u1-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:25:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AiYR0-0000kA-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:23:15 -0500
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AiYNa-0000WY-00
	for nemo@ietf.org; Mon, 19 Jan 2004 07:19:42 -0500
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 19 Jan 2004 13:19:30 +0100
Received: from xbe-lon-312.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id i0JCIPYU015821
	for <nemo@ietf.org>; Mon, 19 Jan 2004 13:18:25 +0100 (MET)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 19 Jan 2004 12:18:45 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Jan 2004 12:18:43 -0000
Message-ID: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
Thread-Topic: Make  usages draft a WG DOC
Thread-Index: AcPehZ0UPAO79hMfTxasqZEZQEZ/kw==
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: <nemo@ietf.org>
X-OriginalArrivalTime: 19 Jan 2004 12:18:45.0156 (UTC) FILETIME=[623B8E40:01C3DE86]
Content-Transfer-Encoding: quoted-printable
Subject: [nemo] Make  usages draft a WG DOC
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi;

During last meeting, we voted that the usages document should be a WG
document but needed more work and maybe more content. An advice was
voiced that since at the moment the draft is about the organization of
the home network, it should be renamed (which it will be anyway as a WG
doc).=20

So I'm posting this to ask you all to discuss areas where revisions and
additions are needed. It's time to discuss this now if we want the
modifications ready by IETF deadline. Ideas?

Pascal





From nemo-admin@ietf.org  Thu Jan 22 21:55:36 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26038
	for <nemo-archive@lists.ietf.org>; Thu, 22 Jan 2004 21:55:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrTK-0008Hu-T8; Thu, 22 Jan 2004 21:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrSa-0008HO-4C
	for nemo@optimus.ietf.org; Thu, 22 Jan 2004 21:54:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26000
	for <nemo@ietf.org>; Thu, 22 Jan 2004 21:54:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrSX-0006MK-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:54:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjrRZ-0006KA-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:53:14 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrQd-0006H0-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:52:15 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0N2pb925067;
	Thu, 22 Jan 2004 18:51:37 -0800
X-mProtect: <200401230251> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdnMVacc; Thu, 22 Jan 2004 18:32:59 PST
Message-ID: <40108A15.4080102@iprg.nokia.com>
Date: Thu, 22 Jan 2004 18:42:29 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: nemo@ietf.org
Subject: Re: [nemo] Make  usages draft a WG DOC
References: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
In-Reply-To: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
Content-Transfer-Encoding: 7bit

hi Pascal,

> So I'm posting this to ask you all to discuss areas where revisions and
> additions are needed. It's time to discuss this now if we want the
> modifications ready by IETF deadline. Ideas?

I would like to see the draft quite restrictive in scope.
it should talk about the different ways in which a home
link can be configured to support mobile routers. the home
link configuration has an impact on the mobile router
behavior (for example, the returning home procedure is
different for each case).

Vijay




From exim@www1.ietf.org  Thu Jan 22 21:56:47 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26074
	for <nemo-archive@odin.ietf.org>; Thu, 22 Jan 2004 21:56:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrUY-0008Nf-5j
	for nemo-archive@odin.ietf.org; Thu, 22 Jan 2004 21:56:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0N2uI4r032209
	for nemo-archive@odin.ietf.org; Thu, 22 Jan 2004 21:56:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrUY-0008NQ-0V
	for nemo-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 21:56:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26069
	for <nemo-web-archive@ietf.org>; Thu, 22 Jan 2004 21:56:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrUV-0006P3-00
	for nemo-web-archive@ietf.org; Thu, 22 Jan 2004 21:56:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjrTY-0006OF-00
	for nemo-web-archive@ietf.org; Thu, 22 Jan 2004 21:55:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrTP-0006NT-00
	for nemo-web-archive@ietf.org; Thu, 22 Jan 2004 21:55:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrTK-0008Hu-T8; Thu, 22 Jan 2004 21:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AjrSa-0008HO-4C
	for nemo@optimus.ietf.org; Thu, 22 Jan 2004 21:54:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26000
	for <nemo@ietf.org>; Thu, 22 Jan 2004 21:54:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrSX-0006MK-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:54:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AjrRZ-0006KA-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:53:14 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AjrQd-0006H0-00
	for nemo@ietf.org; Thu, 22 Jan 2004 21:52:15 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0N2pb925067;
	Thu, 22 Jan 2004 18:51:37 -0800
X-mProtect: <200401230251> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdnMVacc; Thu, 22 Jan 2004 18:32:59 PST
Message-ID: <40108A15.4080102@iprg.nokia.com>
Date: Thu, 22 Jan 2004 18:42:29 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
CC: nemo@ietf.org
Subject: Re: [nemo] Make  usages draft a WG DOC
References: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
In-Reply-To: <AC60B39EEE7320498063D37799FB82D9030484D7@xbe-lon-313.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

hi Pascal,

> So I'm posting this to ask you all to discuss areas where revisions and
> additions are needed. It's time to discuss this now if we want the
> modifications ready by IETF deadline. Ideas?

I would like to see the draft quite restrictive in scope.
it should talk about the different ways in which a home
link can be configured to support mobile routers. the home
link configuration has an impact on the mobile router
behavior (for example, the returning home procedure is
different for each case).

Vijay





From nemo-admin@ietf.org  Tue Jan 27 19:06:53 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02224
	for <nemo-archive@lists.ietf.org>; Tue, 27 Jan 2004 19:06:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AldCE-0007wu-1j; Tue, 27 Jan 2004 19:04:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlAt7-0005f5-0l
	for nemo@optimus.ietf.org; Mon, 26 Jan 2004 12:51:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14256
	for <nemo@ietf.org>; Mon, 26 Jan 2004 12:51:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlAt5-00032L-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:51:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlAs8-0002z4-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:50:05 -0500
Received: from postoffice8.mail.cornell.edu ([132.236.56.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlArJ-0002wk-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:49:14 -0500
Received: from Panacea_2.cornell.edu (dhcp-128-84-210-142-r3a-desktop.ece.cornell.edu [128.84.210.142])
	by postoffice8.mail.cornell.edu (8.12.10/8.12.6) with ESMTP id i0QHnCj9002947;
	Mon, 26 Jan 2004 12:49:12 -0500 (EST)
Message-Id: <5.2.1.1.2.20040126124541.027bade0@postoffice7.mail.cornell.edu>
X-Sender: pp59@postoffice7.mail.cornell.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 26 Jan 2004 12:49:08 -0500
To: nemo@ietf.org
From: Panos Papadimitratos <pp59@cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	LINES_OF_YELLING,LINES_OF_YELLING_2 autolearn=no version=2.60
Subject: [nemo] CfP: 1st European Workshop on Security in Ad-Hoc and Sensor
 Networks (ESAS 2004)
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>

CALL FOR PAPERS

1st European Workshop on Security in Ad-Hoc and Sensor Networks (ESAS 2004)

5-6 August, 2004

EURESCOM, Heidelberg, Germany

http://www.netlab.nec.de/esas/esas2004.html

Technically co-sponsored by COMSOC Germany Chapter

------------------------------------------------------------------------

GENERAL INFORMATION

With more and more devices getting smart and interconnected, ad hoc and 
sensor networks will open up a realm of new communication and data exchange 
opportunities. These upcoming networks are characterized by their dynamic 
structure, lack of a pre-established fixed infrastructure, and constrained 
resources. In order to allow their successful deployment, various security 
challenges must be met. Examples include missing `a priori' security 
associations, no clear line of defense, the lack of a trusted 
infrastructure, complex multiple domain relationships, as well as 
bandwidth, computing, memory and energy constraints. Due to the pervasive 
nature of applications relying on ad-hoc and sensor networks effective 
provisions for robust security solutions in a reliable and power efficient 
way must be taken.

This workshop seeks submissions presenting novel research on all aspects of 
security and cryptography for ad-hoc and sensor networks. ESAS 2004 will be 
a workshop where the cryptography, security and wireless networking 
communities meet. Submission of papers based on work-in-progress is encouraged.

The topics include but are not limited to:

    * Cryptographic protocols
    * Trust establishment, negotiation, and management
    * Security in constrained environments
    * Cooperation and fairness based protocols
    * Key management
    * Scalability evaluation of secure and reliable protocols
    * Secure routing
    * Secure hardware modules
    * Implementations of secure protocols
    * Deployment of secure protocols
    * Privacy and anonymity
    * Secure MAC protocols


INSTRUCTIONS FOR AUTHORS

Authors are invited to submit original papers. The preferred submission 
form is by electronic mail to Claude.Castelluccia@inrialpes.fr. The 
submissions must not exceed 10 pages (excluding the title page, 
bibliography and appendices) nor 12 pages overall. The final version should 
not exceed 15 pages. Please submit the paper in Postscript or PDF, together 
with an extra file containing the email and physical address of the 
authors, an indication of the corresponding author and a copy of the title, 
key words and abstract. We recommend that you generate the PS or PDF file 
using LaTeX and the LNCS style available at www.springer.de/comp/lncs. All 
submissions will be refereed. Submissions must not substantially duplicate 
work that any of the authors have published elsewhere or have submitted in 
parallel.


The workshop will also include a poster and demonstrator session. 
Submissions will include a 2-page summary as well as a rough draft of the 
poster.


IMPORTANT DATES

Submission Deadline:		15th March, 2004
Acceptance Notifications: 	30th April, 2004
Final Version due:		1st June, 2004
Workshop:			5th-6th August, 2004
Proceedings Version Deadline: 	6th September, 2004


MAILING LIST

If you want to receive subsequent Call for Papers and registration 
information, please send a brief mail to majordomo@netlab.nec.de and in the 
mail body write "subscribe esasworkshop".


REGISTRATION

Registration is available now! 
(http://www.eurescom.de/Public/Events/2004/ESAS_2004/esas_2004_registration.asp) 
All sessions will be held at EURESCOM (http://www.eurescom.de).


WORKSHOP ORGANIZERS

Claude Castelluccia, INRIA, France (Claude.Castelluccia@inrialpes.fr)
Hannes Hartenstein, University of Karlsruhe, Germany 
(hannes.hartenstein@rz.uni-karlsruhe.de)
Christof Paar, University of Bochum, Germany (cpaar@crypto-ruhr-uni-bochum.de)
Dirk Westhoff, NEC Network Labs Heidelberg, Germany 
(dirk.westhoff@netlab.nec.de)


PROGRAM COMMITTEE

N. Asokan, Nokia, Finland
Levente Buttyan, BME-HIT, Hungary
Sonja Buchegger, EPFL, Switzerland
Claude Castelluccia, INRIA, France
Claudia Eckert, TU Darmstadt, Germany
Hannes Hartenstein, University of Karlsruhe, Germany
Stefan Lucks, University of Mannheim, Germany
Refik Molva, Eurecom, France
Gabriel Montenegro, SunLabs, France
Pekka Nikander, Ericsson, Finland
Christof Paar, University of Bochum, Germany
Panagiotis Papadimitratos, Cornell University, USA
Frank Stajano, University of Cambridge, UK
Gene Tsudik, UC Irvine, USA
Andre Weimerskirch, University of Bochum, Germany
Nathalie Weiler, ETH Zuerich, Switzerland
Dirk Westhoff, NEC Europe Ltd., Germany
Susanne Wetzel, Stevens Institute of Technology, USA
Manel Guerrero Zapata, University Pompeu Fabra, Barcelona, Spain


WORKSHOP PROCEEDINGS

The Proceedings will be published by Springer after the Workshop in the 
Lecture Notes in Computer Science (LNCS) Series 
(www.springer.de/comp/lncs). Notice that in order to be included in the 
proceedings, the authors of an accepted paper must guarantee to present 
their contribution at the workshop.


FURTHER WORKSHOP INFORMATION

Dirk Westhoff
NEC Europe Ltd.
Kurfuersten-Anlage 36
D-69115 Heidelberg
Germany

Phone: +49/(0)6221/90511-49
Fax: +49/(0)6221/90511-55
Email: dirk.westhoff@netlab.nec.de
------------------------------------------------------------------------

Technically co-sponsored by IEEE Communications Society, Germany Chapter 
(http://it.e-technik.uni-ulm.de/comsoc/), Supported by Inria 
(http://www.inria.fr/), Supported by Cosy Group 
(http://www.crypto.rub.de/Seminare/Krypt/Krypto_engwise0203.html), 
Supported by DSN Group  (cid:part6.00090903.08050200@ccrle.nec.de), 
Supported by NL-E (http://www.ccrle.nec.de/), Proceedings published as 
Springer LNCS 
(http://www.springerlink.com/app/home/main.asp?wasp=1b22a8h1021trge130e)
------------------------------------------------------------------------




From exim@www1.ietf.org  Tue Jan 27 19:34:47 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05008
	for <nemo-archive@odin.ietf.org>; Tue, 27 Jan 2004 19:34:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aldeu-0006aE-3Z
	for nemo-archive@odin.ietf.org; Tue, 27 Jan 2004 19:34:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S0YKEg025302
	for nemo-archive@odin.ietf.org; Tue, 27 Jan 2004 19:34:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aldet-0006a1-V7
	for nemo-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 19:34:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04939
	for <nemo-web-archive@ietf.org>; Tue, 27 Jan 2004 19:34:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aldes-0001c9-00
	for nemo-web-archive@ietf.org; Tue, 27 Jan 2004 19:34:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aldd5-0001B2-00
	for nemo-web-archive@ietf.org; Tue, 27 Jan 2004 19:32:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AldcR-00011c-00
	for nemo-web-archive@ietf.org; Tue, 27 Jan 2004 19:31:47 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AldRm-00062U-V7
	for nemo-web-archive@ietf.org; Tue, 27 Jan 2004 19:20:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AldCE-0007wu-1j; Tue, 27 Jan 2004 19:04:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AlAt7-0005f5-0l
	for nemo@optimus.ietf.org; Mon, 26 Jan 2004 12:51:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14256
	for <nemo@ietf.org>; Mon, 26 Jan 2004 12:51:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlAt5-00032L-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:51:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AlAs8-0002z4-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:50:05 -0500
Received: from postoffice8.mail.cornell.edu ([132.236.56.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AlArJ-0002wk-00
	for nemo@ietf.org; Mon, 26 Jan 2004 12:49:14 -0500
Received: from Panacea_2.cornell.edu (dhcp-128-84-210-142-r3a-desktop.ece.cornell.edu [128.84.210.142])
	by postoffice8.mail.cornell.edu (8.12.10/8.12.6) with ESMTP id i0QHnCj9002947;
	Mon, 26 Jan 2004 12:49:12 -0500 (EST)
Message-Id: <5.2.1.1.2.20040126124541.027bade0@postoffice7.mail.cornell.edu>
X-Sender: pp59@postoffice7.mail.cornell.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 26 Jan 2004 12:49:08 -0500
To: nemo@ietf.org
From: Panos Papadimitratos <pp59@cornell.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [nemo] CfP: 1st European Workshop on Security in Ad-Hoc and Sensor
 Networks (ESAS 2004)
Sender: nemo-admin@ietf.org
Errors-To: nemo-admin@ietf.org
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>,
	<mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Id: NEMO Working Group <nemo.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.0 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	LINES_OF_YELLING,LINES_OF_YELLING_2 autolearn=no version=2.60

CALL FOR PAPERS

1st European Workshop on Security in Ad-Hoc and Sensor Networks (ESAS 2004)

5-6 August, 2004

EURESCOM, Heidelberg, Germany

http://www.netlab.nec.de/esas/esas2004.html

Technically co-sponsored by COMSOC Germany Chapter

------------------------------------------------------------------------

GENERAL INFORMATION

With more and more devices getting smart and interconnected, ad hoc and 
sensor networks will open up a realm of new communication and data exchange 
opportunities. These upcoming networks are characterized by their dynamic 
structure, lack of a pre-established fixed infrastructure, and constrained 
resources. In order to allow their successful deployment, various security 
challenges must be met. Examples include missing `a priori' security 
associations, no clear line of defense, the lack of a trusted 
infrastructure, complex multiple domain relationships, as well as 
bandwidth, computing, memory and energy constraints. Due to the pervasive 
nature of applications relying on ad-hoc and sensor networks effective 
provisions for robust security solutions in a reliable and power efficient 
way must be taken.

This workshop seeks submissions presenting novel research on all aspects of 
security and cryptography for ad-hoc and sensor networks. ESAS 2004 will be 
a workshop where the cryptography, security and wireless networking 
communities meet. Submission of papers based on work-in-progress is encouraged.

The topics include but are not limited to:

    * Cryptographic protocols
    * Trust establishment, negotiation, and management
    * Security in constrained environments
    * Cooperation and fairness based protocols
    * Key management
    * Scalability evaluation of secure and reliable protocols
    * Secure routing
    * Secure hardware modules
    * Implementations of secure protocols
    * Deployment of secure protocols
    * Privacy and anonymity
    * Secure MAC protocols


INSTRUCTIONS FOR AUTHORS

Authors are invited to submit original papers. The preferred submission 
form is by electronic mail to Claude.Castelluccia@inrialpes.fr. The 
submissions must not exceed 10 pages (excluding the title page, 
bibliography and appendices) nor 12 pages overall. The final version should 
not exceed 15 pages. Please submit the paper in Postscript or PDF, together 
with an extra file containing the email and physical address of the 
authors, an indication of the corresponding author and a copy of the title, 
key words and abstract. We recommend that you generate the PS or PDF file 
using LaTeX and the LNCS style available at www.springer.de/comp/lncs. All 
submissions will be refereed. Submissions must not substantially duplicate 
work that any of the authors have published elsewhere or have submitted in 
parallel.


The workshop will also include a poster and demonstrator session. 
Submissions will include a 2-page summary as well as a rough draft of the 
poster.


IMPORTANT DATES

Submission Deadline:		15th March, 2004
Acceptance Notifications: 	30th April, 2004
Final Version due:		1st June, 2004
Workshop:			5th-6th August, 2004
Proceedings Version Deadline: 	6th September, 2004


MAILING LIST

If you want to receive subsequent Call for Papers and registration 
information, please send a brief mail to majordomo@netlab.nec.de and in the 
mail body write "subscribe esasworkshop".


REGISTRATION

Registration is available now! 
(http://www.eurescom.de/Public/Events/2004/ESAS_2004/esas_2004_registration.asp) 
All sessions will be held at EURESCOM (http://www.eurescom.de).


WORKSHOP ORGANIZERS

Claude Castelluccia, INRIA, France (Claude.Castelluccia@inrialpes.fr)
Hannes Hartenstein, University of Karlsruhe, Germany 
(hannes.hartenstein@rz.uni-karlsruhe.de)
Christof Paar, University of Bochum, Germany (cpaar@crypto-ruhr-uni-bochum.de)
Dirk Westhoff, NEC Network Labs Heidelberg, Germany 
(dirk.westhoff@netlab.nec.de)


PROGRAM COMMITTEE

N. Asokan, Nokia, Finland
Levente Buttyan, BME-HIT, Hungary
Sonja Buchegger, EPFL, Switzerland
Claude Castelluccia, INRIA, France
Claudia Eckert, TU Darmstadt, Germany
Hannes Hartenstein, University of Karlsruhe, Germany
Stefan Lucks, University of Mannheim, Germany
Refik Molva, Eurecom, France
Gabriel Montenegro, SunLabs, France
Pekka Nikander, Ericsson, Finland
Christof Paar, University of Bochum, Germany
Panagiotis Papadimitratos, Cornell University, USA
Frank Stajano, University of Cambridge, UK
Gene Tsudik, UC Irvine, USA
Andre Weimerskirch, University of Bochum, Germany
Nathalie Weiler, ETH Zuerich, Switzerland
Dirk Westhoff, NEC Europe Ltd., Germany
Susanne Wetzel, Stevens Institute of Technology, USA
Manel Guerrero Zapata, University Pompeu Fabra, Barcelona, Spain


WORKSHOP PROCEEDINGS

The Proceedings will be published by Springer after the Workshop in the 
Lecture Notes in Computer Science (LNCS) Series 
(www.springer.de/comp/lncs). Notice that in order to be included in the 
proceedings, the authors of an accepted paper must guarantee to present 
their contribution at the workshop.


FURTHER WORKSHOP INFORMATION

Dirk Westhoff
NEC Europe Ltd.
Kurfuersten-Anlage 36
D-69115 Heidelberg
Germany

Phone: +49/(0)6221/90511-49
Fax: +49/(0)6221/90511-55
Email: dirk.westhoff@netlab.nec.de
------------------------------------------------------------------------

Technically co-sponsored by IEEE Communications Society, Germany Chapter 
(http://it.e-technik.uni-ulm.de/comsoc/), Supported by Inria 
(http://www.inria.fr/), Supported by Cosy Group 
(http://www.crypto.rub.de/Seminare/Krypt/Krypto_engwise0203.html), 
Supported by DSN Group  (cid:part6.00090903.08050200@ccrle.nec.de), 
Supported by NL-E (http://www.ccrle.nec.de/), Proceedings published as 
Springer LNCS 
(http://www.springerlink.com/app/home/main.asp?wasp=1b22a8h1021trge130e)
------------------------------------------------------------------------





