From mip4-bounces@ietf.org Tue Jan 01 14:11:51 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J9mWk-0001tU-5K; Tue, 01 Jan 2008 14:11:50 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1J9mWj-0001tL-2Y
	for mip4-confirm+ok@megatron.ietf.org; Tue, 01 Jan 2008 14:11:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J9mWi-0001tD-P0
	for mip4@ietf.org; Tue, 01 Jan 2008 14:11:48 -0500
Received: from mail153.messagelabs.com ([216.82.253.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1J9mWi-0005QY-DX
	for mip4@ietf.org; Tue, 01 Jan 2008 14:11:48 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-3.tower-153.messagelabs.com!1199214705!16309635!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 3835 invoked from network); 1 Jan 2008 19:11:45 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-3.tower-153.messagelabs.com with SMTP;
	1 Jan 2008 19:11:45 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id m01JBix5003178
	for <mip4@ietf.org>; Tue, 1 Jan 2008 12:11:44 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id m01JBhJ6020525
	for <mip4@ietf.org>; Tue, 1 Jan 2008 13:11:44 -0600 (CST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id m01JBg9n020518
	for <mip4@ietf.org>; Tue, 1 Jan 2008 13:11:43 -0600 (CST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 1 Jan 2008 14:11:41 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130227C298@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MIP4 Minutes from IETF70 (Vancouver)
thread-index: AchMqiQ4bro5Kcw4RoiUDfBhRwdg/g==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: Levkowetz Henrik <henrik@levkowetz.com>
Subject: [Mip4] MIP4 Minutes from IETF70 (Vancouver)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The minutes from our Vancouver meeting have been posted
at:

http://www3.ietf.org/proceedings/07dec/minutes/mip4.txt

Please look them over and send any corrections as soon
as possible.

Thanks to Acee Lindem, Marco Liebsch, and George Tsirtsis
for acting as note takers.

-Pete


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Jan 04 12:30:36 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JAqNP-0001Dh-Ue; Fri, 04 Jan 2008 12:30:35 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JAqNP-0001DZ-B4
	for mip4-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 12:30:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JAqNP-0001DR-09; Fri, 04 Jan 2008 12:30:35 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JAqNO-00048J-Jn; Fri, 04 Jan 2008 12:30:34 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 3C3A31760B;
	Fri,  4 Jan 2008 17:30:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JAqMr-0001tf-Od; Fri, 04 Jan 2008 12:30:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1JAqMr-0001tf-Od@stiedprstage1.ietf.org>
Date: Fri, 04 Jan 2008 12:30:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
	Author(s)       : K. Leung, et al.
	Filename        : draft-ietf-mip4-nemo-v4-base-07.txt
	Pages           : 24
	Date            : 2008-01-04

This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-ietf-mip4-nemo-v4-base-07.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-ietf-mip4-nemo-v4-base-07.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-01-04122158.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemo-v4-base-07.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-01-04122158.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--NextPart--





From mip4-bounces@ietf.org Fri Jan 04 12:38:26 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JAqUz-0002BX-Q3; Fri, 04 Jan 2008 12:38:25 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JAqUy-00028Q-H0
	for mip4-confirm+ok@megatron.ietf.org; Fri, 04 Jan 2008 12:38:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JAqUy-00026B-6E
	for mip4@ietf.org; Fri, 04 Jan 2008 12:38:24 -0500
Received: from mail153.messagelabs.com ([216.82.253.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JAqUx-00006U-PH
	for mip4@ietf.org; Fri, 04 Jan 2008 12:38:24 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-153.messagelabs.com!1199468302!21481016!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 9366 invoked from network); 4 Jan 2008 17:38:22 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-7.tower-153.messagelabs.com with SMTP;
	4 Jan 2008 17:38:22 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id m04HcMgH007049
	for <mip4@ietf.org>; Fri, 4 Jan 2008 10:38:22 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id m04HcLhC007400
	for <mip4@ietf.org>; Fri, 4 Jan 2008 11:38:22 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id m04HcJxo007377
	for <mip4@ietf.org>; Fri, 4 Jan 2008 11:38:20 -0600 (CST)
Message-ID: <477E6F0A.20009@gmail.com>
Date: Fri, 04 Jan 2008 18:38:18 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
CC: mip4@ietf.org
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
References: <E1JAqMr-0001tf-Od@stiedprstage1.ietf.org>
In-Reply-To: <E1JAqMr-0001tf-Od@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080103-0, 03/01/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Dear MIP4 WG,

The seventh version of the NEMOv4 draft is corresponding
to a change in format - now the draft exists as XML source. The XML can
be found at:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-07.xml

Alex

Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Mobility for IPv4 Working Group of the IETF.
> 
> 
> 	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
> 	Author(s)       : K. Leung, et al.
> 	Filename        : draft-ietf-mip4-nemo-v4-base-07.txt
> 	Pages           : 24
> 	Date            : 2008-01-04
> 
> This document describes a protocol for supporting Mobile Networks
> between a Mobile Router and a Home Agent by extending the Mobile IPv4
> protocol.  A Mobile Router is responsible for the mobility of one or
> more network segments or subnets moving together.  The Mobile Router
> hides its mobility from the nodes on the mobile network.  The nodes
> on the Mobile Network may be fixed in relationship to the Mobile
> Router and may not have any mobility function.
> 
> Extensions to Mobile IPv4 are introduced to support Mobile Networks.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt

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


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 08 06:57:23 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCD56-0008Lu-LF; Tue, 08 Jan 2008 06:57:20 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JCD54-0008Lm-IJ
	for mip4-confirm+ok@megatron.ietf.org; Tue, 08 Jan 2008 06:57:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCD54-0008K7-7h; Tue, 08 Jan 2008 06:57:18 -0500
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1JCD50-0006dy-VE; Tue, 08 Jan 2008 06:57:18 -0500
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jme4783a0bd; Tue, 08 Jan 2008 20:10:38 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm21e477ed0d4; Sat, 05 Jan 2008 02:10:12 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Sat, 05 Jan 2008 02:10:12 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JAqNR-0001Dz-Gg; Fri, 04 Jan 2008 12:30:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JAqNP-0001DR-09; Fri, 04 Jan 2008 12:30:35 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JAqNO-00048J-Jn; Fri, 04 Jan 2008 12:30:34 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 3C3A31760B;
	Fri,  4 Jan 2008 17:30:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JAqMr-0001tf-Od; Fri, 04 Jan 2008 12:30:01 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1JAqMr-0001tf-Od@stiedprstage1.ietf.org>
Date: Fri, 04 Jan 2008 12:30:01 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Archive: <http://www1.ietf.org/pipermail/i-d-announce>
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: Internet-Drafts@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 2.7 (++)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt 
X-BeenThere: mip4@ietf.org
Reply-To: internet-drafts@ietf.org
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
	Author(s)       : K. Leung, et al.
	Filename        : draft-ietf-mip4-nemo-v4-base-07.txt
	Pages           : 24
	Date            : 2008-01-04

This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-ietf-mip4-nemo-v4-base-07.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-ietf-mip4-nemo-v4-base-07.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-01-04122158.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemo-v4-base-07.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-01-04122158.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--NextPart--






From mip4-bounces@ietf.org Wed Jan 09 16:36:29 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JCib6-0001Ql-Kh; Wed, 09 Jan 2008 16:36:28 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JCib5-0001Qd-LH
	for mip4-confirm+ok@megatron.ietf.org; Wed, 09 Jan 2008 16:36:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JCib5-0001QT-BO
	for mip4@ietf.org; Wed, 09 Jan 2008 16:36:27 -0500
Received: from qmta07.emeryville.ca.mail.comcast.net ([76.96.30.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCib4-0002TP-KW
	for mip4@ietf.org; Wed, 09 Jan 2008 16:36:27 -0500
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id b7761Y0061GXsuc0A0Ew00; Wed, 09 Jan 2008 21:36:26 +0000
Received: from [192.168.10.35] ([68.41.54.91])
	by OMTA07.emeryville.ca.mail.comcast.net with comcast
	id b9c21Y00H1y4cik8T00000; Wed, 09 Jan 2008 21:36:03 +0000
X-Authority-Analysis: v=1.0 c=1 a=ADP1vPCUax0A:10 a=Tw5KaLuHAAAA:8
	a=PS-qks92ZV3LtEiSlcUA:9 a=RvDi4NaWHZDuPcIca04A:7
	a=Vvg9d_B2WVShGxHBVrPAAT_nOrIA:4 a=XS0JvM4Kc5YA:10
Message-ID: <47853E57.1080605@acm.org>
Date: Wed, 09 Jan 2008 16:36:23 -0500
From: Ken Laberteaux <klaberte@acm.org>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: mip4@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Subject: [Mip4] CFP--VehiculAr Inter-NETworking (VANET) 2008
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

ANNOUNCEMENT  and CALL FOR PAPERS

ACM VANET 2008

Vehicle to Vehicle -- Vehicle to Roadside -- Vehicle to Internet

The Fifth ACM International Workshop on VehiculAr Inter-NETworking

In conjunction with ACM MobiCom 2008
Date: To be announced
San Francisco, California, USA

Sponsored by ACM SIGMOBILE

http://www.sigmobile.org/workshops/vanet2008/

Important Dates (tentative):
Paper Submission Deadline: April 6th
Notification of Acceptance: June 6th
Camera-Ready Deadline: June 27th

The goal of this workshop is to present and discuss recent advances in 
the development of vehicular inter-networking (VANET) technologies. 
Based on short- and medium-range communication as well as on cellular 
systems, vehicular inter-networking will enable vehicular safety 
applications (including collision and other safety warnings) as well as 
non-safety applications (like real-time traffic congestion and routing 
information, high-speed tolling, mobile infotainment, and many others).

The creation of high-performance, highly reliable, highly scalable, 
secure, and privacy-preserving VANET technologies presents an 
extraordinary challenge for the wireless research community. A high 
degree of communication reliability is needed under unfavorable 
conditions.  Clearly, the specificity of vehicular inter-networking in 
terms of mobility behavior, applications scenarios, and application 
requirements makes VANET research an exciting and demanding application- 
and purpose-driven sub-discipline of wireless networking.

Furthermore, VANET present a very active field of research, development, 
standardization, and field trials.  Throughout the world, there are many 
national and international projects in government, industry, and 
academia devoted to VANET.  These include consortia like Vehicle Safety 
Consortium (US), Car-2-Car Communication Consortium (Europe), and 
Advanced Safety Vehicle Program (Japan), standardization efforts like 
IEEE 802.11p (WAVE), and field trials like the large-scale Vehicle 
Infrastructure Integration Program (VII) in the US.

Following the successes of VANET 2004 held in Philadelphia, VANET 2005 
held in Cologne, Germany, VANET 2006 in Los Angeles, CA, and VANET 2007 
in Montréal, QC, Canada, the Fifth ACM International Workshop on 
Vehicular Inter-Networking (VANET) will be held in San Francisco, CA in 
conjunction with MobiCom 2008.

Authors are invited to submit papers presenting new research related to 
the theory or practice of vehicular inter-networking (VANET).  All 
submissions must describe original research, not published or currently 
under review for another workshop, conference, or journal.

Areas of interest include, but are not limited to:

- Channel modeling
- Modulation and coding
- Power control and scalability issues
- Medium access control protocols
- Multi-channel organization and operation
- Communication protocol design
- Safety and non-safety applications
- Vehicle-to-vehicle/roadside/Internet communication
- Simulation frameworks
- Field operational testing
- Network management
- Security issues and countermeasures
- Privacy issues

Submission Instructions

All paper submissions will be handled electronically.  Papers must be in 
PDF format, no longer than 10 pages (single- or double-column), in font 
no smaller than 11 points, and must fit properly on US Letter-sized 
paper (8.5 inch x 11 inch) with reasonable margins. Submitted papers 
will be judged based on their quality through a double-blind review 
process, where the identities of the authors are withheld from the 
reviewers.  Detailed instructions for paper submission will be posted on 
the VANET 2008 web page at:
http://www.sigmobile.org/workshops/vanet2008/.


Organizing Committee:

General Co-Chairs:
Varsha Sadekar, General Motors
Paolo Santi, Italian Natl. Research Council

Technical Program Co-Chairs:
Yih-Chun Hu, University of Illinois at Urbana-Champaign
Martin Mauve, Heinrich-Heine University in Düsseldorf

Technical Program Committee:
Fan Bai , General Motors
Levente Buttyan  Budapest University of Technology and Economics
Eylem Ekici, Ohio State University
Andreas Festag, NEC Europe Ltd
Hannes Hartenstein, University of Karlsruhe
Jean-Pierre Hubaux, EPFL
Markus Jakobsson , Indiana University
Daniel Jiang, Mercedes-Benz Research & Development North America, Inc.
Frank Kargl, Ulm University
Timo Kosch , BMW
Ken Laberteaux, Toyota Research
Christof Paar, Ruhr-University Bochum
Panagiotis (Panos) Papadimitratos, EPFL
Maxim Raya, EPFL
Björn Scheuermann, Heinrich Heine University Düsseldorf
Rajeev Shorey, General Motors Research
Daniel Stancil, Carnegie Mellon University
Pravin Varaiya, University of California at Berkeley
Michele Weigle, Old Dominion University
Andre Weimerskirch, escrypt GmbH

Web and Publicity Chair:
Ken Laberteaux, Toyota Technical Center


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 04:31:28 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFR5r-0004MH-H6; Thu, 17 Jan 2008 04:31:27 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFR5p-0004M3-OI
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 04:31:25 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFR5p-0004Ls-9Z
	for mip4@ietf.org; Thu, 17 Jan 2008 04:31:25 -0500
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFR5o-00074V-J7
	for mip4@ietf.org; Thu, 17 Jan 2008 04:31:25 -0500
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JUS000A07R7Y1@szxga04-in.huawei.com> for
	mip4@ietf.org; Thu, 17 Jan 2008 17:30:43 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JUS00HXY7R7AQ@szxga04-in.huawei.com> for
	mip4@ietf.org; Thu, 17 Jan 2008 17:30:43 +0800 (CST)
Received: from z49950 ([10.121.33.161])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JUS003737R3M0@szxml04-in.huawei.com> for
	mip4@ietf.org; Thu, 17 Jan 2008 17:30:43 +0800 (CST)
Date: Thu, 17 Jan 2008 17:30:39 +0800
From: "John.zhao" <john.zhao@huawei.com>
Subject: RE: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
In-reply-to: <E1JAqMr-0001tf-Od@stiedprstage1.ietf.org>
To: mip4@ietf.org
Message-id: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com>
Organization: Huawei Technologies Co., LTD.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchO942f1m50KrVuTHOxUrAQUPdBkAJ814kQ
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: john.zhao@huawei.com
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi,all
	In the section 7, to co-located mode MR, it seems that it can also
send traffics based on the optimization and only tunnel once with the CoA as
its source address. Right?
	Best Rgds,
Thanks,

John.zhao 





-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 05:21:03 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFRrq-0001mK-PC; Thu, 17 Jan 2008 05:21:02 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFRrm-0001i1-Gu
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 05:20:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFRrm-0001hs-2f
	for mip4@ietf.org; Thu, 17 Jan 2008 05:20:58 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1JFRrl-0006Vv-Pk
	for mip4@ietf.org; Thu, 17 Jan 2008 05:20:58 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-12.tower-119.messagelabs.com!1200565256!26194946!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [144.189.100.105]
Received: (qmail 21108 invoked from network); 17 Jan 2008 10:20:56 -0000
Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105)
	by server-12.tower-119.messagelabs.com with SMTP;
	17 Jan 2008 10:20:56 -0000
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id m0HAKu5e021381;
	Thu, 17 Jan 2008 03:20:56 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244])
	by az33exr04.mot.com (8.13.1/Vontu) with SMTP id m0HAKte2016713;
	Thu, 17 Jan 2008 04:20:55 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id m0HAKrha016677;
	Thu, 17 Jan 2008 04:20:54 -0600 (CST)
Message-ID: <478F2C05.3030901@gmail.com>
Date: Thu, 17 Jan 2008 11:20:53 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: john.zhao@huawei.com
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
References: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com>
In-Reply-To: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080116-1, 16/01/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

John.zhao wrote:
> Hi,all In the section 7, to co-located mode MR, it seems that it can 
> also send traffics based on the optimization and only tunnel once 
> with the CoA as its source address. Right?

Hi John, thanks for pointing this.  The intention is indeed to have the
simple encapsulation (optimization of double encapsulation) described in
a separate document and not here.

I would like to know which paragraph in section 7 read made you think
optimization is used?  I would like to identify it and keep track.

I could think of the following in section 7:
> For optimization, the Home Agent SHOULD only encapsulate the packet 
> with the tunnel header (source IP address set to Home Agent and 
> destination IP address set to CoA) for Collocated CoA mode.

Also know that I'm not sure who/how/when can make modifications to the
document, since it's advanced a bit past the WG discussion.

Alex

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


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 06:42:44 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFT8t-0008Hm-R4; Thu, 17 Jan 2008 06:42:43 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFT8s-0008Hh-OH
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFT8s-0008HZ-BE
	for mip4@ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JFT8r-0002uI-PD
	for mip4@ietf.org; Thu, 17 Jan 2008 06:42:42 -0500
X-VirusChecked: Checked
X-Env-Sender: Christophe.Janneteau@motorola.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1200570160!1334323!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 26800 invoked from network); 17 Jan 2008 11:42:40 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-2.tower-128.messagelabs.com with SMTP;
	17 Jan 2008 11:42:40 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m0HBgdrX028279;
	Thu, 17 Jan 2008 04:42:39 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr03.mot.com (8.13.1/Vontu) with SMTP id m0HBgdPd009382;
	Thu, 17 Jan 2008 05:42:39 -0600 (CST)
Received: from [10.161.201.129] (zfr01-2129.crm.mot.com [10.161.201.129])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id m0HBgbdR009363;
	Thu, 17 Jan 2008 05:42:38 -0600 (CST)
Message-ID: <478F3F2D.2050201@motorola.com>
Date: Thu, 17 Jan 2008 12:42:37 +0100
From: Christophe Janneteau <Christophe.Janneteau@motorola.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
References: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com>
	<478F2C05.3030901@gmail.com>
In-Reply-To: <478F2C05.3030901@gmail.com>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: john.zhao@huawei.com, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

John, Alex,

My understanding is that the base NEMOv4 specification 
(draft-ietf-mip4-nemo-v4-base-07.txt) requires double encapsulation to 
be used for the Foreign Agent CoA mode, but makes it optional for the 
Collocated CoA mode. In other words, in Collocated CoA mode, the spec 
allows (and actually encourages = SHOULD) the simple (bi-directional) 
encapsulation between MR and HA to be used.

The double encapsulation is required in the FA CoA mode, to ensure 
transparency with respect to legacy (RFC3344) Foreign Agent. If simple 
encapsulation only would be used, the FA would need to be able to 
forward a packet addressed to an LFN address while only the MR's HoA is 
present in the FA's visitor list...and the packet would be dropped. The 
draft "FA extensions to NEMOv4 Base" (draft-ietf-mip4-nemov4-fa-01.txt) 
aims at addressing this specific issue by defining extension to FA to 
make it NEMOv4 aware and thus allow the use of simple encapsulation 
(i.e. of the sole FA<->HA tunnel and nor more the additional inner 
MR_HOA<-->HA tunnel).

Can authors confirm this was the intention of the two different specs 
(i.e. the NEMOv4 base spec allowing simple encapsulation for the 
Collocated CoA mode, while a separate doc specifying it for the FA CoA 
mode)?

I have not checked the last version of the base NEMOv4 spec to determine 
if the current text is explicit enough about these aspects. John what do 
you think?

Thanks
Christophe.

Alexandru Petrescu wrote:
> John.zhao wrote:
>> Hi,all In the section 7, to co-located mode MR, it seems that it can 
>> also send traffics based on the optimization and only tunnel once with 
>> the CoA as its source address. Right?
> 
> Hi John, thanks for pointing this.  The intention is indeed to have the
> simple encapsulation (optimization of double encapsulation) described in
> a separate document and not here.
> 
> I would like to know which paragraph in section 7 read made you think
> optimization is used?  I would like to identify it and keep track.
> 
> I could think of the following in section 7:
>> For optimization, the Home Agent SHOULD only encapsulate the packet 
>> with the tunnel header (source IP address set to Home Agent and 
>> destination IP address set to CoA) for Collocated CoA mode.
> 
> Also know that I'm not sure who/how/when can make modifications to the
> document, since it's advanced a bit past the WG discussion.
> 
> Alex
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 09:27:37 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFViO-0004Xc-3U; Thu, 17 Jan 2008 09:27:32 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFViM-0004XS-Gt
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 09:27:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFViM-0004XJ-70
	for mip4@ietf.org; Thu, 17 Jan 2008 09:27:30 -0500
Received: from hs-out-0708.google.com ([64.233.178.250]
	helo=hs-out-2122.google.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFViJ-0005Gp-Fe
	for mip4@ietf.org; Thu, 17 Jan 2008 09:27:30 -0500
Received: by hs-out-2122.google.com with SMTP id 54so492283hsz.5
	for <mip4@ietf.org>; Thu, 17 Jan 2008 06:27:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=V9z7YuBDl+ICdie4DTzePYtps2VUtXo9eV3wOlmzWsM=;
	b=IaKIw1K5mP8KGUod2QfxDeZVVSr/5psi2nTAcxHuiZ8kqEYiHpmxs0m/mt3e2ddOXm7BF510+lxYesqioLg+L3jPd/tJH1ItOcL3k0QtDPts2GyPzDjlft+0ZiX1jpOt25gbjC+MDXmFah9aeUqni8OZ/BUniDbjzb4J+0ynI8I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=rBEVS0cRfR0DIGrJtu2jvGxCUA/sXDjzvDLGiNJfDbSHBe1k/jD1Z3RzkVKF+34QV5X3a/g+x5izU0KdBo/1yqv2G99kUr0ZSRT79a6pgqF13fGnVTzMzp8OZyG/lts7Ar7zaSvM2Y3k+lSUio6z2dg7gKsl9S6oq6aMnVVxDBQ=
Received: by 10.142.237.20 with SMTP id k20mr1230032wfh.112.1200580043991;
	Thu, 17 Jan 2008 06:27:23 -0800 (PST)
Received: by 10.142.11.11 with HTTP; Thu, 17 Jan 2008 06:27:23 -0800 (PST)
Message-ID: <d3886a520801170627k7ecba877v3f39d7cd90380d53@mail.gmail.com>
Date: Thu, 17 Jan 2008 09:27:23 -0500
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: "Christophe Janneteau" <Christophe.Janneteau@motorola.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
In-Reply-To: <478F3F2D.2050201@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <00bd01c858eb$9fc6bda0$a864a8c0@china.huawei.com>
	<478F2C05.3030901@gmail.com> <478F3F2D.2050201@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: john.zhao@huawei.com, Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Christophe,

Yes, I think your understanding is correct. Please review
draft-ietf-mip4-nemov4-fa-01.txt and provide me (and/or the list) with
comments. I would appreciate it since we are now going to try to
progress this draft too.

Regards
George

On Jan 17, 2008 6:42 AM, Christophe Janneteau
<Christophe.Janneteau@motorola.com> wrote:
> John, Alex,
>
> My understanding is that the base NEMOv4 specification
> (draft-ietf-mip4-nemo-v4-base-07.txt) requires double encapsulation to
> be used for the Foreign Agent CoA mode, but makes it optional for the
> Collocated CoA mode. In other words, in Collocated CoA mode, the spec
> allows (and actually encourages = SHOULD) the simple (bi-directional)
> encapsulation between MR and HA to be used.
>
> The double encapsulation is required in the FA CoA mode, to ensure
> transparency with respect to legacy (RFC3344) Foreign Agent. If simple
> encapsulation only would be used, the FA would need to be able to
> forward a packet addressed to an LFN address while only the MR's HoA is
> present in the FA's visitor list...and the packet would be dropped. The
> draft "FA extensions to NEMOv4 Base" (draft-ietf-mip4-nemov4-fa-01.txt)
> aims at addressing this specific issue by defining extension to FA to
> make it NEMOv4 aware and thus allow the use of simple encapsulation
> (i.e. of the sole FA<->HA tunnel and nor more the additional inner
> MR_HOA<-->HA tunnel).
>
> Can authors confirm this was the intention of the two different specs
> (i.e. the NEMOv4 base spec allowing simple encapsulation for the
> Collocated CoA mode, while a separate doc specifying it for the FA CoA
> mode)?
>
> I have not checked the last version of the base NEMOv4 spec to determine
> if the current text is explicit enough about these aspects. John what do
> you think?
>
> Thanks
> Christophe.
>
>
> Alexandru Petrescu wrote:
> > John.zhao wrote:
> >> Hi,all In the section 7, to co-located mode MR, it seems that it can
> >> also send traffics based on the optimization and only tunnel once with
> >> the CoA as its source address. Right?
> >
> > Hi John, thanks for pointing this.  The intention is indeed to have the
> > simple encapsulation (optimization of double encapsulation) described in
> > a separate document and not here.
> >
> > I would like to know which paragraph in section 7 read made you think
> > optimization is used?  I would like to identify it and keep track.
> >
> > I could think of the following in section 7:
> >> For optimization, the Home Agent SHOULD only encapsulate the packet
> >> with the tunnel header (source IP address set to Home Agent and
> >> destination IP address set to CoA) for Collocated CoA mode.
> >
> > Also know that I'm not sure who/how/when can make modifications to the
> > document, since it's advanced a bit past the WG discussion.
> >
> > Alex
> >
> > ______________________________________________________________________
> > This email has been scanned by the MessageLabs Email Security System.
> > For more information please visit http://www.messagelabs.com/email
> > ______________________________________________________________________
> >
> >
>
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 20:49:22 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFgME-0002JA-9e; Thu, 17 Jan 2008 20:49:22 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFgMD-0002J5-QV
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 20:49:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFgMD-0002Ix-FX
	for mip4@ietf.org; Thu, 17 Jan 2008 20:49:21 -0500
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFgM8-0003h6-D3
	for mip4@ietf.org; Thu, 17 Jan 2008 20:49:21 -0500
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JUT00F5PH1097@szxga03-in.huawei.com> for
	mip4@ietf.org; Fri, 18 Jan 2008 09:48:36 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JUT00DTBH0ZHC@szxga03-in.huawei.com> for
	mip4@ietf.org; Fri, 18 Jan 2008 09:48:36 +0800 (CST)
Received: from z49950 ([10.121.33.161])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JUT00L58H0VRN@szxml04-in.huawei.com> for
	mip4@ietf.org; Fri, 18 Jan 2008 09:48:35 +0800 (CST)
Date: Fri, 18 Jan 2008 09:48:25 +0800
From: "John.zhao" <john.zhao@huawei.com>
Subject: RE: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-07.txt
In-reply-to: <478F3F2D.2050201@motorola.com>
To: 'Christophe Janneteau' <Christophe.Janneteau@motorola.com>,
	'Alexandru Petrescu' <alexandru.petrescu@gmail.com>
Message-id: <005901c85974$3b3b4e80$a864a8c0@china.huawei.com>
Organization: Huawei Technologies Co., LTD.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AchY/jodO7bfi+NORj6++/bm6qIJZAAdU59g
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: john.zhao@huawei.com
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi,Christophe and Alex
 	Yes,I think I have though it as you have just mentioned below. But,
in section 7, just as Alex has pointed, the first paragraph mention that HA
can use the optimization encapsulation, but to those packets sent from MR,
there isn't the related choice. So I just pointed this one hope authors can
clarify and keep the consensus with that <fa-01> doc.
	
	Best Rgds,
Thanks.
John.zhao
> John, Alex,
> 
> My understanding is that the base NEMOv4 specification
> (draft-ietf-mip4-nemo-v4-base-07.txt) requires double encapsulation to
> be used for the Foreign Agent CoA mode, but makes it optional for the
> Collocated CoA mode. In other words, in Collocated CoA mode, the spec
> allows (and actually encourages = SHOULD) the simple (bi-directional)
> encapsulation between MR and HA to be used.
> 
> The double encapsulation is required in the FA CoA mode, to ensure
> transparency with respect to legacy (RFC3344) Foreign Agent. If simple
> encapsulation only would be used, the FA would need to be able to
> forward a packet addressed to an LFN address while only the MR's HoA is
> present in the FA's visitor list...and the packet would be dropped. The
> draft "FA extensions to NEMOv4 Base" (draft-ietf-mip4-nemov4-fa-01.txt)
> aims at addressing this specific issue by defining extension to FA to
> make it NEMOv4 aware and thus allow the use of simple encapsulation
> (i.e. of the sole FA<->HA tunnel and nor more the additional inner
> MR_HOA<-->HA tunnel).
> 
> Can authors confirm this was the intention of the two different specs
> (i.e. the NEMOv4 base spec allowing simple encapsulation for the
> Collocated CoA mode, while a separate doc specifying it for the FA CoA
> mode)?
> 
> I have not checked the last version of the base NEMOv4 spec to determine
> if the current text is explicit enough about these aspects. John what do
> you think?
> 
> Thanks
> Christophe.
> 
> Alexandru Petrescu wrote:
> > John.zhao wrote:
> >> Hi,all In the section 7, to co-located mode MR, it seems that it can
> >> also send traffics based on the optimization and only tunnel once with
> >> the CoA as its source address. Right?
> >
> > Hi John, thanks for pointing this.  The intention is indeed to have the
> > simple encapsulation (optimization of double encapsulation) described in
> > a separate document and not here.
> >
> > I would like to know which paragraph in section 7 read made you think
> > optimization is used?  I would like to identify it and keep track.
> >
> > I could think of the following in section 7:
> >> For optimization, the Home Agent SHOULD only encapsulate the packet
> >> with the tunnel header (source IP address set to Home Agent and
> >> destination IP address set to CoA) for Collocated CoA mode.
> >
> > Also know that I'm not sure who/how/when can make modifications to the
> > document, since it's advanced a bit past the WG discussion.
> >
> > Alex
> >
> > ______________________________________________________________________
> > This email has been scanned by the MessageLabs Email Security System.
> > For more information please visit http://www.messagelabs.com/email
> > ______________________________________________________________________
> >
> >
> 
> 
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 22:30:34 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFhw6-000461-NS; Thu, 17 Jan 2008 22:30:30 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFUbc-0007uq-Cw
	for mip4-confirm+ok@megatron.ietf.org; Thu, 17 Jan 2008 08:16:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFUbc-0007uf-2s
	for mip4@ietf.org; Thu, 17 Jan 2008 08:16:28 -0500
Received: from letter.sics.se ([193.10.64.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JFUbb-0002P6-6r
	for mip4@ietf.org; Thu, 17 Jan 2008 08:16:28 -0500
Received: from a4.sics.se (a4.sics.se [193.10.64.34])
	by letter.sics.se (Postfix) with ESMTP id 73D77409CD
	for <mip4@ietf.org>; Thu, 17 Jan 2008 14:16:21 +0100 (CET)
Received: from scheutz.sics.se (scheutz.sics.se [193.10.66.136])
	by a4.sics.se (8.13.8/8.13.8) with ESMTP id m0HDGL0G025040
	for <mip4@ietf.org>; Thu, 17 Jan 2008 14:16:21 +0100
Received: (from adam@localhost)
	by scheutz.sics.se (8.10.2+Sun/8.10.2) id m0HDGKL09247
	for mip4@ietf.org; Thu, 17 Jan 2008 14:16:20 +0100 (MET)
Date: Thu, 17 Jan 2008 14:16:20 +0100 (MET)
Message-Id: <200801171316.m0HDGKL09247@scheutz.sics.se>
To: mip4@ietf.org
From: Adam Dunkels <adam@sics.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Proofpoint-Virus-Version: vendor=fsecure engine=4.65.5502:2.3.11, 1.2.37,
	4.0.164 definitions=2008-01-17_04:2008-01-16, 2008-01-17,
	2008-01-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
	ipscore=0 phishscore=0 bulkscore=10 adultscore=0
	classifier=spam adjust=0 reason=mlx engine=3.1.0-0708230000
	definitions=main-0801170021
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 1.8 (+)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-Mailman-Approved-At: Thu, 17 Jan 2008 22:30:29 -0500
Subject: [Mip4] CFP REALWSN 2008
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


     The REALWSN'08 Workshop on Real-World Wireless Sensor Networks
		    http://www.sics.se/realwsn08/

			    April 1, 2008
			  Glasgow, Scotland
		 In conjunction with ACM EuroSys 2008

The purpose of the third Workshop on Real-World Wireless Sensor Networks=20
is to bring together researchers and practitioners working in the area=20
of sensor networks, with focus on real-world experiments or deployments
of wireless sensor networks.

When working with real-world experiments or deployments, many new issues=20
arise: the network environment may be composed of a variety of different=20
technologies, leading to very heterogeneous network structures; software
development for large scale networks poses new types of problems;=20
prototype networks may differ significantly from the deployed system;=20
actual sensor network deployments may need a complex combination of=20
autonomous and manual configuration. Furthermore, results obtained=20
through simulation are typically not directly applicable to operational=20
networks and it is therefore imperative for the community to produce=20
results from experimental research.

Authors are invited to submit papers (5 pages, double column) for=20
presentation at the workshop. Papers will be selected based on=20
originality, technical merit and relevance. Published papers will
be archived in the ACM Digital Library.

All topics pertaining to real-world wireless sensor networks are of=20
interest, including but not limited to:

     * Experiences with real-world deployments
     * Experimental validation/refutation of previous simulation results =
obtained by others
     * Real-world performance of self-organization and self-management
     * Debugging, testing, and management
     * Deployment and configuration
     * Applications in medicine, industry, science, environmental monitor=
ing, etc.
     * Security and trust
     * Scalability in practice
     * Development and prototyping platforms
     * Operating systems, sensor network programming paradigms, and langu=
ages
     * Middleware for heterogeneous networks
     * Real-time and dependability issues
     * Hardware support for real-world sensor networks
     * Robustness at all levels: communication, software, hardware
     * Energy efficient protocols
     * Hardware and software methods for energy measurement and profiling

Important dates (tentative)

Electronic submissions due: 10 February, 2008
Notification of acceptance: 3 March, 2008
Camera-ready copy due: 13 March, 2008
Workshop: 1 April 2008

Organizers

Workshop Chair:

     * Thiemo Voigt, Swedish Institute of Computer Science

Technical program committee chairs:

     * Adam Dunkels, Swedish Institute of Computer Science
     * Pedro Jos=E9 Marron, University of Bonn, Germany

Technical program committee (under construction):

    * Muneeb Ali, TU Delft, The Netherlands
    * Torsten Braun, University of Bern, Switzerland
    * Nirupama Bulusu, Portland State University, USA
    * Saumitra M. Das, Purdue University, USA
    * Carlo Fischione, UC Berkeley, USA
    * Per Gunningberg, Uppsala University, Sweden
    * Wen Hu, CSIRO, Australia
    * Holger Karl, University of Paderborn, Germany
    * Koen Langendoen, TU Delft, The Netherlands
    * Luis Orozco, University of Castilla la Mancha, Spain
    * Gian Pietro Picco, University of Trento, Italy
    * Joe Polastre, Sentilla, USA
    * Utz R=F6dig, University of Lancaster, UK
    * Christian Rohner, Uppsala University, Sweden
    * Kay R=F6mer, ETH Z=FCrich, Switzerland
    * Vlasios Tsiatsis, Ericsson Research
    * Jochen Schiller, FU Berlin, Germany
    * Cormac Sreenan, UC Cork, Ireland
    * Arno Wacker, University of Duisburg, Germany=20

--=20
Adam Dunkels <adam@sics.se>
http://www.sics.se/~adam/





-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Jan 17 22:31:11 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFhwl-0005TM-2g; Thu, 17 Jan 2008 22:31:11 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JF9qk-0002Lh-Mf
	for mip4-confirm+ok@megatron.ietf.org; Wed, 16 Jan 2008 10:06:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JF9qk-0002LZ-Bo
	for mip4@ietf.org; Wed, 16 Jan 2008 10:06:42 -0500
Received: from xsmtp0.ethz.ch ([82.130.70.14])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JF9qj-0005XW-St
	for mip4@ietf.org; Wed, 16 Jan 2008 10:06:42 -0500
Received: from xfe2.d.ethz.ch ([82.130.124.42]) by XSMTP0.ethz.ch with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 16 Jan 2008 16:06:40 +0100
Received: from vs9.inf.ethz.ch ([129.132.130.188]) by xfe2.d.ethz.ch over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 16 Jan 2008 16:06:39 +0100
Received: by vs9.inf.ethz.ch (sSMTP sendmail emulation);
	Wed, 16 Jan 2008 16:07:24 +0100
Date: Wed, 16 Jan 2008 16:07:24 +0100
From: Marc Langheinrich - IOT 2008 <info@iot2008.org>
To: mip4@ietf.org
Message-ID: <20080116150724.GA29299@inf.ethz.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
X-OriginalArrivalTime: 16 Jan 2008 15:06:39.0308 (UTC)
	FILETIME=[652CA8C0:01C85851]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
X-Mailman-Approved-At: Thu, 17 Jan 2008 22:31:09 -0500
Subject: [Mip4] IOT'08: Call for Participation (plus: Workshop Submission
	Deadlines Extended)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


             **********************************************
                 ANNOUNCEMENT AND CALL FOR PARTICIPATION
             **********************************************
                                   
                         INTERNET OF THINGS 2008
                 March 26-28, 2008, Zurich (Switzerland)
         Organized by ETH Zurich, University St.Gallen, and MIT
                                   
                     www.internet-of-things-2008.org
                                   
            -------------------------------------------------
             Registration now open! See www.iot2008.org/reg/
            -------------------------------------------------
  
  The Internet of  Things 2008 conference provides  an in-depth, state-
  of-the-art view  onto the emerging  field of the Internet  of Things.
  The main program  on Thursday (27th) and Friday  (28th) features four
  distinct  keynotes  by  Dr.  Peter Zencke  (SAP),  Dr.  Bob  Iannucci
  (Nokia),  Dr.  Gerd  Wolfram  (Metro), and  Prof.  Haruhisa  Ichikawa
  (NTT/UEC  Tokyo).  It  also   offers  40  scientific  and  industrial
  presentations  in three  parallel tracks,  as well  as an  exhibition
  space with hands-on demos of current technology. A separate tutorials
  and  workshops program  on  Wednesday (26th)  allows participants  to
  choose from the following topics:
  
   [T1] Smart Items - Business Logic on the Items
   [T2] RFID Application Development with the Accada Open Source
        Middleware Platform
   [W1] Producing Standards for the Internet of Things
   [W2] Sketchtools - Creative Tools for Prototyping Smart Devices
   [W3] First International Workshop on Interoperable Vehicles
   [W4] Designing the Internet of Things for Workplace Realities: 
        Social and Cultural Aspects in Design and Organisation
  
                *****************************************
                 WORKSHOP SUBMISSION DEADLINES EXTENDED!
                 See: www.iot2008.org/cfp/workshops.html
                *****************************************
  
  Important Dates:
   * January 20,23,26,27: Workshop submission deadlines (extended)
   * January 25: Guaranteed conference hotel room rate expires
   * February 24: Early registration rates end
   * March 26-28: Conference in the Swissotel in Zurich

-- 
For more information see: www.internet-of-things-2008.org
Questions? Contact us: info@iot2008.org 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Jan 18 10:32:24 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JFtCi-0001ao-6w; Fri, 18 Jan 2008 10:32:24 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JFtCf-0001Zy-Q3
	for mip4-confirm+ok@megatron.ietf.org; Fri, 18 Jan 2008 10:32:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JFtCf-0001Zk-ET
	for mip4@ietf.org; Fri, 18 Jan 2008 10:32:21 -0500
Received: from smtps.di.fc.ul.pt ([194.117.22.93])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JFtCe-0006RL-Ci
	for mip4@ietf.org; Fri, 18 Jan 2008 10:32:21 -0500
Received: from [10.101.86.14] (di-casim.di.fc.ul.pt [10.101.86.14])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by smtps.di.fc.ul.pt (Postfix) with ESMTP id D14B21B83F0
	for <mip4@ietf.org>; Fri, 18 Jan 2008 15:32:16 +0000 (WET)
Message-ID: <4790C67F.7030306@di.fc.ul.pt>
Date: Fri, 18 Jan 2008 15:32:15 +0000
From: Antonio Casimiro Costa <casim@di.fc.ul.pt>
Organization: FCUL
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: mip4@ietf.org
Content-Type: multipart/mixed; boundary="------------050600030804010608070303"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Subject: [Mip4] CFP: IJAACS Special Issue on "Security, Trust,
 and Privacy in DTN and Vehicular Communications"
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: casim@di.fc.ul.pt
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050600030804010608070303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear Colleagues,

I'm sending this Call for Papers for a special issue of the IJAACS 
Journal, which may be of interest to some of you. Please apologize if 
you receive any duplicates.

Best regards,
Antonio Casimiro


--------------050600030804010608070303
Content-Type: text/plain;
 name="IJAACS-CFP.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline;
 filename="IJAACS-CFP.txt"


Call For Papers

International Journal of Autonomous and Adaptive Communications Systems (=
IJAACS)

Special Issue on: "Security, Trust, and Privacy in DTN and Vehicular Comm=
unications"

Guest Editors:
Zonghua Zhang, INRIA, France
Farid Na=EFt-Abdesselam, University of Sciences and Technologies of Lille=
, France
Sherali Zeadally, University of the District of Columbia, USA
Ant=F3nio Casimiro, University of Lisboa, Portugal


Recent years have witnessed the rapid development and wide-spread applica=
tion of wireless communication technologies, which have significantly enh=
anced access to Internet services and provide various means for ubiquitou=
s computing that enables high-speed and high-quality information exchange=
 between mobile/portable devices located anywhere in the globe. Among the=
 various application scenarios enabled by these technologies, DTN (Delay-=
Tolerant Networks) and VANETs (Vehicular Ad-hoc NETworks) represent the m=
ost promising and popular ones, as they are characterized by autonomous a=
nd adaptive communications.

DTN concerns partial sub-networks, aiming at providing network connection=
s between devices and areas that are not well-served by current networkin=
g technology. The nodes in DTN carry the packets while they are moving, a=
nd then forward the packets once a wireless connection is available betwe=
en them. Vehicular communications allow the real-time information exchang=
e between vehicles and infrastructures, with the objective of enhancing r=
oad safety and optimizing road traffic. VANETs are primarily enabled by i=
nter-vehicular (or Car-to-Car, C2C) communications and vehicle-roadside c=
ommunications (or Car-to-Infrastructure, C2I).

Despite their tremendous potential and far-reaching impacts on the revolu=
tion of human life, both DTNs and VANETs suffer from security and privacy=
 issues which dramatically limit their applications. First of all, they h=
ave similar vulnerabilities to other wireless networks, which allow attac=
kers to manipulate and inject messages, breaching system availability, co=
nfidentiality and integrity. Besides the traditional prevention technique=
s, trust management may serve as another security basis for nodes coopera=
tion and information dissemination. Furthermore, the unique characteristi=
cs of DTNs and VANETs such as uncertain mobility and unpredictable latenc=
y, make security for those networks even more challenging. In particular,=
 due to the frequent disconnections between nodes in DTNs, distributed ce=
rtificate authorities rather than centralized ones are more desirable (wh=
ile the frequent distribution of a large amount of certificates should be=
 avoided due to high round-trip time), and the user credentials/keys shou=
ld be updated periodically instead of relying on revocation messages. Mor=
eover, due to the sporadic connectivity and long delay of message transmi=
ssions in DTNs, secure message management is needed to eliminate expired =
messages and avoid information leakage.

In VANETs, the high-speed mobility and the large number of network entiti=
es call for time-efficient and cost-saving authorization and authenticati=
on models, as well as fast attacker detection, revocation and trace back =
schemes. In addition, both DTN and VANETs suffer from the privacy-invasiv=
e issue, which naturally arises in the environment where the mobile equip=
ments are bounded to the moving users. A suite of privacy-preserving tech=
niques are required to provide the fine level protection of the critical =
information and user profiles, e.g., a set of equipments related to a par=
ticular user in DTNs, personal information (and the liability in case of =
authority investigation) related to drivers and passengers in VANETs.

This special issue is devoted to the most state-of-the-art proposals and =
cutting-edge research achievements on security and privacy issues in both=
 DTN and VANETs.


*** Subject Coverage

We solicit papers that report original and unpublished work on topics inc=
luding, but not limited to, the following:

    * Anonymity, authentication and key management
    * Attacker trace back
    * Denial of service and Sybil attacks
    * Identity theft and phishing in VANETs
    * Location privacy and user privacy
    * Intrusion detection, misbehaviour detection and response
    * Privacy preserving
    * Revocation of compromised nodes
    * Security models/architectures and threat models
    * Secure communications protocols
    * Secure positioning
    * Secure billing in VANETs
    * Surveillance and monitoring
    * Tamper proof device
    * Trust management
    * Vulnerability/attacker modeling and analysis


*** Notes for Intending Authors

Submitted papers should not have been previously published nor be current=
ly under consideration for publication elsewhere

All papers are refereed through a peer review process. A guide for author=
s, sample copies and other relevant information for submitting papers are=
 available on the Author Guidelines page


*** Important Dates

Manuscripts due: 1 June, 2008
Notification to authors: 1 October, 2008
Revised papers due: 1 November, 2008


*** Editors and Notes

You may send one copy in the form of an MS Word file attached to an e-mai=
l (details in Author Guidelines) to the following:

    Zonghua Zhang
    INRIA
    Villeneuve d'Ascq
    France
    Email: zonghua.zhang@inria.fr

    Farid Na=EFt-Abdesselam
    University of Sciences and Technologies of Lille
    59655 Villeneuve d'Ascq Cedex
    France
    Email: naf@ieee.org

    Sherali Zeadally
    University of the District of Columbia
    Washington, DC 20008
    USA
    Email: szeadally@udc.edu

    Antonio Casimiro
    University of Lisboa
    Faculty of Sciences
    1749-016 Lisboa
    Portugal
    Email: casim@di.fc.ul.pt

    with a copy to:

    IEL Editorial Office
    E-mail: ijaacs@inderscience.com

Please include in your submission the title of the Special Issue, the tit=
le of the Journal and the name of the Guest Editor
--------------050600030804010608070303
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--------------050600030804010608070303--





From mip4-bounces@ietf.org Mon Jan 21 10:40:13 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGyku-0001vU-TE; Mon, 21 Jan 2008 10:40:12 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JGykt-0001qk-DI
	for mip4-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 10:40:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGykt-0001qc-3J
	for mip4@ietf.org; Mon, 21 Jan 2008 10:40:11 -0500
Received: from p130.piuha.net ([2001:14b8:400::130] helo=smtp.piuha.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JGyks-0001GX-H7
	for mip4@ietf.org; Mon, 21 Jan 2008 10:40:11 -0500
Received: from smtp.piuha.net (localhost [127.0.0.1])
	by smtp.piuha.net (Postfix) with ESMTP id D03F2198CF9;
	Mon, 21 Jan 2008 17:40:09 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130])
	by smtp.piuha.net (Postfix) with ESMTP id 9744E198CAF;
	Mon, 21 Jan 2008 17:40:09 +0200 (EET)
Message-ID: <4794BCDC.2050508@piuha.net>
Date: Mon, 21 Jan 2008 17:40:12 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071022)
MIME-Version: 1.0
To: draft-ietf-mip4-nemo-v4-base@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] AD review of draft-ietf-mip4-nemo-v4-base
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

I have reviewed this specification. It is generally in good shape. There
are a few observations below; I think you should address them but they
were not grave enough for me to block the progress of the document. If
you can, it would be helpful if you could revise the document in the
next few days, as I will be starting IETF Last Call.

Regarding recent discussion on the list, please do not introduce new
changes to the draft, except if there's a clear bug. Route optimization,
etc. should be out of scope.

Technical:

> Optionally, all requested Mobile
> Networks could be acknowledged using only one Mobile Network
> Acknowledgement extension with "Prefix Length" and "Prefix" fields
> set to zero. 
I think this is unnecessary complexity. Suggest deleting this possibility.

>    5.  Propagate Mobile Network Prefix routes via routing protocol
This seems unnecessary in some typical cases, such as when the home
agent already advertises a shorter prefix that contains this new prefix.

> The
>    solution described here does not place any restriction on the number
>    of levels for nested mobility.  But note that this might introduce
>    significant overhead on the data packets as each level of nesting
>    introduces another tunnel header encapsulation.
In fairness, it should be noted that this specification is incapable of
detecting loops in such nesting configurations. As a result, I think we
should warn the reader about these configurations with stronger language
than there is currently.

>    If a dynamic routing protocol is used between the Mobile Router and
>    the Home Agent to propagate the mobile network information into the
>    home network, the routing updates SHOULD be protected with IPsec ESP
>    confidentiality between the Mobile Router and Home Agent, to prevent
>    information about home network topology from being visible to
>    eavesdroppers.
>
>    A routing protocol message protected with ESP, and sent through the
>    Mobile Router - Home Agent bidirectional tunnel, SHOULD NOT contain
>    the Mobile IPv4 Mobile-Home Authentication Extension, since ESP
>    provides enough security.
Are you specifying how to protect the routing protocol in question (not
your job!) or merely requiring the tunnel packets carrying these routing
exchanges are ESP protected? If the former, revise. If the latter, OK.
But even in that case, is the Mobile IPv4 Mobile-Home Authentication
Extension really used on tunnel packets?

>    The policy of future assignments to this number space should be
>    following Expert Review.
>   
I believe "Standards Action or IESG Approval" would be more appropriate,
for reasons of ensuring interoperability.

Editorial:

>    Although Mobile IPv4 stated that Mobile Network can be supported by
>    the Mobile Router and Home Agent using static configuration or
>    running a routing protocol, there is no solution
I suppose you meant "Although the original Mobile IPv4 specifications
claimed that ..."

Jari



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Jan 21 12:04:05 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JH045-0002IC-D6; Mon, 21 Jan 2008 12:04:05 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JH044-0002Hm-Pn
	for mip4-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 12:04:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JH044-0002He-F6; Mon, 21 Jan 2008 12:04:04 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1JH044-0006yI-6g; Mon, 21 Jan 2008 12:04:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id D6E84175C3;
	Mon, 21 Jan 2008 17:04:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JH043-0004NL-Ce; Mon, 21 Jan 2008 12:04:03 -0500
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1JH043-0004NL-Ce@stiedprstage1.ietf.org>
Date: Mon, 21 Jan 2008 12:04:03 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip4@ietf.org
Subject: [Mip4] Last Call: draft-ietf-mip4-nemo-v4-base (Network Mobility 
 (NEMO) Extensions for Mobile IPv4) to Proposed Standard 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The IESG has received a request from the Mobility for IPv4 WG (mip4) to 
consider the following document:

- 'Network Mobility (NEMO) Extensions for Mobile IPv4 '
   <draft-ietf-mip4-nemo-v4-base-07.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-02-04. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-07.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=15858&rfc_flag=0



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 22 11:47:57 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHMI1-00057X-01; Tue, 22 Jan 2008 11:47:57 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHMHz-00057C-Ka
	for mip4-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 11:47:55 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHMHz-000573-8Z
	for mip4@ietf.org; Tue, 22 Jan 2008 11:47:55 -0500
Received: from mail153.messagelabs.com ([216.82.253.51])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JHMHy-0001u7-AB
	for mip4@ietf.org; Tue, 22 Jan 2008 11:47:55 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-153.messagelabs.com!1201020472!5014327!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 25918 invoked from network); 22 Jan 2008 16:47:52 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-5.tower-153.messagelabs.com with SMTP;
	22 Jan 2008 16:47:52 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m0MGlkln014971;
	Tue, 22 Jan 2008 09:47:50 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id m0MGljDI005819;
	Tue, 22 Jan 2008 10:47:45 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id m0MGlhTV005735;
	Tue, 22 Jan 2008 10:47:44 -0600 (CST)
Message-ID: <47961E2A.2090709@gmail.com>
Date: Tue, 22 Jan 2008 17:47:38 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4794BCDC.2050508@piuha.net>
In-Reply-To: <4794BCDC.2050508@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080121-0, 21/01/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: draft-ietf-mip4-nemo-v4-base@tools.ietf.org,
	Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] Re: AD review of draft-ietf-mip4-nemo-v4-base
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Jari, thanks for reviewing this document,

Jari Arkko wrote:
> I have reviewed this specification. It is generally in good shape. 
> There are a few observations below; I think you should address them 
> but they were not grave enough for me to block the progress of the 
> document. If you can, it would be helpful if you could revise the 
> document in the next few days, as I will be starting IETF Last Call.
> 
> Regarding recent discussion on the list, please do not introduce new 
> changes to the draft, except if there's a clear bug. Route 
> optimization, etc. should be out of scope.

Ok.

> Technical:
> 
>> Optionally, all requested Mobile Networks could be acknowledged 
>> using only one Mobile Network Acknowledgement extension with 
>> "Prefix Length" and "Prefix" fields set to zero.
> I think this is unnecessary complexity. Suggest deleting this 
> possibility.

Ok, just deleted this possibility and text.  I've also checked - I think
in no other place does the text mention this possibility.

>> 5.  Propagate Mobile Network Prefix routes via routing protocol
> 
> This seems unnecessary in some typical cases, such as when the home 
> agent already advertises a shorter prefix that contains this new 
> prefix.

That is right to me, in some deployments the mobile network prefixes are
aggregated into a shorter prefix which is already assigned as pointing
to HA, but in some cases it's not really the case.  Can we add [if
necessary] like this:

"5.  Propagate Mobile Network Prefix routes via routing protocol if
      necessary"

>> The solution described here does not place any restriction on the 
>> number of levels for nested mobility.  But note that this might 
>> introduce significant overhead on the data packets as each level of
>>  nesting introduces another tunnel header encapsulation.
> 
> In fairness, it should be noted that this specification is incapable
>  of detecting loops in such nesting configurations. As a result, I 
> think we should warn the reader about these configurations with 
> stronger language than there is currently.

Ok, how about the following:

        "[...] The solution described here
	does not place any restriction on the number of levels for
	nested mobility.  Two issues should be noted though.  First,
	whenever physical loops occur in a nested aggregation of
	mobile networks this protocol does neither detect nor solve
	them - datagram forwarding may be blocked.  Second, Mobile
	Routers in a deep nested aggregation of mobile networks might
	introduce significant overhead on the data packets as each
	level of nesting introduces another tunnel header
	encapsulation."

>> If a dynamic routing protocol is used between the Mobile Router and
>>  the Home Agent to propagate the mobile network information into 
>> the home network, the routing updates SHOULD be protected with 
>> IPsec ESP confidentiality between the Mobile Router and Home Agent,
>>  to prevent information about home network topology from being 
>> visible to eavesdroppers.
>> 
>> A routing protocol message protected with ESP, and sent through the
>>  Mobile Router - Home Agent bidirectional tunnel, SHOULD NOT 
>> contain the Mobile IPv4 Mobile-Home Authentication Extension, since
>>  ESP provides enough security.
> 
> Are you specifying how to protect the routing protocol in question 
> (not your job!) or merely requiring the tunnel packets carrying these
>  routing exchanges are ESP protected? If the former, revise. If the 
> latter, OK. But even in that case, is the Mobile IPv4 Mobile-Home 
> Authentication Extension really used on tunnel packets?

Right, the goal is halfway towards the latter.  And I think indeed the 
Mobile-Home auth extension is only used on RegReq/Rep and not on the 
tunnelled packets.

Let's drop the following paragraph(?):
   "A routing protocol message protected with ESP, and sent through the
    Mobile Router - Home Agent bidirectional tunnel, SHOULD NOT contain
    the Mobile IPv4 Mobile-Home Authentication Extension, since ESP
    provides enough security."

>> The policy of future assignments to this number space should be 
>> following Expert Review.
>> 
> I believe "Standards Action or IESG Approval" would be more 
> appropriate, for reasons of ensuring interoperability.

Ok, modified it.  For info, the description of "Standards Action", "IESG 
Approval" and "Expert Review" are described in RFC2434 and to some 
extent RFC2780.  Other?

This could be discussed in the context of NEMO FA-extensions draft: 
would it prefer its RegRep Sub-type 'NEMOv4 Tunneling Extension' set by 
the HA allocated by a "Designated Expert"?  By "Standards Action"?  or 
by "IESG Review"?  I'd prefer the middle.

> Editorial:
> 
>> Although Mobile IPv4 stated that Mobile Network can be supported by
>>  the Mobile Router and Home Agent using static configuration or 
>> running a routing protocol, there is no solution
> 
> I suppose you meant "Although the original Mobile IPv4 specifications
>  claimed that ..."

Right, modified it to say:
    "Although the original Mobile IPv4 specifications stated that Mobile
     Networks can be supported by the Mobile Router and Home Agent using
     static configuration or running a routing protocol (see Section 4.5
     of RFC 3344 [RFC3344]),"

Alex


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


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 22 12:07:34 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHMb0-0005j5-HT; Tue, 22 Jan 2008 12:07:34 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHMb0-0005iz-4L
	for mip4-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 12:07:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHMaz-0005ir-Qy
	for mip4@ietf.org; Tue, 22 Jan 2008 12:07:33 -0500
Received: from p130.piuha.net ([2001:14b8:400::130] helo=smtp.piuha.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHMaz-0000qO-Bf
	for mip4@ietf.org; Tue, 22 Jan 2008 12:07:33 -0500
Received: from smtp.piuha.net (localhost [127.0.0.1])
	by smtp.piuha.net (Postfix) with ESMTP id AB36A198C8E;
	Tue, 22 Jan 2008 19:07:32 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130])
	by smtp.piuha.net (Postfix) with ESMTP id 47442198B4A;
	Tue, 22 Jan 2008 19:07:32 +0200 (EET)
Message-ID: <479622D7.90205@piuha.net>
Date: Tue, 22 Jan 2008 19:07:35 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071022)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <4794BCDC.2050508@piuha.net> <47961E2A.2090709@gmail.com>
In-Reply-To: <47961E2A.2090709@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: draft-ietf-mip4-nemo-v4-base@tools.ietf.org,
	Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] Re: AD review of draft-ietf-mip4-nemo-v4-base
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


> Can we add [if
> necessary] like this:
>
> "5.  Propagate Mobile Network Prefix routes via routing protocol if
>      necessary"

OK.

>
>>> The solution described here does not place any restriction on the
>>> number of levels for nested mobility.  But note that this might
>>> introduce significant overhead on the data packets as each level of
>>>  nesting introduces another tunnel header encapsulation.
>>
>> In fairness, it should be noted that this specification is incapable
>>  of detecting loops in such nesting configurations. As a result, I
>> think we should warn the reader about these configurations with
>> stronger language than there is currently.
>
> Ok, how about the following:
>
>        "[...] The solution described here
>     does not place any restriction on the number of levels for
>     nested mobility.  Two issues should be noted though.  First,
>     whenever physical loops occur in a nested aggregation of
>     mobile networks this protocol does neither detect nor solve
>     them - datagram forwarding may be blocked.  Second, Mobile
>     Routers in a deep nested aggregation of mobile networks might
>     introduce significant overhead on the data packets as each
>     level of nesting introduces another tunnel header
>     encapsulation."

OK

>
> Right, the goal is halfway towards the latter.  And I think indeed the
> Mobile-Home auth extension is only used on RegReq/Rep and not on the
> tunnelled packets.
>
> Let's drop the following paragraph(?):
>   "A routing protocol message protected with ESP, and sent through the
>    Mobile Router - Home Agent bidirectional tunnel, SHOULD NOT contain
>    the Mobile IPv4 Mobile-Home Authentication Extension, since ESP
>    provides enough security."

OK

>
>>> The policy of future assignments to this number space should be
>>> following Expert Review.
>>>
>> I believe "Standards Action or IESG Approval" would be more
>> appropriate, for reasons of ensuring interoperability.
>
> Ok, modified it.  For info, the description of "Standards Action",
> "IESG Approval" and "Expert Review" are described in RFC2434 and to
> some extent RFC2780.  Other?

draft-narten-iana-considerations-rfc2434bis, and you should add
reference to it.

>
> This could be discussed in the context of NEMO FA-extensions draft:
> would it prefer its RegRep Sub-type 'NEMOv4 Tunneling Extension' set
> by the HA allocated by a "Designated Expert"?  By "Standards Action"? 
> or by "IESG Review"?  I'd prefer the middle.

Lets take that up separately. Just change the rules for this draft now.

>
>> Editorial:
>>
>>> Although Mobile IPv4 stated that Mobile Network can be supported by
>>>  the Mobile Router and Home Agent using static configuration or
>>> running a routing protocol, there is no solution
>>
>> I suppose you meant "Although the original Mobile IPv4 specifications
>>  claimed that ..."
>
> Right, modified it to say:
>    "Although the original Mobile IPv4 specifications stated that Mobile
>     Networks can be supported by the Mobile Router and Home Agent using
>     static configuration or running a routing protocol (see Section 4.5
>     of RFC 3344 [RFC3344]),"
Good.

Thanks.

Jari



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 22 17:57:39 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHS3n-0000s4-Jt; Tue, 22 Jan 2008 17:57:39 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JGhJx-0000fN-NL
	for mip4-confirm+ok@megatron.ietf.org; Sun, 20 Jan 2008 16:03:13 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JGhJx-0000fE-Df
	for mip4@ietf.org; Sun, 20 Jan 2008 16:03:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JGhI0-0007AN-8I; Sun, 20 Jan 2008 16:01:12 -0500
Received: from caip.rutgers.edu ([128.6.236.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JGhHz-0004Tm-Ap; Sun, 20 Jan 2008 16:01:12 -0500
Received: from LENOVO5C399A8F (pool-71-187-228-213.nwrknj.fios.verizon.net
	[71.187.228.213]) (authenticated bits=0)
	by caip.rutgers.edu (8.13.8/8.13.5) with ESMTP id m0KL0fTL010739;
	Sun, 20 Jan 2008 16:00:42 -0500
From: "Dario Pompili" <pompili@caip.rutgers.edu>
To: "'Dario Pompili'" <pompili@caip.rutgers.edu>
References: <019b01c825aa$7e016db0$0201a8c0@LENOVO5C399A8F>
Date: Sun, 20 Jan 2008 16:00:42 -0500
Message-ID: <008e01c85ba7$87131560$0201a8c0@LENOVO5C399A8F>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acglqn28DEAlzHPVTZqfOGmq5QVRjA1/AtIQ
In-Reply-To: <019b01c825aa$7e016db0$0201a8c0@LENOVO5C399A8F>
X-Scanned-By: MIMEDefang 2.62 on 128.6.236.16
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6437e26f1586b9f35812ea5ebeedf4ad
X-TMDA-Confirmed: Sun, 20 Jan 2008 16:03:13 -0500
X-Mailman-Approved-At: Tue, 22 Jan 2008 17:57:38 -0500
Cc: 
Subject: [Mip4] CFP: The IEEE International Conference on Pervasive Services
	(ICPS'08) - MANUSCRIPT DEADLINE: February 1, 2008
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[We apologize in advance if you receive multiple copies of this CFP]

=20

                                                =
____________________________

                                  		The IEEE International
Conference

                                          on Pervasive Services =
(ICPS=9208)

=20

                                          July 6-10, 2008, Sorrento, =
Italy

=09
http://www.icpsconference.org

                                                =
____________________________

=20

The International Conference on Pervasive Services is a forum for the
presentation and discussion of approaches, research findings, =
applications
and experiences in the area of pervasive computing. The ultimate goal is =
to
envision new trends and ideas about practical aspects of designing,
implementing, and evaluating next paradigms/systems for all aspects of
pervasive computing including distributed and mobile computing, where
services built out of pervasive infrastructure and information, and are
seamlessly available anywhere, anytime, and in any format. The =
conference
technical program will consist of high-quality papers that are selected =
by
the program committee for presentation and publication.=20

=20

Topics of interest include but are not limited to:

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

=95           Applications of and experiences with pervasive services

=95           Pervasive and autonomous computing and architectures

=95           Mobile and/or wearable computing

=95           Smart devices and wireless networks

=95           Wireless & sensor networks

=95           Middleware support for pervasive and mobile computing

=95           Pervasive computing and management

=95           User interfaces and interaction model

=95           Positioning and tracking technologies

=95           Programmable and active networks

=95           Service dissemination and discovery protocols

=95           Environments & algorithms for pervasive application =
development

=95           Runtime support for next generation of pervasive services

=95           Security services for applications in pervasive =
environments

=95           Programming paradigms for pervasive computing applications

=95           Pervasive computing applications requirements

=95           Performance measurement and Benchmarking

=95           Next generation services

=20

Demo/Exhibit Session

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

ICPS'08 will feature a demo and exhibit session consisting of prototypes =
and
technology artifacts such as demonstrating pervasive services and
applications. A separate call for demonstrations and exhibits will be
issued. Entries will be judged by a separate subcommittee led by the
demo/exhibit chair. Please see the conference web site for more =
information.

=20

Workshops & Tutorials

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

ICPS'08 will feature workshops and tutorials on topics related to =
pervasive
services. The objectives of the workshops are to complement the main =
program
and to extend the scope of the conference. Proposals for half-day and =
full
day workshops and tutorials are solicited. Entries will be judged by a
separate subcommittee, headed by the workshop and tutorial chairs
respectively.

=20

Paper/Poster Submissions and Publication

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

Full papers (a maximum of 10 pages in length) and posters (2 pages) are
invited on a wide variety of topics relating to pervasive computing as
indicated above. All manuscripts will be reviewed and judged on merits
including correctness, originality, technical strength, quality of
presentation, and relevance to the conference themes. Submitted papers =
must
include original work, and may not be under consideration for another
conference or journal. They should also not be under review or be =
submitted
to another forum during the ICPS'08 review process. Posters are not =
subject
to any of these restrictions. Authors should submit full papers or =
posters
electronically (PDF or postscript) via the ICPS'08 conference web site =
at
http://www.icpsconference.org, and should follow IEEE CS format - style
files can be found at
ftp://pubftp.computer.org/Press/Outgoing/proceedings/.Submission implies =
the
willingness of at least one of the authors to register and present the
paper. Accepted papers and posters will appear in proceedings, which =
will be
distributed at the conference.

=20

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


                                    IMPORTANT DEADLINES

                        Manuscripts due:            February 1, 2008

                Workshops proposal due:       January 11, 2008

                        Tutorial proposals due:     March 28, 2008

                Acceptance notification:            March 28, 2008

                Camera ready copies due:          April 18, 2008

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

Paper submissions will be handled via the conference web site.

=20

General Chairs

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

Manish Parashar, Rutgers University, NJ, USA

Mario Lauria, TIGEM, Naples, Italy

=20

Program Chairs=20

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

Julie A. McCann, Imperial College, London, UK

Domenico Cotroneo, University of Naples =93Federico II=94, Italy


Program Committee

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

Alex Delis, University of Athens, Greece

Ali Akoglu, University of Arizona, USA

Antonio Liotta, University of Essex, UK

Arkady Zaslavsky, Monash University, Australia

Selim Balcisoy, Sabanci University, Turkey

Cristian Borcea, New Jersey Institute of Technology, USA

Christos Douligeris, University of Piraeus, Greece

Claudia Roncancio, IMAG, France

Eylem Ekici, Ohio State University, USA

Gunter Haring, University of Vienna, Austria

Simon Dobson, UCD, Dublin

Hongbing Wang, Southeast University, China

Jaafar Gaber, UTBM, France

Helen Karatza, Aristotle University of Thessaloniki, Greece

Karin Hummel, University of Vienna, Austria

Laurence Yang, St Francis Xavier University, Canada

Marian Scuturici, LIRIS, INSA de Lyon, France

Martin Olivier, University of Pretoria, South Africa

Paul Roe, Queensland University of Technology, Australia

Sara Tucci Piergiovanni, Univ. of Rome =93La Sapienza=94, Italy

Sylvain Lecomte, University of Valenciennes, France

Eymann Torsten, Universitat Bayreuth, Germany

Cristiano Di Flora, Tampere Nokia Research Center, Finland

Salvatore Orlando, University of Naples =93Federico II=94, Italy

Sotirios Terzis, University of Strathclyde, Ireland

Paolo Bellavista, University di Bologna, Italy

Tatsuo Nakajima,Waseda University, Japan

Soren Christensen, University of Aarhus, Denmark

Oriana Riva, University of Helsinki, Finland

Fillia Makedon, University of Texas at Arlington, USA

Kasper Hallenborg, University of Southern Denmark, Denmark

Rajeev Muralidhar, Intel India, India

Frederic Le Mou=E9l, CITI Lab. / INRIA ARES Team , France=20

=20
Publicity Chairs

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

Richard Anthony, University of Greenwick, UK

Dario Pompili, Rutgers University, USA

Ichiro Satoh, Nat. Inst. of Informatics, Tokyo, Japan

=20

Publication/Financial Chair

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

Kelly Sutton, University of Arizona

=20

Workshop/Tutorials Chair

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

Marcello Cinque, University of Naples =93Federico II=94, Italy

Local Arrangement Chairs

Gabriella Carrozza, Catello Di Martino, Roberto Pietrantuono, University =
of
Naples =93Federico II=94, Italy  =20

=20

Steering Committee

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

Salim Hariri, Univ. of Arizona, USA

Mazin Yousif, Intel Corporation, USA

Laurent Lefevre, INRIA, France

Jean-Marc Pierson, IRIT, Toulouse, France

Manish Parashar, Rutgers University, USA

Aris M. Ouksel, University of Illinois at Chicago, USA

=20

For further information contact:   =20

Julie McAnn <jamm@doc.ic.ac.uk>

Domenico Controneo <cotroneo@unina.it>

=20
=20
------------------------------------------------------------------
Dario Pompili, Ph.D.
Assistant Professor
Department of Electrical & Computer Engineering
CoRE Building - Room 615
Rutgers, The State University of New Jersey
96 Frelinghuysen Road, Piscataway, NJ 08854
Phone: (732) 445-6400 ext. 202
Fax: (732) 445-0593
Email1: pompili@ece.rutgers.edu
Email2: pompili@caip.rutgers.edu
WWW: http://www.ece.rutgers.edu/~pompili
-------------------------------------------------------------------





-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 22 17:57:48 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHS3w-0000t5-Tm; Tue, 22 Jan 2008 17:57:48 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JGz03-0003US-Cf
	for mip4-confirm+ok@megatron.ietf.org; Mon, 21 Jan 2008 10:55:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JGz02-0003Jc-Lh
	for mip4@ietf.org; Mon, 21 Jan 2008 10:55:50 -0500
Received: from caip.rutgers.edu ([128.6.236.16])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JGz01-0003jv-Pk
	for mip4@ietf.org; Mon, 21 Jan 2008 10:55:50 -0500
Received: from LENOVO5C399A8F (pool-71-187-228-213.nwrknj.fios.verizon.net
	[71.187.228.213]) (authenticated bits=0)
	by caip.rutgers.edu (8.13.8/8.13.5) with ESMTP id m0LFtdTY017251
	for <mip4@ietf.org>; Mon, 21 Jan 2008 10:55:42 -0500
From: "Dario Pompili" <pompili@caip.rutgers.edu>
To: <mip4@ietf.org>
Date: Mon, 21 Jan 2008 10:55:40 -0500
Message-ID: <004d01c85c46$13f99910$0201a8c0@LENOVO5C399A8F>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: Acglqn28DEAlzHPVTZqfOGmq5QVRjA1/AtIQACY5YMAAAaaysA==
X-Scanned-By: MIMEDefang 2.62 on 128.6.236.16
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6437e26f1586b9f35812ea5ebeedf4ad
X-Mailman-Approved-At: Tue, 22 Jan 2008 17:57:47 -0500
Subject: [Mip4] CFP: The IEEE International Conference on Pervasive Services
	(ICPS'08) - MANUSCRIPT DEADLINE: February 1, 2008
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[We apologize in advance if you receive multiple copies of this CFP]

=20

                                                =
____________________________

                                  		The IEEE International
Conference

                                          on Pervasive Services =
(ICPS=9208)

=20

                                          July 6-10, 2008, Sorrento, =
Italy

=09
http://www.icpsconference.org

                                                =
____________________________

=20

The International Conference on Pervasive Services is a forum for the
presentation and discussion of approaches, research findings, =
applications
and experiences in the area of pervasive computing. The ultimate goal is =
to
envision new trends and ideas about practical aspects of designing,
implementing, and evaluating next paradigms/systems for all aspects of
pervasive computing including distributed and mobile computing, where
services built out of pervasive infrastructure and information, and are
seamlessly available anywhere, anytime, and in any format. The =
conference
technical program will consist of high-quality papers that are selected =
by
the program committee for presentation and publication.=20

=20

Topics of interest include but are not limited to:

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

=95           Applications of and experiences with pervasive services

=95           Pervasive and autonomous computing and architectures

=95           Mobile and/or wearable computing

=95           Smart devices and wireless networks

=95           Wireless & sensor networks

=95           Middleware support for pervasive and mobile computing

=95           Pervasive computing and management

=95           User interfaces and interaction model

=95           Positioning and tracking technologies

=95           Programmable and active networks

=95           Service dissemination and discovery protocols

=95           Environments & algorithms for pervasive application =
development

=95           Runtime support for next generation of pervasive services

=95           Security services for applications in pervasive =
environments

=95           Programming paradigms for pervasive computing applications

=95           Pervasive computing applications requirements

=95           Performance measurement and Benchmarking

=95           Next generation services

=20

Demo/Exhibit Session

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

ICPS'08 will feature a demo and exhibit session consisting of prototypes =
and
technology artifacts such as demonstrating pervasive services and
applications. A separate call for demonstrations and exhibits will be
issued. Entries will be judged by a separate subcommittee led by the
demo/exhibit chair. Please see the conference web site for more =
information.

=20

Workshops & Tutorials

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

ICPS'08 will feature workshops and tutorials on topics related to =
pervasive
services. The objectives of the workshops are to complement the main =
program
and to extend the scope of the conference. Proposals for half-day and =
full
day workshops and tutorials are solicited. Entries will be judged by a
separate subcommittee, headed by the workshop and tutorial chairs
respectively.

=20

Paper/Poster Submissions and Publication

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

Full papers (a maximum of 10 pages in length) and posters (2 pages) are
invited on a wide variety of topics relating to pervasive computing as
indicated above. All manuscripts will be reviewed and judged on merits
including correctness, originality, technical strength, quality of
presentation, and relevance to the conference themes. Submitted papers =
must
include original work, and may not be under consideration for another
conference or journal. They should also not be under review or be =
submitted
to another forum during the ICPS'08 review process. Posters are not =
subject
to any of these restrictions. Authors should submit full papers or =
posters
electronically (PDF or postscript) via the ICPS'08 conference web site =
at
http://www.icpsconference.org, and should follow IEEE CS format - style
files can be found at
ftp://pubftp.computer.org/Press/Outgoing/proceedings/.Submission implies =
the
willingness of at least one of the authors to register and present the
paper. Accepted papers and posters will appear in proceedings, which =
will be
distributed at the conference.

=20

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


                                    IMPORTANT DEADLINES

                        Manuscripts due:            February 1, 2008

                Workshops proposal due:       January 11, 2008

                        Tutorial proposals due:     March 28, 2008

                Acceptance notification:            March 28, 2008

                Camera ready copies due:          April 18, 2008

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

Paper submissions will be handled via the conference web site.

=20

General Chairs

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

Manish Parashar, Rutgers University, NJ, USA

Mario Lauria, TIGEM, Naples, Italy

=20

Program Chairs=20

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

Julie A. McCann, Imperial College, London, UK

Domenico Cotroneo, University of Naples =93Federico II=94, Italy


Program Committee

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

Alex Delis, University of Athens, Greece

Ali Akoglu, University of Arizona, USA

Antonio Liotta, University of Essex, UK

Arkady Zaslavsky, Monash University, Australia

Selim Balcisoy, Sabanci University, Turkey

Cristian Borcea, New Jersey Institute of Technology, USA

Christos Douligeris, University of Piraeus, Greece

Claudia Roncancio, IMAG, France

Eylem Ekici, Ohio State University, USA

Gunter Haring, University of Vienna, Austria

Simon Dobson, UCD, Dublin

Hongbing Wang, Southeast University, China

Jaafar Gaber, UTBM, France

Helen Karatza, Aristotle University of Thessaloniki, Greece

Karin Hummel, University of Vienna, Austria

Laurence Yang, St Francis Xavier University, Canada

Marian Scuturici, LIRIS, INSA de Lyon, France

Martin Olivier, University of Pretoria, South Africa

Paul Roe, Queensland University of Technology, Australia

Sara Tucci Piergiovanni, Univ. of Rome =93La Sapienza=94, Italy

Sylvain Lecomte, University of Valenciennes, France

Eymann Torsten, Universitat Bayreuth, Germany

Cristiano Di Flora, Tampere Nokia Research Center, Finland

Salvatore Orlando, University of Naples =93Federico II=94, Italy

Sotirios Terzis, University of Strathclyde, Ireland

Paolo Bellavista, University di Bologna, Italy

Tatsuo Nakajima,Waseda University, Japan

Soren Christensen, University of Aarhus, Denmark

Oriana Riva, University of Helsinki, Finland

Fillia Makedon, University of Texas at Arlington, USA

Kasper Hallenborg, University of Southern Denmark, Denmark

Rajeev Muralidhar, Intel India, India

Frederic Le Mou=E9l, CITI Lab. / INRIA ARES Team , France=20

=20
Publicity Chairs

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

Richard Anthony, University of Greenwick, UK

Dario Pompili, Rutgers University, USA

Ichiro Satoh, Nat. Inst. of Informatics, Tokyo, Japan

=20

Publication/Financial Chair

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

Kelly Sutton, University of Arizona

=20

Workshop/Tutorials Chair

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

Marcello Cinque, University of Naples =93Federico II=94, Italy

Local Arrangement Chairs

Gabriella Carrozza, Catello Di Martino, Roberto Pietrantuono, University =
of
Naples =93Federico II=94, Italy  =20

=20

Steering Committee

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

Salim Hariri, Univ. of Arizona, USA

Mazin Yousif, Intel Corporation, USA

Laurent Lefevre, INRIA, France

Jean-Marc Pierson, IRIT, Toulouse, France

Manish Parashar, Rutgers University, USA

Aris M. Ouksel, University of Illinois at Chicago, USA

=20

For further information contact:   =20

Julie McAnn <jamm@doc.ic.ac.uk>

Domenico Controneo <cotroneo@unina.it>

=20
=20
------------------------------------------------------------------
Dario Pompili, Ph.D.
Assistant Professor
Department of Electrical & Computer Engineering
CoRE Building - Room 615
Rutgers, The State University of New Jersey
96 Frelinghuysen Road, Piscataway, NJ 08854
Phone: (732) 445-6400 ext. 202
Fax: (732) 445-0593
Email1: pompili@ece.rutgers.edu
Email2: pompili@caip.rutgers.edu
WWW: http://www.ece.rutgers.edu/~pompili
-------------------------------------------------------------------




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 22 18:10:08 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHSFr-0008UN-CP; Tue, 22 Jan 2008 18:10:07 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHSFn-0008Ly-Cw
	for mip4-confirm+ok@megatron.ietf.org; Tue, 22 Jan 2008 18:10:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHSFm-0008Lq-S6; Tue, 22 Jan 2008 18:10:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1JHSFm-00034a-Ff; Tue, 22 Jan 2008 18:10:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5F16726E1B;
	Tue, 22 Jan 2008 23:10:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1JHSFm-00055N-9c; Tue, 22 Jan 2008 18:10:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1JHSFm-00055N-9c@stiedprstage1.ietf.org>
Date: Tue, 22 Jan 2008 18:10:02 -0500
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: mip4@ietf.org
Subject: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08.txt 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv4 Working Group of the IETF.


	Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
	Author(s)       : K. Leung, et al.
	Filename        : draft-ietf-mip4-nemo-v4-base-08.txt
	Pages           : 25
	Date            : 2008-01-22

This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol.  A Mobile Router is responsible for the mobility of one or
more network segments or subnets moving together.  The Mobile Router
hides its mobility from the nodes on the mobile network.  The nodes
on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function.

Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-ietf-mip4-nemo-v4-base-08.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-ietf-mip4-nemo-v4-base-08.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2008-01-22180022.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip4-nemo-v4-base-08.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-01-22180022.I-D\@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--NextPart--





From mip4-bounces@ietf.org Wed Jan 23 04:38:01 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHc3U-0007M8-4M; Wed, 23 Jan 2008 04:38:00 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHc3S-0007Fm-Ln
	for mip4-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 04:37:58 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHc3S-0007FG-Bt
	for mip4@ietf.org; Wed, 23 Jan 2008 04:37:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHc3B-0006xm-Te
	for mip4@ietf.org; Wed, 23 Jan 2008 04:37:41 -0500
Received: from n1b.bullet.mail.tp2.yahoo.com ([203.188.202.108])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JHc3B-0007kX-4U
	for mip4@ietf.org; Wed, 23 Jan 2008 04:37:41 -0500
Received: from [202.43.196.225] by n1.bullet.mail.tp2.yahoo.com with NNFMP;
	23 Jan 2008 09:37:39 -0000
Received: from [217.12.4.214] by t2.bullet.tpe.yahoo.com with NNFMP;
	23 Jan 2008 09:37:38 -0000
Received: from [216.252.122.216] by t1.bullet.ukl.yahoo.com with NNFMP;
	23 Jan 2008 09:37:38 -0000
Received: from [69.147.65.152] by t1.bullet.sp1.yahoo.com with NNFMP;
	23 Jan 2008 09:37:38 -0000
Received: from [127.0.0.1] by omp400.mail.sp1.yahoo.com with NNFMP;
	23 Jan 2008 09:37:38 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 6555.99940.bm@omp400.mail.sp1.yahoo.com
Received: (qmail 24896 invoked by uid 60001); 23 Jan 2008 09:37:37 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=nk5g8iMA9mScVYy65XuNG11PR8LjhnnsTqgDJF3BglUdfyJKznRVP2I/hxT1Bv8mC65xCpE3L4QXml4uu2zeDccSJ18P3DV7uVxFqua5f25z5dicZ2Ug1BrI1clGNdzO4lKXEMl9nmPrkjL+ta6aO9RIyZaG9xdmrhsx3JnLKhc=;
X-YMail-OSG: _JgT5mEVM1mQUnbCWjAwjbKYMNV88dqb2yt_WrQgEEQMHSSfSLwIvtnOJlFo_U2CRsx8fdLWdi_Y.NAwIBS_2NZuWK1.WoLqQzpU
Received: from [71.49.102.78] by web45906.mail.sp1.yahoo.com via HTTP;
	Wed, 23 Jan 2008 01:37:37 PST
Date: Wed, 23 Jan 2008 01:37:37 -0800 (PST)
From: John Edward <jeedward@yahoo.com>
To: mip4@ietf.org
MIME-Version: 1.0
Message-ID: <819307.24799.qm@web45906.mail.sp1.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-TMDA-Confirmed: Wed, 23 Jan 2008 04:37:58 -0500
Subject: [Mip4] HPCNCS-08 Final call for papers
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1635717366=="
Errors-To: mip4-bounces@ietf.org

--===============1635717366==
Content-Type: multipart/alternative; boundary="0-1592666519-1201081057=:24799"
Content-Transfer-Encoding: 8bit

--0-1592666519-1201081057=:24799
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

HPCNCS-08 Final call for papers
   
  The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) and the (website: www.PromoteResearch.org ) will be held during July 7-10 2008 in Orlando, FL, USA. We invite draft paper submissions. The conference will be held at the same time and place where several other major events are taking place. The website contains more details.
   
  Sincerely
  John Edward

       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
--0-1592666519-1201081057=:24799
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div class=MsoNormal style="MARGIN: 0in 0in 0pt"><A name=OLE_LINK4></A><A name=OLE_LINK3><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="times new roman" size=3>HPCNCS-08 Final call for papers</FONT></SPAN></A></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><FONT face="times new roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="times new roman" size=3>The 2008 International Conference on High Performance Computing, Networking and Communication Systems (HPCNCS-08) and the (website: </FONT></SPAN></SPAN><A href="http://www.promoteresearch.org/"><FONT size=3><FONT face="times new roman"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark:
 OLE_LINK4">www.PromoteResearch.org</SPAN></SPAN><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"></SPAN></SPAN></FONT></FONT></A><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="times new roman" size=3> ) will be held during July 7-10 2008 in Orlando, FL, USA. We invite draft paper submissions. The conference will be held at the same time and place where several other major events are taking place. The website contains more details.</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><o:p><FONT face="times new roman" size=3>&nbsp;</FONT></o:p></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="times new roman" size=3>Sincerely</FONT></SPAN></SPAN></div>  <div class=MsoNormal style="MARGIN: 0in 0in
 0pt"><SPAN style="mso-bookmark: OLE_LINK3"><SPAN style="mso-bookmark: OLE_LINK4"><FONT face="times new roman" size=3>John Edward</FONT></SPAN></SPAN></div><p>&#32;
      <hr size=1>Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>
--0-1592666519-1201081057=:24799--





--===============1635717366==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1635717366==--







From mip4-bounces@ietf.org Wed Jan 23 13:13:57 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JHk6n-0008Iq-0w; Wed, 23 Jan 2008 13:13:57 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JHk6m-0008Il-4E
	for mip4-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 13:13:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JHk6l-0008Id-QH
	for mip4@ietf.org; Wed, 23 Jan 2008 13:13:55 -0500
Received: from email.reefpoint.com ([66.152.209.162] helo=ZOE.RPS.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHk6j-0000IX-LA
	for mip4@ietf.org; Wed, 23 Jan 2008 13:13:55 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 23 Jan 2008 13:13:09 -0500
Message-ID: <4BAEA3008BEC574095447FF2A47AAD080129E7B3@ZOE.RPS.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding progress of drafts to meet goals defined in
	RFC 5030
Thread-Index: Achd65wLO0T3+rkGQsO+DE0K1fRBmA==
From: "Sullivan, Jim" <jsullivan@nextpointnetworks.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Subject: [Mip4] question regarding progress of drafts to meet goals defined
	in RFC 5030
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1512191766=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1512191766==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C85DEB.9C52D4C5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C85DEB.9C52D4C5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

RFC 5030 states as a goal to standardize RADIUS attributes and define
procedures by which MIP agents map the MIP registration message fields
to proposed RADIUS attributes and vice versa....

=20

Can someone update me on the status, or provide a pointer to a draft?

=20

Thanks

=20

=20

=20

=20


------_=_NextPart_001_01C85DEB.9C52D4C5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>RFC 5030 states as a goal to standardize RADIUS =
attributes
and define procedures by which MIP agents map the MIP registration =
message
fields to proposed RADIUS attributes and vice =
versa&#8230;.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Can someone update me on the status, or provide a =
pointer to
a draft?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C85DEB.9C52D4C5--



--===============1512191766==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1512191766==--





From mip4-bounces@ietf.org Mon Jan 28 22:13:53 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJgv3-0005fW-1c; Mon, 28 Jan 2008 22:13:53 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JJgv1-0005fP-8c
	for mip4-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 22:13:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJgv0-0005fH-Pu
	for mip4@ietf.org; Mon, 28 Jan 2008 22:13:50 -0500
Received: from szxga04-in.huawei.com ([61.144.161.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJgv0-0004Eq-46
	for mip4@ietf.org; Mon, 28 Jan 2008 22:13:50 -0500
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVD001GFY9X5M@szxga04-in.huawei.com> for
	mip4@ietf.org; Tue, 29 Jan 2008 11:13:09 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JVD002NQY9X2M@szxga04-in.huawei.com> for
	mip4@ietf.org; Tue, 29 Jan 2008 11:13:09 +0800 (CST)
Received: from q52443 ([10.164.9.85])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JVD004YIY9WNK@szxml04-in.huawei.com> for
	mip4@ietf.org; Tue, 29 Jan 2008 11:13:09 +0800 (CST)
Date: Tue, 29 Jan 2008 11:13:08 +0800
From: qinxia <alice.Q@huawei.com>
Subject: [MIP4] IMHO, the traffic could be forwarded directly while bothe the
	MN and the CN are located in the same PMA.
To: kleung@cisco.com
Message-id: <000001c86224$df9b22d0$5509a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7BIT
Thread-index: AchiJN7VCfQR6MCQSBmXejkJzVERXw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello Kent,

I am no sure if this question had been discussed, if I missed it, could you expain the reason for me? Thanks for your patience.

IMO, the traffic could be forwarded directly while both the MN and CN are located in the same PMA. 

The forwarding could be also based on the destination IP address and ingress HA tunnel, if the CN is still in the PMA, why not forward them directly via the shortcut in the PMA.

BR
Alice 
[qouted]

4.2.2.  Forwarding Between Devices on same PMA

   When the communication peers are both attached to the same PMA, the
   packet is forwarded as specified in Section 4.2.1.  The traffic
   between them are still routed via the HA without taking local
   shortcut on the PMA.

*********************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
*********************************************************************************




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Jan 28 23:11:36 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJhou-0004KF-PS; Mon, 28 Jan 2008 23:11:36 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JJhot-0004If-1K
	for mip4-confirm+ok@megatron.ietf.org; Mon, 28 Jan 2008 23:11:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJhos-0004Fv-L5
	for mip4@ietf.org; Mon, 28 Jan 2008 23:11:34 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JJhos-0005tu-72
	for mip4@ietf.org; Mon, 28 Jan 2008 23:11:34 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 28 Jan 2008 20:11:33 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m0T4BXE3016890; 
	Mon, 28 Jan 2008 20:11:33 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0T4BXj5001919;
	Tue, 29 Jan 2008 04:11:33 GMT
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 28 Jan 2008 20:11:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [MIP4] IMHO,
	the traffic could be forwarded directly while bothe the MN and the CN
	are located in the same PMA.
Date: Mon, 28 Jan 2008 20:11:32 -0800
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5205563870@xmb-sjc-235.amer.cisco.com>
In-Reply-To: <000001c86224$df9b22d0$5509a40a@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIP4] IMHO,
	the traffic could be forwarded directly while bothe the MN and
	the CN are located in the same PMA.
Thread-Index: AchiJN7VCfQR6MCQSBmXejkJzVERXwAAz6zQ
From: "Kent Leung (kleung)" <kleung@cisco.com>
To: "qinxia" <alice.Q@huawei.com>
X-OriginalArrivalTime: 29 Jan 2008 04:11:33.0587 (UTC)
	FILETIME=[08825A30:01C8622D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1876; t=1201579893;
	x=1202443893; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=20=22Kent=20Leung=20(kleung)=22=20<kleung@cisco.com>
	|Subject:=20RE=3A=20[MIP4]=20IMHO,=20the=20traffic=20could=
	20be=20forwarded=20directly=20while=20bothe=20the=20MN=20and
	=20the=20CN=20are=20located=20in=20the=20same=20PMA.
	|Sender:=20; bh=IbKycM6b5Ot+4oFMaGXmiRfFjg3LTAMyDGFbf85LB1s=;
	b=BXBi+CdVASmYbNOyCeW9vZ81yM8M+VjZbTEqiot7BZOqLxLMHe9b64ITt/
	D7+NoGRvCwweUqcgZi6J27++Ov98STFlCHgbNWccLRQceM9zgNMvvYTCeXRg
	3jVCxvntqb;
Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Alice.

The shortcut is avoided to prevent bypassing of data traffic policy
enforcement at the HA.  It's possible to forward directly between MN and
CN if that is so desired. =20

Kent=20

-----Original Message-----
From: qinxia [mailto:alice.Q@huawei.com]=20
Sent: Monday, January 28, 2008 7:13 PM
To: Kent Leung (kleung)
Cc: mip4@ietf.org
Subject: [MIP4] IMHO, the traffic could be forwarded directly while
bothe the MN and the CN are located in the same PMA.

Hello Kent,

I am no sure if this question had been discussed, if I missed it, could
you expain the reason for me? Thanks for your patience.

IMO, the traffic could be forwarded directly while both the MN and CN
are located in the same PMA.=20

The forwarding could be also based on the destination IP address and
ingress HA tunnel, if the CN is still in the PMA, why not forward them
directly via the shortcut in the PMA.

BR
Alice
[qouted]

4.2.2.  Forwarding Between Devices on same PMA

   When the communication peers are both attached to the same PMA, the
   packet is forwarded as specified in Section 4.2.1.  The traffic
   between them are still routed via the HA without taking local
   shortcut on the PMA.

************************************************************************
*********
This e-mail and its attachments contain confidential information from
HUAWEI, which is intended only for the person or entity whose address is
listed above. Any use of the information contained herein in any way
(including, but not limited to, total or partial disclosure,
reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please
notify the sender by phone or email immediately and delete it!
************************************************************************
*********




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Jan 29 10:09:42 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JJs5l-0003IL-Vj; Tue, 29 Jan 2008 10:09:41 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JJs5k-0003FH-K0
	for mip4-confirm+ok@megatron.ietf.org; Tue, 29 Jan 2008 10:09:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JJs5k-0003F9-AC
	for mip4@ietf.org; Tue, 29 Jan 2008 10:09:40 -0500
Received: from wr-out-0506.google.com ([64.233.184.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JJs5j-0002JC-LQ
	for mip4@ietf.org; Tue, 29 Jan 2008 10:09:40 -0500
Received: by wr-out-0506.google.com with SMTP id 68so1188845wra.13
	for <mip4@ietf.org>; Tue, 29 Jan 2008 07:09:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	bh=1kWzwf3vlF/bwKy6lO0WzgODzqZZU67z6PdwHI0x52Y=;
	b=w+JmWh8iNJAk+ErzPowGX8ZgIi8Fxg2nIlibtnJOWGkIekxJLD4fQ1skXJms82lzZwYjOcwg6DmJoDUNty3hcw3pc+jppCbL8Zy+x9+I/acENgYoLnk8nyjcokaQvdVhqDoJudD1H1rwYPLeau+wtxdlwYcR1PJu+zQNZx0tN2M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=bc9Dr6dmYntoOsTUuMSxllhyglW84hgByIi1ecTjJeVEa9L2iClZX+p4DPE4Ue1Br8nFtINFOy2SQ/veDZsoMtnSuyacMdM964aiAs48OfvpyIqoV7OrWR5MnCNPyUTXIuNV6YtBlSxgkt4mZaUTZrUC/1lRwys1EUfoZ+f5gks=
Received: by 10.142.177.7 with SMTP id z7mr3325816wfe.47.1201619378374;
	Tue, 29 Jan 2008 07:09:38 -0800 (PST)
Received: by 10.142.165.1 with HTTP; Tue, 29 Jan 2008 07:09:38 -0800 (PST)
Message-ID: <d3886a520801290709v58acc53dh6a4b06955a61bac2@mail.gmail.com>
Date: Tue, 29 Jan 2008 15:09:38 +0000
From: "George Tsirtsis" <tsirtsis@googlemail.com>
To: mip4@ietf.org
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08.txt
In-Reply-To: <E1JHSFm-00055N-9c@stiedprstage1.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1JHSFm-00055N-9c@stiedprstage1.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Alex,

I see that v08 still shows all Sub-Types and Code fields in the
message extensions as "TBA". While the extension Type field will be
assigned by IANA, should we not assign numbers to the Sub-Types and
Codes as part of the draft, before it becomes an RFC? or is this
handled differently?

Thanks
George

2008/1/22  <Internet-Drafts@ietf.org>:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Mobility for IPv4 Working Group of the IETF.
>
>
>         Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
>         Author(s)       : K. Leung, et al.
>         Filename        : draft-ietf-mip4-nemo-v4-base-08.txt
>         Pages           : 25
>         Date            : 2008-01-22
>
> This document describes a protocol for supporting Mobile Networks
> between a Mobile Router and a Home Agent by extending the Mobile IPv4
> protocol.  A Mobile Router is responsible for the mobility of one or
> more network segments or subnets moving together.  The Mobile Router
> hides its mobility from the nodes on the mobile network.  The nodes
> on the Mobile Network may be fixed in relationship to the Mobile
> Router and may not have any mobility function.
>
> Extensions to Mobile IPv4 are introduced to support Mobile Networks.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
> 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-ietf-mip4-nemo-v4-base-08.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-ietf-mip4-nemo-v4-base-08.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.
>
>
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>
>


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Jan 30 08:49:02 2008
Return-path: <mip4-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1JKDJF-0002oY-Tw; Wed, 30 Jan 2008 08:49:01 -0500
Received: from mip4 by megatron.ietf.org with local (Exim 4.43)
	id 1JKDJE-0002fh-CF
	for mip4-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 08:49:00 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1JKDJE-0002bh-0k
	for mip4@ietf.org; Wed, 30 Jan 2008 08:49:00 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1JKDJD-0005vy-AR
	for mip4@ietf.org; Wed, 30 Jan 2008 08:48:59 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-5.tower-119.messagelabs.com!1201700937!20652847!1
X-StarScan-Version: 5.5.12.14.2; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 31234 invoked from network); 30 Jan 2008 13:48:57 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-5.tower-119.messagelabs.com with SMTP;
	30 Jan 2008 13:48:57 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id m0UDmvIJ029456;
	Wed, 30 Jan 2008 06:48:57 -0700 (MST)
Received: from il06vts01.mot.com (il06vts01.mot.com [129.188.137.141])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id m0UDmuBh029678;
	Wed, 30 Jan 2008 07:48:57 -0600 (CST)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id m0UDmt8m029663;
	Wed, 30 Jan 2008 07:48:55 -0600 (CST)
Message-ID: <47A08046.2080902@gmail.com>
Date: Wed, 30 Jan 2008 14:48:54 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: George Tsirtsis <tsirtsis@googlemail.com>
Subject: Re: [Mip4] I-D Action:draft-ietf-mip4-nemo-v4-base-08.txt
References: <E1JHSFm-00055N-9c@stiedprstage1.ietf.org>
	<d3886a520801290709v58acc53dh6a4b06955a61bac2@mail.gmail.com>
In-Reply-To: <d3886a520801290709v58acc53dh6a4b06955a61bac2@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080129-0, 29/01/2008), Outbound message
X-Antivirus-Status: Clean
X-CFilter-Loop: Reflected
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

George Tsirtsis wrote:
> Alex,
> 
> I see that v08 still shows all Sub-Types and Code fields in the
> message extensions as "TBA". While the extension Type field will be
> assigned by IANA, should we not assign numbers to the Sub-Types and
> Codes as part of the draft, before it becomes an RFC? or is this
> handled differently?

Well we took a direction by which we request IANA to assign both that 
RegReq Type ("Mobile Network Extension") as well as the Sub-Types and 
the Codes in both MNExtensions and in the existing RegReq and RegRep. 
This involves modification of existing MIP4 sub-registries and 
assignments of new ones.

The policies of future assignments within the new sub-registries are 
"Standards Action" or "IESG Approval".  This means what it means for 
"NEMOv4 Tunneling Extension" Sub-Type of draft-ietf-mip4-nemov4-fa-01.txt

I think this course of action is satisfying many involved parties.

Alex
PS: "Standards Action", "IESG Approval" and other policies for future 
assignments within a new space/registry are desribed in 
draft-narten-iana-considerations-rfc2434bis-08.txt

> 
> Thanks
> George
> 
> 2008/1/22  <Internet-Drafts@ietf.org>:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the Mobility for IPv4 Working Group of the IETF.
>>
>>
>>         Title           : Network Mobility (NEMO) Extensions for Mobile IPv4
>>         Author(s)       : K. Leung, et al.
>>         Filename        : draft-ietf-mip4-nemo-v4-base-08.txt
>>         Pages           : 25
>>         Date            : 2008-01-22
>>
>> This document describes a protocol for supporting Mobile Networks
>> between a Mobile Router and a Home Agent by extending the Mobile IPv4
>> protocol.  A Mobile Router is responsible for the mobility of one or
>> more network segments or subnets moving together.  The Mobile Router
>> hides its mobility from the nodes on the mobile network.  The nodes
>> on the Mobile Network may be fixed in relationship to the Mobile
>> Router and may not have any mobility function.
>>
>> Extensions to Mobile IPv4 are introduced to support Mobile Networks.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-08.txt
>>
>> To remove yourself from the I-D Announcement list, send a message to
>> i-d-announce-request@ietf.org with the word unsubscribe in the body of
>> the message.
>> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>> to change your subscription settings.
>>
>> 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-ietf-mip4-nemo-v4-base-08.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-ietf-mip4-nemo-v4-base-08.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.
>>
>>
>> --
>> Mip4 mailing list: Mip4@ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>> Supplemental site: http://www.mip4.org/
>>
>>
> 
> 


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


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



