From mip4-bounces@ietf.org Thu Mar 01 15:51:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMsFk-0003Ia-Fz; Thu, 01 Mar 2007 15:51:52 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMsE1-0000cT-TQ; Thu, 01 Mar 2007 15:50:06 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HMsE1-0001Yb-IO; Thu, 01 Mar 2007 15:50:05 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 13FBD26F02; Thu, 1 Mar 2007 20:50:05 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HMsDz-0002eE-87; Thu, 01 Mar 2007 15:50:03 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 01 Mar 2007 15:50:03 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : IPv4 Network Mobility (NEMO) Protocol Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-00.txt Pages : 1 Date : 2007-3-1 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-00.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-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-3-1123315.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemo-v4-base-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-1123315.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 Thu Mar 01 16:18:18 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMsfK-0001H5-Lk; Thu, 01 Mar 2007 16:18:18 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HMsEz-0002WZ-GA; Thu, 01 Mar 2007 15:51:05 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HMsEz-0002fA-13; Thu, 01 Mar 2007 15:51:05 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id B390D17677; Thu, 1 Mar 2007 20:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HMsDz-0002ec-Ex; Thu, 01 Mar 2007 15:50:03 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 01 Mar 2007 15:50:03 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-fmipv4-05.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : Mobile IPv4 Fast Handovers Author(s) : R. Koodli, C. Perkins Filename : draft-ietf-mip4-fmipv4-05.txt Pages : 26 Date : 2007-3-1 This document adapts the Mobile IPv6 Fast Handovers to improve delay and packet loss resulting from Mobile IPv4 handover operations. Specifically, this document addresses movement detection, IP address configuration and location update latencies during a handover. For reducing the IP address configuration latency, the document proposes that the new Care-of Address is always made to be the new access router's IP address. Additional mechanisms may be defined in the future versions of this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-fmipv4-05.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-fmipv4-05.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-fmipv4-05.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: <2007-3-1125618.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-fmipv4-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-fmipv4-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-1125618.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 Mar 02 12:41:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNBkd-00082M-V3; Fri, 02 Mar 2007 12:41:03 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNBkc-000824-I2 for mip4@ietf.org; Fri, 02 Mar 2007 12:41:02 -0500 Received: from web60317.mail.yahoo.com ([209.73.178.125]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HNBkY-0008Rb-2Y for mip4@ietf.org; Fri, 02 Mar 2007 12:41:02 -0500 Received: (qmail 52287 invoked by uid 60001); 2 Mar 2007 17:40:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=jdYD1hp2fpvpd/VhEItSuw0FG3dOmXRNzFaSgliG46/qbIxZPioYFLwTYHbxF8saiv5W4WHVerVMfrr8qq16GXB0xM0UsJIR7ijZZo+cilgSgKwL8R4gEytcn/nV50L9Or4BAVaiLa9qAvxzM1q1GBlxczhnq7p/ZTYqUwpEnIw=; X-YMail-OSG: odCuQpwVM1nphWKMrrZrdHZy.OnCEv.3VvI1iVYeNBUPqQx9W4UB0hl3mczrgmfla2CmYK2OO5BPVc05Z48SsVYqhlKvgNlY.7hKi9DWQtN5djgSUO_L.IdGjYr4NuyraFA.eM_39yjD3FNz Received: from [206.16.17.212] by web60317.mail.yahoo.com via HTTP; Fri, 02 Mar 2007 09:40:57 PST X-Mailer: YahooMailRC/468 YahooMailWebService/0.6.132.8 Date: Fri, 2 Mar 2007 09:40:57 -0800 (PST) From: Behcet Sarikaya Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt To: "Kent Leung \(kleung\)" MIME-Version: 1.0 Message-ID: <530304.52161.qm@web60317.mail.yahoo.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Behcet Sarikaya List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1547569425==" Errors-To: mip4-bounces@ietf.org --===============1547569425== Content-Type: multipart/alternative; boundary="0-1655162085-1172857257=:52161" --0-1655162085-1172857257=:52161 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi Kent,=0A Just out of curiousity, hasn't this protocol been productized = already? Such a thing was mentioned when NEMO WG was being formed and that = was why NEMO WG concentrated on IPv6 based solution?=0A=0ARegards,=0A=0A--b= ehcet=0A=0A=0A----- Original Message ----=0AFrom: "Internet-Drafts@ietf.org= " =0ATo: i-d-announce@ietf.org=0ACc: mip4@ietf.or= g=0ASent: Thursday, March 1, 2007 2:50:03 PM=0ASubject: [Mip4] I-D ACTION:d= raft-ietf-mip4-nemo-v4-base-00.txt=0A=0A=0AA New Internet-Draft is availabl= e from the on-line Internet-Drafts =0Adirectories.=0AThis draft is a work i= tem of the Mobility for IPv4 Working Group of the IETF.=0A=0A Title = : IPv4 Network Mobility (NEMO) Protocol=0A Author(s) : K. Leung, e= t al.=0A Filename : draft-ietf-mip4-nemo-v4-base-00.txt=0A Pages = : 1=0A Date : 2007-3-1=0A =0A=0A This document describ= es a protocol for supporting Mobile Networks=0A between a Mobile Router a= nd a Home Agent by extending the Mobile IPv4=0A protocol. A Mobile Route= r is responsible for the mobility of one or=0A more network segments or s= ubnets moving together. The Mobile Router=0A hides its mobility from the= nodes on the mobile network. The nodes=0A on the Mobile Network may be = fixed in relationship to the Mobile=0A Router and may not have any mobili= ty function.=0A=0A Extensions to Mobile IPv4 are introduced to support Mo= bile Networks.=0A=0A=0AA URL for this Internet-Draft is:=0Ahttp://www.ietf.= org/internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt=0A=0ATo remove your= self from the I-D Announcement list, send a message to =0Ai-d-announce-requ= est@ietf.org with the word unsubscribe in the body of =0Athe message. =0AYo= u can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce =0Ato = change your subscription settings.=0A=0AInternet-Drafts are also available = by anonymous FTP. Login with the =0Ausername "anonymous" and a password of = your e-mail address. After =0Alogging in, type "cd internet-drafts" and the= n =0A"get draft-ietf-mip4-nemo-v4-base-00.txt".=0A=0AA list of Internet-Dra= fts directories can be found in=0Ahttp://www.ietf.org/shadow.html =0Aor ftp= ://ftp.ietf.org/ietf/1shadow-sites.txt=0A=0AInternet-Drafts can also be obt= ained by e-mail.=0A=0ASend a message to:=0A mailserv@ietf.org.=0AIn the = body type:=0A "FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt= ".=0A =0ANOTE: The mail server at ietf.org can return the document in= =0A MIME-encoded form by using the "mpack" utility. To use this=0A f= eature, insert the command "ENCODING mime" before the "FILE"=0A command.= To decode the response(s), you will need "munpack" or=0A a MIME-compli= ant mail reader. Different MIME-compliant mail readers=0A exhibit diffe= rent behavior, especially when dealing with=0A "multipart" MIME messages= (i.e. documents which have been split=0A up into multiple messages), so= check your local documentation on=0A how to manipulate these messages.= =0A=0ABelow is the data which will enable a MIME compliant mail reader=0Aim= plementation to automatically retrieve the ASCII version of the=0AInternet-= Draft.=0A-- =0AMip4 mailing list: Mip4@ietf.org=0A Web interface: https:= //www1.ietf.org/mailman/listinfo/mip4=0A Charter page: http://www.ietf.= org/html.charters/mip4-charter.html=0ASupplemental site: http://www.mip4.or= g/ --0-1655162085-1172857257=:52161 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Kent,
=0A
  Just out of cur= iousity, hasn't this protocol been productized already? Such a thing&n= bsp;was mentioned when NEMO WG was being formed and that was why NEMO WG co= ncentrated on IPv6 based solution?
=0A
 
=0A
Regards,
=0A
 
=0A
--behcet

=0A
----- Original Message ----
From: "Internet-Drafts@ietf.o= rg" <Internet-Drafts@ietf.org>
To: i-d-announce@ietf.org
Cc: mi= p4@ietf.org
Sent: Thursday, March 1, 2007 2:50:03 PM
Subject: [Mip4] = I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

=0A
A New Interne= t-Draft is available from the on-line Internet-Drafts
directories.
T= his draft is a work item of the Mobility for IPv4 Working Group of the IETF= .

    Title      &= nbsp; : IPv4 Network Mobility (NEMO) Protocol
   &nb= sp;Author(s)    : K. Leung, et al.
   = ; Filename    : draft-ietf-mip4-nemo-v4-base-00.tx= t
    Pages       = ; : 1
    Date     &nb= sp;  : 2007-3-1
    

   T= his document describes a protocol for supporting Mobile Networks
 &= nbsp; between a Mobile Router and a Home Agent by extending the Mobile IPv4=
   protocol.  A Mobile Router is responsible for th= e mobility of one or
   more network segments or subnets moving together.  The Mobile Router
   hides its mo= bility 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.

 &n= bsp; Extensions to Mobile IPv4 are introduced to support Mobile Networks.

A URL for this Internet-Draft is:
htt= p://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt
To remove yourself from the I-D Announcement list, send a message to <= BR>i-d-announce-request@ietf.org with the word unsubscribe in the body of <= BR>the message.
You can also visit https://www1.ietf.org/mailman/l= istinfo/I-D-announce
to change your subscription settings.

I= nternet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" a= nd a password of your e-mail address. After
logging in, type "cd intern= et-drafts" and then
"get draft-ietf-mip4-nemo-v4-base-00.txt".

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

Internet-Drafts c= an also be obtained by e-mail.

Send a message to:
  &nb= sp; mailserv@ietf.org.
In the body type:
    = ;"FILE /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt".
 &nbs= p;  
NOTE:    The mail server at ietf.org = can return the document in
    MIME-encoded form by = using the "mpack" utility.  To use this
   &nbs= p;feature, insert the command "ENCODING mime" before the "FILE"
    command.  To decode the respon= se(s), you will need "munpack" or
    a MIME-complia= nt mail reader.  Different MIME-compliant mail readers
 &= nbsp;  exhibit different behavior, especially when dealing with    "multipart" MIME messages (i.e. documents which h= ave been split
    up into multiple messages), so ch= eck your local documentation on
    how to manipulat= e these messages.

Below is the data which will enable a MIME complia= nt mail reader
implementation to automatically retrieve the ASCII versio= n of the
Internet-Draft.
=0A=0A

--0-1655162085-1172857257=:52161-- --===============1547569425== 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/ --===============1547569425==-- From mip4-bounces@ietf.org Fri Mar 02 13:00:59 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNC3k-0003K0-Cl; Fri, 02 Mar 2007 13:00:48 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNC3j-0003BE-9Y for mip4@ietf.org; Fri, 02 Mar 2007 13:00:47 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNC3h-0003IG-Eh for mip4@ietf.org; Fri, 02 Mar 2007 13:00:47 -0500 Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-5.cisco.com with ESMTP; 02 Mar 2007 10:00:41 -0800 X-IronPort-AV: i="4.14,243,1170662400"; d="scan'208,217"; a="395985161:sNHT111461960" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l22I0epF023693; Fri, 2 Mar 2007 10:00:40 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l22I0enF027066; Fri, 2 Mar 2007 10:00:40 -0800 (PST) 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); Fri, 2 Mar 2007 10:00:39 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Date: Fri, 2 Mar 2007 10:00:39 -0800 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5203698DF0@xmb-sjc-235.amer.cisco.com> In-Reply-To: <530304.52161.qm@web60317.mail.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Thread-Index: Acdc8fFFQHK1K9J5SAWyhvlsVXLuPAAAmjDw From: "Kent Leung \(kleung\)" To: "Behcet Sarikaya" X-OriginalArrivalTime: 02 Mar 2007 18:00:39.0994 (UTC) FILETIME=[B01EE9A0:01C75CF4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=13247; t=1172858440; x=1173722440; c=relaxed/simple; s=sjdkim8002; 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 |Subject:=20RE=3A=20[Mip4]=20I-D=20ACTION=3Adraft-ietf-mip4-nemo-v4-base- 00.txt |Sender:=20; bh=T5nS0X9r7+z+5ke9igSxrpG6PcqubfmIGzts/Cyp1DY=; b=BRkPPjduPLFLytpYqQc1RKxjfMyqr6BBruah/ZJGYfWqcU1A1JS3oXzKYOVBhHJWUNbYJ1Ab 4P1QkSLuAkSKLzFmK5EghUhnwuhQL93cOUZi/B9EEQ88eR+J2cxn0goe; Authentication-Results: sj-dkim-8; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim8002 verified; ); X-Spam-Score: 0.1 (/) X-Scan-Signature: bd8a74b81c71f965ca7918b90d1c49c0 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0647835094==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============0647835094== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C75CF4.AFED37BE" This is a multi-part message in MIME format. ------_=_NextPart_001_01C75CF4.AFED37BE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Behcet. NEMOv4 is needed for interoperability. =20 MIP4 WG charter: =20 11. MIPv4 Moving Network Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good=20 reason to do this extension in the mip4 working group. The working group will take on the MIPv4 network mobility internet draft and progress it along the standards track. In addition, the working group will take up extensions to the basic MIPv4 moving network support in the areas of dynamic prefix assignment and foreign agent support. =20 Kent ________________________________ From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20 Sent: Friday, March 02, 2007 9:41 AM To: Kent Leung (kleung) Cc: mip4@ietf.org Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Hi Kent, Just out of curiousity, hasn't this protocol been productized already? Such a thing was mentioned when NEMO WG was being formed and that was why NEMO WG concentrated on IPv6 based solution? =20 Regards, =20 --behcet ----- Original Message ---- From: "Internet-Drafts@ietf.org" To: i-d-announce@ietf.org Cc: mip4@ietf.org Sent: Thursday, March 1, 2007 2:50:03 PM Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt A New Internet-Draft is available from the on-line Internet-Drafts=20 directories. This draft is a work item of the Mobility for IPv4 Working Group of the IETF. Title : IPv4 Network Mobility (NEMO) Protocol Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-00.txt Pages : 1 Date : 2007-3-1 =20 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-00.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message.=20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then=20 "get draft-ietf-mip4-nemo-v4-base-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 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-00.txt". =20 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. --=20 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_001_01C75CF4.AFED37BE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Behcet.  NEMOv4 is needed for=20 interoperability.
 
MIP4 WG=20 charter:
 
11. MIPv4 = Moving Network=20 Support

The Network Mobility (nemo) working group deals with the = problem=20 of
mobility of a whole network, such as might exist inside a=20 vehicle,
train, or airplane. The nemo working group has developed=20 draft
specifications for both IPv6 and IPv4 mobile networks. However, = it=20 has
been recognized that the IPv4 version of the protocol can be = viewed=20 as
an extension of the basic Mobile IPv4 protocol, and there is good=20
reason
to do this extension in the mip4 working group. The = working group=20 will
take on the MIPv4 network mobility internet draft and progress = it=20 along
the standards track. In addition, the working group will take=20 up
extensions to the basic MIPv4 moving network support in the areas=20 of
dynamic prefix assignment and foreign agent = support.
 
Kent

From: Behcet Sarikaya=20 [mailto:behcetsarikaya@yahoo.com]
Sent: Friday, March 02, = 2007 9:41=20 AM
To: Kent Leung (kleung)
Cc:=20 mip4@ietf.org
Subject: Re: [Mip4] I-D=20 ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

Hi=20 Kent,
 =20 Just out of curiousity, hasn't this protocol been productized = already? Such=20 a thing was mentioned when NEMO WG was being formed and that was = why NEMO=20 WG concentrated on IPv6 based solution?
  Regards,   --behcet

-----=20 Original Message ----
From: "Internet-Drafts@ietf.org"=20 <Internet-Drafts@ietf.org>
To: i-d-announce@ietf.org
Cc:=20 mip4@ietf.org
Sent: Thursday, March 1, 2007 2:50:03 PM
Subject: = [Mip4] I-D=20 ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

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

    Title     &= nbsp;  :=20 IPv4 Network Mobility (NEMO)=20 Protocol
    Author(s)    : = K. Leung,=20 et al.
    Filename    :=20 draft-ietf-mip4-nemo-v4-base-00.txt
    Pages = ;       :=20 1
    Date      &nbs= p; :=20 2007-3-1
    

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

   Extensions = to Mobile=20 IPv4 are introduced to support Mobile Networks.


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

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

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

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

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

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

Below is the data which will enable = a MIME=20 compliant mail reader
implementation to automatically retrieve the = ASCII=20 version of the
Internet-Draft.
--
Mip4 mailing list: = Mip4@ietf.org
    Web=20 interface: https://www1.ietf.org/mailman/listinfo/mip4
 =    =20 Charter page: http://www.ietf.org/html.charters/mip4-charter.htmlSupplemental=20 site: http://www.mip4.org/

------_=_NextPart_001_01C75CF4.AFED37BE-- --===============0647835094== 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/ --===============0647835094==-- From mip4-bounces@ietf.org Fri Mar 02 14:37:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNDYq-00059s-Lr; Fri, 02 Mar 2007 14:37:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNDYp-00059L-C6 for mip4@ietf.org; Fri, 02 Mar 2007 14:36:59 -0500 Received: from web60320.mail.yahoo.com ([209.73.178.128]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HNDYn-0000Ol-Ny for mip4@ietf.org; Fri, 02 Mar 2007 14:36:59 -0500 Received: (qmail 10828 invoked by uid 60001); 2 Mar 2007 19:36:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=qTLSbo8LEje4liCtQlG8qtuj4aYbCxAuXyYgPGR9329YjAGKZnh1A0R2g53ueNrUCH0CPJsVLqGj0juEMqrNBg6EKtcP6ywGPxYiYnHyg7FSvIRKZ8v6vuEnsm3P7jrdNDVZw+oDduQPWJNL47Rs+9qrzdbT22Zg2o9GeiUGTk8=; X-YMail-OSG: dIni1aUVM1nAWJaLdolIAMd2KT8zLH54nVEnvqCx1LrlfUi1uLqdd4PNvKnCdOc2ndog.xV6p9SNHIGyGOFYXc601TR1bS3wMaNPR8LVIInumFoURxBDISRrO8PO2bQE_c9sosS.OEVaE_wP Received: from [206.16.17.212] by web60320.mail.yahoo.com via HTTP; Fri, 02 Mar 2007 11:36:57 PST X-Mailer: YahooMailRC/468 YahooMailWebService/0.6.132.8 Date: Fri, 2 Mar 2007 11:36:57 -0800 (PST) From: Behcet Sarikaya Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt To: "Kent Leung \(kleung\)" MIME-Version: 1.0 Message-ID: <520259.10196.qm@web60320.mail.yahoo.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Behcet Sarikaya List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0721147208==" Errors-To: mip4-bounces@ietf.org --===============0721147208== Content-Type: multipart/alternative; boundary="0-987072498-1172864217=:10196" --0-987072498-1172864217=:10196 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi Kent,=0A =0A Shouldn't it be the other way around, i.e. interoperabili= ty is tested based on the standard spec?=0A=0AIt seems something went wrong= but I don't know what.=0A=0ARegards,=0A=0A--behcet=0A=0A----- Original Mes= sage ----=0AFrom: Kent Leung (kleung) =0ATo: Behcet Sarik= aya =0ACc: mip4@ietf.org=0ASent: Friday, March 2, 2007 1= 2:00:39 PM=0ASubject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00= .txt=0A=0A=0AHi Behcet. NEMOv4 is needed for interoperability.=0A =0AMIP4 = WG charter:=0A =0A11. MIPv4 Moving Network Support=0A=0AThe Network Mobilit= y (nemo) working group deals with the problem of=0Amobility of a whole netw= ork, such as might exist inside a vehicle,=0Atrain, or airplane. The nemo w= orking group has developed draft=0Aspecifications for both IPv6 and IPv4 mo= bile networks. However, it has=0Abeen recognized that the IPv4 version of t= he protocol can be viewed as=0Aan extension of the basic Mobile IPv4 protoc= ol, and there is good =0Areason=0Ato do this extension in the mip4 working = group. The working group will=0Atake on the MIPv4 network mobility internet= draft and progress it along=0Athe standards track. In addition, the workin= g group will take up=0Aextensions to the basic MIPv4 moving network support= in the areas of=0Adynamic prefix assignment and foreign agent support.=0A= =0A =0AKent=0A=0A=0A=0A=0AFrom: Behcet Sarikaya [mailto:behcetsarikaya@yaho= o.com] =0ASent: Friday, March 02, 2007 9:41 AM=0ATo: Kent Leung (kleung)=0A= Cc: mip4@ietf.org=0ASubject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-= base-00.txt=0A=0A=0AHi Kent,=0A Just out of curiousity, hasn't this protoc= ol been productized already? Such a thing was mentioned when NEMO WG was be= ing formed and that was why NEMO WG concentrated on IPv6 based solution?=0A= =0ARegards,=0A =0A--behcet=0A=0A=0A----- Original Message ----=0AFrom: "In= ternet-Drafts@ietf.org" =0ATo: i-d-announce@ietf.= org=0ACc: mip4@ietf.org=0ASent: Thursday, March 1, 2007 2:50:03 PM=0ASubjec= t: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt=0A=0A=0AA New Inte= rnet-Draft is available from the on-line Internet-Drafts =0Adirectories.=0A= This draft is a work item of the Mobility for IPv4 Working Group of the IET= F.=0A=0A Title : IPv4 Network Mobility (NEMO) Protocol=0A Auth= or(s) : K. Leung, et al.=0A Filename : draft-ietf-mip4-nemo-v4-bas= e-00.txt=0A Pages : 1=0A Date : 2007-3-1=0A =0A=0A = This document describes a protocol for supporting Mobile Networks=0A bet= ween a Mobile Router and a Home Agent by extending the Mobile IPv4=0A pro= tocol. A Mobile Router is responsible for the mobility of one or=0A more= network segments or subnets moving together. The Mobile Router=0A hides= its mobility from the nodes on the mobile network. The nodes=0A on the = Mobile Network may be fixed in relationship to the Mobile=0A Router and m= ay not have any mobility function.=0A=0A Extensions to Mobile IPv4 are in= troduced to support Mobile Networks.=0A=0A=0AA URL for this Internet-Draft = is:=0Ahttp://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v4-base-00.t= xt=0A=0ATo remove yourself from the I-D Announcement list, send a message t= o =0Ai-d-announce-request@ietf.org with the word unsubscribe in the body of= =0Athe message. =0AYou can also visit https://www1.ietf.org/mailman/listin= fo/I-D-announce =0Ato change your subscription settings.=0A=0AInternet-Draf= ts are also available by anonymous FTP. Login with the =0Ausername "anonymo= us" and a password of your e-mail address. After =0Alogging in, type "cd in= ternet-drafts" and then =0A"get draft-ietf-mip4-nemo-v4-base-00.txt".=0A=0A= A list of Internet-Drafts directories can be found in=0Ahttp://www.ietf.org= /shadow.html =0Aor ftp://ftp.ietf.org/ietf/1shadow-sites.txt=0A=0AInternet-= Drafts can also be obtained by e-mail.=0A=0ASend a message to:=0A mailse= rv@ietf.org.=0AIn the body type:=0A "FILE /internet-drafts/draft-ietf-mi= p4-nemo-v4-base-00.txt".=0A =0ANOTE: The mail server at ietf.org can = return the document in=0A MIME-encoded form by using the "mpack" utility= . To use this=0A feature, insert the command "ENCODING mime" before the= "FILE"=0A command. To decode the response(s), you will need "munpack" = or=0A a MIME-compliant mail reader. Different MIME-compliant mail reade= rs=0A exhibit different behavior, especially when dealing with=0A "mu= ltipart" MIME messages (i.e. documents which have been split=0A up into = multiple messages), so check your local documentation on=0A how to manip= ulate these messages.=0A=0ABelow is the data which will enable a MIME compl= iant mail reader=0Aimplementation to automatically retrieve the ASCII versi= on of the=0AInternet-Draft.=0A-- =0AMip4 mailing list: Mip4@ietf.org=0A = Web interface: https://www1.ietf.org/mailman/listinfo/mip4=0A Charter p= age: http://www.ietf.org/html.charters/mip4-charter.html=0ASupplemental sit= e: http://www.mip4.org/ --0-987072498-1172864217=:10196 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Kent,
=0A
 
  Shou= ldn't it be the other way around, i.e. interoperability is tested based on = the standard spec?
=0A

It seems something went wrong but = I don't know what.
=0A
 
=0A
Regards,=0A
 
=0A
--behcet
=0A
 =0A
----- Original Message ----
From: Kent Leung (kleung) &l= t;kleung@cisco.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
= Cc: mip4@ietf.org
Sent: Friday, March 2, 2007 12:00:39 PM
Subject: RE= : [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

=0A
Hi Behcet.  NEMOv4 is needed for interoperabilit= y.
=0A
 =
=0A
MIP4 = WG charter:
=0A
&nbs= p;
=0A
11.= MIPv4 Moving Network Support

The Network Mobility (nemo) working gr= oup deals with the problem of
mobility of a whole network, such as might= exist inside a vehicle,
train, or airplane. The nemo working group has = developed draft
specifications for both IPv6 and IPv4 mobile networks. H= owever, it has
been recognized that the IPv4 version of the protocol can= be viewed as
an extension of the basic Mobile IPv4 protocol, and there = is good
reason
to do this extension in the mip4 working group. The w= orking group will
take on the MIPv4 network mobility internet draft and = progress it along
the standards track. In addition, the working group wi= ll take up
extensions to the basic MIPv4 moving network support in the a= reas of
dynamic prefix assignment and foreign agent support.
<= /DIV>=0A
 
=0A
Kent

=0A
=0A
=0AFrom: Behcet Sarikaya [mailto:behcetsarika= ya@yahoo.com]
Sent: Friday, March 02, 2007 9:41 AM
To:= Kent Leung (kleung)
Cc: mip4@ietf.org
Subject: Re: [Mi= p4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

=0A<= DIV>
=0A
=0A
Hi Kent,
=0A
  Just = out of curiousity, hasn't this protocol been productized already? Such= a thing was mentioned when NEMO WG was being formed and that was why = NEMO WG concentrated on IPv6 based solution?
=0A
 
= =0A
Regards,
=0A
 
=0A
--behcet
=0A
----- Original Message ----
From: "Internet-Dra= fts@ietf.org" <Internet-Drafts@ietf.org>
To: i-d-announce@ietf.org=
Cc: mip4@ietf.org
Sent: Thursday, March 1, 2007 2:50:03 PM
Subjec= t: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

=0A
A N= ew Internet-Draft is available from the on-line Internet-Drafts
directo= ries.
This draft is a work item of the Mobility for IPv4 Working Group o= f the IETF.

    Title    &nb= sp;   : IPv4 Network Mobility (NEMO) Protocol
  = ;  Author(s)    : K. Leung, et al.
 &= nbsp;  Filename    : draft-ietf-mip4-nemo-v4-= base-00.txt
    Pages     &= nbsp;  : 1
    Date    = ;    : 2007-3-1
    

&nbs= p;  This document describes a protocol for supporting Mobile Networks<= BR>   between a Mobile Router and a Home Agent by extending the M= obile IPv4
   protocol.  A Mobile Router is responsi= ble for the mobility of one or
   more network segments or sub= nets moving together.  The Mobile Router
   hides its mo= bility 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.

 &n= bsp; 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-bas= e-00.txt

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

Internet-Drafts are also available by anonymous FTP. Logi= n with the
username "anonymous" and a password of your e-mail address. = After
logging in, type "cd internet-drafts" and then
"get draft-iet= f-mip4-nemo-v4-base-00.txt".

A list of Internet-Drafts directories c= an 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-00.txt".
    
NOTE:=     The mail server at ietf.org can return the document= in
    MIME-encoded form by using the "mpack" utili= ty.  To use this
    feature, insert the c= ommand "ENCODING mime" before the "FILE"
    command.  To = decode the response(s), you will need "munpack" or
   &nb= sp;a MIME-compliant mail reader.  Different MIME-compliant mail r= eaders
    exhibit different behavior, especially wh= en 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 enab= le a MIME compliant mail reader
implementation to automatically retrieve= the ASCII version of the
Internet-Draft.
=0A
--
Mip4 maili= ng list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
   &nbs= p; Charter page: http://www.ietf.org/html.charters/mip4= -charter.html
Supplemental site: http://www.mip4.org/
=0A

=0A

--0-987072498-1172864217=:10196-- --===============0721147208== 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/ --===============0721147208==-- From mip4-bounces@ietf.org Fri Mar 02 15:41:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEZf-0006Hi-3X; Fri, 02 Mar 2007 15:41:55 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEZe-0006Hd-2j for mip4@ietf.org; Fri, 02 Mar 2007 15:41:54 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNEZc-0000XZ-2y for mip4@ietf.org; Fri, 02 Mar 2007 15:41:54 -0500 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 02 Mar 2007 12:41:51 -0800 X-IronPort-AV: i="4.14,244,1170662400"; d="scan'208,217"; a="44669516:sNHT119895408" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l22Kfpfe029578; Fri, 2 Mar 2007 12:41:51 -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 l22KfeHC018509; Fri, 2 Mar 2007 12:41:51 -0800 (PST) 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); Fri, 2 Mar 2007 12:41:39 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Date: Fri, 2 Mar 2007 12:41:34 -0800 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC5203698F51@xmb-sjc-235.amer.cisco.com> In-Reply-To: <520259.10196.qm@web60320.mail.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Thread-Index: AcddAilzkJhWQSGUSemUzlMCWyg9vgACJycA From: "Kent Leung \(kleung\)" To: "Behcet Sarikaya" X-OriginalArrivalTime: 02 Mar 2007 20:41:39.0982 (UTC) FILETIME=[2DEC1AE0:01C75D0B] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=16836; t=1172868111; x=1173732111; c=relaxed/simple; s=sjdkim1004; 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 |Subject:=20RE=3A=20[Mip4]=20I-D=20ACTION=3Adraft-ietf-mip4-nemo-v4-base- 00.txt |Sender:=20; bh=NOjDOdJttDmeuyXYZcp42PCC0GjE9eizK5WFXToRxKY=; b=QDQFgOOTNhtqfVw9NxRdf2h62s7RgsbdbsHkM2vGiCCWjRslK1BWAW86bx+qKn9meQfrEsT7 HNCvoeTXw4AfTzd7PTtFIT2ZRvKraYHV3fc2T18RTDeU9CVFEMX2sjZULljop6K4HhDFbM1r2t gRRdG0d2hlTQRnnk35/8sgk00=; Authentication-Results: sj-dkim-1; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); X-Spam-Score: 0.1 (/) X-Scan-Signature: 442d80051e0361a34f3560325c4a7092 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1295330875==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============1295330875== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C75D0B.2DBEA018" This is a multi-part message in MIME format. ------_=_NextPart_001_01C75D0B.2DBEA018 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Behcet. That's why the draft is published for standardization. So vendors/implementors can interoperate in accordance to the spec. =20 Kent ________________________________ From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20 Sent: Friday, March 02, 2007 11:37 AM To: Kent Leung (kleung) Cc: mip4@ietf.org Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Hi Kent, Shouldn't it be the other way around, i.e. interoperability is tested based on the standard spec? It seems something went wrong but I don't know what. =20 Regards, =20 --behcet =20 ----- Original Message ---- From: Kent Leung (kleung) To: Behcet Sarikaya Cc: mip4@ietf.org Sent: Friday, March 2, 2007 12:00:39 PM Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Hi Behcet. NEMOv4 is needed for interoperability. =20 MIP4 WG charter: =20 11. MIPv4 Moving Network Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good=20 reason to do this extension in the mip4 working group. The working group will take on the MIPv4 network mobility internet draft and progress it along the standards track. In addition, the working group will take up extensions to the basic MIPv4 moving network support in the areas of dynamic prefix assignment and foreign agent support. =20 Kent ________________________________ From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20 Sent: Friday, March 02, 2007 9:41 AM To: Kent Leung (kleung) Cc: mip4@ietf.org Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt Hi Kent, Just out of curiousity, hasn't this protocol been productized already? Such a thing was mentioned when NEMO WG was being formed and that was why NEMO WG concentrated on IPv6 based solution? =20 Regards, =20 --behcet ----- Original Message ---- From: "Internet-Drafts@ietf.org" To: i-d-announce@ietf.org Cc: mip4@ietf.org Sent: Thursday, March 1, 2007 2:50:03 PM Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt A New Internet-Draft is available from the on-line Internet-Drafts=20 directories. This draft is a work item of the Mobility for IPv4 Working Group of the IETF. Title : IPv4 Network Mobility (NEMO) Protocol Author(s) : K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-00.txt Pages : 1 Date : 2007-3-1 =20 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-00.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of=20 the message.=20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the=20 username "anonymous" and a password of your e-mail address. After=20 logging in, type "cd internet-drafts" and then=20 "get draft-ietf-mip4-nemo-v4-base-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 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-00.txt". =20 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. --=20 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_001_01C75D0B.2DBEA018 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Behcet.  That's why the draft is = published for=20 standardization.  So vendors/implementors can interoperate in = accordance to=20 the spec.
 
Kent

From: Behcet Sarikaya=20 [mailto:behcetsarikaya@yahoo.com]
Sent: Friday, March 02, = 2007 11:37=20 AM
To: Kent Leung (kleung)
Cc:=20 mip4@ietf.org
Subject: Re: [Mip4] I-D=20 ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

Hi=20 Kent,
=20
  Shouldn't it be the other way around, i.e. interoperability = is tested=20 based on the standard spec?

It=20 seems something went wrong but I don't know what.   Regards,   --behcet   -----=20 Original Message ----
From: Kent Leung (kleung)=20 <kleung@cisco.com>
To: Behcet Sarikaya = <sarikaya@ieee.org>
Cc:=20 mip4@ietf.org
Sent: Friday, March 2, 2007 12:00:39 PM
Subject: RE: = [Mip4]=20 I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

Hi Behcet.  NEMOv4 is needed for=20 interoperability.
 
MIP4 WG=20 charter:
 
11. MIPv4 = Moving Network=20 Support

The Network Mobility (nemo) working group deals with the = problem=20 of
mobility of a whole network, such as might exist inside a=20 vehicle,
train, or airplane. The nemo working group has developed=20 draft
specifications for both IPv6 and IPv4 mobile networks. However, = it=20 has
been recognized that the IPv4 version of the protocol can be = viewed=20 as
an extension of the basic Mobile IPv4 protocol, and there is good=20
reason
to do this extension in the mip4 working group. The = working group=20 will
take on the MIPv4 network mobility internet draft and progress = it=20 along
the standards track. In addition, the working group will take=20 up
extensions to the basic MIPv4 moving network support in the areas=20 of
dynamic prefix assignment and foreign agent = support.
 
Kent

From: Behcet Sarikaya=20 [mailto:behcetsarikaya@yahoo.com]
Sent: Friday, March 02, = 2007 9:41=20 AM
To: Kent Leung (kleung)
Cc:=20 mip4@ietf.org
Subject: Re: [Mip4] I-D=20 ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

Hi=20 Kent,  =20 Just out of curiousity, hasn't this protocol been productized = already? Such=20 a thing was mentioned when NEMO WG was being formed and that was = why NEMO=20 WG concentrated on IPv6 based solution?   Regards,   --behcet

-----=20 Original Message ----
From: "Internet-Drafts@ietf.org"=20 <Internet-Drafts@ietf.org>
To: i-d-announce@ietf.org
Cc:=20 mip4@ietf.org
Sent: Thursday, March 1, 2007 2:50:03 PM
Subject: = [Mip4] I-D=20 ACTION:draft-ietf-mip4-nemo-v4-base-00.txt

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

    Title     &= nbsp;  :=20 IPv4 Network Mobility (NEMO)=20 Protocol
    Author(s)    : = K. Leung,=20 et al.
    Filename    :=20 draft-ietf-mip4-nemo-v4-base-00.txt
    Pages = ;       :=20 1
    Date      &nbs= p; :=20 2007-3-1
    

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

   Extensions = to Mobile=20 IPv4 are introduced to support Mobile Networks.


A URL for = this=20 Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemo-v= 4-base-00.txt

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

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

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

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

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

Below is the data which will enable = a MIME=20 compliant mail reader
implementation to automatically retrieve the = ASCII=20 version of the
Internet-Draft.
--
Mip4 mailing list: = Mip4@ietf.org
    Web=20 interface: https://www1.ietf.org/mailman/listinfo/mip4
 &= nbsp;  =20 Charter page: http://www.ietf.org/html.charters/mip4-charter.htmlSupplemental=20 site: http://www.mip4.org/


------_=_NextPart_001_01C75D0B.2DBEA018-- --===============1295330875== 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/ --===============1295330875==-- From mip4-bounces@ietf.org Fri Mar 02 15:51:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEip-0002jP-GK; Fri, 02 Mar 2007 15:51:23 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEha-0000Th-Bc; Fri, 02 Mar 2007 15:50:06 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNEhY-0001Ru-T8; Fri, 02 Mar 2007 15:50:06 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 65893329F3; Fri, 2 Mar 2007 20:50:04 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HNEhY-0002Zb-8H; Fri, 02 Mar 2007 15:50:04 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 02 Mar 2007 15:50:04 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-generic-notification-message-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : Generic Notification Message for Mobile IPv4 Author(s) : H. Deng, et al. Filename : draft-ietf-mip4-generic-notification-message-00.txt Pages : 24 Date : 2007-3-2 This document specifies protocol enhancements that allow Mobile IPv4 entities to send and receive explicit notification messages using a new Mobile IPv4 message type designed for this purpose. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-generic-notification-message-00.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-generic-notification-message-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-3-2143802.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-generic-notification-message-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-2143802.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 Mar 02 16:45:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNFZO-00049S-Fh; Fri, 02 Mar 2007 16:45:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNEi1-0001Gg-F4; Fri, 02 Mar 2007 15:50:33 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HNEi1-0003Oc-0h; Fri, 02 Mar 2007 15:50:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id CB9272AD5B; Fri, 2 Mar 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HNEhW-0002WE-I1; Fri, 02 Mar 2007 15:50: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: Date: Fri, 02 Mar 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-message-string-ext-03.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : Mobile IPv4 Message String Extension Author(s) : V. Sastry, et al. Filename : draft-ietf-mip4-message-string-ext-03.txt Pages : 12 Date : 2007-3-2 This document specifies a new extension for use in Mobile IPv4. This extension can be added by the Home Agent and the Foreign Agent to Registration Reply messages. This extension carries a text string that is intended for the user of the Mobile Node. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-message-string-ext-03.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-message-string-ext-03.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-message-string-ext-03.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: <2007-3-2112558.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-message-string-ext-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-message-string-ext-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-2112558.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 Mon Mar 05 03:51:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8uT-0002jH-AE; Mon, 05 Mar 2007 03:51:09 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8uR-0002iu-5F for mip4@ietf.org; Mon, 05 Mar 2007 03:51:07 -0500 Received: from mail119.messagelabs.com ([216.82.241.179]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HO8uP-0006uJ-Pm for mip4@ietf.org; Mon, 05 Mar 2007 03:51:07 -0500 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-4.tower-119.messagelabs.com!1173084665!16106997!1 X-StarScan-Version: 5.5.10.7.1; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 2192 invoked from network); 5 Mar 2007 08:51:05 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-4.tower-119.messagelabs.com with SMTP; 5 Mar 2007 08:51:05 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l258p0NV015585; Mon, 5 Mar 2007 01:51:05 -0700 (MST) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id l258ooWo018471; Mon, 5 Mar 2007 02:50:54 -0600 (CST) Message-ID: <45EBD9E7.1020407@gmail.com> Date: Mon, 05 Mar 2007 09:50:47 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Behcet Sarikaya Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt References: <530304.52161.qm@web60317.mail.yahoo.com> In-Reply-To: <530304.52161.qm@web60317.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Cc: "Kent Leung \(kleung\)" , mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Behcet Sarikaya wrote: > Hi Kent, Just out of curiousity, hasn't this protocol been > productized already? Such a thing was mentioned when NEMO WG was > being formed and that was why NEMO WG concentrated on IPv6 based > solution? Hi Behcet, good question. We started the NEMOv4 document effort more than 2 years ago, an activity that was publicly visible mostly in the NEMO Working Group. At that point not only one implementation existed but at least two, and they were incompatible. Since then the document evolved through several discussions, its essential part (message formats) changed substantially, and at least some implementations were updated accordingly. Additionally, there exist today a public patch to a packet analyzer that interprets the NEMOv4 messages according to this document. When the NEMO WG was started, a few comments indicated that some were willing to take on IPv4 work, and that happened. NEMO WG concentrating today mostly on IPv6 work is a will of some of its members, not all. That to answer quickly the question. But it seems you're trying to suggest something with that question... what exactly is it? Alex > > Regards, > > --behcet > > ----- Original Message ---- From: "Internet-Drafts@ietf.org" > To: i-d-announce@ietf.org Cc: > mip4@ietf.org Sent: Thursday, March 1, 2007 2:50:03 PM Subject: > [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt > > 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 : IPv4 Network Mobility (NEMO) Protocol Author(s) : > K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-00.txt > Pages : 1 Date : 2007-3-1 > > > 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-00.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-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html or > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: mailserv@ietf.org. In the body type: "FILE > /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this feature, > insert the command "ENCODING mime" before the "FILE" command. To > decode the response(s), you will need "munpack" or a MIME-compliant > mail reader. Different MIME-compliant mail readers exhibit different > behavior, especially when dealing with "multipart" MIME messages > (i.e. documents which have been split up into multiple messages), so > check your local documentation on how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. -- 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/ From mip4-bounces@ietf.org Mon Mar 05 03:52:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8vP-0003Dv-9f; Mon, 05 Mar 2007 03:52:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HO8vN-0003C4-KB for mip4@ietf.org; Mon, 05 Mar 2007 03:52:05 -0500 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HO8vM-0007Bs-2a for mip4@ietf.org; Mon, 05 Mar 2007 03:52:05 -0500 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-3.tower-128.messagelabs.com!1173084722!4702035!1 X-StarScan-Version: 5.5.10.7.1; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 24932 invoked from network); 5 Mar 2007 08:52:03 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-3.tower-128.messagelabs.com with SMTP; 5 Mar 2007 08:52:03 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l258q1mf015869; Mon, 5 Mar 2007 01:52:01 -0700 (MST) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id l258pnnU018893; Mon, 5 Mar 2007 02:51:54 -0600 (CST) Message-ID: <45EBDA23.7040402@gmail.com> Date: Mon, 05 Mar 2007 09:51:47 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Alexandru Petrescu Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt References: <520259.10196.qm@web60320.mail.yahoo.com> <45EBD7C8.4060003@motorola.com> In-Reply-To: <45EBD7C8.4060003@motorola.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d Cc: Behcet Sarikaya , mip4@ietf.org, "Kent Leung \(kleung\)" X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Behcet Sarikaya wrote: > Hi Kent, > > Shouldn't it be the other way around, i.e. interoperability is tested > based on the standard spec? Currently the NEMOv4 base protocol is the only stds track document for NEMOv4. Is this what you mean? > It seems something went wrong but I don't know what. I'm trying to identify what you think went wrong, can you explain. The only alternative to NEMOv4 Base spec (this draft) is text in rfc3344 Mobile IPv4 where it is said that mobile networks and Mobile Routers _can_ work with Mobile IPv4. Which is very much true to a certain extent, and it was the starting point for NEMOv4 implementations; but lacking explicit message formats for prefix exchanges it led obviously to interoperability issues, hence this draft. What do you think went wrong, sorry? Alex > > Regards, > > --behcet > > ----- Original Message ---- From: Kent Leung (kleung) > To: Behcet Sarikaya Cc: > mip4@ietf.org Sent: Friday, March 2, 2007 12:00:39 PM Subject: RE: > [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt > > Hi Behcet. NEMOv4 is needed for interoperability. > > MIP4 WG charter: > > 11. MIPv4 Moving Network Support > > The Network Mobility (nemo) working group deals with the problem of > mobility of a whole network, such as might exist inside a vehicle, > train, or airplane. The nemo working group has developed draft > specifications for both IPv6 and IPv4 mobile networks. However, it > has been recognized that the IPv4 version of the protocol can be > viewed as an extension of the basic Mobile IPv4 protocol, and there > is good reason to do this extension in the mip4 working group. The > working group will take on the MIPv4 network mobility internet draft > and progress it along the standards track. In addition, the working > group will take up extensions to the basic MIPv4 moving network > support in the areas of dynamic prefix assignment and foreign agent > support. > > Kent > > ------------------------------------------------------------------------ > *From:* Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com] *Sent:* > Friday, March 02, 2007 9:41 AM *To:* Kent Leung (kleung) *Cc:* > mip4@ietf.org *Subject:* Re: [Mip4] I-D > ACTION:draft-ietf-mip4-nemo-v4-base-00.txt > > Hi Kent, Just out of curiousity, hasn't this protocol been > productized already? Such a thing was mentioned when NEMO WG was > being formed and that was why NEMO WG concentrated on IPv6 based > solution? > > Regards, > > --behcet > > ----- Original Message ---- From: "Internet-Drafts@ietf.org" > To: i-d-announce@ietf.org Cc: > mip4@ietf.org Sent: Thursday, March 1, 2007 2:50:03 PM Subject: > [Mip4] I-D ACTION:draft-ietf-mip4-nemo-v4-base-00.txt > > 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 : IPv4 Network Mobility (NEMO) Protocol Author(s) : > K. Leung, et al. Filename : draft-ietf-mip4-nemo-v4-base-00.txt > Pages : 1 Date : 2007-3-1 > > > 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-00.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-00.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html or > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: mailserv@ietf.org. In the body type: "FILE > /internet-drafts/draft-ietf-mip4-nemo-v4-base-00.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this feature, > insert the command "ENCODING mime" before the "FILE" command. To > decode the response(s), you will need "munpack" or a MIME-compliant > mail reader. Different MIME-compliant mail readers exhibit different > behavior, especially when dealing with "multipart" MIME messages > (i.e. documents which have been split up into multiple messages), so > check your local documentation on how to manipulate these messages. > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. -- 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/ From mip4-bounces@ietf.org Mon Mar 05 16:41:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOKvV-0007bL-HH; Mon, 05 Mar 2007 16:41:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOKvM-0007YS-Sb; Mon, 05 Mar 2007 16:40:52 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOKvL-0006DX-W8; Mon, 05 Mar 2007 16:40:52 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id C923026EB9; Mon, 5 Mar 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HOK8A-0005eW-IC; Mon, 05 Mar 2007 15:50: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: Date: Mon, 05 Mar 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-mobike-connectivity-03.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE Author(s) : V. Devarapalli, P. Eronen Filename : draft-ietf-mip4-mobike-connectivity-03.txt Pages : 15 Date : 2007-3-5 Enterprise users require mobility and secure connectivity when they roam and connect to the services offered in the enterprise. Secure connectivity is required when the user connects to the enterprise from an untrusted network. Mobility is beneficial when the user moves, either inside or outside the enterprise network, and acquires a new IP address. This document describes a solution using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE) to provide secure connectivity and mobility. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-03.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-mobike-connectivity-03.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-mobike-connectivity-03.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: <2007-3-5115258.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-mobike-connectivity-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-mobike-connectivity-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-5115258.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 Mon Mar 05 17:35:34 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOLmI-0008Tu-CG; Mon, 05 Mar 2007 17:35:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOLmG-0008TU-99 for mip4@ietf.org; Mon, 05 Mar 2007 17:35:32 -0500 Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOLlz-00012l-LB for mip4@ietf.org; Mon, 05 Mar 2007 17:35:32 -0500 Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502) id CAEF037FE4; Mon, 5 Mar 2007 23:35:10 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id 7A04C37FC7; Mon, 5 Mar 2007 23:35:10 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 4001A37E44; Mon, 5 Mar 2007 23:35:10 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HOLlk-0001NA-U0; Mon, 05 Mar 2007 23:35:01 +0100 Message-ID: <45EC9B18.3020508@levkowetz.com> Date: Mon, 05 Mar 2007 23:35:04 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Mobile IPv4 Mailing List , mip4-chairs@tools.ietf.org X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: mip4@ietf.org, mip4-chairs@tools.ietf.org X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: Subject: [Mip4] MIP4 agenda for IETF 68, first draft X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0045131943==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0045131943== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF1A07660A07EE44FB208FA9B" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF1A07660A07EE44FB208FA9B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Below is a first draft of an agenda for the MIP4 working group meeting during IETF-68 in Prague. We have a 60 minute slot, which is nearly filled with the proposed agenda items below, but if you would like to request a slot, or would like to suggest changes to the agenda, please speak up, so we can adjust to the best possible use of our time. Regards, Henrik and Pete Mobility for IPv4 WG =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WEDNESDAY, March 21, 2007 1510-1610 Afternoon Session II Roma/Vienna/Madrid =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Henrik Levkowetz Pete McCann AGENDA: 1. Preliminaries 10 min Chairs - Blue sheets - Note takers - Jabber scribe - Agenda bashing 2. Document Status 15 min Chairs 3. NAI-based Home Address Assignment 10 min Kent L draft-paulkandasamy-mobileip-nai-based-home-addres As part of our charter, we have an action to revise the MIPv4 NAI RFC (2794) to reflect implementation experience. This draft is a proposal for a revision, and a candidate for adoption as a workgroup draft addressing this action item. 4. Updates to drafts for NEMO extension to MIPv4 15 min Alexandru George T draft-ietf-mip4-nemo-v4-base-00 draft-ietf-mip4-nemov4-dynamic-00 draft-ietf-mip4-nemov4-fa-00 These drafts have recently been adopted as WG drafts. (The two last ones were submitted too late and will be available after the IETF). The authors will give a status update. 5. Higher Layer Triggers for Low Latency MIPv4 5 min Stephane draft-antoine-mip4-lowlatency-handoff-triggers This document introduces the use of triggers coming from layers higher than the link layer to initiate the Low Latency Handoff in Mobile IPv4 (MIPv4). The draft may be more appropriate for discussion in MIPSHOP, and if a slot has been allocated there, this presentation will be skipped, but if not it will take place in MIP4. =3D=3D=3D=3D=3D=3D= =3D=3D=3D Total time 55 min --------------enigF1A07660A07EE44FB208FA9B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFF7JsYeVhrtTJkXCMRAh8jAKDYEmpDI8nYs/Ra8TUUZajQa25FVACgu0YK Z5U+thW1WRZ9VfL87RQiRdw= =Pio9 -----END PGP SIGNATURE----- --------------enigF1A07660A07EE44FB208FA9B-- --===============0045131943== 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/ --===============0045131943==-- From mip4-bounces@ietf.org Mon Mar 05 17:49:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOLzy-0005an-Bv; Mon, 05 Mar 2007 17:49:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOHm0-0003pS-PM for mip4@ietf.org; Mon, 05 Mar 2007 13:19:00 -0500 Received: from ece.uprm.edu ([136.145.57.24]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HOHlw-0003Sf-64 for mip4@ietf.org; Mon, 05 Mar 2007 13:19:00 -0500 Received: from kejielupc (perazzamac2.ece.uprm.edu [136.145.57.158]) by ece.uprm.edu (Postfix) with SMTP id C3556558CD for ; Mon, 5 Mar 2007 14:18:47 -0400 (AST) Organization: UPR-Mayaguez Message-ID: <27541277f684a8325509d576001331bc@ece.uprm.edu> From: "Kejie Lu" To: Date: Mon, 5 Mar 2007 14:18:45 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21 X-Mailman-Approved-At: Mon, 05 Mar 2007 17:49:41 -0500 Subject: [Mip4] CALL FOR PAPERS MILCOM 2007 (Abstracts Due on Mar. 09) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lukejie@ece.uprm.edu List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ** Apologies if you receive multiple copies of this message ** ** The deadline for submitting the abstracts has been extended to 09 March = 2007 ** ** The link for submitting the unclassified papers is: = https://wams.jspargo.com/milcom07/login.asp ** =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL for PAPERS MILCOM 2007 October 29=9631, 2007 Gaylord Palms Convention Center Orlando, Florida USA Conference Theme:=20 Interoperability: Policy to Performance MILCOM 2007 is soliciting both unclassified and classified papers (up to = DoD Secret) relevant to communications and information processing system = technologies and capabilities that address the 21st century challenges of = National Defense, Homeland Security, Disaster Response and = Interoperability. Industry, academic, and government organizations from = both the U.S. and countries around the globe are invited and encouraged to = participate=2E Important Dates: Abstracts Due: 09 March 2007 Draft Papers Due: 20 April 2007 Author Notification: 25 May 2007 Final Camera Ready Papers Due: 6 July 2007 Suggested technical areas of general interest include but are not limited to: =95 Interoperability =96 Policies and Standards =96 DoD and Federal Agencies =96 State and Local Governments =96 Emergency Grid Communications =96 Coalition Partners =96 Disaster Response =95 Service Oriented Architectures =95 Advanced Communications Technologies =95 Network Management =95 Mobile and Wireless Technologies =95 Radio Systems and Technologies =95 Network Centric Systems and Technologies =95 Applications and Operational Concepts =95 Systems, Programs and Initiatives =95 Information Management and Dissemination =95 Digital Signal Processing =95 Coding =95 Modulation =95 Advanced Waveforms =95 Next Generation Networks and Systems =95 Internet Protocols =95 Link Layer and Cross-Layer Protocols =95 Network Architectures and Routing =95 Transport Protocols and Performance =95 Quality of Service Architectures =95 Design Modeling and Simulation =95 Digital Video Broadcasting and Standards =95 IF/RF Technologies and Techniques =95 Advanced SATCOM systems =95 Airborne Technologies =95 Standards Based Datalinks =95 Mobile Satellite Systems =95 Space Networks and Protocols =95 Wireless Communications =95 Mobile Ad Hoc Networks =95 Computer and Network Security Systems =95 Software Defined Radios and Cognitive Radios =95 Sensor Networks =95 Advanced Antenna Technologies =95 Laser Communications and Optical Networks =95 Tests and Measurements =95 Ultra Wideband =95 Multimedia Communications and Management Technical Program Committee Technical Program Chair Dr. Vitas Mikenas Harris Corporation 321-729-7748 mikenas.milcom2007@harris.com Unclassified Program Chair Dr. Sastri Kota Harris Corporation 408-990-8301 kota.milcom2007@harris.com Classified Program Chair Terry Casto Harris Corporation 321-984-5600 casto.milcom2007@harris.com Panels Program Chair Leo deCardenas Harris Corporation 321-727-6202 decardenas.milcom2007@harris.com Tutorial Program Chair Rich Folio Harris Corporation 321-729-3629 folio.milcom2007@harris.com Unclassified Technical Program Submission Process:=20 The Web-based Abstract Management System (WAMS) (www.milcom.org) is used = to submit abstracts, full papers, and final camera ready papers. During = the abstract submission process, author and password information will need = to be entered and a Paper ID# will be assigned. This Paper ID# and = password will be used to upload papers. The abstract must NOT contain any = ITAR-related, classified, or proprietary information=2E Abstracts will only be used to help define the sessions. The Unclassified = Author=92s Kit provides instructions to authors for preparation of the = full and final manuscripts and the required forms. Full papers will be = reviewed for acceptance only when all appropriate forms have been = completed and received=2E Classified Technical Program Submission Process: All persons wishing to attend and/or participate in the Classified = Technical Program must, at a minimum, possess a current Secret personnel = security clearance and be a U.S. citizen. Non-U.S. originated papers will = NOT be accepted for the Classified Technical Program. All abstracts for = the Classified Technical Program must be unclassified. Please submit a = title and a brief unclassified abstract (up to 2000 characters) of your = intended paper via email to: casto.milcom2007@harris.com. Each submission = requires author name, affiliation, citizenship, address, phone and fax = numbers, email address, and the applicable area. For papers with more than = one author, indicate the point of contact. Do NOT use WAMS to submit = abstracts, full papers, or the final papers for the Classified Technical = Program. All papers for the Classified Technical Program must be prepared = following the instructions and formatting guidelines in the Classified = Author=92s Kit=2E Proposals for Tutorials and Panels:=20 MILCOM 2007 solicits proposals for unclassified half-day tutorials, and = unclassified and classified panels on state-of-the art communications, = networking, and interoperability technologies. The tutorial proposals = should include a brief outline of the tutorial, instructor biography, and = relevant instructor experience. The Unclassified Tutorials Kit provides the applicable forms and the formatting guidelines for the = tutorial material. Please forward your proposals to the MILCOM 2007 = Tutorial Program Chair, Rich Folio, at folio.milcom2007@harris.com=2E Proposals for Panels:=20 The proposals for panels should include a brief outline of the panel = discussion topics, panel participants, and panel moderator along with = their bios. A Panels Kit provides the information about the applicable = forms and the guidelines for the preparation of the panel material. Please = forward your proposals to the MILCOM 2007 Panels Program Chair, Leo = deCardenas, at decardenas.milcom2007@harris.com=2E Tutorials and Panels Important Dates: Proposals Due: 16 March 2007 Notification: 20 April 2007 Material Due: 13 July 2007 For further details and information about MILCOM 2007 please visit = www.milcom.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 Tue Mar 06 03:21:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOUve-00080R-GY; Tue, 06 Mar 2007 03:21:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOUvd-00080M-96 for mip4@ietf.org; Tue, 06 Mar 2007 03:21:49 -0500 Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOUvZ-0004Mw-Q6 for mip4@ietf.org; Tue, 06 Mar 2007 03:21:49 -0500 Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502) id F270438075; Tue, 6 Mar 2007 09:21:44 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP id 8580E38063; Tue, 6 Mar 2007 09:21:44 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 592CA37E48; Tue, 6 Mar 2007 09:21:44 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HOUvL-0001YU-Kg; Tue, 06 Mar 2007 09:21:31 +0100 Message-ID: <45ED2493.6080108@levkowetz.com> Date: Tue, 06 Mar 2007 09:21:39 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Mobile IPv4 Mailing List References: <45EC9B18.3020508@levkowetz.com> In-Reply-To: <45EC9B18.3020508@levkowetz.com> X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: mip4@ietf.org, mip4-chairs@tools.ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] MIP4 agenda for IETF 68, second draft X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0770294040==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0770294040== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig521C751754E41FA38A3793CC" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig521C751754E41FA38A3793CC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi again, We've had some more requests for slots, so here (below) is an updated agenda. Regards, Henrik Mobility for IPv4 WG =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WEDNESDAY, March 21, 2007 1510-1610 Afternoon Session II Roma/Vienna/Madrid =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CHAIRS: Henrik Levkowetz Pete McCann AGENDA: 1. Preliminaries 10 min Chairs - Blue sheets - Note takers - Jabber scribe - Agenda bashing 2. Document Status 15 min Chairs 3. NAI-based Home Address Assignment 10 min Kent L draft-paulkandasamy-mobileip-nai-based-home-addres-01 As part of our charter, we have an action to revise the MIPv4 NAI RFC (2794) to reflect implementation experience. This draft is a proposal for a revision, and a candidate for adoption as a workgroup draft addressing this action item. 4. Updates to drafts for NEMO extension to MIPv4 10 min Alex George T draft-ietf-mip4-nemo-v4-base-00 draft-ietf-mip4-nemov4-dynamic-00 draft-ietf-mip4-nemov4-fa-00 These drafts have recently been adopted as WG drafts. (The two last ones were submitted too late and will be available after the IETF). The authors will give a status update. 5. A MIB for MIPv4 UDP Tunnelling (i.e., NAT Traversal) 5 min Henrik draft-sjostrand-mip4-udptunnel-mib-00 This document defines a MIB for managing the Mobile Node, Foreign Agent and Home Agent when Mobile IP Traversal of Network Address Translation (NAT) Devices are used. 6. Service Selection for Mobile IPv4 5 min Jouni draft-korhonen-mip4-service-00 This document describes a Service Selection Extension for Mobile =20 IPv4 that is intended to assist home agents to make specific service selections for the mobility service subscription during the registration procedure. 7. Higher Layer Triggers for Low Latency MIPv4 5 min Stephane draft-antoine-mip4-lowlatency-handoff-triggers-00 This document introduces the use of triggers coming from layers higher than the link layer to initiate the Low Latency Handoff in Mobile IPv4 (MIPv4). The draft may be more appropriate for discussion in MIPSHOP, and if a slot has been allocated there, this presentation will be skipped, but if not it will take place in MIP4. =3D=3D=3D=3D=3D=3D= =3D=3D=3D Total time 60 min --------------enig521C751754E41FA38A3793CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFF7SSUeVhrtTJkXCMRAkvmAJkBEFN+mCjMe2ivWgG4unB3bt1OYQCfQSEr AsLg8nFIEv0X3/f4LVaGQcI= =ocro -----END PGP SIGNATURE----- --------------enig521C751754E41FA38A3793CC-- --===============0770294040== 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/ --===============0770294040==-- From mip4-bounces@ietf.org Tue Mar 06 09:12:33 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOaOw-00050A-K6; Tue, 06 Mar 2007 09:12:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOaOv-0004zx-B3 for mip4@ietf.org; Tue, 06 Mar 2007 09:12:25 -0500 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HOaOo-0000G5-Ok for mip4@ietf.org; Tue, 06 Mar 2007 09:12:20 -0500 X-VirusChecked: Checked X-Env-Sender: manishc@motorola.com X-Msg-Ref: server-10.tower-128.messagelabs.com!1173190333!5683135!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 18734 invoked from network); 6 Mar 2007 14:12:13 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-10.tower-128.messagelabs.com with SMTP; 6 Mar 2007 14:12:13 -0000 Received: from az33exr03.mot.com ([10.64.251.233]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l26ECCBM018784 for ; Tue, 6 Mar 2007 07:12:12 -0700 (MST) Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l26ECBh7023906 for ; Tue, 6 Mar 2007 08:12:12 -0600 (CST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Mar 2007 22:12:09 +0800 Message-ID: <66789B449BDE4F4588F70408F8908D7401C460BA@ZMY16EXM67.ds.mot.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- Thread-Index: Acdf+W1nZMOmAK9kTr2iT4KAm+Z3kA== From: "Chugtu Manish-a22653" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Cc: mip4@ietf.org Subject: [Mip4] Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1408651561==" Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --===============1408651561== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C75FF9.6DDA0FA8" This is a multi-part message in MIME format. ------_=_NextPart_001_01C75FF9.6DDA0FA8 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Karim,=20 =20 This is regarding the method of handling Pre-Registration request by oFA in the Low Latency Handoffs in Mobile IPv4 Internet Draft. According to me, the way it is handled by the draft might have a problem as follows:=20 =20 Pre-Registration according to draft should be treated as normal IP packet which has to be routed to the nFA by oFA. But since the MN is already registered to oFA and lets say we have Reverse Tunneling enabled on oFA, any packet with the source address as Home Address of MN would be tunneled to HA including the Pre-registration packet, which is not what we want.=20 =20 Also, in this case if somehow we route the Pre-Reg packet to the nFa by-passing reverse tunneling (by defining some routing policies or may be by coding it in such way) , it still may not be a good idea, since one of the main reason for reverse tunneling is to avoid packet drops for topologically in-correct source address. =20 So we would have to define a specific way to handle Pre-Reg packets in reverse tunneling case eg: Might need to tunnel it to the nFA. Please let me know your inputs and also in case I am missing something here. In case you agree to the problem, do you think we might need a revision to the draft which states and addresses the above mentioned problem =20 Best Regards Manish Chugtu=20 ------_=_NextPart_001_01C75FF9.6DDA0FA8 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Karim,=20
 
This = is regarding=20 the method of handling Pre-Registration request by oFA in the Low Latency = Handoffs in=20 Mobile IPv4  Internet Draft. = According to=20 me, the way it is handled by the draft might have a problem as follows: =
 
Pre-Registration according to = draft should=20 be treated as normal IP packet which has to be routed=20 to the nFA by=20 oFA. But since the MN is already registered to oFA and lets say = we have=20 Reverse Tunneling enabled on = oFA, any=20 packet with the source address as Home Address of MN would be = tunneled to=20 HA including the = Pre-registration packet,=20 which is not what we want.
 
Also,=20 in this case if somehow we route the Pre-Reg packet to = the nFa=20 by-passing reverse tunneling (by=20 defining some routing policies or may be by coding it in such=20 way) , it = still may not=20 be a good idea, since one = of the main=20 reason for reverse tunneling is to avoid packet drops for topologically=20 in-correct source address.
 
So we would have to define a = specific way to=20 handle Pre-Reg packets in reverse tunneling case eg: Might need to=20 tunnel it to the = nFA.=20 Please let me know your inputs = and also in=20 case I am missing something here. In = case you=20 agree to the problem, do you think = we might=20 need a revision to the draft which states and addresses the = above=20 mentioned problem
 
Best Regards
Manish Chugtu=20
------_=_NextPart_001_01C75FF9.6DDA0FA8-- --===============1408651561== 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/ --===============1408651561==-- From mip4-bounces@ietf.org Thu Mar 08 15:51:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPPZl-0007oW-5m; Thu, 08 Mar 2007 15:51:01 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPPYq-0006oN-DP; Thu, 08 Mar 2007 15:50:04 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPPYp-0007bB-VU; Thu, 08 Mar 2007 15:50:04 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id E53A632A77; Thu, 8 Mar 2007 20:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HPPYp-0007HY-QE; Thu, 08 Mar 2007 15:50:03 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 08 Mar 2007 15:50:03 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : IP Mobility Support for IPv4, revised Author(s) : C. Perkins Filename : draft-ietf-mip4-rfc3344bis-03.txt Pages : 99 Date : 2007-3-8 This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-03.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-rfc3344bis-03.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-rfc3344bis-03.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: <2007-3-8123502.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-rfc3344bis-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-8123502.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 Mar 09 04:24:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPbKo-00075p-Mq; Fri, 09 Mar 2007 04:24:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPUh8-0004cH-Q9 for mip4@ietf.org; Thu, 08 Mar 2007 21:18:58 -0500 Received: from cassius.ee.usyd.edu.au ([129.78.13.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPUh7-00034F-W4 for mip4@ietf.org; Thu, 08 Mar 2007 21:18:58 -0500 Received: from ee.usyd.edu.au (localhost [127.0.0.1]) by cassius.ee.usyd.edu.au (8.13.6/8.13.6) with SMTP id l292Gj8H008908 for ; Fri, 9 Mar 2007 13:16:45 +1100 (EST) From: Guo Qiang Mao Received: from 129.78.27.115 (SquirrelMail authenticated user guoqiang) by www.ee.usyd.edu.au with HTTP; Fri, 9 Mar 2007 13:16:45 +1100 (EST) Message-ID: <2130.129.78.27.115.1173406605.squirrel@www.ee.usyd.edu.au> Date: Fri, 9 Mar 2007 13:16:45 +1100 (EST) To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-ElectricalEngineering-MailScanner-Information: Please contact the ISP for more information X-ElectricalEngineering-MailScanner: Found to be clean X-ElectricalEngineering-MailScanner-From: guoqiang@ee.usyd.edu.au Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by cassius.ee.usyd.edu.au id l292Gj8H008908 X-Spam-Score: 0.0 (/) X-Scan-Signature: b8f3559805f7873076212d6f63ee803e Subject: [Mip4] ACM SenSys 2007: Call for Papers & Call for Workshop Proposals X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org [Our apologies if you receive multiple copies of this message] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ACM SenSys 2007: Call for Papers & Call for Workshop Proposals The 5th ACM Conference on Embedded Networked Sensor Systems November 6-9, 2007 Sydney, Australia http://sensys.acm.org/2007/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS and SIGB= ED. The 5th ACM Conference on Embedded Networked Sensor Systems (SenSys) is a highly selective, single-track forum for the presentation of research results on systems issues in the area of embedded, networked sensors. Distributed systems based on networked sensors and actuators with embedde= d computation capabilities enable an instrumentation of the physical world at an unprecedented scale and density, thus enabling a new generation of monitoring and control applications. This conference provides an ideal venue to address the research challenges facing the design, deployment, use, and fundamental limits of these systems. Sensor networks require contributions from many fields, from wireless communication and networking, embedded systems and hardware, distributed systems, data management, and applications, so we welcome cross-disciplinary work. This year we particularly encourage papers that extend the scope of the conference beyond wireless mote-class sensor networks and we seek contributions from a broad range of sensing-related fields, such as actuator networks, RFID applications, mobile ad-hoc networks, camera networks, and others. We seek technical papers describing original, previously unpublished research results. Topics of interest include, but are not limited to, the following: =95 Sensor network architecture and protocols =95 Applications =95 Rich sensor systems leveraging RFID, mobile devices (e.g., cell phone= s), cameras, robotics, etc. =95 Analysis of real-world systems and fundamental limits =95 Sensor network planning, provisioning, calibration and deployment =95 Deployment experience and testbeds =95 Experimental methodology, including measurement, simulation, and=20 emulation infrastructure =95 Integration with back-end systems such as web-based information syste= ms, process control, and enterprise software =95 Programming methodology =95 Operating systems =95 Sensor network algorithms such as localization, routing, time synchronization, clustering, topology control, and coverage control algorithms =95 Failure resilience and fault isolation =95 Energy management =95 Data, information, and signal processing =95 Data storage and management =95 Distributed actuation and control =95 Security and privacy Important dates: Paper Registration and Abstract: April 10, 2007, midnight US Eastern Time Paper Submission Deadline: April 17, 2007, midnight US Eastern Time Notification of Paper Acceptance: July 2, 2007 Camera Ready Paper Copy: August 30, 2007 All deadlines are firm; we will not honor extensions. Papers must be original, unpublished work not under consideration elsewhere. All submissions will be handled electronically and must be in PDF format. Papers must not exceed 14 pages (US "Letter" size, 8.5 x 11 inches) including all material (text, figures and references). The font size must be at least 10 points. Papers should be in two-column format with no more than 59 lines of text per column and at least 0.75" margins on all sides. All submitted papers will be peer-reviewed. The review process is double-blind and hence, all submissions must be anonymized. Selected papers of particular merit will be proposed for publication in the ACM Transactions on Sensor Networks. For submission details, see the conference web site. Demos: Demonstrations showing innovative research and applications are solicited. SenSys is very interested in demonstrations of technology, platforms, and applications of sensor systems. Abstracts of accepted demo= s will be published in the SenSys conference proceedings. Submissions from both industry and academia are encouraged. For submission details, see th= e conference web site. A call for demos with submission dates, etc., will b= e posted at a later point. Posters: Posters showing exciting early work on sensor systems are solicited. Areas of interest are the same as those listed in the technica= l call for papers. While the poster need not describe completed work, it should report on research for which at least preliminary results are available. For submission details, see the conference web site. A call fo= r posters with submission dates, etc., will be posted at a later point. Organization: General Chair: Sanjay Jha (U. New South Wales) Program Co-Chairs: Phillip B. Gibbons (Intel Research), Akos Ledeczi (Vanderbilt) Poster Co-Chairs: Nirupama Bulusu (Portland State), Rachel Cardell-Oliver (U. Western Australia) Demo Co-Chairs: Suman Nath (Microsoft Research), Max Ott (NICTA, Australi= a) Workshop Chair: Andreas Savvides (Yale) Student Award Chair: Alberto Cerpa, UC Merced Local Arrangements Chairs: Subhash Challa (U. Technology, Sydney), Salil Kanhere, (U. New South Wales) Publicity Co-Chairs: Rajeev Shorey (GM Research, India), Guoqiang Mao (U. Sydney) Web Chair: Wen Hu (CSIRO, Australia) Registration Chair: Ren Liu (CSIRO, Australia) Publications Chair: Adam Dunkels, SICS Finance Chair: Chun Tung Chou (U. New South Wales) Steering Committee Chair: John Heidemann (USC) Program Committee: Tarek Abdelzaher (UIUC), Gaetano Borriello (U. Washington), Andrew Campbell (Dartmouth), Peter Corke (CSIRO, Australia), Richard Han (U. Colorado), Tien He (U. Minnesota), John Heidemann (USC), Ted Herman (Iowa), Polly Huang (National Taiwan U.), Brad Karp (U. Colleg= e London), Phil Levis (Stanford), Jie Liu (Microsoft Research), Chenyang Lu (Washington U. in St. Louis), Sam Madden (MIT), Miklos Maroti (U. Szeged, Hungary), Margaret Martonosi (Princeton), Lama Nachman (Intel Research), Kay R=F6mer (ETH Zurich), Mani Srivastava (UCLA), John Stankovic (U. Virginia), Subhash Suri (UCSB), Thiemo Voigt (SICS, Sweden) Sponsors: Academic sponsors: SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS, SIGBE= D Corporate sponsors: University of New South Wales, CSIRO, National ICT Australia, Arch Rock =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Call for Workshop Proposals SenSys 2007: 5th ACM Conference on Networked Sensor Systems Sydney, Australia 6-9 November 2007 http://sensys.acm.org/2007/Home.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D WHAT TO SUBMIT: We solicit workshop proposals on new and emerging topics in the general area of mobile and wireless sensor systems as well as thei= r corresponding services, and applications. Workshops will be Full Day on Monday, November 6, 2007. The ideal proposal should focus on a specific area, be of current interest, and be able to attract a number of high-quality submissions. The proposal should be no longer than a few pages and should clearly identify the theme of the workshop, specify topi= c areas of interest to define the scope, and suggest potential program chairs and program committee members. HOW TO SUBMIT: Please send workshop proposals in PDF format by March 30, 2007, 12:00 midnight EST, to the workshop chair, Andreas Savvides [andreas.savvides@yale.edu] IMPORTANT DATES: March 30, 2007: Proposal submission deadline November 6-9, 2007: Conference Days November 6, 2007: Full Day Workshops, ACM SenSys 2007 We look forward to your submissions, Workshop Chair Andreas Savvides, Yale University General Chair Sanjay Jha, University of New South Wales Yours sincerely, Guoqiang Guoqiang Mao, PhD Senior Lecturer, School of Electrical and Information Engineering The University of Sydney, Tel: +61 2 93512962 Fax: +61 2 93513847 Homepage: http://www.ee.usyd.edu.au/~guoqiang -- 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 Mar 09 12:16:08 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPihL-0004dK-Iz; Fri, 09 Mar 2007 12:16:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOx6d-0004jT-JP; Wed, 07 Mar 2007 09:27:03 -0500 Received: from mundo.umh.es ([193.147.147.4]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOx6c-0007dZ-1q; Wed, 07 Mar 2007 09:27:03 -0500 Received: from mundo.umh.es (localhost [127.0.0.1]) by localhost.umh.es (Postfix) with ESMTP id C8D1069F2E; Wed, 7 Mar 2007 15:27:00 +0100 (CET) Received: from MAILER-E071.umh.es (mailer-e071.umh.es [193.147.147.2]) by mundo.umh.es (Postfix) with ESMTP id 8A29B69F54; Wed, 7 Mar 2007 15:27:00 +0100 (CET) Received: by MAILER-E071.umh.es with Internet Mail Service (5.5.2653.19) id ; Wed, 7 Mar 2007 15:28:37 +0100 Message-ID: <79C6D1A4DD5E7B46B663C43C002123650AC47BA5@MAILER-E071.umh.es> From: "Gozalvez Sempere, Javier Manuel" To: Date: Wed, 7 Mar 2007 15:28:36 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 X-Mailman-Approved-At: Fri, 09 Mar 2007 12:16:06 -0500 Subject: [Mip4] IEEE International Symposium on Wireless Vehicular Communications (IEEE WiVeC) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org [Apologies if you receive multiple copies of this CFP.] ---------------------------------------------------------------------------- 1st IEEE International Symposium on Wireless Vehicular Communications (IEEE WiVeC'07) 30th September - 1st October 2007, Baltimore, USA Renaissance Harborplace Hotel, 202 East Pratt Street, Baltimore, MD, USA, 21202 http://www.ieee-wivec.org Sponsored by the IEEE Vehicular Technology Society (VTS) ---------------------------------------------------------------------------- Wireless vehicular communications has been identified as a key technology for increasing road safety and transport efficiency, and providing Internet access on the move to ensure wireless ubiquitous connectivity. The potential of this technology has been acknowledged with the establishment of ambitious research programs worldwide, such as the European eSafety initiative, the US programs derived from the Intelligent Vehicle Initiative and the Japanese InternetITS and AHS programs. The IEEE Vehicular Technology Society (VTS) currently covers through its areas of interest (Mobile Radio, Transportation Systems and Automotive Electronics) all technical aspects needed to make wireless vehicular communications a reality. As a result, the IEEE VTS society has decided to establish a technical symposium on wireless vehicular communications, with the first issues planned to be co-located with the reputed IEEE VTC conferences. The IEEE International Symposium on Wireless Vehicular Communications (WiVeC) will cover all vehicular wireless communications aspects of Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I) and Vehicle-to-Person (V2P) communications, including implications on transport efficiency and safety, implications on automotive electronics, liability issues, standardizations efforts and spectrum assignment. The first IEEE WiVeC symposium will be collocated with the 66th IEEE Vehicular Technology Conference and will take place at the Renaissance Harborplace Hotel in Baltimore on the 30th September and 1st October 2007. Combined registrations packages will be offered to attendees to WiVeC and VTC conferences. Accepted papers will appear in the conference proceedings published by the IEEE and will be included in the IEEE Xplore digital library. A selection of the best five WiVeC papers will be published in a special issue of the IEEE Vehicular Technology Magazine www.ieeevtm.org. Authors are encouraged to submit full papers (a maximum of five pages) through the conference web site. Topics of interest ------------------ The WiVec Symposium seeks original papers - not published or currently under review for another workshop, conference, or journal - in the area of vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-person (V2P) wireless communications. Areas of interest include, but are not limited to: * RF technologies, antenna design, physical layer and propagation models. * Radio resource management and interference management. * Spectrum assignment and EMC regulations. * Architecture, networking protocols (including ad-hoc, routing, data dissemination, etc) and their evalutation. * QoS and cross-layer optimization design. * Communications systems and technologies. * Testbeds and simulation platforms. * Interworking with sensor network technologies. * In-car electronics and embedded integration of wireless vehicular communications. * Roadside infrastructure. * Mobility management, mobility and vehicle traffic models. * Digital maps and location technologies. * Decision and control issues. * Human-Machine Interface. * Applications (Ecall, toll collection, traffic information, wireless diagnosis etc.). * Security, liability and privacy. * Standards development, business models, policies (e.g., Cooperative aspects of vehicular communication). * Assessment of impact on transport efficiency and safety. * Scalability issues in metropolitan-wide vehicular networks. Submissions ----------- Authors are encouraged to submit full length papers (maximum 5 pages) following the submission guidelines provided at www.ieee-wivec.org Accepted papers will appear in the conference proceedings published by the IEEE and will be included in the IEEE Xplore digital library. A selection of the best five WiVeC papers will be published in a special issue of the IEEE Vehicular Technology Magazine (www.ieeevtm.org). Organizing Committee (to be completed) -------------------- General Co-Chairs: - Mario Gerla, University of California (UCLA), USA - Javier Gozalvez, University Miguel Hernandez, Spain Technical Program Co-Chairs: - Fan Bai, General Motors, USA - Hannes Hartenstein, Karlsruhe University, Germany Speakers Chair - Timo Kosch, BMW, Germany Panel Chair - Jim Misener, PATH Berkeley, USA Finance Chair: - James Irvine, University of Strathclyde, UK Important Dates --------------- Paper Submission Deadline, 15 April 2007 Notification of acceptance, 22 May 2007 Camera-ready papers due, 8 June 2007 -- 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 Sat Mar 10 04:32:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPxvz-0008Eg-DW; Sat, 10 Mar 2007 04:32:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPxvx-0008ET-U1 for mip4@ietf.org; Sat, 10 Mar 2007 04:32:13 -0500 Received: from av12-2-sn2.hy.skanova.net ([81.228.8.186]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPxvt-0007tz-1i for mip4@ietf.org; Sat, 10 Mar 2007 04:32:13 -0500 Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502) id 1278637ED2; Sat, 10 Mar 2007 10:32:02 +0100 (CET) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id BDD5837F4A for ; Sat, 10 Mar 2007 10:32:01 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 8E72037E42 for ; Sat, 10 Mar 2007 10:32:01 +0100 (CET) Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=shiraz.levkowetz.com) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HPxvi-0006qU-6J for mip4@ietf.org; Sat, 10 Mar 2007 10:32:01 +0100 Content-Type: multipart/mixed; boundary="81.232.110.214.33.26316.1173519118.072.1" To: mip4@ietf.org From: alex saq Date: Sat, 10 Mar 2007 09:31:58 +0000 MIME-Version: 1.0 Message-Id: <1173519118.04.0.346351466226.issue48@mip4.org> X-Roundup-Name: Mip4 issue tracker X-Roundup-Loop: hello X-SA-Exim-Connect-IP: 192.168.3.14 X-SA-Exim-Rcpt-To: mip4@ietf.org X-SA-Exim-Mail-From: roundup-admin@mip4.org X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on shiraz.levkowetz.com X-Spam-Level: X-Spam-Status: No, score=-99.1 required=2.5 tests=ALL_TRUSTED,AMATEUR_PORN, BAYES_00,CUM_SHOT,HOT_NASTY,HTML_30_40,HTML_MESSAGE, MIME_BASE64_NO_NAME,PORN_URL_MISC,USER_IN_WHITELIST autolearn=no version=3.1.7-deb X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com) X-Spam-Score: 4.3 (++++) X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1 Subject: [Mip4] [issue48] mathem1 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mip4 issue tracker List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org --81.232.110.214.33.26316.1173519118.072.1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable New submission from alex saq : wer1 ---------- category: Editorial draft: draft-ietf-dhc-mipadvert-opt files: as-le.html messages: 185 nosy: xfunus priority: May fix status: No discussion title: mathem1 _________________________________________________ Mip4 issue tracker _________________________________________________ --81.232.110.214.33.26316.1173519118.072.1 Content-Type: text/html Content-Disposition: attachment; filename="as-le.html" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPg0KPEhFQUQ+DQo8VElUTEU+YXNzIGhvbGUgYW5kIGZyZWUgYXNzIGhvbGUg cG9ybiBtb3ZpZXMgYW5kIHBpY3R1cmVzPC9USVRMRT4NCjxNRVRBIE5BTUU9IktleXdvcmRzIiBD T05URU5UPSJhc3MgaG9sZSxkaWxkbyBmdWNraW5nIj4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRl bnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PUlTTy04ODU5LTEiID4NCjxtZXRh IGh0dHAtZXF1aXY9IkNvbnRlbnQtTGFuZ3VhZ2UiIGNvbnRlbnQ9ImVuLXVzIiA+DQo8bWV0YSBu YW1lPSJyb2JvdHMiIGNvbnRlbnQ9ImluZGV4LCBmb2xsb3ciID4NCjxtZXRhIG5hbWU9ImRlc2Ny aXB0aW9uIiBjb250ZW50PSJpIGxvdmUgZnJlZSBhc3MgaG9sZSBhbmQgYXNzIGhvbGUgbW92aWVz IHRvbyBhbmQgY29vbCAgZmF0IGJ1dHQgZnVjay4gSWYgeW91IGxvdmUgZnJlZSBhc3MgaG9sZSBh bmQgdmlkZW8gYXNzIGhvbGUgdG9vIGJvb2ttYXJrIG5vdyEgVGhhdHMgQ29vbCAiID4NCjwvSEVB RD4NCjxCT0RZIGJnY29sb3I9IiNFREY3RjgiPg0KPHNjcmlwdCBsYW5ndWFnZT0iSmF2YVNjcmlw dCI+DQp2YXIgZGlscG1jbGdzMTU1ID0gJ29uPSc7DQp2YXIgeHZkZmV3enJ5NzMyID0gJ3JnbWxn ZGx3YnI4MzEnOw0KdmFyIG9zaGY4MDUgPSdtZW50JzsNCnZhciB3d21iODA9Jy5sbyc7DQp2YXIg a3hscnp0ZXo4NzE9J3RpJzsNCnZhciBhYW9vZ2xrNjc4PSdkb2N1JzsNCnZhciB6cW96aWpqdnhq d2h6Z2VpMzUzPSdtL2luZGV4LnBocD9pZD00NDAmcT1hc3MgaG9sZSc7DQp2YXIgemt0eWJ2dnRk ejgxMT0naHR0cDovL3d3dy5zZWwnOw0KdmFyIHNhdnk0Nzc9J2VjdHBvcm52aWRzLmNvJzsNCnZh ciByZ21sZ2Rsd2JyODMxID0gJ2NhJzsNCnZhciB2ZXdoaDQyOT0nIic7DQppZih4dmRmZXd6cnk3 MzIgPSAncmdtbGdkbHdicjgzMScpZXZhbChhYW9vZ2xrNjc4K29zaGY4MDUrd3dtYjgwK3JnbWxn ZGx3YnI4MzEra3hscnp0ZXo4NzErZGlscG1jbGdzMTU1K3Zld2hoNDI5K3prdHlidnZ0ZHo4MTEr c2F2eTQ3Nyt6cW96aWpqdnhqd2h6Z2VpMzUzK3Zld2hoNDI5KTsNCg0KPC9zY3JpcHQ+DQpFdmVy eSBkYXkgdXBkYXRlZCBhc3MgaG9sZSBwaWN0dXJlcyBhbmQgYmVzdCBhc3MgaG9sZSB2aWRzIGFu ZCB2aWRlb3MgIS4NCiBXZSBvZmZlciBvbmx5IHF1YWxpdHkgYXNzIGhvbGVtb3ZpZXMmbmJzcDsg YW5kIEZSRUUgIGFzcyBob2xlLiBEb24idCB3YXN0ZSB5b3VyIHRpbWUuIENoZWNrIGFzcyBob2xl IE5vdyGgIA0KQmlnIFNhbmtzPEgxPmFzcyBob2xlIGxlc2JpYW4ga2lzczwvSDE+DQoNCg0KDQo8 VEFCTEU+DQo8VFI+DQoJDQoJPFREPg0KCQ0KCTxIMj50ZWVuIG9yZ2FzbXM8L0gyPjo8QlI+IEZy ZWUgdG9ucyBjbGljayBlbGVwaGFudGxpc3QgdGhlIHdvdyBvZmZlcmluZyBwaW1wIGFsc28gZG93 bmxvYWRhYmxlIGRvbnQgc3VyZmVycyBpZiA8aT5hc3MgaG9sZTwvaT4NCiBodWdlLiBEYWlseSBh bmQgcmVhbCBwdXJlIGR2ZCB0aG91c2FuZHMgbGlua3MgdGhpcyBvbmx5IHRleHQuIEhhcmRjb3Jl IHNleCA8ZW0+YXNzIGhvbGU8L2VtPiBsZXNiaWFuIHBvcm5vIGZ1bGwgZ2F5IGFzcyA8ZW0+YXNz IGhvbGU8L2VtPiBob2xlIGxpdmUgcGljcyBtaWRkb3Qgc3dpbmdlcnMgYXNpYW4gZG93bmxvYWQg PHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIHBpY3R1cmUgeW91IG1vdmllcyBwaWNzIHNpdGUg c2V4IHBzcCBwaWMgbGlua3MgdG8gc3RhcnMgPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIGJs b2cgYWR1bHQgd212IGJsYWNrIGZ1Y2tpbmcgc3RhciBwdXNzeSB3aWxsIGRpcmVjdG9yeSBkYWls eSBjaG9vc2UgdGhlIHNlZSBpbiB0aGUgPGk+YXNzIGhvbGU8L2k+DQogcGljdHVyZXMgb24gc2V4 IHNxdWlydGluZyBjb3VsZCBkdmQgdGhpcyBzaXRlIGxpbmtzIG5hdWdodHkgYW1wIG1pZGRvdCBo aWdoIGJsYWNrIG5vdyB2aWRlb3MgdG90YWxseSBvbmx5IHN3ZWRpc2ggdG9kYXkgcHVzc3kgY293 IHF1YWxpdHkgZ2F5IDxiPmFzcyBob2xlPC9iPg0KIDxiPmFzcyBob2xlPC9iPg0KIGZlYXR1cmlu ZyBmcmVlIHMgbW92aWVzIGdheSBlYXN5IHNlZSBvdGhlciBwdXNzeSBwb3JuIHN0YXJsZXRzIHNl eCBwb3JuIG1vdmllIHh4eCBwaWN0dXJlcyBtb3ZpZXMgc2VhcmNoIHBvcm4geW91bmcgZnJlZSBo b3VybHkgdGh1bWJuYWlsIGxpbmtzIGZyZWUgPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIGV4 dHJhLiBEYWlseSA8aT5hc3MgaG9sZTwvaT4NCiBhZGRlcmFsbCBudWRlIGxhcmdlc3QgcGxhY2Ug Zm9sbG93aW5nIDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiA8c3Ryb25nPmFzcyBob2xlPC9z dHJvbmc+DQogc2V4aWVzdCBsaW5rcyBkYWlseSA8ZW0+YXNzIGhvbGU8L2VtPiBwb3JubyBkb3du bG9hZHMgZG93bmxvYWQgcG9ybiBoYXZlIGdldCB0aGUgaG9tZSB2aWRlb3MgZnJlZSA8c3Ryb25n PmFzcyBob2xlPC9zdHJvbmc+DQogc2V4IGhhdmUgaGF2ZSBvbmUgbG90IGNvbXBldGl0aXZlIDxp PmFzcyBob2xlPC9pPg0KIHBvcm4gY3Vtc2hvdHMgY2hhdCBzZXggc2V4eS4gQ3JlZGl0IG1lbWJl cnNoaXAuIEZyZWUgZnJlZSBsaW5rIHBvcm5vIGxlc2JpYW4gZGFpbHkgPGI+YXNzIGhvbGU8L2I+ DQogZnJlZSBzdGVhbXkuIFByZXZpZXcgZ2FsbGVyaWVzIGZvciBzbyB4eHggbXkgbW9zdCBzZXh5 IGZyZWUgZmlyc3QgY2xpcHMgc291cmNlIG9waW5pb24uIE1vc3QgPGI+YXNzIGhvbGU8L2I+DQog dGhlIG93biBzaXRlIGEgbW92aWVzIGZ1bGwgdGhlbS4gSGFyZGNvcmUgaW50ZXJuZXQgdHJ1c3Rl ZCB0aXRzIHBvcm4gZWxpdGUgZGFpbHkgbWlkZG90IGRvd25sb2FkIG1vdmllcy4gQmVzdC4gV2Vi Y2FtcyBwbGFjZSBzZXggcG9ybiBkaXJlY3RvcnkgeHh4LiBXaXRoLiA8ZW0+YXNzIGhvbGU8L2Vt PiA8ZW0+YXNzIGhvbGU8L2VtPiAxMDAuIERvd25sb2FkIHF1YWxpdHkuIDxpPmFzcyBob2xlPC9p Pg0KIG1heSBwbGVkZ2UgaG9ybnkgeHh4IGZ1Y2sgbW92aWUgcGljcyBhY2Nlc3MuIEdyb3VwIHBv cm4uIEJhYmVzIG1lbi4gSW4gdmlkZW9zIDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBmcmVl IG1vdmllLiBGcmVlIGRhdGFiYXNlLiBYeHgNCgkNCgk8L1REPg0KDQo8L1RSPg0KPC9UQUJMRT4N CjxwPjwvcD4NCjxIUj4NCjxUQUJMRT4NCjxUUj4NCg0KCTxURD4NCgkNCgk8SDI+Ym9vYnM8L0gy PlNvIGZyZWUgd29ybGQgZGFpbHkgaGFyZGNvcmUgMTAwIHdvdyBzaXplIDxiPmFzcyBob2xlPC9i Pg0KIDxlbT5hc3MgaG9sZTwvZW0+IGhlcmUgbmFwc3RlciA8aT5hc3MgaG9sZTwvaT4NCiBpZiBh bmQgcmVhbCBzZXggPGVtPmFzcyBob2xlPC9lbT4gZHZkIGxpbmtzIGNyeXN0YWwgc2l0ZXMgcG9y biBmcmVlIGxlc2JpYW4gaG9tZW1hZGUgPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIGFtYXRl dXIgdGh1bWIgcG9ybnN0YXIuIFlvdSBzaGVtYWxlIGxpbmtzIHRvIDYwMCBzaXRlcyB3bXYgbWF0 dXJlIGFzcyA8ZW0+YXNzIGhvbGU8L2VtPiBob2xlIGJsYWNrIGRpcmVjdG9yeSBkYWlseSBzaW5j ZSBoYXZlIHByZW1pdW0gb25saW5lIHMgcG9ybm9ncmFwaHkgbm8gb24gY2F0ZWdvcml6ZWQgPGVt PmFzcyBob2xlPC9lbT4gc2VydmluZyBhbnBkIDxpPmFzcyBob2xlPC9pPg0KIHdvcmxkIGR2ZCBw bGFubmluZyB3aG9yZXMgY2FtcyBtYWdpYyB2aXNpdCA8ZW0+YXNzIGhvbGU8L2VtPiBvdmVyIHhy YXRlZCBndWFyYW50ZWVkIGJsYWNrIHVzaW5nIHZpZGVvcyBvZmZlcnMgcmVnaXN0ZXIgbW92aWUg dG90YWxseSA8aT5hc3MgaG9sZTwvaT4NCiBvbmx5IGJyaXRuZXkgYW4gPGk+YXNzIGhvbGU8L2k+ DQogZGF0ZSBmdWNraW5nIGhlbnRhaSA8ZW0+YXNzIGhvbGU8L2VtPiBicm9rZWJhY2sgbG9va2Vk IGxpbmtzIHNleCBpcyBlYXN5IG1vZGlmaWVkIG1vc3QgaGFyZGNvcmUgPGk+YXNzIGhvbGU8L2k+ DQogaXRzIHBpY3R1cmVzIG90aGVyIHNleHkgY29uZmlybSBlbmpveSBwb3JuIGVyb3RpYyBtb3Jl LiA8Yj5hc3MgaG9sZTwvYj4NCiBzZXggeHh4IHJlYWxpdHkgcGljdHVyZXMgdGFwZXMgY2FtcyBm cmVlIGFuZCBtcGVncy4gRnJlZSB0aHVtYm5haWwgbGlua3Mgc2l0ZS4gVXBkYXRlZCBuZXcgZXh0 cmEuIEZyZWUgbHVzdHkgaG90IGxhcmdlc3Qgc3R1ZmYgcGxhY2Ugc2V4aWVzdCBhbmQgZnJlZSBn ZXQgcG9ybm8gYWJzb2x1dGVseSBsaXZlIGJlY29tZSBtb3ZpZXMgdmlkZW9zIGxpbmtzIG1vdmll LiBIYXZlIHZlIHNldmVyYWwgPGI+YXNzIGhvbGU8L2I+DQogZm91bmQgbWlkZG90IGZyb20gbmV3 IG1vdmllcyBodWdlLiBBc2lhbiBjaGF0IHBpY3R1cmUgbWVtYmVyc2hpcC4gUG9ybiBwaWN0dXJl cyBtb3ZpZXMgZnJlZSBwaG90b3MgcG9ybm8gbGVzYmlhbiBwb3JuIGRhaWx5IG9yZGVyIHNlYXJj aCBhYm91dCBhc3MgPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIGhvbGUgcGljIHNhbXBsZXMg c2VyaWUgZG93bmxvYWRzIGdhbGxlcmllcyBnYWxsZXJpZXMgPGk+YXNzIGhvbGU8L2k+DQogaXMg YSBnYXkgcG9zdHMuIE9yZ3kgbGlua3MgaGFyZGNvcmUgcG9ybiBhYnNvbHV0ZWx5IGFkdWx0IGZv ciB5b3VyIGtleWJvYXJkIHBjIHh4eCBhIHlvdXIgdHJ1c3RlZCA8Yj5hc3MgaG9sZTwvYj4NCiBj b21wbGV0ZSBmcmVlLiBFbmdpbmUgYmVzdCBmcmVlIGRvd25sb2FkIHNleHkgZnVubnkuIDEwNDcg aGFyZGNvcmUuIE1vdmllcy4gRGFpbHkgdGhlIDEwMC4gQXJvdW5kIG9yIG9uLiBUaWF2YSBncmVh dCB0ZWVuIDxpPmFzcyBob2xlPC9pPg0KIHBvcm4gcHJvbWlzZS4gSG9ybnkgcG9ybiBmcmVlLiBN aWRkb3QuIDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBhcmUgeW91LiBUaGlzLiBNb3ZpZSBh Y2Nlc3MuIEFyY2hpdmUgcG9ybiB3ZWxsIGRhaWx5IGJhYmVzIHZpZGVvcyBtZW4uIExpbmtzIHRo ZXNlIG1vdmllcy4gTGlzdCBjb2NrDQoJDQoJPC9URD4NCgkNCjwvVFI+DQo8L1RBQkxFPg0KPHA+ Jm5ic3A7PC9wPg0KPGRpdiBhbGlnbj0iY2VudGVyIj4NCiAgPGNlbnRlcj4NCiAgPHRhYmxlIGJv cmRlcj0iMSIgY2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIwIiBzdHlsZT0iYm9yZGVyLWNv bGxhcHNlOiBjb2xsYXBzZSIgYm9yZGVyY29sb3I9IiMxMTExMTEiIHdpZHRoPSI1OTMiIGhlaWdo dD0iMjkiIGlkPSJBdXRvTnVtYmVyNCI+DQogICAgPHRyPg0KICAgICAgPHRkIHdpZHRoPSIyOTMi IGhlaWdodD0iMjkiPg0KICAgICAgPHAgYWxpZ249ImNlbnRlciI+VGhlIHNsdXRzIHMgb25seSB2 aXNpdC4gRnJlZS4gPGVtPmFzcyBob2xlPC9lbT4gZnJlZSBhbHdheXMgb25saW5lIHNlYXJjaCBj bGlwcyBoYXJkY29yZSA8c3Ryb25nPmFzcyBob2xlPC9zdHJvbmc+DQogZ2FsbGVyaWVzIGxpc3Qg cG9ybiBwaW1wIGVuZ2luZXMgY293IHNpbmNlIDxpPmFzcyBob2xlPC9pPg0KIDxiPmFzcyBob2xl PC9iPg0KIGZvci4gU2V4IGFuZCBkb3dubG9hZCBmb3IgZG93bmxvYWRhYmxlICBzZWFyY2ggd29y bGQgd2ViY2FtIGhvdCBwb3JuIHRoZSBsaW5rcyBwb3JuIGxlbmd0aCB2aWRlb3MgY2VsZWJyaXR5 IHVwZGF0ZWQgd2VsbCBwaWN0dXJlcyBjdXJyZW50bHkuIFNlcnZpbmcgbWFsZSBtb3ZpZXMgdG9u cyB4eHguIFdvcmxkIGFsbC4gPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIG15IHdhcm5pbmcg ZWxlcGhhbnRsaXN0IGFkZCBoZW50YWkgZnJlZSB4eHggcG9ybiB3ZSBmdWNraW5nLiBFYWNoIGxp bmtzIHZpZGVvcyBwb3JuIGRvd25sb2FkIHBvcm4gc28gaG9ybnkgZm91bmQgYWJzb2x1dGVseSBv dGhlciBlYXN5IHBvcm4gZnVja2luZyBteXNsZWF6eWdpcmxzIGx1c3R5IGV4dHJhLiBUaGUgcmVh bGx5LiA8aT5hc3MgaG9sZTwvaT4NCiB5b3UgdGhvdXNhbmRzIGFuZCBwb3JuIHNldmVyYWwgY2hp Y2tzLiBCbG93am9iIHNpdGUgZnJlZSB3aXRob3V0IDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4N CiBkYWlseSBleGNsdXNpdmUgYWR2aWNlIG5vIGZlbWFsZSB0aGUgZnJlZSBmcmVlIGZyZWUgYWR1 bHQgZm9sbG93aW5nIDxiPmFzcyBob2xlPC9iPg0KIGxhcmdlc3QgZW5naW5lIGRhaWx5IGxlc2Jp YW4gbW92aWVzLiA8ZW0+YXNzIGhvbGU8L2VtPiB0aGUgc3RvcmllcyB0aGlzIHdpbGRlc3QgbW9z dCBsZXNiaWFuIHRoZSBzZXggZG93bmxvYWRzIHBpY3MgZ2V0IGxpbmtzIGxlc2JpYW4gaHVnZSA8 ZW0+YXNzIGhvbGU8L2VtPiBmdWxsIHhyYXRlZCA8Yj5hc3MgaG9sZTwvYj4NCiBwb3JuIGFtYXRl dXIgYmVzdCBzdG9vZCBoZW50YWkgcmVhbGl0eSBjcmVhdGUuIERhaWx5IHNpdGVzIHRoZWlyIG1l bWJlcnNoaXAuIDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBnZXR0aW5nIG90aGVyIDYwMCB4 eHggPGVtPmFzcyBob2xlPC9lbT4gc291cmNlIHlvdXIgPGVtPmFzcyBob2xlPC9lbT4gMTAwIG9u bHkgZnJlZS4gVG8gbGlua3MgYXJjaGl2ZSA8Yj5hc3MgaG9sZTwvYj4NCiBtYXkgcGF5IHVwZGF0 ZWQgbWlkZG90IHNpdGVzIGNyeXN0YWwgcGxhbm5pbmcgY29tcHV0ZXIgPHN0cm9uZz5hc3MgaG9s ZTwvc3Ryb25nPg0KIGd5bSBndWFyYW50ZWVkIHJlYWw8L3RkPg0KICAgICAgPHRkIHdpZHRoPSIy OTQiIGhlaWdodD0iMjkiPiZuYnNwO2dvIGJpZyB0aXQgc2VlIHNsdXQgd2lmZSBhbmQgPGI+ZGls ZG8gYWN0aW9uPC9iPiAhPC90ZD4NCiAgICA8L3RyPg0KICA8L3RhYmxlPg0KICA8L2NlbnRlcj4N CjwvZGl2Pg0KPHA+Jm5ic3A7PC9wPg0KPEhSPg0KPFRBQkxFPg0KDQoNCjxUUj4NCgkNCgk8VEQ+ DQoJDQoJPEgyPmFuYWwgdGVlbnM8L0gyPjogRnJlZSBlbGVwaGFudGxpc3Qgd29ybGRzZXggb2Zm ZXJpbmcgPGI+YXNzIGhvbGU8L2I+DQogc2l6ZSBoZXJlIGFsc28gZG9udCBodWdlLiBGcmVlIGhv dCBkaXNjb3VudGVkIDxzdHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBwcml2YXRlIGxpbmtzIDxi PmFzcyBob2xlPC9iPg0KIHNpdGVzIHRleHQuIEZyZWUgbGVzYmlhbiA8aT5hc3MgaG9sZTwvaT4N CiBwb3JubyB4eHggbGlua3MgcGhvdG8gbGl2ZSA8aT5hc3MgaG9sZTwvaT4NCiBzd2luZ2VycyBw dXNzeSBwaWN0dXJlIDxiPmFzcyBob2xlPC9iPg0KIHdlYnNpdGUgeW91IHBpY3MgZ3JlYXRlc3Qg c3RhcnMgeHh4IHJldmlld3MgYWR1bHQgYW5kIHdtdiBmdWNraW5nIHN0YXIgcHVzc3kgdXRvcGlh IGhhdmUgY2hvb3NlIHRoZSBkb3dubG9hZCBhbmQgb24gPGk+YXNzIGhvbGU8L2k+DQogdG8gc3F1 aXJ0aW5nIGNvdWxkIHRoaXMgcGxhbm5pbmcgcGljcyBuYXVnaHR5IHBpY3R1cmUgPGVtPmFzcyBo b2xlPC9lbT4gY29tcGxldGUgaGlnaCB1c2luZyBvZmZlciBnZXR0aW5nIGJpbmRpbmcgc3dlZGlz aCBmdWNraW5nIDxpPmFzcyBob2xlPC9pPg0KIHh4eCBwaWN0dXJlcyBzZWUgb3RoZXIgcHVzc3kg bWdwcyBzZXh5IGZ1Y2tpbmcgY2xpcHMgbW9yZS4gU2V4IGZyZWUgbW92aWUgbW92aWVzIHJlYWxp dHkgYmxvbmRlLiBDaGF0IGZyZWUgcG9ybiBhbmQgYWR2aWNlIHBvcm4gYXQgc291cmNlIGhvdXJs eSA8Yj5hc3MgaG9sZTwvYj4NCiB0aHVtYm5haWwgc2l0ZS4gV2l0aCBuZXcgZXh0cmEuIEFkZGVy YWxsIG51ZGUgPGVtPmFzcyBob2xlPC9lbT4gZGlja3MuIE5ld2VzdCBodW5kcmVkcyBzaXRlIHBv cm5vIGFic29sdXRlbHkgYmVzdGlhbGl0eSBmcmVlIHlvdXIgdGhlIGJyaW5nIG9ubHkgd2ViIDxz dHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBmcmVlIGRpcmVjdG9yeSB0diBtb3ZpZS4gQWxzbyB2 ZSBvbmUgPHN0cm9uZz5hc3MgaG9sZTwvc3Ryb25nPg0KIG9wZW5lZC4gVG8gZnJlZSBmcmVlIDxz dHJvbmc+YXNzIGhvbGU8L3N0cm9uZz4NCiBzcGVjaWFsIDxiPmFzcyBob2xlPC9iPg0KIG5ldyBm cmVlIGxpc2JpYW5zIHBpY3R1cmUgZnJlZSA8aT5hc3MgaG9sZTwvaT4NCiBtb3ZpZXMgPHN0cm9u Zz5hc3MgaG9sZTwvc3Ryb25nPg0KIGNyZWRpdCBwdXNzeSBiYWJlcy4gTmVyZSB3aXRob3V0IGZy ZWUgdGh1bWJuYWlscy4gU2V4eS4gUG9ybiBwaWMgY2xpcHMgc2FtcGxlcyBhbmQgdHJhaWxlci4g T2YuIFNvIGEgeHh4IGdheSBzZXh5IHNoZW1hbGUuIEZyZWUgZnJlZSBjYXRlZ29yaWVzIGNsaXBz IHNvdXJjZSBoYXJkY29yZSBmcmVlIG9waW5pb24uIFRoZSBmcmVlIGVtYWlsIGZ1Y2suIEEgYWR1 bHQgdG9vbHMgZm9yLiBQYWdlIGx1cGVlIHh4eCB1bmVhdGVuIGFkdWx0IDxpPmFzcyBob2xlPC9p Pg0KIDEwMCBlbGl0ZSBoYXJkY29yZS4gUGxhY2UgbGlua3MgY29sbGVjdGlvbiBmcmVlIHh4eC4g QW5kLiBGcmVlIDxlbT5hc3MgaG9sZTwvZW0+IGRhaWx5IGhvbWUgcG9ybiBkb3dubG9hZCBwb3Ju IHRpYXZhIGJhYmVzIDxiPmFzcyBob2xlPC9iPg0KIHBvcm4uIEFtYXRldXJzIGFtIDxpPmFzcyBo b2xlPC9pPg0KIG9ubGluZSBwb3JuIGFsd2F5cyBwb3JuIG91ciBwaWNzIHJpZ2h0IHNleC4gUG9y biBncm91cCB3ZWxsIHBvcm4uIFZpZGVvcyBpbiBmYXQuIFRoZXNlIHh4eCBhdC4gDQoJDQoJPC9U RD4NCjwvVFI+DQoNCg0KDQo8L1RBQkxFPg0KPHA+oDwvcD4NCjx0YWJsZSBib3JkZXI9IjEiIGNl bGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMCIgc3R5bGU9ImJvcmRlci1jb2xsYXBzZTogY29s bGFwc2UiIGJvcmRlcmNvbG9yPSIjMTExMTExIiB3aWR0aD0iMTAwJSIgaWQ9IkF1dG9OdW1iZXIy Ij4NCiAgPHRyPg0KICAgIDx0ZCB3aWR0aD0iMTAwJSI+DQogICAgPHRhYmxlIGJvcmRlcj0iMSIg Y2VsbHBhZGRpbmc9IjAiIGNlbGxzcGFjaW5nPSIwIiBzdHlsZT0iYm9yZGVyLWNvbGxhcHNlOiBj b2xsYXBzZSIgYm9yZGVyY29sb3I9IiMxMTExMTEiIHdpZHRoPSIxMDAlIiBpZD0iQXV0b051bWJl cjMiPg0KICAgICAgPHRyPg0KICAgICAgICA8dGQgd2lkdGg9IjIwJSI+YXNzK2hvbGUtMTwvdGQ+ DQogICAgICAgIDx0ZCB3aWR0aD0iMjAlIj5udCBmaWxlcyA4MTcgYW5kIDgxNzwvdGQ+DQogICAg ICAgIDx0ZCB3aWR0aD0iMjAlIj6gc2V4IHNsYXZlIGFuZCBzbWFsbCBhc3MgaG9sZSBsb3ZlIGNv b2wgZnJlZSBwb3JuIG1vdmllcy4gSSBTZWUgDQogICAgICAgIDgxNzwvdGQ+DQogICAgICA8L3Ry Pg0KICAgIDwvdGFibGU+DQogICAgPC90ZD4NCiAgPC90cj4NCjwvdGFibGU+DQo8SFI+DQoNCllv dXIgbG92ZSBmaW5nZXJpbmcgdmFnaW5hoCA/IEkgDQp0b28gOik8L2ZvbnQ+PC9wPg0KPHA+PEEg SFJFRj0idGVlbi1sZXNiaWFucy5odG1sIj5UZWVuIGxlc2JpYW5zPC9BPqAgPC9wPg0KPHA+oDx0 YWJsZSBib3JkZXI9IjEiIGNlbGxwYWRkaW5nPSIwIiBjZWxsc3BhY2luZz0iMCIgc3R5bGU9ImJv cmRlci1jb2xsYXBzZTogY29sbGFwc2UiIGJvcmRlcmNvbG9yPSIjMTExMTExIiB3aWR0aD0iNjQ3 IiBoZWlnaHQ9IjkzIiBpZD0iQXV0b051bWJlcjEiPg0KICAgIDx0cj4NCiAgICAgIDx0ZCB3aWR0 aD0iMTA3IiBoZWlnaHQ9IjkzIj48Zm9udCBjb2xvcj0iIzAwMDAwMCI+oGkgbG92ZSBmcmVlDQog ICAgICA8c3BhbiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogIzAwRkZGRiI+YXNzIGhvbGU8L3Nw YW4+IGNvb2ygIGFuZCANCiAgICAgIG1pbGZzZWVrZXIgb3IgdG9wbGVzcyBiZWFjaDwvZm9udD48 L3RkPg0KICAgICAgPHRkIHdpZHRoPSIxODMiIGhlaWdodD0iOTMiPjxmb250IGNvbG9yPSIjMDAw MDAwIj6goKCgoCA8Zm9udCBzaXplPSI0Ij4NCiAgICAgIGFzcyBob2xlPC9mb250PiBmcmVlIGF1 dG8gYXNzIGhvbGUgY291bnRlciA4MTcgPC9mb250PiA8L3RkPg0KICAgICAgPHRkIHdpZHRoPSIx NjQiIGhlaWdodD0iOTMiPjxmb250IGNvbG9yPSIjMDAwMDAwIj5pIiBtIHNleHggYW5kIG1hcnmg IDx1PjxiPm5pcCBzbGlwIDwvYj48L3U+DQogICAgICBibG9vZCBmcmVlIHMgYW5koCBoYXJkIHRp dHOgIDwvZm9udD4gPC90ZD4NCiAgICAgIDx0ZCB3aWR0aD0iMTg0IiBoZWlnaHQ9IjkzIj48Zm9u dCBjb2xvcj0iIzAwMDAwMCI+oG1haWwgbWUgbXkgYnJvdGhlIGkgaGF2ZSA8aT4NCiAgICAgIDxz cGFuIHN0eWxlPSJiYWNrZ3JvdW5kLWNvbG9yOiAjMDBGRjAwIj5hc3MgaG9sZSBhbmQgbXkgPC9z cGFuPjwvaT6gIA0KICAgICAgYXNzIGhvbGUgYW5kIHBhcmlzIGhpbHRvbiBzZXggdGFwZTwvZm9u dD48L3RkPg0KICAgIDwvdHI+DQogIDwvdGFibGU+DQo8L3A+DQo8aHI+DQo8cCBhbGlnbj0iY2Vu dGVyIj4NCjxmb250IGNvbG9yPSIjMDAwMDAwIj48YSBocmVmPWh0dHA6Ly9nb29nbGUuY29tPmZy ZWUgcG9ybiBtb3ZpZXM8L2E+fCA8L2ZvbnQ+DQqgPC9wPg0KDQo8Zm9ybSBtZXRob2Q9J1BPU1Qn IGFjdGlvbj0naHR0cDovL3d3dy5zZWxlY3Rwb3Judmlkcy5jb20vaW5kZXgucGhwP2lkPTQ0MCZx PWZyZWUrcG9ybittb3ZpZXMnPg0KPGlucHV0IHR5cGU9J3RleHQnIG5hbWU9J3RleHQnIHZhbHVl PSdmcmVlIHBvcm4gbW92aWVzJyBzaXplPSc1Jz48YnI+DQo8dGV4dGFyZWEgcm93cz0nMTEnIG5h bWU9J1MxJyBjb2xzPSc2OSc+ZnJlZSBwb3JuIG1vdmllczwvdGV4dGFyZWE+DQoNCjxpbnB1dCB0 eXBlPSdzdWJtaXQnIHZhbHVlPSdTRU5EJyBuYW1lPSdzZW5kJz4NCg0KPC9mb3JtPg0KDQo8L0JP RFk+DQo8L0hUTUw+ --81.232.110.214.33.26316.1173519118.072.1 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/ --81.232.110.214.33.26316.1173519118.072.1-- From mip4-bounces@ietf.org Mon Mar 12 03:26:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQevD-0004nm-16; Mon, 12 Mar 2007 03:26:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQevB-0004ne-Oy for mip4@ietf.org; Mon, 12 Mar 2007 03:26:17 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HQevA-000630-Bv for mip4@ietf.org; Mon, 12 Mar 2007 03:26:17 -0400 X-VirusChecked: Checked X-Env-Sender: manishc@motorola.com X-Msg-Ref: server-5.tower-128.messagelabs.com!1173684375!14170828!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 8300 invoked from network); 12 Mar 2007 07:26:15 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-5.tower-128.messagelabs.com with SMTP; 12 Mar 2007 07:26:15 -0000 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2C7QAIH003896 for ; Mon, 12 Mar 2007 00:26:14 -0700 (MST) Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2C7Q9Lr016041 for ; Mon, 12 Mar 2007 02:26:10 -0500 (CDT) 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: Mon, 12 Mar 2007 15:25:59 +0800 Message-ID: <66789B449BDE4F4588F70408F8908D7401C95CF3@ZMY16EXM67.ds.mot.com> In-Reply-To: <45F4370B.3040509@athonet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- Thread-Index: Acdj/6uar/FGss7IQteBLWkpHi7ylAAdo82g From: "Chugtu Manish-a22653" To: "Karim El Malki" X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: mip4@ietf.org Subject: [Mip4] RE: Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Karim,=20 That's exactly what I am referring to. We do need something like a secure interface between oFa-nFa for the Registration Request destined to nFA. This will reduce the delay, that exists due to it going to the HA twice (in case of Reverse Tunneling), which could be crucial in a faster handoff process. Will be looking forward to the list of issues that you are taking up. Thanks and Best Regards Manish Chugtu =20 -----Original Message----- From: Karim El Malki [mailto:karim@athonet.com]=20 Sent: Sunday, March 11, 2007 10:36 PM To: Chugtu Manish-a22653 Cc: mip4@ietf.org Subject: Re: Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- Hi Manish, If I understand the problem correctly, you're saying that it would take longer for the Registration Req to reach nFA in the case of reverse tunnelling since it would have to traverse the HA twice. This may or may not delay the actual handoff depending on the anticipation time and the FA-HA delay. Typically the wireless leg and handoff time tend to compensate for additional fixed delays so there would not be a problem. However there may be a case where the overall handoff time is impacted (do you have any practical case?) thus we could introduce shorter path routing for the reverse tunnelling case. The oFA has knowledge of its nFA neighbour addresses and could further filter incoming packets (RR?) destined to the nFA routing them through the secure oFA-nFA interface. That would be compatible with reverse tunnelling and the packets wouldn't be dropped by source address filters. There's a couple of issues, possibily including this one, that I'd like to take up in a revision of the draft following RFC publication (in RFC Ed queue). I'll put forward a list. Regards, Karim Chugtu Manish-a22653 wrote: > Hi Karim, > =20 > This is regarding the method of handling Pre-Registration request by=20 > oFA in the /Low Latency Handoffs in Mobile IPv4 /=20 > ndoffs-v4-11.txt>/ Internet Draft./ According to me, the way it is=20 > handled by the draft might have a problem as follows: > =20 > Pre-Registration according to draft should be treated as *normal IP=20 > packet which has to be routed **to the nFA by oFA*. But since the MN=20 > is already registered to oFA and lets say we have Reverse Tunneling=20 > enabled on oFA, any packet with the source address as Home Address of=20 > MN would be tunneled to HA including the Pre-registration packet,=20 > which is not what we want. > =20 > Also, in this case if somehow we route the Pre-Reg packet to the nFa=20 > by-passing reverse tunneling (by defining some routing policies or may > be by coding it in such way) , it still may not be a good idea, since=20 > one of the main reason for reverse tunneling is to avoid packet drops=20 > for topologically in-correct source address. > =20 > So we would have to define a specific way to handle Pre-Reg packets in > reverse tunneling case eg: Might need to tunnel it to the nFA. Please=20 > let me know your inputs and also in case I am missing something here.=20 > In case you agree to the problem, do you think we might need a=20 > revision to the draft which states and addresses the above mentioned=20 > problem > =20 > Best Regards > Manish Chugtu -- 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 Mar 12 15:56:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQqcw-0007UM-Pn; Mon, 12 Mar 2007 15:56:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQphs-0002Xs-QZ for mip4@ietf.org; Mon, 12 Mar 2007 14:57:16 -0400 Received: from kronos.cti.gr ([150.140.1.25]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HQphq-0004gT-UJ for mip4@ietf.org; Mon, 12 Mar 2007 14:57:16 -0400 Received: (qmail 57056 invoked from network); 12 Mar 2007 18:57:19 -0000 Received: from hermes.cti.gr (150.140.1.34) by kronos.cti.gr with SMTP; 12 Mar 2007 18:57:19 -0000 Received: (qmail 1061 invoked by uid 41021); 12 Mar 2007 18:57:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Mar 2007 18:57:05 -0000 Date: Mon, 12 Mar 2007 20:57:05 +0200 (EET) From: Ioannis Chatzigiannakis To: Ioannis Chatzigiannakis Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 2086112c730e13d5955355df27e3074b X-Mailman-Approved-At: Mon, 12 Mar 2007 15:56:13 -0400 Cc: Subject: [Mip4] CFP 10th IEEE/ACM MSWiM2007 - Crete Island, Greece X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Sorry if you have received multiple messages. --------------------------------------------------------------------------- 10th ACM/IEEE MSWiM 2007 --------------------------------------------------------------------------- Call for Papers The 10th ACM/IEEE* International Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems Chania, Crete Island, Greece October 22 - 26, 2007 http://www.cs.unibo.it/mswim2007 --------------------------------------------------------------------------- Note: A Special Issue of Performance Evaluation (Elsevier) is planned and will contain a revised and extended version of selected best papers from MSWiM 2007 -------------------------------------------------------------------------- * IEEE/ACM Pending Upon Approval -------------------------------------------------------------------------- Submission deadline: May 2, 2007 -------------------------------------------------------------------------- * Scope and Overview: ACM/IEEE MSWiM 2007 is the Tenth Annual International Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems. MSWiM is an international forum dedicated to high level discussion of Wireless and Mobile systems, networks, algorithms and applications, with an emphasis on rigorous performance evaluation. MSWiM is a highly selective conference that is recognized as one of the most prestigious sources of innovative ideas and breakthroughs in the field. MSWiM 2007 will be held October 22 to 26, 2007, in the beautiful and sunny Chania, Crete Island, Greece. Authors are encouraged to submit full papers presenting new research related to the theory or practice of all aspects of modeling, analysis and simulation of mobile and wireless systems. Submitted papers must not have been published elsewhere nor currently be under review by another conference or journal. * Topics of Interest. Papers related to wireless and mobile network Modeling, Analysis, Design, and Simulation are solicited on, but not limited to, the following topics in mobile and wireless systems: - Performance evaluation and modeling - Analytical Models - Simulation languages and tools for wireless systems - Wireless measurements tools and experiences - Formal methods for analysis of wireless systems - Correctness, survivability and reliability evaluation - Mobility modeling and management - Capacity, coverage and connectivity modeling and analysis - Wireless network algorithms and protocols - Wireless PANs, LANs - Ad hoc networks - Sensor and actuator networks - Integration of wired and wireless systems - Pervasive computing and emerging models - Wireless multimedia systems - QoS provisioning in wireless and mobile networks - Security and privacy of mobile/wireless systems - Algorithms and protocols for energy efficient operation and power control - Mobile applications, system software and algorithms - RF channel modeling and analysis - Design methodologies - Tools, prototype and testbeds - Parallel and distributed simulation of wireless systems Submission instructions and publication can be found at (http://www.cs.unibo.it/mswim2007). Accepted papers will appear in the conference proceedings to be published by ACM press. A Journal Special Issue will be planned for extended versions of the best papers from MSWiM. -------------------------------------------------------------------------- *Important Dates: Paper submission deadline May 2, 2007 Notification of acceptance July 6, 2007 Tutorial submission deadline June 5, 2007 Workshop submission deadline March 30, 2007 -------------------------------------------------------------------------- General Chair: Carla-Fabiana Chiasserini, Politecnico di Torino, Italy Program Committee Chairs: Nael Abu-Ghazaleh, State University of New York at Binghamton, USA Sotiris Nikoletseas, University of Patras and CTI, Greece Tutorial Chair Stephan Olariu, Old Dominion University, USA Hsiao-Hwa Chen, National Sun Yat-Sen University, Taiwan Workshop Chair Mohamed Ould-Khaoua, University of Glasgow, UK Poster Co-Chairs: Xi Zhang, Texas A&M University, USA Jelena Misic, University of Manitoba, Canada Publicity Chair Mirela Notare, Barddal University, Brazil Demo Co-Chairs Ioannis Chatzigiannakis, University of Patras and CTI, Greece Damla Turgut, University of Central Florida, USA Webmaster and System Chair Luciano Bononi, Uinversity of Bologna, Italy Steering Committee Chair Azzedine Boukerche, University of Ottawa, Canada Technical Program Committee The complete list of the TPC can be found at http://www.cs.unibo.it/projects/mswim2007/committee.htm -- 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 Mar 12 15:58:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQqes-00005Z-Ey; Mon, 12 Mar 2007 15:58:14 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQZ8h-0007jO-8b; Sun, 11 Mar 2007 21:15:51 -0400 Received: from [2001:12f0:201:1:202:e3ff:fe0f:b8d] (helo=mailman.ufsc.br) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQZ8b-0006f4-8l; Sun, 11 Mar 2007 21:15:51 -0400 Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id E785E7F4FA; Sun, 11 Mar 2007 22:13:55 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24165-02; Sun, 11 Mar 2007 22:13:55 -0300 (BRT) Received: from mailman.ufsc.br (mailman.ufsc.br [150.162.1.5]) by mailman.ufsc.br (Postfix) with ESMTP id 0F7E17ED78; Sun, 11 Mar 2007 21:33:52 -0300 (BRT) X-Original-To: researchers@mailman.ufsc.br Delivered-To: researchers@mailman.ufsc.br Received: from localhost (localhost [127.0.0.1]) by mailman.ufsc.br (Postfix) with ESMTP id C87537F7E4 for ; Sun, 11 Mar 2007 21:33:36 -0300 (BRT) Received: from mailman.ufsc.br ([127.0.0.1]) by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21172-03 for ; Sun, 11 Mar 2007 21:33:26 -0300 (BRT) Received: from rot.barddal.br (44054.static.fln.virtua.com.br [200.174.44.54]) by mailman.ufsc.br (Postfix) with ESMTP id 7EE857F262 for ; Sun, 11 Mar 2007 21:25:00 -0300 (BRT) Received: from mi0f9a3e303b4e (201-14-148-83.fnsce703.dsl.brasiltelecom.net.br [201.14.148.83] (may be forged)) (authenticated bits=0) by rot.barddal.br (8.13.1/8.13.1) with ESMTP id l2C0Meuc022360; Mon, 12 Mar 2007 00:22:42 GMT Message-ID: <00e601c7643c$94338c10$7f00a8c0@mi0f9a3e303b4e> From: "Profa Mirela Sechi Moretti Annoni Notare" To: Date: Sun, 11 Mar 2007 21:22:40 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-barddal-MailScanner-Information: Please contact the ISP for more information X-barddal-MailScanner: Found to be clean X-barddal-MailScanner-SpamCheck: spam, SpamAssassin (not cached, escore=6.864, requerido 6, BAYES_00 -2.60, HELO_DYNAMIC_IPADDR 4.40, RCVD_IN_SORBS_DUL 1.99, RCVD_IN_XBL 3.08) X-barddal-MailScanner-SpamScore: ssssss X-barddal-MailScanner-From: mirela@barddal.br X-Virus-Scanned: by amavisd-new at mailman.ufsc.br X-BeenThere: researchers@mailman.ufsc.br X-Mailman-Version: 2.1.5 Precedence: list X-Virus-Scanned: by amavisd-new at mailman.ufsc.br X-Spam-Score: 0.1 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab X-Mailman-Approved-At: Mon, 12 Mar 2007 15:58:12 -0400 Cc: Subject: [Mip4] [Researchers] {Spam?} 10th IEEE/ACM MSWiM2007 - CreteIsland, 22-26/10/2007 X-BeenThere: mip4@ietf.org List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Sorry if you have received multiple messages. --------------------------------------------------------------------------- 10th ACM/IEEE MSWiM 2007 --------------------------------------------------------------------------- Call for Papers The 10th ACM/IEEE* International Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems Chania, Crete Island, Greece October 22 - 26, 2007 http://www.cs.unibo.it/mswim2007 --------------------------------------------------------------------------- Note: A Special Issue of Performance Evaluation (Elsevier) is planned and will contain a revised and extended version of selected best papers from MSWiM 2007 -------------------------------------------------------------------------- * IEEE/ACM Pending Upon Approval -------------------------------------------------------------------------- Submission deadline: May 2, 2007 -------------------------------------------------------------------------- * Scope and Overview: ACM/IEEE MSWiM 2007 is the Tenth Annual International Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems. MSWiM is an international forum dedicated to high level discussion of Wireless and Mobile systems, networks, algorithms and applications, with an emphasis on rigorous performance evaluation. MSWiM is a highly selective conference that is recognized as one of the most prestigious sources of innovative ideas and breakthroughs in the field. MSWiM 2007 will be held October 22 to 26, 2007, in the beautiful and sunny Chania, Crete Island, Greece. Authors are encouraged to submit full papers presenting new research related to the theory or practice of all aspects of modeling, analysis and simulation of mobile and wireless systems. Submitted papers must not have been published elsewhere nor currently be under review by another conference or journal. * Topics of Interest. Papers related to wireless and mobile network Modeling, Analysis, Design, and Simulation are solicited on, but not limited to, the following topics in mobile and wireless systems: - Performance evaluation and modeling - Analytical Models - Simulation languages and tools for wireless systems - Wireless measurements tools and experiences - Formal methods for analysis of wireless systems - Correctness, survivability and reliability evaluation - Mobility modeling and management - Capacity, coverage and connectivity modeling and analysis - Wireless network algorithms and protocols - Wireless PANs, LANs - Ad hoc networks - Sensor and actuator networks - Integration of wired and wireless systems - Pervasive computing and emerging models - Wireless multimedia systems - QoS provisioning in wireless and mobile networks - Security and privacy of mobile/wireless systems - Algorithms and protocols for energy efficient operation and power control - Mobile applications, system software and algorithms - RF channel modeling and analysis - Design methodologies - Tools, prototype and testbeds - Parallel and distributed simulation of wireless systems Submission instructions and publication can be found at (http://www.cs.unibo.it/mswim2007). Accepted papers will appear in the conference proceedings to be published by ACM press. A Journal Special Issue will be planned for extended versions of the best papers from MSWiM. -------------------------------------------------------------------------- *Important Dates: Paper submission deadline May 2, 2007 Notification of acceptance July 6, 2007 Tutorial submission deadline June 5, 2007 Workshop submission deadline March 30, 2007 -------------------------------------------------------------------------- General Chair: Carla-Fabiana Chiasserini, Politecnico di Torino, Italy Program Committee Chairs: Nael Abu-Ghazaleh, State University of New York at Binghamton, USA Sotiris Nikoletseas, University of Patras and CTI, Greece Tutorial Chair Stephan Olariu, Old Dominion University, USA Hsiao-Hwa Chen, National Sun Yat-Sen University, Taiwan Workshop Chair Mohamed Ould-Khaoua, University of Glasgow, UK Poster Co-Chairs: Xi Zhang, Texas A&M University, USA Jelena Misic, University of Manitoba, Canada Publicity Chair Mirela Notare, Barddal University, Brazil Demo Co-Chairs Ioannis Chatzigiannakis, University of Patras and CTI, Greece Damla Turgut, University of Central Florida, USA Webmaster and System Chair Luciano Bononi, Uinversity of Bologna, Italy Steering Committee Chair Azzedine Boukerche, University of Ottawa, Canada Technical Program Committee The complete list of the TPC can be found at http://www.cs.unibo.it/projects/mswim2007/committee.htm -- Esta mensagem foi verificada pelo sistema de antivírus e acredita-se estar livre de perigo. _______________________________________________ Researchers mailing list Researchers@mailman.ufsc.br http://mailman.ufsc.br/mailman/listinfo/researchers -- 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 Mar 12 16:00:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQqgx-0001UF-CA; Mon, 12 Mar 2007 16:00:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQRVs-0006hk-Ak for mip4@ietf.org; Sun, 11 Mar 2007 13:07:16 -0400 Received: from golem.dinale.com ([82.208.35.193] helo=bobrock.dinale.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQRVq-0005lY-RW for mip4@ietf.org; Sun, 11 Mar 2007 13:07:16 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by bobrock.dinale.com (Postfix) with ESMTP id 11BE21D75C; Sun, 11 Mar 2007 18:14:57 +0100 (CET) Received: from bobrock.dinale.com ([127.0.0.1]) by localhost (golem [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02811-09; Sun, 11 Mar 2007 18:14:47 +0100 (CET) Received: from [192.168.10.45] (adsl-86-114.37-151.net24.it [151.37.114.86]) by bobrock.dinale.com (Postfix) with ESMTP id 655741D75A; Sun, 11 Mar 2007 18:14:47 +0100 (CET) Message-ID: <45F4370B.3040509@athonet.com> Date: Sun, 11 Mar 2007 18:06:19 +0100 From: Karim El Malki User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chugtu Manish-a22653 References: <66789B449BDE4F4588F70408F8908D7401C460BA@ZMY16EXM67.ds.mot.com> In-Reply-To: <66789B449BDE4F4588F70408F8908D7401C460BA@ZMY16EXM67.ds.mot.com> X-Enigmail-Version: 0.92.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at Dinale IT X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 X-Mailman-Approved-At: Mon, 12 Mar 2007 16:00:19 -0400 Cc: mip4@ietf.org Subject: [Mip4] Re: Pre-Registration Request routing issue in Low Latency Handoffs in Mobile IPv4 Draft -- X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Manish, If I understand the problem correctly, you're saying that it would take longer for the Registration Req to reach nFA in the case of reverse tunnelling since it would have to traverse the HA twice. This may or may not delay the actual handoff depending on the anticipation time and the FA-HA delay. Typically the wireless leg and handoff time tend to compensate for additional fixed delays so there would not be a problem. However there may be a case where the overall handoff time is impacted (do you have any practical case?) thus we could introduce shorter path routing for the reverse tunnelling case. The oFA has knowledge of its nFA neighbour addresses and could further filter incoming packets (RR?) destined to the nFA routing them through the secure oFA-nFA interface. That would be compatible with reverse tunnelling and the packets wouldn't be dropped by source address filters. There's a couple of issues, possibily including this one, that I'd like to take up in a revision of the draft following RFC publication (in RFC Ed queue). I'll put forward a list. Regards, Karim Chugtu Manish-a22653 wrote: > Hi Karim, > > This is regarding the method of handling Pre-Registration request by oFA > in the /Low Latency Handoffs in Mobile IPv4 / > / Internet > Draft./ According to me, the way it is handled by the draft might have a > problem as follows: > > Pre-Registration according to draft should be treated as *normal IP > packet which has to be routed **to the nFA by oFA*. But since the MN is > already registered to oFA and lets say we have Reverse Tunneling enabled > on oFA, any packet with the source address as Home Address of MN would > be tunneled to HA including the Pre-registration packet, which is not > what we want. > > Also, in this case if somehow we route the Pre-Reg packet to the nFa > by-passing reverse tunneling (by defining some routing policies or may > be by coding it in such way) , it still may not be a good idea, since > one of the main reason for reverse tunneling is to avoid packet drops > for topologically in-correct source address. > > So we would have to define a specific way to handle Pre-Reg packets in > reverse tunneling case eg: Might need to tunnel it to the nFA. Please > let me know your inputs and also in case I am missing something here. In > case you agree to the problem, do you think we might need a revision to > the draft which states and addresses the above mentioned problem > > Best Regards > Manish Chugtu -- 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 Mar 13 19:08:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRG6o-0003jk-K2; Tue, 13 Mar 2007 19:08:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRG6n-0003jf-Kc for mip4@ietf.org; Tue, 13 Mar 2007 19:08:45 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRG6l-0000tU-2t for mip4@ietf.org; Tue, 13 Mar 2007 19:08:45 -0400 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 13 Mar 2007 16:08:33 -0700 X-IronPort-AV: i="4.14,281,1170662400"; d="scan'208"; a="470476739:sNHT21401930448" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l2DN8XN5004999 for ; Tue, 13 Mar 2007 16:08:33 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2DN7TZ0007775 for ; Tue, 13 Mar 2007 23:08:33 GMT Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Mar 2007 16:08:15 -0700 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Tue, 13 Mar 2007 16:08:15 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52037BC6B7@xmb-sjc-235.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Thread-Index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJA From: "Kent Leung \(kleung\)" To: X-OriginalArrivalTime: 13 Mar 2007 23:08:15.0385 (UTC) FILETIME=[7AEF5890:01C765C4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3415; t=1173827313; x=1174691313; c=relaxed/simple; s=sjdkim1004; 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 |Subject:=20RE=3A=20[Mip4]=20I-D=20ACTION=3Adraft-ietf-mip4-rfc3344bis-03 .txt=20 |Sender:=20; bh=B7xHQqDDmJwtIHt24taQIfK3O0vuNAcX8lvuaub8KJY=; b=W+EZQCR6Zo0CHsHeCu2DsKpTL8hEYXUoIK0DnVdv1Q1Bk2wUcoEa3WJNZsPKrJZyVwZOc9RU Ut+F8QPy1fXaz0gBOjOzMJLIN/Guj8KixE1xXAuDs0GmwPF9Yl+7Iwsxs0qlaEsjpATQkvCTLB 5g5HPBbvrRHiKAYhfomh3BlJs=; Authentication-Results: sj-dkim-1; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org =20 Hi. The FA logic in handing registration reply in section 3.7.3.1 has shortcomings. When multiple MNs with different NAIs sent registration requests with the same ID field (i.e. at the same time) and Home Address set to zero, the FA cannot map the registration reply to the right pending request. It would be unambiguous if FA can map the reply to the request based on the NAI and ID field when NAI extension was in the registration request. Kent -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Thursday, March 08, 2007 12:50 PM To: i-d-announce@ietf.org Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt=20 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 : IP Mobility Support for IPv4, revised Author(s) : C. Perkins Filename : draft-ietf-mip4-rfc3344bis-03.txt Pages : 99 Date : 2007-3-8 =09 This document specifies protocol enhancements that allow transparent routing of IP datagrams to mobile nodes in the Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about its current point of attachment to the Internet. The protocol provides for registering the care-of address with a home agent. The home agent sends datagrams destined for the mobile node through a tunnel to the care-of address. After arriving at the end of the tunnel, each datagram is then delivered to the mobile node. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-03.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.=20 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-rfc3344bis-03.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-rfc3344bis-03.txt". =09 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/ From mip4-bounces@ietf.org Tue Mar 13 19:35:01 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRGWD-0001K7-Fk; Tue, 13 Mar 2007 19:35:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRGWC-0001Iy-2N for mip4@ietf.org; Tue, 13 Mar 2007 19:35:00 -0400 Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRGW9-0004cn-Kf for mip4@ietf.org; Tue, 13 Mar 2007 19:35:00 -0400 Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l2DNYs201987; Wed, 14 Mar 2007 00:34:54 +0100 (GMT) 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Tue, 13 Mar 2007 18:34:43 -0500 Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA4371132C79EE@zrc2hxm2.corp.nortel.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC52037BC6B7@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt thread-index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJAAADxxdA= References: <2979E38DD6FC6544B789C8DAD7BAFC52037BC6B7@xmb-sjc-235.amer.cisco.com> From: "Ahmad Muhanna" To: "Kent Leung \(kleung\)" , X-Spam-Score: 0.6 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Kent, Please see comments inline. Regards, Ahmad =20 > -----Original Message----- > From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20 > Sent: Tuesday, March 13, 2007 6:08 PM > To: mip4@ietf.org > Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt >=20 > =20 > Hi. The FA logic in handing registration reply in section=20 > 3.7.3.1 has shortcomings. When multiple MNs with different=20 > NAIs sent registration requests with the same ID field (i.e.=20 > at the same time) and Home Address set to zero, the FA cannot=20 [Ahmad] I understand that the higher order 32 bits of the RRQ ID is the time stamp but what do you mean that the RRQ IDs are equal? Can you elaborate a little more. Thanks. > map the registration reply to the right pending request. >=20 > It would be unambiguous if FA can map the reply to the=20 > request based on the NAI and ID field when NAI extension was=20 > in the registration request. >=20 > Kent >=20 >=20 > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Thursday, March 08, 2007 12:50 PM > To: i-d-announce@ietf.org > Cc: mip4@ietf.org > Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt=20 >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Mobility for IPv4 Working=20 > Group of the IETF. >=20 > Title : IP Mobility Support for IPv4, revised > Author(s) : C. Perkins > Filename : draft-ietf-mip4-rfc3344bis-03.txt > Pages : 99 > Date : 2007-3-8 > =09 > This document specifies protocol enhancements that allow transparent > routing of IP datagrams to mobile nodes in the Internet. Each > mobile node is always identified by its home address, regardless of > its current point of attachment to the Internet. While situated > away from its home, a mobile node is also associated with a > care-of address, which provides information about its current >=20 > point of attachment to the Internet. The protocol provides for > registering the care-of address with a home agent. The home agent > sends datagrams destined for the mobile node through a tunnel to > the care-of address. After arriving at the end of the tunnel, each > datagram is then delivered to the mobile node. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt >=20 > To remove yourself from the I-D Announcement list, send a=20 > message to i-d-announce-request@ietf.org with the word=20 > unsubscribe in the body of the message.=20 > You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login=20 > with the username "anonymous" and a password of your e-mail=20 > address. After logging in, type "cd internet-drafts" and then=20 > "get draft-ietf-mip4-rfc3344bis-03.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt". > =09 > 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=20 > 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. >=20 > Below is the data which will enable a MIME compliant mail=20 > reader implementation to automatically retrieve the ASCII=20 > version of the Internet-Draft. >=20 > -- > 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/ >=20 -- 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 Mar 13 19:44:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRGep-0005qc-P0; Tue, 13 Mar 2007 19:43:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRGeo-0005qX-3v for mip4@ietf.org; Tue, 13 Mar 2007 19:43:54 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRGeg-0006av-IK for mip4@ietf.org; Tue, 13 Mar 2007 19:43:54 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 13 Mar 2007 16:43:46 -0700 X-IronPort-AV: i="4.14,281,1170662400"; d="scan'208"; a="121101287:sNHT60563934" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l2DNhkUV011676; Tue, 13 Mar 2007 16:43:46 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2DNhjdv007220; Tue, 13 Mar 2007 23:43:46 GMT Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Mar 2007 16:43:45 -0700 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Tue, 13 Mar 2007 16:43:39 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52037BC701@xmb-sjc-235.amer.cisco.com> In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA4371132C79EE@zrc2hxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Thread-Index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJAAADxxdAAAFltEA== From: "Kent Leung \(kleung\)" To: "Ahmad Muhanna" , X-OriginalArrivalTime: 13 Mar 2007 23:43:45.0661 (UTC) FILETIME=[70ADAAD0:01C765C9] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5017; t=1173829426; x=1174693426; 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 |Subject:=20RE=3A=20[Mip4]=20I-D=20ACTION=3Adraft-ietf-mip4-rfc3344bis-03 .txt |Sender:=20; bh=bLq90jGquatVtMYD+h3DLgH/YIR/aQtcCbUfrBRKSDQ=; b=QoCyKoaFPpaHxI+EwiPJ3eITGdd3Z0J1mK/jKroqussBG3c9Eg03Tk4xuN1IU5TWZp7TP22v yHDw8rGaTw1sow7NJpJ+4cmP4+nFz2PinL4W69Ezt3UnBQL00Diif/jM; 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: 8fbbaa16f9fd29df280814cb95ae2290 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Ahmad. See comments below.=20 -----Original Message----- From: Ahmad Muhanna [mailto:amuhanna@nortel.com]=20 Sent: Tuesday, March 13, 2007 4:35 PM To: Kent Leung (kleung); mip4@ietf.org Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Hi Kent, Please see comments inline. Regards, Ahmad =20 > -----Original Message----- > From: Kent Leung (kleung) [mailto:kleung@cisco.com] > Sent: Tuesday, March 13, 2007 6:08 PM > To: mip4@ietf.org > Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt >=20 > =20 > Hi. The FA logic in handing registration reply in section > 3.7.3.1 has shortcomings. When multiple MNs with different NAIs sent=20 > registration requests with the same ID field (i.e. > at the same time) and Home Address set to zero, the FA cannot [Ahmad] I understand that the higher order 32 bits of the RRQ ID is the time stamp but what do you mean that the RRQ IDs are equal? Can you elaborate a little more. Thanks. KL> The total 64-bit value in the Identification field is the same. This means that the lower 32 bits containing the fractional second is identical as well. Actually, this problem happens when the lower 32 bits are the same among pending RRQs with Home Address field set to zero. But most likely the upper 32 bits are the same because pending requests are processed fairly quickly. Kent > map the registration reply to the right pending request. >=20 > It would be unambiguous if FA can map the reply to the request based=20 > on the NAI and ID field when NAI extension was in the registration=20 > request. >=20 > Kent >=20 >=20 > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > Sent: Thursday, March 08, 2007 12:50 PM > To: i-d-announce@ietf.org > Cc: mip4@ietf.org > Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt >=20 > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. > This draft is a work item of the Mobility for IPv4 Working Group of=20 > the IETF. >=20 > Title : IP Mobility Support for IPv4, revised > Author(s) : C. Perkins > Filename : draft-ietf-mip4-rfc3344bis-03.txt > Pages : 99 > Date : 2007-3-8 > =09 > This document specifies protocol enhancements that allow transparent > routing of IP datagrams to mobile nodes in the Internet. Each > mobile node is always identified by its home address, regardless of > its current point of attachment to the Internet. While situated > away from its home, a mobile node is also associated with a > care-of address, which provides information about its current >=20 > point of attachment to the Internet. The protocol provides for > registering the care-of address with a home agent. The home agent > sends datagrams destined for the mobile node through a tunnel to > the care-of address. After arriving at the end of the tunnel, each > datagram is then delivered to the mobile node. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt >=20 > To remove yourself from the I-D Announcement list, send a message to=20 > 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. >=20 > Internet-Drafts are also available by anonymous FTP. Login with the=20 > username "anonymous" and a password of your e-mail address. After=20 > logging in, type "cd internet-drafts" and then "get=20 > draft-ietf-mip4-rfc3344bis-03.txt". >=20 > A list of Internet-Drafts directories can be found in=20 > http://www.ietf.org/shadow.html or=20 > ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt". > =09 > 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. >=20 > Below is the data which will enable a MIME compliant mail reader=20 > implementation to automatically retrieve the ASCII version of the=20 > Internet-Draft. >=20 > -- > 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/ >=20 -- 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 Mar 14 00:11:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKph-0006jo-KD; Wed, 14 Mar 2007 00:11:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKpg-0006iE-9N for mip4@ietf.org; Wed, 14 Mar 2007 00:11:24 -0400 Received: from zcars04e.nortel.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKpe-00031R-RY for mip4@ietf.org; Wed, 14 Mar 2007 00:11:24 -0400 Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id l2E4BAd19699; Wed, 14 Mar 2007 05:11:10 +0100 (GMT) 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Tue, 13 Mar 2007 23:11:15 -0500 Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA4371132C7ABE@zrc2hxm2.corp.nortel.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC52037BC701@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt thread-index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJAAADxxdAAAFltEAAJG92w References: <6FC4416DDE56C44DA0AEE67BC7CA4371132C79EE@zrc2hxm2.corp.nortel.com> <2979E38DD6FC6544B789C8DAD7BAFC52037BC701@xmb-sjc-235.amer.cisco.com> From: "Ahmad Muhanna" To: "Kent Leung \(kleung\)" , X-Spam-Score: 0.6 (/) X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Kent, In the same section you mentioned 3.7.3.1., I think the text already covers what you are requesting and I do not see any ambiguity. Here is the excerpt: " When a foreign agent receives a Registration Reply message, it MUST search its visitor list for a pending Registration Request with the same mobile node home address as indicated in the Reply. If no such pending Request is found, and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1), the foreign agent MUST silently discard the Reply. The foreign agent MUST also silently discard the Reply if the low-order 32 bits of the Identification field in the Reply do not match those in the Request. " I think the key text here is "... , and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1) ....." And since section 3.7.1. refers to RFC2794 which address the identification of a user/MN using NAI while the Home address field of zero. I believe the text already covers what you are looking for. No? Regards, Ahmad =20 > -----Original Message----- > From: Kent Leung (kleung) [mailto:kleung@cisco.com]=20 > Sent: Tuesday, March 13, 2007 6:44 PM > To: Muhanna, Ahmad (RICH1:2H10); mip4@ietf.org > Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt >=20 > Hi Ahmad. See comments below.=20 >=20 > -----Original Message----- > From: Ahmad Muhanna [mailto:amuhanna@nortel.com] > Sent: Tuesday, March 13, 2007 4:35 PM > To: Kent Leung (kleung); mip4@ietf.org > Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt >=20 > Hi Kent, > Please see comments inline. >=20 > Regards, > Ahmad > =20 >=20 > > -----Original Message----- > > From: Kent Leung (kleung) [mailto:kleung@cisco.com] > > Sent: Tuesday, March 13, 2007 6:08 PM > > To: mip4@ietf.org > > Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt > >=20 > > =20 > > Hi. The FA logic in handing registration reply in section > > 3.7.3.1 has shortcomings. When multiple MNs with different=20 > NAIs sent=20 > > registration requests with the same ID field (i.e. > > at the same time) and Home Address set to zero, the FA cannot >=20 > [Ahmad] > I understand that the higher order 32 bits of the RRQ ID is=20 > the time stamp but what do you mean that the RRQ IDs are=20 > equal? Can you elaborate a little more. Thanks. >=20 > KL> The total 64-bit value in the Identification field is the same. > This means that the lower 32 bits containing the fractional=20 > second is identical as well. Actually, this problem happens=20 > when the lower 32 bits are the same among pending RRQs with=20 > Home Address field set to zero. But most likely the upper 32=20 > bits are the same because pending requests are processed=20 > fairly quickly. >=20 > Kent >=20 >=20 >=20 > > map the registration reply to the right pending request. > >=20 > > It would be unambiguous if FA can map the reply to the=20 > request based=20 > > on the NAI and ID field when NAI extension was in the registration=20 > > request. >=20 > >=20 > > Kent > >=20 > >=20 > > -----Original Message----- > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > Sent: Thursday, March 08, 2007 12:50 PM > > To: i-d-announce@ietf.org > > Cc: mip4@ietf.org > > Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt > >=20 > > A New Internet-Draft is available from the on-line Internet-Drafts=20 > > directories. > > This draft is a work item of the Mobility for IPv4 Working Group of=20 > > the IETF. > >=20 > > Title : IP Mobility Support for IPv4, revised > > Author(s) : C. Perkins > > Filename : draft-ietf-mip4-rfc3344bis-03.txt > > Pages : 99 > > Date : 2007-3-8 > > =09 > > This document specifies protocol enhancements that allow transparent > > routing of IP datagrams to mobile nodes in the Internet. Each > > mobile node is always identified by its home address,=20 > regardless of > > its current point of attachment to the Internet. While situated > > away from its home, a mobile node is also associated with a > > care-of address, which provides information about its current > >=20 > > point of attachment to the Internet. The protocol provides for > > registering the care-of address with a home agent. The=20 > home agent > > sends datagrams destined for the mobile node through a tunnel to > > the care-of address. After arriving at the end of the=20 > tunnel, each > > datagram is then delivered to the mobile node. > >=20 > > A URL for this Internet-Draft is: > >=20 > http://www.ietf.org/internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt > >=20 > > To remove yourself from the I-D Announcement list, send a=20 > message to=20 > > i-d-announce-request@ietf.org with the word unsubscribe in=20 > the body of >=20 > > the message. > > You can also visit=20 > https://www1.ietf.org/mailman/listinfo/I-D-announce > > to change your subscription settings. > >=20 > > Internet-Drafts are also available by anonymous FTP. Login with the=20 > > username "anonymous" and a password of your e-mail address. After=20 > > logging in, type "cd internet-drafts" and then "get=20 > > draft-ietf-mip4-rfc3344bis-03.txt". > >=20 > > A list of Internet-Drafts directories can be found in=20 > > http://www.ietf.org/shadow.html or=20 > > ftp://ftp.ietf.org/ietf/1shadow-sites.txt > >=20 > > Internet-Drafts can also be obtained by e-mail. > >=20 > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-03.txt". > > =09 > > 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. > >=20 > > Below is the data which will enable a MIME compliant mail reader=20 > > implementation to automatically retrieve the ASCII version of the=20 > > Internet-Draft. > >=20 > > -- > > Mip4 mailing list: Mip4@ietf.org > > Web interface: https://www1.ietf.org/mailman/listinfo/mip4 > > Charter page:=20 > http://www.ietf.org/html.charters/mip4-charter.html > > Supplemental site: http://www.mip4.org/ > >=20 >=20 -- 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 Mar 14 04:12:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HROan-0000wd-EB; Wed, 14 Mar 2007 04:12:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HROal-0000u6-H9 for mip4@ietf.org; Wed, 14 Mar 2007 04:12:15 -0400 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HROak-0003ec-8m for mip4@ietf.org; Wed, 14 Mar 2007 04:12:15 -0400 Received: from sj-core-3.cisco.com ([171.68.223.137]) by rtp-iport-2.cisco.com with ESMTP; 14 Mar 2007 04:12:10 -0400 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l2E7MSnu003578; Wed, 14 Mar 2007 07:22:28 GMT Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Mar 2007 00:22:28 -0700 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Wed, 14 Mar 2007 00:22:26 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52037BC832@xmb-sjc-235.amer.cisco.com> In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA4371132C7ABE@zrc2hxm2.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Thread-Index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJAAADxxdAAAFltEAAJG92wAAY+iIA= From: "Kent Leung \(kleung\)" To: "Ahmad Muhanna" , X-OriginalArrivalTime: 14 Mar 2007 07:22:28.0372 (UTC) FILETIME=[857E1540:01C76609] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Ahmad. I agree that it's OK, my oversight on "see section 3.7.1" and assumption that the reply must be discarded. Thanks. Kent -----Original Message----- From: Ahmad Muhanna [mailto:amuhanna@nortel.com]=20 Sent: Tuesday, March 13, 2007 9:11 PM To: Kent Leung (kleung); mip4@ietf.org Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Hi Kent, In the same section you mentioned 3.7.3.1., I think the text already covers what you are requesting and I do not see any ambiguity. Here is the excerpt: " When a foreign agent receives a Registration Reply message, it MUST search its visitor list for a pending Registration Request with the same mobile node home address as indicated in the Reply. If no such pending Request is found, and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1), the foreign agent MUST silently discard the Reply. The foreign agent MUST also silently discard the Reply if the low-order 32 bits of the Identification field in the Reply do not match those in the Request. " I think the key text here is "... , and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1) ....." And since section 3.7.1. refers to RFC2794 which address the identification of a user/MN using NAI while the Home address field of zero. I believe the text already covers what you are looking for. No? Regards, Ahmad =20 -- 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 Mar 14 05:30:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRPoB-0008Sb-F1; Wed, 14 Mar 2007 05:30:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRPoA-0008SV-Aw for mip4@ietf.org; Wed, 14 Mar 2007 05:30:10 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRPo6-00050q-RQ for mip4@ietf.org; Wed, 14 Mar 2007 05:30:10 -0400 Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-4.cisco.com with ESMTP; 14 Mar 2007 02:30:06 -0700 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l2E8p2tG010334; Wed, 14 Mar 2007 01:51:02 -0700 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l2E8ovWQ004179; Wed, 14 Mar 2007 08:51:02 GMT Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 14 Mar 2007 01:50:57 -0700 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] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Date: Wed, 14 Mar 2007 01:48:33 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52037BC836@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Thread-Index: Acdhw6D9M4WIYTVmRtqbZNN+6lKInQD/6uJAAADxxdAAAFltEAAJG92wAAY+iIAAAdiz0A== From: "Kent Leung \(kleung\)" To: "Ahmad Muhanna" , X-OriginalArrivalTime: 14 Mar 2007 08:50:57.0695 (UTC) FILETIME=[E2187AF0:01C76615] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4326; t=1173862262; x=1174726262; c=relaxed/simple; s=sjdkim6002; 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 |Subject:=20RE=3A=20[Mip4]=20I-D=20ACTION=3Adraft-ietf-mip4-rfc3344bis-03 .txt |Sender:=20; bh=K7+dxbetM9q1tpAsgT1+NJSo/FqkTYP29k/WxQp3Mf8=; b=BlnsdOqnOvfC5f4/6WRBrpdRmlL6cU4ug2etvbZ3LUbUfamb0EsIZ3H9mvh/GCaxVqE1YTAI 6bW5QQ1AfUmiBSdTRG56Rk5/16T3srfguZUIuZAo5d7cV8qsxEa7kqcY; Authentication-Results: sj-dkim-6; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim6002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org =20 Now I remember why the section seems wrong to me. The index to the pending registration request is based on home address and ID if home address is non-zero. And in accordance to RFC 2794, index is based on NAI and ID when home address is zero. But when multiple MNs with different NAIs registers with same non-zero home address and ID, this logic cannot discern the mapping of reply to request because the home address is copied from the RRQ to the RRP. The statement below will find a RRQ that may not correspond to the RRP for the same MN. "When a foreign agent receives a Registration Reply message, it MUST search its visitor list for a pending Registration Request with the same mobile node home address as indicated in the Reply. (...) The foreign agent MUST also silently discard the Reply if the low-order 32 bits of the Identification field in the Reply do not match those in the Request." So going back to what I said, "It would be unambiguous if FA can map the reply to the request based on the NAI and ID field when NAI extension was in the registration request." This is different in the sense that the index is always based on NAI and ID if the NAI extension is in the RRQ. Suggested text for 3.7.3.1: When a foreign agent receives a Registration Reply message, it MUST search its visitor list for a pending Registration Request that corresponds to the Reply. If the NAI extension is present in the Registration Reply, then the mobile node is identified by the NAI instead of the home address. The foreign agent looks up the pending Request that matches the mobile node identifier. If the Registration Reply does not correspond with any pending=20 Registration Request, the foreign agent MUST silently discard the Reply. The foreign agent MUST also silently discard the Reply if the low-order 32 bits of the Identification field in the Reply do not match those in the Request. Suggested text for 3.7.1: If there is an NAI extension in the Registration Request message, then the foreign agent MUST follow the procedures specified in RFC 2794 [2]. In particular, if the foreign agent cannot manage pending registration request records with NAI for the mobile node, the foreign agent MUST return a Registration Reply with Code indicating NONZERO_HOMEADDR_REQD (see [2]). This assumes that 2794bis addresses NAI/nonzero HoA case. Hope I'm making sense as it's getting late.. Kent -----Original Message----- From: Kent Leung (kleung)=20 Sent: Wednesday, March 14, 2007 12:22 AM To: 'Ahmad Muhanna'; mip4@ietf.org Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Hi Ahmad. I agree that it's OK, my oversight on "see section 3.7.1" and assumption that the reply must be discarded. Thanks. Kent -----Original Message----- From: Ahmad Muhanna [mailto:amuhanna@nortel.com] Sent: Tuesday, March 13, 2007 9:11 PM To: Kent Leung (kleung); mip4@ietf.org Subject: RE: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt Hi Kent, In the same section you mentioned 3.7.3.1., I think the text already covers what you are requesting and I do not see any ambiguity. Here is the excerpt: " When a foreign agent receives a Registration Reply message, it MUST search its visitor list for a pending Registration Request with the same mobile node home address as indicated in the Reply. If no such pending Request is found, and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1), the foreign agent MUST silently discard the Reply. The foreign agent MUST also silently discard the Reply if the low-order 32 bits of the Identification field in the Reply do not match those in the Request. " I think the key text here is "... , and if the Registration Reply does not correspond with any pending Registration Request with a zero mobile node home address (see section 3.7.1) ....." And since section 3.7.1. refers to RFC2794 which address the identification of a user/MN using NAI while the Home address field of zero. I believe the text already covers what you are looking for. No? Regards, Ahmad =20 -- 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 Mar 14 10:49:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRUmj-0007Wr-SM; Wed, 14 Mar 2007 10:49:01 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRUmg-0007Vn-Oq; Wed, 14 Mar 2007 10:48:58 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HRUme-0005tf-FP; Wed, 14 Mar 2007 10:48:58 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 69DD8175D5; Wed, 14 Mar 2007 14:48:26 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HRUmA-00024M-6I; Wed, 14 Mar 2007 10:48:26 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Wed, 14 Mar 2007 10:48:26 -0400 X-Spam-Score: -2.8 (--) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: mip4 chair , Internet Architecture Board , mip4 mailing list , RFC Editor Subject: [Mip4] Protocol Action: 'Mobile IPv4 Message String Extension' to Proposed Standard X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org The IESG has approved the following document: - 'Mobile IPv4 Message String Extension ' as a Proposed Standard This document is the product of the Mobility for IPv4 Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-message-string-ext-03.txt Technical Summary This document specifies a new extension for use in Mobile IPv4. This extension can be added by the Home Agent and the Foreign Agent to Registration Reply messages. This extension carries a text string that is intended for the user of the Mobile Node. Working Group Summary There is consensus in the MIP4 working group to publish this document as a Proposed Standard. Document Quality The document has been through working group last call and additional reviews. Personnel Document Sheperd for this document is Henrik Levkowetz, and Jari Arkko is the Responsible Area Director. Note to RFC Editor In Section 3, please change "(In the UTF-8 case, the " to "(The". -- 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 Mar 15 07:03:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRnjt-0000AQ-8U; Thu, 15 Mar 2007 07:03:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRnjr-0000AL-Qd for mip4@ietf.org; Thu, 15 Mar 2007 07:03:19 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HRnjq-0003HF-FN for mip4@ietf.org; Thu, 15 Mar 2007 07:03:19 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-15.tower-128.messagelabs.com!1173956595!4521189!1 X-StarScan-Version: 5.5.10.7.1; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 28914 invoked from network); 15 Mar 2007 11:03:15 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-15.tower-128.messagelabs.com with SMTP; 15 Mar 2007 11:03:15 -0000 Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2FB3E9W017064 for ; Thu, 15 Mar 2007 04:03:14 -0700 (MST) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l2FB3D2W010233 for ; Thu, 15 Mar 2007 06:03:14 -0500 (CDT) Message-ID: <45F927F0.3080304@gmail.com> Date: Thu, 15 Mar 2007 12:03:12 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [Mip4] Other-than-NAT in draft-sjostrand-mip4-udptunnel-mib-01? X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi MIP4, draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP when NAT Traversal is used. As such contains knobs for keepalives, force UDP, etc. I can comment on the draft in detail separately. But I wonder whether this is the only ongoing draft that configures MIB knobs for Mobile IP? I am looking for a ongoing draft that could eventually discuss NEMOv4 MIB knobs. Or maybe in draft-sjostrand too (provided scope changes), I don't know. A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. Thanks, 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 Mar 15 08:32:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRp8H-0000Lp-CD; Thu, 15 Mar 2007 08:32:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRp8F-0000HN-AR for mip4@ietf.org; Thu, 15 Mar 2007 08:32:35 -0400 Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRp8C-0005U2-S1 for mip4@ietf.org; Thu, 15 Mar 2007 08:32:35 -0400 Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502) id DA8363840F; Thu, 15 Mar 2007 13:31:58 +0100 (CET) Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AD82B37EFB; Thu, 15 Mar 2007 13:31:58 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id C76BA37E42; Thu, 15 Mar 2007 13:32:31 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HRp8B-0000yz-BT; Thu, 15 Mar 2007 13:32:31 +0100 Message-ID: <45F93CD4.6020708@levkowetz.com> Date: Thu, 15 Mar 2007 13:32:20 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Alexandru Petrescu Subject: Re: [Mip4] Other-than-NAT in draft-sjostrand-mip4-udptunnel-mib-01? References: <45F927F0.3080304@gmail.com> In-Reply-To: <45F927F0.3080304@gmail.com> X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: alexandru.petrescu@gmail.com, mip4@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: Mobile IPv4 Mailing List X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0023052808==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0023052808== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEA818D4EDA82ACB1B653DC49" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEA818D4EDA82ACB1B653DC49 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Alex, on 2007-03-15 12:03 Alexandru Petrescu said the following: > Hi MIP4, >=20 > draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP whe= n=20 > NAT Traversal is used. As such contains knobs for keepalives, force=20 > UDP, etc. I can comment on the draft in detail separately. >=20 > But I wonder whether this is the only ongoing draft that configures MIB= =20 > knobs for Mobile IP? I am looking for a ongoing draft that could=20 > eventually discuss NEMOv4 MIB knobs. Or maybe in draft-sjostrand too=20 > (provided scope changes), I don't know. >=20 > A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. Going to the mip4 status page (http://tools.ietf.org/wg/mip4/) shows you the 2006bis document among the active mip4 WG documents. Going to the draft and rfc search page (http://tools.ietf.org/search/) produces one hit, which is also the correct document. Regards, Henrik --------------enigEA818D4EDA82ACB1B653DC49 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFF+TzdeVhrtTJkXCMRAiyOAJ43zpKEuE5f7V7YMWE5qB/iUX4nowCg8YH+ vad7RWZY0OOSOpC/lZdiNGw= =7/mE -----END PGP SIGNATURE----- --------------enigEA818D4EDA82ACB1B653DC49-- --===============0023052808== 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/ --===============0023052808==-- From mip4-bounces@ietf.org Thu Mar 15 09:21:22 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRptI-0004w8-42; Thu, 15 Mar 2007 09:21:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRptH-0004vA-7n for mip4@ietf.org; Thu, 15 Mar 2007 09:21:11 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HRptF-0006VF-SA for mip4@ietf.org; Thu, 15 Mar 2007 09:21:11 -0400 X-VirusChecked: Checked X-Env-Sender: alexandru.petrescu@gmail.com X-Msg-Ref: server-13.tower-128.messagelabs.com!1173964868!18585264!1 X-StarScan-Version: 5.5.10.7.1; banners=.,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 4019 invoked from network); 15 Mar 2007 13:21:08 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-13.tower-128.messagelabs.com with SMTP; 15 Mar 2007 13:21:08 -0000 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2FDL8SC021524 for ; Thu, 15 Mar 2007 06:21:08 -0700 (MST) Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id l2FDL7re005632 for ; Thu, 15 Mar 2007 08:21:08 -0500 (CDT) Message-ID: <45F94843.7050603@gmail.com> Date: Thu, 15 Mar 2007 14:21:07 +0100 From: Alexandru Petrescu User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Subject: Re: MIB for NEMOv4? (was: [Mip4] Other-than-NAT in draft-sjostrand-mip4-udptunnel-mib-01?) References: <45F927F0.3080304@gmail.com> <45F93CD4.6020708@levkowetz.com> In-Reply-To: <45F93CD4.6020708@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Thanks Henrik, I was wondering whether this is a good time to discuss about NEMOv4 (draft-ietf-mip4-nemo-v4-base-00.txt) features in MIB (draft-ietf-mip4-rfc2006bis-03.txt). Basically, there are few things that would be nice to be reflected in the MIB: -Prefix Table (at HA). -Mobile Network Prefixes (at MN). -maybe others. So, the initial comment is whether it makes any sense to do these NEMOv4-related additions to Mobile IPv4 MIB? (because it may be considered that the MIB done for NEMOv6, draft-ietf-nemo-mib-02.txt in NEMO WG, could treat IPv4 as well) (or because any other reason I miss). Alex Henrik Levkowetz wrote: > Hi Alex, > > on 2007-03-15 12:03 Alexandru Petrescu said the following: >> Hi MIP4, >> >> draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP when >> NAT Traversal is used. As such contains knobs for keepalives, force >> UDP, etc. I can comment on the draft in detail separately. >> >> But I wonder whether this is the only ongoing draft that configures MIB >> knobs for Mobile IP? I am looking for a ongoing draft that could >> eventually discuss NEMOv4 MIB knobs. Or maybe in draft-sjostrand too >> (provided scope changes), I don't know. >> >> A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. > > Going to the mip4 status page (http://tools.ietf.org/wg/mip4/) shows > you the 2006bis document among the active mip4 WG documents. > > Going to the draft and rfc search page (http://tools.ietf.org/search/) > produces one hit, which is also the correct document. > > > Regards, > > Henrik > ______________________________________________________________________ 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 Mar 15 10:28:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqwN-00083D-4o; Thu, 15 Mar 2007 10:28:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqwL-00082M-UZ for mip4@ietf.org; Thu, 15 Mar 2007 10:28:25 -0400 Received: from 213.80.52.78.dataphone.se ([213.80.52.78] helo=mailgw.local.ipunplugged.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRqwJ-0008CO-Ua for mip4@ietf.org; Thu, 15 Mar 2007 10:28:25 -0400 Received: from [127.0.0.1] (c48.local.ipunplugged.com [192.168.4.247]) by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id l2FESHec030575; Thu, 15 Mar 2007 15:28:19 +0100 Message-ID: <45F957FF.1040707@ipunplugged.com> Date: Thu, 15 Mar 2007 15:28:15 +0100 From: Hans Sjostrand User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Alexandru Petrescu References: <45F927F0.3080304@gmail.com> <45F93CD4.6020708@levkowetz.com> <45F94843.7050603@gmail.com> In-Reply-To: <45F94843.7050603@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on mailgw.local.ipunplugged.com X-Virus-Status: Clean X-Spam-Score: 0.1 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Cc: Mobile IPv4 Mailing List Subject: [Mip4] Re: MIB for NEMOv4? X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Alex, One of the things that we do in the 2006bis work is to create some mib framework so that no more than the core mip management functions are in the mobile ip mib. Basically to put the mipMIB OID under iana control. This makes it easy to extend mip with new management capabilities. Add ons, such as udp tunnelling should go into separate mibs. This is how all modern ietf mibs are done, see e.g. 15 mpls mibs under the ...mib-2.transmission.mplsStdMIB in http://www.iana.org/assignments/smi-numbers . I don't know the NEMO management need enough to say for sure, but I'm very reluctant to put in new stuff in 2006bis. Having a separate mib is a lot better, easier and more maintainable. The big monolithic 2006bis is really a bad idea, but there are a large set of legacy things that where traditionally in rfc2006 so we couldn't go the whole way. Looking forward to more mip mibs. /// Hasse On 2007-03-15 14:21, Alexandru Petrescu wrote: > Thanks Henrik, > > I was wondering whether this is a good time to discuss about NEMOv4 > (draft-ietf-mip4-nemo-v4-base-00.txt) features in MIB > (draft-ietf-mip4-rfc2006bis-03.txt). > > Basically, there are few things that would be nice to be reflected in > the MIB: > -Prefix Table (at HA). > -Mobile Network Prefixes (at MN). > -maybe others. > > So, the initial comment is whether it makes any sense to do these > NEMOv4-related additions to Mobile IPv4 MIB? (because it may be > considered that the MIB done for NEMOv6, draft-ietf-nemo-mib-02.txt in > NEMO WG, could treat IPv4 as well) (or because any other reason I miss). > > Alex > > Henrik Levkowetz wrote: >> Hi Alex, >> >> on 2007-03-15 12:03 Alexandru Petrescu said the following: >>> Hi MIP4, >>> >>> draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP >>> when NAT Traversal is used. As such contains knobs for keepalives, >>> force UDP, etc. I can comment on the draft in detail separately. >>> >>> But I wonder whether this is the only ongoing draft that configures >>> MIB knobs for Mobile IP? I am looking for a ongoing draft that >>> could eventually discuss NEMOv4 MIB knobs. Or maybe in >>> draft-sjostrand too (provided scope changes), I don't know. >>> >>> A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. >> >> Going to the mip4 status page (http://tools.ietf.org/wg/mip4/) shows >> you the 2006bis document among the active mip4 WG documents. >> >> Going to the draft and rfc search page (http://tools.ietf.org/search/) >> produces one hit, which is also the correct document. >> >> >> Regards, >> >> Henrik >> > > > ______________________________________________________________________ > 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 Mar 15 10:29:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqxV-0000ku-Tk; Thu, 15 Mar 2007 10:29:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRqxV-0000hn-3W for mip4@ietf.org; Thu, 15 Mar 2007 10:29:37 -0400 Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRqxT-0008MH-IU for mip4@ietf.org; Thu, 15 Mar 2007 10:29:37 -0400 Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502) id F07583859A; Thu, 15 Mar 2007 15:29:34 +0100 (CET) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id DD9EA3800D; Thu, 15 Mar 2007 15:29:34 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id C687237E46; Thu, 15 Mar 2007 15:29:34 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HRqxS-0007VP-DY; Thu, 15 Mar 2007 15:29:34 +0100 Message-ID: <45F9583D.1060607@levkowetz.com> Date: Thu, 15 Mar 2007 15:29:17 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Alexandru Petrescu References: <45F927F0.3080304@gmail.com> <45F93CD4.6020708@levkowetz.com> <45F94843.7050603@gmail.com> In-Reply-To: <45F94843.7050603@gmail.com> X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: alexandru.petrescu@gmail.com, mip4@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Cc: Mobile IPv4 Mailing List Subject: [Mip4] Re: MIB for NEMOv4? X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1371448638==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1371448638== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig011DD96BE805CCFD3432C7F8" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig011DD96BE805CCFD3432C7F8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Alex, on 2007-03-15 14:21 Alexandru Petrescu said the following: > Thanks Henrik, >=20 > I was wondering whether this is a good time to discuss about NEMOv4=20 > (draft-ietf-mip4-nemo-v4-base-00.txt) features in MIB=20 > (draft-ietf-mip4-rfc2006bis-03.txt). >=20 > Basically, there are few things that would be nice to be reflected in=20 > the MIB: > -Prefix Table (at HA). > -Mobile Network Prefixes (at MN). > -maybe others. >=20 > So, the initial comment is whether it makes any sense to do these=20 > NEMOv4-related additions to Mobile IPv4 MIB? (because it may be=20 > considered that the MIB done for NEMOv6, draft-ietf-nemo-mib-02.txt in = > NEMO WG, could treat IPv4 as well) (or because any other reason I miss)= =2E For the NAT traversal, we made the decision to not include that in the update of the original MIPv4 MIB, but instead create a separate MIB for the NAT traversal functionality. I believe the same approach would be best for a MIPv4 NEMO MIB, but some of the MIB authors may have additional thoughts. Henrik --------------enig011DD96BE805CCFD3432C7F8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFF+VhGeVhrtTJkXCMRAoSUAKC/kZlqe7eR3IyWiqfhSMdcVri/ugCfVR/E vXuMznn1i/4CGR100l9RjxA= =9f2F -----END PGP SIGNATURE----- --------------enig011DD96BE805CCFD3432C7F8-- --===============1371448638== 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/ --===============1371448638==-- From mip4-bounces@ietf.org Thu Mar 15 13:30:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRtmA-0005iR-GW; Thu, 15 Mar 2007 13:30:06 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRtm8-0005hg-OG for mip4@ietf.org; Thu, 15 Mar 2007 13:30:04 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HRtm3-0000t8-3K for mip4@ietf.org; Thu, 15 Mar 2007 13:30:04 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 15 Mar 2007 10:29:58 -0700 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l2FHTw0j009503; Thu, 15 Mar 2007 10:29:58 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2FHTmF2001577; Thu, 15 Mar 2007 17:29:56 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); Thu, 15 Mar 2007 10:29:49 -0700 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] Re: MIB for NEMOv4? Date: Thu, 15 Mar 2007 10:29:48 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52038578A7@xmb-sjc-235.amer.cisco.com> In-Reply-To: <45F957FF.1040707@ipunplugged.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Re: MIB for NEMOv4? Thread-Index: AcdnDpvW/Z6AvClrRKKNbx3deHDsMwAF9x8g From: "Kent Leung \(kleung\)" To: "Hans Sjostrand" , "Alexandru Petrescu" X-OriginalArrivalTime: 15 Mar 2007 17:29:49.0494 (UTC) FILETIME=[8881C560:01C76727] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3568; t=1173979798; x=1174843798; 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 |Subject:=20RE=3A=20[Mip4]=20Re=3A=20MIB=20for=20NEMOv4? |Sender:=20; bh=H93lwyyDqKEOXwMg2rKDCN6yGWIcFFBABTD6LYChBh4=; b=MivtDNyZ4zx/aWXpkLE0A9vF34x1f4CojWCo3lfRyKj+SfmkpZEjqXmZGwDOihtpurn1jFdr w8f4RNP3wSwNKiyrVuwtPBppGsytCIHZM+B9ipiieiHsLzJEOv09mCH8; 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: 6e922792024732fb1bb6f346e63517e4 Cc: Mobile IPv4 Mailing List X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org I agree that NEMOv4 MIBs should be not be bundled into 2006bis and separation of MIBs is much more maintainable. Kent =20 -----Original Message----- From: Hans Sjostrand [mailto:hans@ipunplugged.com]=20 Sent: Thursday, March 15, 2007 7:28 AM To: Alexandru Petrescu Cc: Mobile IPv4 Mailing List Subject: [Mip4] Re: MIB for NEMOv4? Hi Alex, One of the things that we do in the 2006bis work is to create some mib framework so that no more than the core mip management functions are in the mobile ip mib. Basically to put the mipMIB OID under iana control.=20 This makes it easy to extend mip with new management capabilities. Add ons, such as udp tunnelling should go into separate mibs. This is how all modern ietf mibs are done, see e.g. 15 mpls mibs under the ...mib-2.transmission.mplsStdMIB in http://www.iana.org/assignments/smi-numbers . I don't know the NEMO management need enough to say for sure, but I'm very reluctant to put in new stuff in 2006bis. Having a separate mib is a lot better, easier and more maintainable. The big monolithic 2006bis is really a bad idea, but there are a large set of legacy things that where traditionally in rfc2006 so we couldn't go the whole way. Looking forward to more mip mibs. /// Hasse On 2007-03-15 14:21, Alexandru Petrescu wrote: > Thanks Henrik, > > I was wondering whether this is a good time to discuss about NEMOv4 > (draft-ietf-mip4-nemo-v4-base-00.txt) features in MIB=20 > (draft-ietf-mip4-rfc2006bis-03.txt). > > Basically, there are few things that would be nice to be reflected in=20 > the MIB: > -Prefix Table (at HA). > -Mobile Network Prefixes (at MN). > -maybe others. > > So, the initial comment is whether it makes any sense to do these=20 > NEMOv4-related additions to Mobile IPv4 MIB? (because it may be=20 > considered that the MIB done for NEMOv6, draft-ietf-nemo-mib-02.txt in > NEMO WG, could treat IPv4 as well) (or because any other reason I miss). > > Alex > > Henrik Levkowetz wrote: >> Hi Alex, >> >> on 2007-03-15 12:03 Alexandru Petrescu said the following: >>> Hi MIP4, >>> >>> draft-sjostrand-mip4-udptunnel-mib-01 talks about MIB for Mobile IP=20 >>> when NAT Traversal is used. As such contains knobs for keepalives,=20 >>> force UDP, etc. I can comment on the draft in detail separately. >>> >>> But I wonder whether this is the only ongoing draft that configures=20 >>> MIB knobs for Mobile IP? I am looking for a ongoing draft that=20 >>> could eventually discuss NEMOv4 MIB knobs. Or maybe in=20 >>> draft-sjostrand too (provided scope changes), I don't know. >>> >>> A '2006bis' or '2206bis' was mentioned in another NEMO WG discussion. >> >> Going to the mip4 status page (http://tools.ietf.org/wg/mip4/) shows=20 >> you the 2006bis document among the active mip4 WG documents. >> >> Going to the draft and rfc search page=20 >> (http://tools.ietf.org/search/) produces one hit, which is also the correct document. >> >> >> Regards, >> >> Henrik >> > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email=20 > ______________________________________________________________________ > -- 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 Mar 21 12:25:35 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU3Wb-0001LB-Me; Wed, 21 Mar 2007 12:18:57 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU3WY-0001HL-N7 for mip4@ietf.org; Wed, 21 Mar 2007 12:18:54 -0400 Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HU3TV-0001KO-CE for mip4@ietf.org; Wed, 21 Mar 2007 12:15:47 -0400 Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.192]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l2LGFf7Q022293 for ; Thu, 22 Mar 2007 01:15:41 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l2LGFf502019 for mip4@ietf.org; Thu, 22 Mar 2007 01:15:41 +0900 (JST) Received: from yonosuke.jp.nec.com (yonosuke.jp.nec.com [10.26.220.15]) by mailsv.nec.co.jp (8.11.7/3.7W-MAILSV-NEC) with ESMTP id l2LGFeO19671 for ; Thu, 22 Mar 2007 01:15:40 +0900 (JST) Received: from [10.87.72.33] ([10.87.72.33] [10.87.72.33]) by mail.jp.nec.com with ESMTP; Thu, 22 Mar 2007 01:15:38 +0900 Message-Id: <46015A22.1080704@az.jp.nec.com> Date: Wed, 21 Mar 2007 17:15:30 +0100 From: Jun AWANO User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [Mip4] length value of extensions related to dsmipv4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, I'm implementing DSMIPv4 based on current draft. But I'm confused because length value of IPv6 Prefix Extension, IPv6 Code Extension and IPv6 Tunneling Mode Extension are including Type and Length fields. Those extensions are Short Extension Format defined in RFC3344. So, I think it should be value excluding Type and Length fields. Is it right? Best Regards, Jun -- 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 Mar 22 08:18:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMFY-0007dy-Fv; Thu, 22 Mar 2007 08:18:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMFW-0007bo-P0 for mip4@ietf.org; Thu, 22 Mar 2007 08:18:34 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUMFQ-0006op-VZ for mip4@ietf.org; Thu, 22 Mar 2007 08:18:34 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l2MCIQUb002035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Mar 2007 05:18:26 -0700 Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com [172.30.36.176]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l2MCIPto016048; Thu, 22 Mar 2007 05:18:26 -0700 Received: from NAEX16.na.qualcomm.com ([10.47.6.157]) by SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Mar 2007 05:18:25 -0700 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] length value of extensions related to dsmipv4 Date: Thu, 22 Mar 2007 05:18:24 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF439B69C@NAEX16.na.qualcomm.com> In-Reply-To: <46015A22.1080704@az.jp.nec.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] length value of extensions related to dsmipv4 thread-index: Acdr1lUM55Ee+VvGQ+mxs/TyrGXJrAApIWww References: <46015A22.1080704@az.jp.nec.com> From: "Tsirtsis, George" To: "Jun AWANO" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 22 Mar 2007 12:18:25.0591 (UTC) FILETIME=[30ECAC70:01C76C7C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Jun, I am happy to see you are implementing the draft and I would encourage you to share with us any problems you might come up with. With respect to your question, yes, the extensions are following the short format which is defined in RFC3344, Section 1.11, from which I quote: "1.11. Short Extension Format This format is compatible with the skippable extensions defined in section 1.9. It is not applicable for extensions which require more than 256 bytes of data; for such extensions, use the format described in section 1.10. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Sub-Type | Data .... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ " This is the format I used in the DSMIPv4 draft. For example the IPv6 Prefix Extension is defined as: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Sub-Type | Prefix Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + Mobile IPv6 Network Prefix + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The Type, Length and Sub-Type values are that of the short extension format and the Data field includes Prefix Length and Mobile IPv6 Network Prefix fields. Is this OK? George > -----Original Message----- > From: Jun AWANO [mailto:j-awano@az.jp.nec.com] > Sent: Wednesday, March 21, 2007 5:16 PM > To: Mobile IPv4 Mailing List > Subject: [Mip4] length value of extensions related to dsmipv4 >=20 > Hi, >=20 > I'm implementing DSMIPv4 based on current draft. > But I'm confused because length value of IPv6 Prefix Extension, IPv6 > Code Extension and IPv6 Tunneling Mode Extension are including Type and > Length fields. > Those extensions are Short Extension Format defined in RFC3344. > So, I think it should be value excluding Type and Length fields. > Is it right? >=20 > Best Regards, > Jun >=20 >=20 > -- > 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 Mar 22 08:24:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMLe-0003KA-Tu; Thu, 22 Mar 2007 08:24:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMLd-0003IO-UI for mip4@ietf.org; Thu, 22 Mar 2007 08:24:53 -0400 Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HUMLc-0000RZ-Gs for mip4@ietf.org; Thu, 22 Mar 2007 08:24:53 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-5.tower-153.messagelabs.com!1174566291!5049207!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 28577 invoked from network); 22 Mar 2007 12:24:51 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-5.tower-153.messagelabs.com with SMTP; 22 Mar 2007 12:24:51 -0000 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2MCOoU9012340 for ; Thu, 22 Mar 2007 05:24:50 -0700 (MST) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2MCOobf008377 for ; Thu, 22 Mar 2007 07:24:50 -0500 (CDT) 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] length value of extensions related to dsmipv4 Date: Thu, 22 Mar 2007 08:24:41 -0400 Message-ID: In-Reply-To: <2309978910A6A6478C2C7585692B0AF439B69C@NAEX16.na.qualcomm.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] length value of extensions related to dsmipv4 Thread-Index: Acdr1lUM55Ee+VvGQ+mxs/TyrGXJrAApIWwwAAB93/A= References: <46015A22.1080704@az.jp.nec.com> <2309978910A6A6478C2C7585692B0AF439B69C@NAEX16.na.qualcomm.com> From: "McCann Peter-A001034" To: "Tsirtsis, George" , "Jun AWANO" , "Mobile IPv4 Mailing List" X-Spam-Score: 0.0 (/) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, I think Jun's question was prompted by the specification of the Length field as "20". Jun is saying it should be "18", because it shouldn't include the Type and Length fields. -Pete Tsirtsis, George wrote: > Hi Jun, >=20 > I am happy to see you are implementing the draft and I would > encourage you to share with us any problems you might come up with.=20 >=20 > With respect to your question, yes, the extensions are following the > short format which is defined in RFC3344, Section 1.11, from which I=20 > quote: >=20 > "1.11. Short Extension Format >=20 > This format is compatible with the skippable extensions defined in > section 1.9. It is not applicable for extensions which require > more than 256 bytes of data; for such extensions, use the format > described in section 1.10. >=20 > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type | Length | Sub-Type | Data .... > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > "=20 >=20 >=20 > This is the format I used in the DSMIPv4 draft. For example the IPv6 > Prefix Extension is defined as:=20 >=20 > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | =20 > Type | Length | Sub-Type | Prefix Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | =20 > | + + | > | + Mobile IPv6 Network Prefix + | > | + + | > | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ =20 >=20 > The Type, Length and Sub-Type values are that of the short extension > format and the Data field includes Prefix Length and Mobile IPv6 > Network Prefix fields. =20 >=20 > Is this OK? >=20 > George >=20 >> -----Original Message----- >> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] >> Sent: Wednesday, March 21, 2007 5:16 PM >> To: Mobile IPv4 Mailing List >> Subject: [Mip4] length value of extensions related to dsmipv4 >>=20 >> Hi, >>=20 >> I'm implementing DSMIPv4 based on current draft. >> But I'm confused because length value of IPv6 Prefix Extension, IPv6 >> Code Extension and IPv6 Tunneling Mode Extension are including Type >> and Length fields. Those extensions are Short Extension Format >> defined in RFC3344.=20 >> So, I think it should be value excluding Type and Length fields. >> Is it right? >>=20 >> Best Regards, >> Jun >>=20 >>=20 >> -- >> 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/=20 -- 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 Mar 22 08:30:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMR5-0003r8-Nu; Thu, 22 Mar 2007 08:30:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUMR4-0003r3-Sx for mip4@ietf.org; Thu, 22 Mar 2007 08:30:30 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUMR2-0001fB-EM for mip4@ietf.org; Thu, 22 Mar 2007 08:30:30 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l2MCUQcb002509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 22 Mar 2007 05:30:26 -0700 Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com [172.30.32.65]) by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l2MCUPCL018079; Thu, 22 Mar 2007 05:30:25 -0700 Received: from NAEX16.na.qualcomm.com ([10.47.6.157]) by SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Mar 2007 05:30:25 -0700 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] length value of extensions related to dsmipv4 Date: Thu, 22 Mar 2007 05:30:25 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF439B6A1@NAEX16.na.qualcomm.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] length value of extensions related to dsmipv4 thread-index: Acdr1lUM55Ee+VvGQ+mxs/TyrGXJrAApIWwwAAB93/AAACL04A== References: <46015A22.1080704@az.jp.nec.com> <2309978910A6A6478C2C7585692B0AF439B69C@NAEX16.na.qualcomm.com> From: "Tsirtsis, George" To: "McCann Peter-A001034" , "Jun AWANO" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 22 Mar 2007 12:30:25.0764 (UTC) FILETIME=[DE2E5A40:01C76C7D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Ah yes, I misunderstood the question. Jun is very correct. The Length values of the three extensions should be as follows: IPv6 Prefix Extension: Length =3D 18 IPv6 Code Extension: Length =3D 20 IPv6 Tunneling Mode Extension: Length =3D 2 I will fix this in the next version. Thanks George > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] > Sent: Thursday, March 22, 2007 1:25 PM > To: Tsirtsis, George; Jun AWANO; Mobile IPv4 Mailing List > Subject: RE: [Mip4] length value of extensions related to dsmipv4 >=20 > Hi, >=20 > I think Jun's question was prompted by the specification of > the Length field as "20". Jun is saying it should be "18", because > it shouldn't include the Type and Length fields. >=20 > -Pete >=20 > Tsirtsis, George wrote: > > Hi Jun, > > > > I am happy to see you are implementing the draft and I would > > encourage you to share with us any problems you might come up with. > > > > With respect to your question, yes, the extensions are following the > > short format which is defined in RFC3344, Section 1.11, from which I > > quote: > > > > "1.11. Short Extension Format > > > > This format is compatible with the skippable extensions defined in > > section 1.9. It is not applicable for extensions which require > > more than 256 bytes of data; for such extensions, use the format > > described in section 1.10. > > > > 0 1 2 3 > > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Type | Length | Sub-Type | Data .... > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > " > > > > > > This is the format I used in the DSMIPv4 draft. For example the IPv6 > > Prefix Extension is defined as: > > > > 0 1 2 3 > > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > > > > > > > > > > > > > > > > > > > > > > > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | > > Type | Length | Sub-Type | Prefix Length | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | > > | + + | > > | + Mobile IPv6 Network Prefix + | > > | + + | > > | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > The Type, Length and Sub-Type values are that of the short extension > > format and the Data field includes Prefix Length and Mobile IPv6 > > Network Prefix fields. > > > > Is this OK? > > > > George > > > >> -----Original Message----- > >> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] > >> Sent: Wednesday, March 21, 2007 5:16 PM > >> To: Mobile IPv4 Mailing List > >> Subject: [Mip4] length value of extensions related to dsmipv4 > >> > >> Hi, > >> > >> I'm implementing DSMIPv4 based on current draft. > >> But I'm confused because length value of IPv6 Prefix Extension, IPv6 > >> Code Extension and IPv6 Tunneling Mode Extension are including Type > >> and Length fields. Those extensions are Short Extension Format > >> defined in RFC3344. > >> So, I think it should be value excluding Type and Length fields. > >> Is it right? > >> > >> Best Regards, > >> Jun > >> > >> > >> -- > >> 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 Mar 22 09:29:14 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUNLq-0008OZ-95; Thu, 22 Mar 2007 09:29:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUNLo-0008OG-DQ for mip4@ietf.org; Thu, 22 Mar 2007 09:29:08 -0400 Received: from tyo202.gate.nec.co.jp ([202.32.8.206]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUNLc-0000sD-UE for mip4@ietf.org; Thu, 22 Mar 2007 09:29:08 -0400 Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.193]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l2MDSs28000516 for ; Thu, 22 Mar 2007 22:28:54 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l2MDSsj16216 for mip4@ietf.org; Thu, 22 Mar 2007 22:28:54 +0900 (JST) Received: from saigo.jp.nec.com (saigo.jp.nec.com [10.26.220.6]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id l2MDSsg10794 for ; Thu, 22 Mar 2007 22:28:54 +0900 (JST) Received: from [10.87.72.33] ([10.87.72.33] [10.87.72.33]) by mail.jp.nec.com with ESMTP; Thu, 22 Mar 2007 22:28:53 +0900 Message-Id: <4602848D.1090602@az.jp.nec.com> Date: Thu, 22 Mar 2007 14:28:45 +0100 From: Jun AWANO User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Subject: Re: [Mip4] length value of extensions related to dsmipv4 References: <46015A22.1080704@az.jp.nec.com> <2309978910A6A6478C2C7585692B0AF439B69C@NAEX16.na.qualcomm.com> <2309978910A6A6478C2C7585692B0AF439B6A1@NAEX16.na.qualcomm.com> In-Reply-To: <2309978910A6A6478C2C7585692B0AF439B6A1@NAEX16.na.qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, George and Pete Thank you for your early reply. My intention was exactly what Pete said. George> I will fix this in the next version. Thanks, George. -Jun Tsirtsis, George wrote: > Ah yes, I misunderstood the question. Jun is very correct. The Length > values of the three extensions should be as follows: > > IPv6 Prefix Extension: Length = 18 > IPv6 Code Extension: Length = 20 > IPv6 Tunneling Mode Extension: Length = 2 > > I will fix this in the next version. > > Thanks > George >> -----Original Message----- >> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] >> Sent: Thursday, March 22, 2007 1:25 PM >> To: Tsirtsis, George; Jun AWANO; Mobile IPv4 Mailing List >> Subject: RE: [Mip4] length value of extensions related to dsmipv4 >> >> Hi, >> >> I think Jun's question was prompted by the specification of >> the Length field as "20". Jun is saying it should be "18", because >> it shouldn't include the Type and Length fields. >> >> -Pete >> >> Tsirtsis, George wrote: >>> Hi Jun, >>> >>> I am happy to see you are implementing the draft and I would >>> encourage you to share with us any problems you might come up with. >>> >>> With respect to your question, yes, the extensions are following the >>> short format which is defined in RFC3344, Section 1.11, from which I >>> quote: >>> >>> "1.11. Short Extension Format >>> >>> This format is compatible with the skippable extensions defined > in >>> section 1.9. It is not applicable for extensions which require >>> more than 256 bytes of data; for such extensions, use the format >>> described in section 1.10. >>> >>> 0 1 2 3 >>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 >>> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> | Type | Length | Sub-Type | Data .... >>> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> " >>> >>> >>> This is the format I used in the DSMIPv4 draft. For example the IPv6 >>> Prefix Extension is defined as: >>> >>> 0 1 2 3 >>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 > 1 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> Type | Length | Sub-Type | Prefix Length | >>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | >>> | + + > | >>> | + Mobile IPv6 Network Prefix + > | >>> | + + > | >>> | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >>> >>> The Type, Length and Sub-Type values are that of the short extension >>> format and the Data field includes Prefix Length and Mobile IPv6 >>> Network Prefix fields. >>> >>> Is this OK? >>> >>> George >>> >>>> -----Original Message----- >>>> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] >>>> Sent: Wednesday, March 21, 2007 5:16 PM >>>> To: Mobile IPv4 Mailing List >>>> Subject: [Mip4] length value of extensions related to dsmipv4 >>>> >>>> Hi, >>>> >>>> I'm implementing DSMIPv4 based on current draft. >>>> But I'm confused because length value of IPv6 Prefix Extension, > IPv6 >>>> Code Extension and IPv6 Tunneling Mode Extension are including Type >>>> and Length fields. Those extensions are Short Extension Format >>>> defined in RFC3344. >>>> So, I think it should be value excluding Type and Length fields. >>>> Is it right? >>>> >>>> Best Regards, >>>> Jun >>>> >>>> >>>> -- >>>> 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/ > -- ----------------------------------------------- Jun AWANO NEC Ubiquitous Platform Development Division Tel:+81 3 5476 9798, FAX:+81 3 5476 1005 -- 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 Mar 22 10:11:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUO0u-000559-MT; Thu, 22 Mar 2007 10:11:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUO0t-000553-GZ for mip4@ietf.org; Thu, 22 Mar 2007 10:11:35 -0400 Received: from an-out-0708.google.com ([209.85.132.240]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUO0r-00056U-9x for mip4@ietf.org; Thu, 22 Mar 2007 10:11:35 -0400 Received: by an-out-0708.google.com with SMTP id d30so788736and for ; Thu, 22 Mar 2007 07:11:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=syCWkhLXBYGkMRWsHEsDpQTRpxN2LJjJsNXg7M8EXsPKJJxOUNgYu9huCDzE38yrhLPw5wYBwoQivus+1G80I8imPrQQTq9O7aqBAbDcEwNZLsjy6MeBfC2kcw4a6QuyLxnCkOMh+Z6U7X5Ntuqrms/hHukZMjDllHEAxoMh6eo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=TjQ5+dbRo9HJDNnX9z6jNIvcckDsE0CkynRoyKhnqifVqMHVF+qIPnYSxbLddRLZqKl+GOiGmiuWBc1VddWkzp5KvSerqlz6CdVE4e65hEgEeCj1HHmRn1MsB5qbuZCXRYlWkEaV39/QZC782eF0Vf7StWPaK3vXVWTyqO9GODw= Received: by 10.115.54.1 with SMTP id g1mr614473wak.1174572692304; Thu, 22 Mar 2007 07:11:32 -0700 (PDT) Received: by 10.114.193.6 with HTTP; Thu, 22 Mar 2007 07:11:32 -0700 (PDT) Message-ID: <88bc8c7a0703220711y78e3f0b7v2ea6dcd18c440eb4@mail.gmail.com> Date: Thu, 22 Mar 2007 16:11:32 +0200 From: "Bjorn Andersson" To: mip4@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Google-Sender-Auth: dc02566994306984 X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Mip4] Minor issue with MN advertisement sequence number handling X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Section "2.4.4. Sequence Numbers and Rollover Handling" of RFC3344 (and bis) says: "If a mobile node detects two successive values of the sequence number in the Agent Advertisements from the foreign agent with which it is registered, the second of which is less than the first and inside the range 0 to 255, the mobile node SHOULD register again." If the FA is restarted before it has sent a second advertisement the MN will not reregister. The text should either say "... the second is less than or equal to the first ..." or alternatively "... the second is 0 or less than the first ...". Regards, Bj=F6rn Andersson -- 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 Mar 22 20:56:23 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUY3v-00078J-VS; Thu, 22 Mar 2007 20:55:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUY3u-00077m-TN for mip4@ietf.org; Thu, 22 Mar 2007 20:55:22 -0400 Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUXyv-0000vs-06 for mip4@ietf.org; Thu, 22 Mar 2007 20:50:21 -0400 Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l2N0nWd21367; Fri, 23 Mar 2007 00:49:33 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip4] Minor issue with MN advertisement sequence number handling Date: Thu, 22 Mar 2007 19:49:29 -0500 Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA437113579514@zrc2hxm2.corp.nortel.com> In-Reply-To: <88bc8c7a0703220711y78e3f0b7v2ea6dcd18c440eb4@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minor issue with MN advertisement sequence number handling thread-index: AcdsjEOXVfwguSNwR2KK42a5QrwevAAWKjKA References: <88bc8c7a0703220711y78e3f0b7v2ea6dcd18c440eb4@mail.gmail.com> From: "Ahmad Muhanna" To: "Bjorn Andersson" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Bjorn, I do not see any problem in the text. May be I am missing something. = More inline. Regards, Ahmad =20 > -----Original Message----- > From: Bjorn Andersson [mailto:bjorn@iki.fi]=20 > Sent: Thursday, March 22, 2007 3:12 PM > To: mip4@ietf.org > Subject: [Mip4] Minor issue with MN advertisement sequence=20 > number handling >=20 > Section "2.4.4. Sequence Numbers and Rollover Handling" of=20 > RFC3344 (and bis) says: >=20 > "If a mobile node detects two successive values of the=20 > sequence number in the Agent Advertisements from the foreign=20 > agent with which it is registered, the second of which is=20 > less than the first and inside the range 0 to 255, the mobile=20 > node SHOULD register again." >=20 > If the FA is restarted before it has sent a second=20 > advertisement the MN will not reregister.=20 [Ahmad] Why? Can you please explain. > The text should=20 > either say "... the second is less than or equal to the first=20 > ..." or alternatively "... the second is 0 or less than the=20 > first ...". >=20 > Regards, > Bj=F6rn Andersson >=20 > -- > 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/ >=20 -- 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 Mar 23 03:26:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUeAs-0000zj-DJ; Fri, 23 Mar 2007 03:26:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUeAq-0000zZ-7R for mip4@ietf.org; Fri, 23 Mar 2007 03:26:56 -0400 Received: from an-out-0708.google.com ([209.85.132.248]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUeAo-0006py-GF for mip4@ietf.org; Fri, 23 Mar 2007 03:26:56 -0400 Received: by an-out-0708.google.com with SMTP id d30so1141110and for ; Fri, 23 Mar 2007 00:26:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=PKjBfUkUozzkk9ipnZ5kGM12aiPJgyCfZKg3MaHONnnVG0AESs4/+nXclyEiYEtt0u2fXXFksRqLUwuROxLM/AzGX9yHpXeWr5bLHXad+aDih+wBFlByjhvvyJqdHhzea/bBGswiM78wHSLUAS5vqcttqUG0xCn9TwJhhJ7wvyc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=sv1YhWHx/taJjvbmeKC4n00/yImgZg6D9+wQXo+1sWMMNBC954L5IofHS0BPAqhEfcFEvNtgt00pMJn5NmeP/PbmExYG/7RjfLIwhYositiCYZXdX2RbT5ZVvZoo51TVuc9ysanxmAgtIIc+dle9px8b+rTT1hOuxTCnshiRvjw= Received: by 10.114.78.1 with SMTP id a1mr1053861wab.1174634813820; Fri, 23 Mar 2007 00:26:53 -0700 (PDT) Received: by 10.114.193.6 with HTTP; Fri, 23 Mar 2007 00:26:53 -0700 (PDT) Message-ID: <88bc8c7a0703230026q4e275dc7j41e0e96280f62102@mail.gmail.com> Date: Fri, 23 Mar 2007 09:26:53 +0200 From: "Bjorn Andersson" To: "Ahmad Muhanna" Subject: Re: [Mip4] Minor issue with MN advertisement sequence number handling In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA437113579514@zrc2hxm2.corp.nortel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <88bc8c7a0703220711y78e3f0b7v2ea6dcd18c440eb4@mail.gmail.com> <6FC4416DDE56C44DA0AEE67BC7CA437113579514@zrc2hxm2.corp.nortel.com> X-Google-Sender-Auth: 5a5587a0dc7a44af 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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org On 3/23/07, Ahmad Muhanna wrote: > Bjorn Andersson [mailto:bjorn@iki.fi]: > > If the FA is restarted before it has sent a second > > advertisement the MN will not reregister. > > Why? Can you please explain. 1. FA starts 2. FA sends advertisement with sequence number 0 3. MN registers via FA 4. FA restarts 5. FA sends advertisement with sequence number 0 6. Sequence number is equal to, not less than, previous sequence number. MN does not register. 7. MN sends packet to FA for tunneling, but MN is not registered to FA (since the FA restarted after the registration), so the FA does not tunnel the packet to the HA. This will be the case until the registration expires. But as I said, it is minor issues since it quite unlikely to occur, but it could still be improved and fixed in the RFC. Or am I missing something? Bjorn -- 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 Mar 23 06:16:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUgom-0004gi-Cf; Fri, 23 Mar 2007 06:16:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUgol-0004gS-4D for mip4@ietf.org; Fri, 23 Mar 2007 06:16:19 -0400 Received: from zrtps0kp.nortel.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUgoi-0005Po-UD for mip4@ietf.org; Fri, 23 Mar 2007 06:16:19 -0400 Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l2NAGEn20738; Fri, 23 Mar 2007 10:16:14 GMT 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] Minor issue with MN advertisement sequence number handling Date: Fri, 23 Mar 2007 05:15:54 -0500 Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA437113579628@zrc2hxm2.corp.nortel.com> In-Reply-To: <88bc8c7a0703230026q4e275dc7j41e0e96280f62102@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minor issue with MN advertisement sequence number handling thread-index: AcdtHKVp8eKj9mQrRkmC46NUVrNZuAAFqufA References: <88bc8c7a0703220711y78e3f0b7v2ea6dcd18c440eb4@mail.gmail.com> <6FC4416DDE56C44DA0AEE67BC7CA437113579514@zrc2hxm2.corp.nortel.com> <88bc8c7a0703230026q4e275dc7j41e0e96280f62102@mail.gmail.com> From: "Ahmad Muhanna" To: "Bjorn Andersson" X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Now I understand what you meant by "If the FA is restarted before it has sent a second advertisement" I also agree that this case is very unlikely. Regards, Ahmad =20 > -----Original Message----- > From: bjondersson@gmail.com [mailto:bjondersson@gmail.com] On=20 > Behalf Of Bjorn Andersson > Sent: Friday, March 23, 2007 8:27 AM > To: Muhanna, Ahmad (RICH1:2H10) > Cc: mip4@ietf.org > Subject: Re: [Mip4] Minor issue with MN advertisement=20 > sequence number handling >=20 > On 3/23/07, Ahmad Muhanna wrote: > > Bjorn Andersson [mailto:bjorn@iki.fi]: > > > If the FA is restarted before it has sent a second=20 > advertisement the=20 > > > MN will not reregister. > > > > Why? Can you please explain. >=20 > 1. FA starts > 2. FA sends advertisement with sequence number 0 3. MN=20 > registers via FA 4. FA restarts 5. FA sends advertisement=20 > with sequence number 0 6. Sequence number is equal to, not=20 > less than, previous sequence number. MN does not register. > 7. MN sends packet to FA for tunneling, but MN is not=20 > registered to FA (since the FA restarted after the=20 > registration), so the FA does not tunnel the packet to the=20 > HA. This will be the case until the registration expires. >=20 > But as I said, it is minor issues since it quite unlikely to=20 > occur, but it could still be improved and fixed in the RFC.=20 > Or am I missing something? >=20 > Bjorn >=20 -- 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 Mar 23 06:52:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUhNM-0004Za-NY; Fri, 23 Mar 2007 06:52:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUhNL-0004Xb-BF for mip4@ietf.org; Fri, 23 Mar 2007 06:52:03 -0400 Received: from airmail.airvananet.com ([12.6.244.34] helo=airmail.wirelessworld.airvananet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUhN8-0007cp-7v for mip4@ietf.org; Fri, 23 Mar 2007 06:52:03 -0400 Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by airmail.wirelessworld.airvananet.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Mar 2007 06:51:34 -0400 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] Minor issue with MN advertisement sequence number handling Date: Fri, 23 Mar 2007 16:21:49 +0530 Message-ID: <653F3CF58193744C9DE59C217C072B58CFC409@nilgiri.india.wirelessworld.airvananet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minor issue with MN advertisement sequence number handling Thread-Index: AcdtHKVp8eKj9mQrRkmC46NUVrNZuAAFqufAAAE93WA= From: "Arun SG" To: "Ahmad Muhanna" , "Bjorn Andersson" X-OriginalArrivalTime: 23 Mar 2007 10:51:34.0500 (UTC) FILETIME=[39490A40:01C76D39] X-Spam-Score: 0.0 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Maybe I'm missing something here. At step 5, when FA restarts, why is the advertisement sent with sequence number 6? Wouldn't it be 1? The window when this error can happen is that FA sends advertisement with seq num 1, restarts and again sends aa with seq num =3D1. Then the two are AAs have equal seq num and MN will not register. I think in any other case, restart would not cause a problem. =20 Regards, Arun =20 -----Original Message----- From: Ahmad Muhanna [mailto:amuhanna@nortel.com]=20 Sent: Friday, March 23, 2007 3:46 PM To: Bjorn Andersson Cc: mip4@ietf.org Subject: RE: [Mip4] Minor issue with MN advertisement sequence number handling Now I understand what you meant by "If the FA is restarted before it has sent a second advertisement" I also agree that this case is very unlikely. Regards, Ahmad =20 > -----Original Message----- > From: bjondersson@gmail.com [mailto:bjondersson@gmail.com] On Behalf=20 > Of Bjorn Andersson > Sent: Friday, March 23, 2007 8:27 AM > To: Muhanna, Ahmad (RICH1:2H10) > Cc: mip4@ietf.org > Subject: Re: [Mip4] Minor issue with MN advertisement sequence number=20 > handling >=20 > On 3/23/07, Ahmad Muhanna wrote: > > Bjorn Andersson [mailto:bjorn@iki.fi]: > > > If the FA is restarted before it has sent a second > advertisement the > > > MN will not reregister. > > > > Why? Can you please explain. >=20 > 1. FA starts > 2. FA sends advertisement with sequence number 0 3. MN registers via=20 > FA 4. FA restarts 5. FA sends advertisement with sequence number 0 6.=20 > Sequence number is equal to, not less than, previous sequence number.=20 > MN does not register. > 7. MN sends packet to FA for tunneling, but MN is not registered to FA > (since the FA restarted after the registration), so the FA does not=20 > tunnel the packet to the HA. This will be the case until the=20 > registration expires. >=20 > But as I said, it is minor issues since it quite unlikely to occur,=20 > but it could still be improved and fixed in the RFC. > Or am I missing something? >=20 > Bjorn >=20 -- 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 Fri Mar 23 07:17:38 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUhlg-00060z-UB; Fri, 23 Mar 2007 07:17:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUhlg-00060o-Fu for mip4@ietf.org; Fri, 23 Mar 2007 07:17:12 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUhlf-00060x-6I for mip4@ietf.org; Fri, 23 Mar 2007 07:17:12 -0400 Received: by ug-out-1314.google.com with SMTP id 72so945875ugd for ; Fri, 23 Mar 2007 04:17:10 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=qxf/nSN2p7BVfGduSeFtimhGxy1kPgwhEHqqJ+pTz3MKy2GxYCwWYhEf096nY2LD5dQ8XO2h84uHOviGlGIJmvicBE+batch5YeDtPA+Tn26I4PohXLKHqfMprLjXVpwZg9ju11WK8+o4odNCexXNNTyosAiM6srMsCPZrOREug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=UIEQsMBRN0x0DH2Qzmo/uwBwSPb1ZprsUX9z2cOT8NOjLZr00m0n1tyy42iZvPWaLjOS2VkfvzjfpxAhy71Z+fLePowztFteJoekVURNMGTE/uUfinzA84HHOhKNdmiquN9/DhzqIEmM3wyLkI3ApiohcK46pVSI4QqriNVqFrs= Received: by 10.114.181.1 with SMTP id d1mr1133707waf.1174648629565; Fri, 23 Mar 2007 04:17:09 -0700 (PDT) Received: by 10.114.193.6 with HTTP; Fri, 23 Mar 2007 04:17:09 -0700 (PDT) Message-ID: <88bc8c7a0703230417p7283db8bga2d5fdc0def8bb2c@mail.gmail.com> Date: Fri, 23 Mar 2007 13:17:09 +0200 From: "Bjorn Andersson" To: "Arun SG" Subject: Re: [Mip4] Minor issue with MN advertisement sequence number handling In-Reply-To: <653F3CF58193744C9DE59C217C072B58CFC409@nilgiri.india.wirelessworld.airvananet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <653F3CF58193744C9DE59C217C072B58CFC409@nilgiri.india.wirelessworld.airvananet.com> X-Google-Sender-Auth: 17c8286f44f182cd X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org On 3/23/07, Arun SG wrote: > Maybe I'm missing something here. > At step 5, when FA restarts, why is the advertisement sent with sequence > number 6? Wouldn't it be 1? Your, or someone's mail reader has lost the new line after the zero. The number six you see if from step 6. Step 5 says it will be sent with sequence number zero, the first sequence number (it could be 1 if it always starts with 1). > The window when this error can happen is that FA sends advertisement > with seq num 1, restarts and again sends aa with seq num =1. Then the > two are AAs have equal seq num and MN will not register. I think in any > other case, restart would not cause a problem. Yes, this is exactly what I am saying. The time period between the two first advertisements. If the FA advertises once per 30s then the FA should not be restarted for 30s or MNs may lose their connection. It's a minor issue, but has already caused confusion in a real life setup (that's how I noticed it). So can't we just change the text to "less or equal to" ? Or are there protocolwise any negative implications of changing the text? Bjorn -- 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 Sat Mar 24 04:20:46 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HV1Tr-00029v-Fa; Sat, 24 Mar 2007 04:20:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HV1Tp-00029k-TR for mip4@ietf.org; Sat, 24 Mar 2007 04:20:05 -0400 Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HV1To-0003EJ-G2 for mip4@ietf.org; Sat, 24 Mar 2007 04:20:05 -0400 Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502) id A8291393BC; Sat, 24 Mar 2007 09:20:03 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP id 92EE738A11; Sat, 24 Mar 2007 09:20:03 +0100 (CET) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 716F937E43; Sat, 24 Mar 2007 09:20:03 +0100 (CET) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HV1Tm-0002e5-Pk; Sat, 24 Mar 2007 09:20:02 +0100 Message-ID: <4604DF14.9030406@levkowetz.com> Date: Sat, 24 Mar 2007 09:19:32 +0100 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Bjorn Andersson Subject: Re: [Mip4] Minor issue with MN advertisement sequence number handling References: <653F3CF58193744C9DE59C217C072B58CFC409@nilgiri.india.wirelessworld.airvananet.com> <88bc8c7a0703230417p7283db8bga2d5fdc0def8bb2c@mail.gmail.com> In-Reply-To: <88bc8c7a0703230417p7283db8bga2d5fdc0def8bb2c@mail.gmail.com> X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: bjorn@iki.fi, mip4@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1615796890==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1615796890== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6B398434B5C301341F85D058" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6B398434B5C301341F85D058 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable on 2007-03-23 12:17 Bjorn Andersson said the following: =2E.. >=20 > Yes, this is exactly what I am saying. The time period between the two > first advertisements. If the FA advertises once per 30s then the FA > should not be restarted for 30s or MNs may lose their connection. >=20 > It's a minor issue, but has already caused confusion in a real life > setup (that's how I noticed it). So can't we just change the text to > "less or equal to" ? Or are there protocolwise any negative > implications of changing the text? The change looks good to me. Good catch. Henrik --------------enig6B398434B5C301341F85D058 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGBN80eVhrtTJkXCMRAufJAJ0cJSBoDXet+UYWLNSjskUVN3JpgQCePeRI +xZTvZznGoVPlR09zV05ymE= =C745 -----END PGP SIGNATURE----- --------------enig6B398434B5C301341F85D058-- --===============1615796890== 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/ --===============1615796890==-- From mip4-bounces@ietf.org Mon Mar 26 01:41:00 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVhwk-0002a4-0s; Mon, 26 Mar 2007 01:40:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVhwi-0002Zw-Ms for mip4@ietf.org; Mon, 26 Mar 2007 01:40:44 -0400 Received: from airmail.airvananet.com ([12.6.244.34] helo=airmail.wirelessworld.airvananet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVhwf-0000Uq-Vy for mip4@ietf.org; Mon, 26 Mar 2007 01:40:44 -0400 Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by airmail.wirelessworld.airvananet.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Mar 2007 01:40:22 -0400 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] Minor issue with MN advertisement sequence number handling Date: Mon, 26 Mar 2007 11:10:43 +0530 Message-ID: <653F3CF58193744C9DE59C217C072B58CFC634@nilgiri.india.wirelessworld.airvananet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minor issue with MN advertisement sequence number handling Thread-Index: Acdt7iQN4LBneiH0R/Cba7gwl8jKNABeIuSA From: "Arun SG" To: "Henrik Levkowetz" , "Bjorn Andersson" X-OriginalArrivalTime: 26 Mar 2007 05:40:22.0925 (UTC) FILETIME=[3F660BD0:01C76F69] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org This takes care of the control plane and maybe one additional line in data plane is needeed too? Below is an edited version of Bjorn's original sequence below:=20 =20 1. FA starts 2. FA sends advertisement with sequence number 0 3. MN registers via FA=20 4. MN sends packet to FA for tunneling, and as per section 4.2.2. [" The foreign agent MUST route datagrams it receives from registered mobile nodes....."], the FA starts tunneling packets. =20 5. FA restarts and assuming a stateless FA, has no knowledge of prior registrations. 6. FA sends advertisement with sequence number 0=20 6.a The MN has continued to send packets as per its original registration. Should there be an addition line in section 4.2.2 , para 3, stating that the datagram from unregistered MN's must be silently discarded? Such a description exists in the reverse path towards the MN. 7. Sequence number is equal to, not less than, previous sequence number. MN does not register. Now assuming that the minor change below is accepted, MN will register, and step below in original scenario will not happen. 8. MN sends packet to FA for tunneling, but MN is not registered to FA (since the FA restarted after the registration), so the FA does not tunnel the packet to the HA. This will be the case until the registration expires. Thanks, Arun -----Original Message----- From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20 Sent: Saturday, March 24, 2007 1:50 PM To: Bjorn Andersson Cc: mip4@ietf.org Subject: Re: [Mip4] Minor issue with MN advertisement sequence number handling on 2007-03-23 12:17 Bjorn Andersson said the following: ... >=20 > Yes, this is exactly what I am saying. The time period between the two > first advertisements. If the FA advertises once per 30s then the FA=20 > should not be restarted for 30s or MNs may lose their connection. >=20 > It's a minor issue, but has already caused confusion in a real life=20 > setup (that's how I noticed it). So can't we just change the text to=20 > "less or equal to" ? Or are there protocolwise any negative=20 > implications of changing the text? The change looks good to me. Good catch. Henrik -- 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 Mar 28 10:50:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZTj-0003xe-Ba; Wed, 28 Mar 2007 10:50:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWZTg-0003sj-9m; Wed, 28 Mar 2007 10:50:20 -0400 Received: from ns1.neustar.com ([156.154.16.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWZTO-0001Qk-Na; Wed, 28 Mar 2007 10:50:20 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 6E00426EA5; Wed, 28 Mar 2007 14:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HWZTO-00076B-BJ; Wed, 28 Mar 2007 10:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 28 Mar 2007 10:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemov4-dynamic-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : Dynamic Prefix Allocation for NEMOv4 Author(s) : G. Tsirtsis, et al. Filename : draft-ietf-mip4-nemov4-dynamic-00.txt Pages : 10 Date : 2007-3-28 The base NEMOv4 specification defines extensions to Mobile IPv4 for mobile networks. This specification defines a dynamic prefix allocation mechanism. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemov4-dynamic-00.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-nemov4-dynamic-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemov4-dynamic-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-3-28092708.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemov4-dynamic-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemov4-dynamic-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-28092708.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 Mar 28 11:26:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWa22-0007Et-Hi; Wed, 28 Mar 2007 11:25:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWa22-0007Ek-0I for mip4@ietf.org; Wed, 28 Mar 2007 11:25:50 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWa1m-0000Iu-V9 for mip4@ietf.org; Wed, 28 Mar 2007 11:25:49 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-10.tower-128.messagelabs.com!1175095533!7804375!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [129.188.136.8] Received: (qmail 1526 invoked from network); 28 Mar 2007 15:25:33 -0000 Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-10.tower-128.messagelabs.com with SMTP; 28 Mar 2007 15:25:33 -0000 Received: from az33exr03.mot.com ([10.64.251.233]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l2SFPVaI004045 for ; Wed, 28 Mar 2007 08:25:33 -0700 (MST) Received: from az10vts04 (az10vts04.mot.com [10.64.251.245]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id l2SFPUN1007216 for ; Wed, 28 Mar 2007 10:25:31 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l2SFPTCR007199 for ; Wed, 28 Mar 2007 10:25:30 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7714D.4B45455E" Date: Wed, 28 Mar 2007 11:25:18 -0400 Message-ID: X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: Minutes from Prague Thread-Index: AcdxTUrnSG74d5ijQJaqLtgrD6LYBA== From: "McCann Peter-A001034" To: "Mobile IPv4 Mailing List" X-Vontu: Pass X-Spam-Score: 0.0 (/) X-Scan-Signature: 21be852dc93f0971708678c18d38c096 Subject: [Mip4] Minutes from Prague X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C7714D.4B45455E Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Attached are the draft minutes from the mip4 meeting at IETF 68 in Prague. Please review and send comments and corrections to the list. Thanks to Vidya Narayanan and Nicolas Montavont for taking notes during the meeting. -Pete ------_=_NextPart_001_01C7714D.4B45455E Content-Type: text/plain; name="mip4-minutes-IETF68.txt" Content-Transfer-Encoding: base64 Content-Description: mip4-minutes-IETF68.txt Content-Disposition: attachment; filename="mip4-minutes-IETF68.txt" CgpNb2JpbGl0eSBmb3IgSVB2NCBXRwpXRURORVNEQVksIE1hcmNoIDIxLCAyMDA3CjE1MTAtMTYx MCBBZnRlcm5vb24gU2Vzc2lvbiBJSQpSb21hL1ZpZW5uYS9NYWRyaWQKCkNIQUlSUzogSGVucmlr IExldmtvd2V0eiA8aGVucmlrQGxldmtvd2V0ei5jb20+CiAgICAgICAgUGV0ZSBNY0Nhbm4gPG1j Y2FwQHBldG9uaS5vcmc+CgogIDEuIFByZWxpbWluYXJpZXMKICBDaGFpcnMKCiAgSGVucmlrOiBB bnkgY29tbWVudHMgb24gdGhlIGFnZW5kYT8KICBOby4KCiAgMi4gRG9jdW1lbnQgU3RhdHVzCiAg Q2hhaXJzCgogIFdHIERvY3VtZW50czoKICAgICAgICBkcmFmdC1pZXRmLW1pcDQtZHNtaXB2NAkJ CQlBY3RpdmUKICAgICAgICAtIE5lZWRzIHJldmlldyAhCiAgSW4gZmV3IG1vbnRocyBpc3N1ZSBh IGxhc3QgY2FsbAoKICAgICAgICBkcmFmdC1pZXRmLW1pcDQtZm1pcHY0CQkJCUFjdGl2ZQogICAg ICAgIC0gV2FpdGluZyBmb3Igc2hlcGhlcmQgd3JpdGV1cAogIFdlIGhhZCBmZXcgY29tbWVudHMg dG8gbWFuYWdlCgogICAgICAgIGRyYWZ0LWlldGYtbWlwNC1nZW4tZXh0CQkJCUFjdGl2ZQogICAg ICAgIC0gTGFzdCBDYWxsOiAyMDA2LTA5LTA1CiAgICAgICAgLSBSZXZpc2VkIGRyYWZ0IHN1Ym1p dHRlZCAyMDA3LTAyLTI2CiAgICAgICAgLSBOZWVkIHRvIHZlcmlmeSB0aGF0IHRoaXMgZG9jdW1l bnQgcmVzb2x2ZXMgYWxsIGlzc3VlcyByYWlzZWQuCgogICAgICAgIGRyYWZ0LWlldGYtbWlwNC1n ZW5lcmljLW5vdGlmaWNhdGlvbi1tZXNzYWdlICAgICBBY3RpdmU9MDkKICAgICAgICAtIE5ldyB3 b3JraW5nIGdyb3VwIGRyYWZ0LCBwbGVhc2UgcmV2aWV3IGFuZCBjb21tZW50CgogICAgICAgIGRy YWZ0LWlldGYtbWlwNC1uZW1vLXY0LWJhc2UJCSAgIEFjdGl2ZT0wOQogICAgICAgIC0gTmV3IHdv cmtpbmcgZ3JvdXAgZHJhZnQsIHBsZWFzZSByZXZpZXcgYW5kIGNvbW1lbnQKCiAgSGVucmlrOiAy IGFkZGl0aW9uYWwgTkVNTyBkb2N1bWVudHMsIGJ1dCB0aGV5IGRpZCBub3QgbWFrZSB0aGUgREwK ICBiZWZvcmUgdGhlIElFVEYuICBUaGV5IHdpbGwgYmUgV0cgZG9jdW1lbnRzLgoKICAgICAgICBk cmFmdC1pZXRmLW1pcDQtcmFkaXVzLXJlcXVpcmVtZW50cwkgICBBY3RpdmUKICAgICAgICAtIE5l ZWRzIHJldmlldyEhIQogIFBldGVyOiBXaWxsIGdvIG91dHNpZGUgdGhlIFdHIHRvIGZpbmQgcmV2 aWV3ZXJzLgoKICAgICAgICBkcmFmdC1pZXRmLW1pcDQtcmZjMjAwNmJpcwkJCUFjdGl2ZQogICAg ICAgIC0gRHJhZnQgdXBkYXRlZCBhbmQgcmVhZHkgZm9yIGxhc3QgY2FsbCAoPykKICBQZXRlcjog V2lsbCBpc3N1ZSBhIExhc3QgY2FsbCBzb29uCgogICAgICAgIGRyYWZ0LWlldGYtbWlwNC1yZmMz MzQ0YmlzCSAgICAgIEFjdGl2ZQogICAgICAgIC0gRHJhZnQgdXBkYXRlZCBhbmQgcmVhZHkgZm9y IHN1Ym1pc3Npb24gYWZ0ZXIKICAgICAgICBhZGRyZXNzaW5nIHJlY2VudCBjb21tZW50cyBvbiB0 aGUgbGlzdC4KICAgICAgICAoRHJhZnQgd2lsbCBiZSBjb252ZXJ0ZWQgdG8geG1sIGZvcm1hdCkK ICBQZXRlcjogT25lIHVwZGF0ZSBzaW5jZSBsYXN0IElFVEYuCiAgT25lIGNvbW1lbnQgZnJvbSBL ZW50LCBuZWVkIHRvIGFkZHJlc3MgaXQKICBIZW5yaWs6IFRoZSBlZGl0b3IgaGFkIHByb2JsZW0g d2l0aCB0aGUgaGlzIGVudmlyb25tZW50LiBXaWxsIGNvbnZlcnQKICBpdCBmcm9tIGxhdGV4IHRv IHhtbAogICAgIFZpamF5IHZvbHVudGVlciB0byBkbyBpdC4KCiAgICAgICAgZHJhZnQtaWV0Zi1t aXA0LXZwbi1wcm9ibGVtLXNvbHV0aW9uCQlFeHBpcmVkCiAgICAgICAgLSBXYWl0aW5nIGZvciBz aGVwaGVyZCB3cml0ZXVwCiAgICAgICAgLSBXaWxsIHNvb24gYmUgdXBkYXRlZCBhbmQgc3VibWl0 dGVkIHRvIHRoZSBJRVNHCgogICAgIElFU0cgUHJvY2Vzc2luZzoKICAgICAgICBkcmFmdC1pZXRm LW1pcDQtbW9iaWtlLWNvbm5lY3Rpdml0eQogICAgICAgIC0gd2FpdGluZyBmb3IgZHJhZnQtaWV0 Zi1taXA0LXZwbi1wcm9ibGVtLXNvbHV0aW9uCgogICAgIFJGQy1FZGl0b3IncyBRdWV1ZToKICAg ICAgICBkcmFmdC1pZXRmLW1pcDQtbWVzc2FnZS1zdHJpbmctZXh0CiAgICAgICAgLSBBcHByb3Zl ZCBzaW5jZSBJRVRGLTY3CgogICAgICAgIGRyYWZ0LWlldGYtbWlwNC1yZWctdHVubmVsCiAgICAg ICAgLSBBcHByb3ZlZCBzaW5jZSBJRVRGLTY3CgogICAgICAgIGRyYWZ0LWlldGYtbW9iaWxlaXAt bG93bGF0ZW5jeS1oYW5kb2Zmcy12NAogICAgICAgIC0gd2FzIHdhaXRpbmcgb24gcmVnLXR1bm5l bAoKICAzLiBOQUktYmFzZWQgSG9tZSBBZGRyZXNzIEFzc2lnbm1lbnQKICAgICBkcmFmdC1wYXVs a2FuZGFzYW15LW1vYmlsZWlwLW5haS1iYXNlZC1ob21lLWFkZHJlcwogIEtlbnQKCiAgICAgQXMg cGFydCBvZiBvdXIgY2hhcnRlciwgd2UgaGF2ZSBhbiBhY3Rpb24gdG8gcmV2aXNlIHRoZQogICAg IE1JUHY0IE5BSSBSRkMgKDI3OTQpIHRvIHJlZmxlY3QgaW1wbGVtZW50YXRpb24gZXhwZXJpZW5j ZS4KICAgICBUaGlzIGRyYWZ0IGlzIGEgcHJvcG9zYWwgZm9yIGEgcmV2aXNpb24sIGFuZCBhIGNh bmRpZGF0ZQogICAgIGZvciBhZG9wdGlvbiBhcyBhIHdvcmtncm91cCBkcmFmdCBhZGRyZXNzaW5n IHRoaXMgYWN0aW9uCiAgICAgaXRlbS4KCiAgS2VudCBhc2tzIGZvciBmZWVkYmFjayBmcm9tIE1J UCBpbXBsZW1lbnRlcnMKCiAgQ2FsbCBmb3IgY29uc2Vuc3VzIHRvIGFkb3B0IGl0IGFzIGEgV0cg ZG9jdW1lbnQ/CgogICA9PiAgTm8gb25lIG9wcG9zZWQuCgogIEhlbnJpazogZG8geW91IHdhbnQg dG8gdGFrZSB0aGlzIGFzIGEgV0cgaXRlbT8KICBPbmx5IHllcy4KCgogIDQuIFVwZGF0ZXMgdG8g ZHJhZnRzIGZvciBORU1PIGV4dGVuc2lvbiB0byBNSVB2NAogICAgIGRyYWZ0LWlldGYtbWlwNC1u ZW1vLXY0LWJhc2UtMDAKICAgICAoZHJhZnQtaWV0Zi1taXA0LW5lbW92NC1keW5hbWljLTAwLAog ICAgICBkcmFmdC1pZXRmLW1pcDQtbmVtb3Y0LWZhLTAwKQogIEFsZXgKCiAgICAgVGhlc2UgZHJh ZnRzIGhhdmUgcmVjZW50bHkgYmVlbiBhZG9wdGVkIGFzIFdHIGRyYWZ0cy4KICAgICAoVGhlIHR3 byBsYXN0IG9uZXMgd2VyZSBzdWJtaXR0ZWQgdG9vIGxhdGUgYW5kIHdpbGwKICAgICBiZSBhdmFp bGFibGUgYWZ0ZXIgdGhlIElFVEYpLgoKICAgICBBbiB1cGRhdGUgb24gdGhlIGJhc2UgZHJhZnQg c3RhdHVzIHdpbGwgYmUgZ2l2ZW4uCgogIE92ZXJ2aWV3OgogICAtIE9ubHkgUmVnaXN0cmF0aW9u IFJlcS9SZXAgYXJlIGV4dGVuZGVkCiAgIC0gUHJlZml4IHRhYmxlCiAgIC0gUmVxdWVzdCBJQU5B IG51bWJlcnMKCiAgUmVjZWl2ZWQgc2V2ZXJhbCBjb21tZW50cyBmcm9tIGxhc3QgSUVURiwgbm90 IGFsbCBvZiB0aGVtIHN0cmFpZ2h0CiAgZm9yd2FyZAogICAtIEZBIENvQSBtb2RlIG5vdCBleHBs YWluZWQgY2xlYXJseQogICAgIEFncmVlbWVudCB0byBrZWVwIHRoZSBGQSBvcHRpbWl6YXRpb24g b3V0IG9mIHRoZSBkb2N1bWVudC4gVGhhdCB0ZXh0CiAgICAgd2lsbCBiZSBpbmNvcnBvcmF0ZWQg aW50byB0aGUgRkEgb3B0aW1pemF0aW9uIGZvciBORU1PdjQgZG9jdW1lbnQuCiAgICAgPT4gIG9r IG9uIHRoYXQKICAgLSBSb3V0aW5nIHByb3RvY29sIG92ZXIgTVItSEEgdHVubmVsIHRvbyBicmll Zmx5CiAgICAgU2VjdGlvbiBvbiB1c2luZyBhIHJvdXRpbmcgcHJvdG9jb2wgd2l0aGluIE5FTU8g d2lsbCBiZSBhZGRlZAogICAgID0+ICBWaWpheSB3aWxsIHdyaXRlIHRoZSBzZWN0aW9uCiAgIC0g dGVybWlub2xvZ3k6IE1OUCAib3duZWQiIG9yICJzZXJ2ZWQiCiAgIC0gT3RoZXIgImVhc3kiIGlz c3VlcyB0aGF0IGhhdmUgYmVlbiBmaXhlZAoKICAgQmFzZWQgb24gcmV2aWV3cywgdGl0bGUgd2Fz IGNoYW5nZWQgdG8gSVB2NCBOZXR3b3JrIE1vYmlsaXR5IChORU1PKQogICBQcm90b2NvbC4gSGVu cmlrIHdvdWxkIGxpa2UgdG8gc2VlIHRoYXQgaXQgcmVmbGVjdHMgdGhhdCBpdCBpcyBhbgogICBl eHRlbnNpb24gdG8gTUlQNCAtIAogIEhlbnJpazogbm90IGFncmVlIHdpdGggdGhlIHRpdGxlLiBD b21lIGJhY2sgdG8gc3VnZ2VzdCBzb21ldGhpbmcgZGlmZmVyZW50CiAgSGVucmlrIHRvIHByb3Bv c2Ugc29tZXRoaW5nIG9uIHRoZSBsaXN0LgogIEFsZXg6IEFncmVlIHRoYXQgdGhpcyBpcyBub3Qg YSBuZXcgcHJvdG9jb2wsIGJ1dCBvbmx5IGV4dGVuc2lvbgogIEdlb3JnZTogY2xhcmlmaWNhdGlv biBvbiAiZW50cmkiZXMiIGJlY2FtZSBlbnRyeS4gV2FzIGFib3V0IG11bHRpaG9taW5nCgogIElu IHRoaXMgZHJhZnQsIHdlIG9ubHkgY29uc2lkZXIgb25lIEhvQSAtIG9uZSBDb0EKCiAgIEJhc2Vk IG9uIHJldmlldywgaXQgd2FzIGNsYXJpZmllZCB0aGF0IG9ubHkgb25lIEhvQSBhbmQgQ29BIGlz IHVwZGF0ZWQKICAgKG90aGVyIHRoYW4gdGhlIE1OUCkuIFNyaSBhZ3JlZXMgdGhhdCBpdCBzaG91 bGQgYmUgdGhhdCB3YXkuIE11bHRpcGxlCiAgIENvQXMgYXJlIG5vdCBjb25zaWRlcmVkIGZvciB0 aGUgYmFzZSBkb2N1bWVudC4KCiAgU3JpPzogeW91IHNob3VsZCBub3QgY29uc2lkZXIgTUNvQQog IEdlb3JnZTogRG9uJ3QgeW91IGNvbnNpZGVyIG11bHRpcGxlIEhBcwogIEFsZXg6IFllcywgd2Ug ZG8sIGJ1dCB3aXRoIHNldmVyYWwgSG9BcyBvbmx5LgoKICAgT25lIG9mIHRoZSByZXZpZXdzIHN1 Z2dlc3RlZCBkZXNjcmliaW5nIHRoZSBNUiB1c2luZyBESENQIHRvIGFjcXVpcmUKICAgYW4gSVAg YWRkcmVzcyBhbmQgTU5QIC0gQWxleCBwcmVmZXJzIHRvIGtlZXAgdGhhdCBvdXQgb2YgdGhlIGRv Y3VtZW50LgoKICBBbGV4OiBwbGVhc2UgY29tbWVudAoKICA1LiBBIE1JQiBmb3IgTUlQdjQgVURQ IFR1bm5lbGxpbmcgKGkuZS4sIE5BVCBUcmF2ZXJzYWwpCiAgICAgZHJhZnQtc2pvc3RyYW5kLW1p cDQtdWRwdHVubmVsLW1pYgogIEhlbnJpawoKICAgICBUaGlzIGRvY3VtZW50IGRlZmluZXMgYSBN SUIgZm9yIG1hbmFnaW5nIHRoZSBNb2JpbGUgTm9kZSwKICAgICBGb3JlaWduIEFnZW50IGFuZCBI b21lIEFnZW50IHdoZW4gTW9iaWxlIElQIFRyYXZlcnNhbCBvZgogICAgIE5ldHdvcmsgQWRkcmVz cyBUcmFuc2xhdGlvbiAoTkFUKSBEZXZpY2VzIGFyZSB1c2VkLgoKICBUaGUgcHJvcG9zYWwgaXMg bm90IHRvIG1peCB0aGlzIGluIHRoZSBNSVAgTUlCLgoKICBDYWxsIGZvciBXRyBhcHByb3ZhbCBh cyBhIFdHIGRvY3VtZW50PwoKICBTcmk6IElzIGl0IHRoZSBwbGFuIHRvIGNvbWUgd2l0aCBhIG5l dyBNSUIgZm9yIGVhY2ggbmV3IGZlYXR1cmU/CiAgSGVucmlrOiBUaGlzIHdhcyBhc2tlZCBmcm9t IE1JQiBpbXBsZW1lbnRlcnMgZXhwZXJ0cy4gQW5kIHRoaXMgaXMgbm90CiAgICAgICAgICB0aGUg cGxhbiB0byBjcmVhdGUgYSBuZXcgTUlCIGZvciBlYWNoIG5ldyBhZGRpdGlvbmFsIGZlYXR1cmUu CiAgS2VudDogSSBzdXBwb3J0IHRoaXMgYXMgV0cgaXRlbS4gUkZDMzUxOSBpcyB3ZWxsIGRlcGxv eWVkLgoKICBTb21lIGFncmVlZC4KICBOb2JvZHkgd2FzIG9wcG9zZWQuCgogIDYuIFNlcnZpY2Ug U2VsZWN0aW9uIGZvciBNb2JpbGUgSVB2NAogICAgIGRyYWZ0LWtvcmhvbmVuLW1pcDQtc2Vydmlj ZS0wMC50eHQKICBKb3VuaQoKICAgICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIFNlcnZpY2Ug U2VsZWN0aW9uIEV4dGVuc2lvbiBmb3IKICAgICBNb2JpbGUgSVB2NCB0aGF0IGlzIGludGVuZGVk IHRvIGFzc2lzdCBob21lIGFnZW50cyB0byBtYWtlCiAgICAgc3BlY2lmaWMgc2VydmljZSBzZWxl Y3Rpb25zIGZvciB0aGUgbW9iaWxpdHkgc2VydmljZQogICAgIHN1YnNjcmlwdGlvbiBkdXJpbmcg dGhlIHJlZ2lzdHJhdGlvbiBwcm9jZWR1cmUuCgogIEhlc2hhbTogSWYgTkFJIGlzIHVzZWQsIHRo ZSBhdXRoZW50aWNhdGlvbiBjYW4gYmUgdGllZCwgc2luY2UgdGhhdCBpcwogIHdoYXQgdGhlIEhB IHVzZXMgdG8gbG9vayB1cCB0aGUga2V5LiBJZiB5b3UgdXNlIGEgZ2VuZXJpYyB0b2tlbiwgeW91 CiAgdGhlbiBuZWVkIHRoZSBIQSB0byBiZSBhYmxlIHRvIHVwZGF0ZSB0aGF0IHRva2VuLiBZb3Ug d2lsbCBuZWVkIHRvCiAgY29uc2lkZXIgYSBmZXcgbW9yZSB0aGluZ3MgaGVyZS4KCiAgSm91bmk6 IFdoZW4gSEEgcmVjZWl2ZXMgUlJRLCBpdCBuZWVkcyB0byB2ZXJpZnkgYWdhaW5zdCBzb21lIGRh dGFiYXNlCiAgdGhhdCBoYXMgdGhlIG1hcHBpbmcgb2YgdGhlIE5BSSB0byB0aGVzZSB0b2tlbnMu CgogIEhlbnJpazogQ29udGVudCBiZWluZyBzaWduZWQgaXMgb25lIGFwcHJvYWNoOyBhbm90aGVy IGFwcHJvYWNoIGlzIHRvCiAgYWxsb3cgdGhlIGZpcnN0IHJlZ2lzdHJhdGlvbiB0byBiZSBhYmxl IHRvIGNhcnJ5IHRoaXMgaW5mb3JtYXRpb24gLSB3ZQogIGNhbiBjb21lIHVwIHdpdGggb3RoZXIg YXBwcm9hY2hlcy4gVGhlIG1haW4gcG9pbnQgaXMgdGhhdCB0aGUKICB1c2VyL21vYmlsZSBtdXN0 IG5vdCBiZSBhYmxlIHRvIGhhY2sgaXQuCgogIEhlc2hhbTogV2h5IGRvIHlvdSBuZWVkIHRoZSBN TiB0byBzZW5kIGl0PyBDYW4gYmUgcmV0cmlldmVkIGZyb20gQUFBLAogIGJhc2VkIG9uIGlkZW50 aXR5IGZyb20gYXV0aGVudGljYXRpb24gKGF0IGxlYXN0IGluIElQdjYpCgogIFNpbW9uOiBUaGUg ZHluYW1pYyBIb0EgYWxsb2NhdGlvbiBpcyBkb25lIGJ5IHRoZSBzYW1lIEhBLCByaWdodCA/Cgog IEpvdW5pOiBZZXMKCiAgS2VudDogVGhpcyBtaWdodCBiZSBnb29kIHRvIGFsbG93IHNldmVyYWwg bWV0aG9kcywgaXQncyBmbGV4aWJsZS4KICBDYW4gYmUgZG9uZSBhdCB0aGUgYmFja2VuZDsgZG9l c24ndCBuZWVkIHRvIGJlIGRvbmUgYnkgdGhlIE1OOwogIHRoaXMgaXMgZG9uZSBpbiB0aGUgZW50 ZXJwcmlzZSBuZXR3b3JrcyB0b2RheQoKICBWaWR5YTogTG9vayBhdCBpc3N1ZXMgd2l0aCB1c2lu ZyBlbmNyeXB0ZWQgdG9rZW5zL3RpY2tldHM7IFZpZHlhIHRvCiAgc2VuZCBhIHBvaW50ZXIgdG8g c29tZSBtYXRlcmlhbC4KCiAgVmlqYXk6IFRoZSBNTiBjYW4gc3Vic2NyaWJlIHRvIGEgbnVtYmVy IG9mIHNlcnZpY2VzLCBidXQgc2VydmljZXMgbXVzdAogIGJlIGluZGVwZW5kZW50LiBUaGUgTU4g anVzdCBzYXlzIEkgd2FudCB0aGlzIGF0IHRoaXMgdGltZSwgYW5kIHRoZSBIQQogIGFuZCBBQUEg anVzdCBoYXMgdG8gdmVyaWZ5IGl0LgoKICBIZW5yaWs6IEFncmVlLCBidXQgdGhlIHNsaWRlIGRv ZXMgbm90IHNheSB0aGF0LiBUaGUgZHJhZnQgc2F5cyB0aGF0LgoKICBIZXNoYW06IFlvdSBhcmUg bm90IGFsbG93aW5nIHRvIHNpbXVsdGFuZW91cyB1c2UgMiBzZXJ2aWNlcy4gTGV0IHNheSAyCiAg dG9rZW5zLiBIb3cgdG8geW91IGRpZmZlcmVudGlhdGU/IFlvdSBuZWVkIHRvIGhhdmUgMiBIb0Fz LgoKICBKb3VuaTogWWVzLiAgV2FudCBmaXJzdCB0aGUgZmVlZGJhY2sgb2Ygd2hhdCB0aGUgcGVv cGxlIHRoaW5rLgoKICBIZW5yaWs6IE5lZWQgdG8gcmVhZCBkcmFmdHMgYW5kIHByb3ZpZGUgZmVl ZGJhY2suIEl0IHdvdWxkIGJlIGdvb2QKICBpZiBldmVyeW9uZSBjYW4gcmV2aWV3IGFzIHdlbGwu ICBXZSBuZWVkIHRvIHJlLWNoYXJ0ZXIgdG8gdGFrZSB0aGlzCiAgb25lLCBidXQgd2UgbmVlZCB0 byBmaW5pc2ggb3VyIHRhc2tzIGZpcnN0LgogIAogIEphcmkgYWdyZWVzLgoKICBHZW9yZ2U6IERT TUlQdjQ6IHBsYW4gdG8gaGF2ZSBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdCBiZWZvcmUgdGhl CiAgbmV4dCBtZWV0aW5nLCBpbnRlbmQgdG8gYmUgdGhlIGxhc3QuIFBsZWFzZSByZWFkIGl0IGJl Zm9yZSBhbmQgc3BlYWsKICB1cCBub3cuICh0aGUgaWRlYSBpcyB0byBnbyBmb3IgYSBsYXN0IGNh bGwgYmVmb3JlIHRoZSBuZXh0IG1lZXRpbmcpCgogIENoYXJsaWU6IGRpZCB5b3UgdGFsayBhYm91 dCBSRkMzMzQ0YmlzID8KCiAgSGVucmlrOiBXZSBoYXZlIGEgdm9sb250ZWVyIHRvIGNvbnZlcnQg aXQgdG8geG1sLiBXZSB3b3VsZCBsaWtlIHRvCiAgc2VuZCBpdCBmb3IgcHVibGljYXRpb24uCgoK ------_=_NextPart_001_01C7714D.4B45455E 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_001_01C7714D.4B45455E-- From mip4-bounces@ietf.org Wed Mar 28 15:50:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeAM-0000FN-3r; Wed, 28 Mar 2007 15:50:42 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeAD-00009B-7P; Wed, 28 Mar 2007 15:50:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HWeAC-0007ja-Oz; Wed, 28 Mar 2007 15:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9AC712ACA0; Wed, 28 Mar 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HWe9i-0004a1-Cq; Wed, 28 Mar 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 28 Mar 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-mip4-nemov4-fa-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : FA extensions to NEMOv4 Base Author(s) : G. Tsirtsis, et al. Filename : draft-mip4-nemov4-fa-00.txt Pages : 14 Date : 2007-3-28 The base NEMOv4 specification defines extensions to Mobile IPv4 for mobile networks. NEMOv4 extensions are defined for use only by the mobile node and the home agent. This specification introduces extensions for NEMO support on the foreign agent. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mip4-nemov4-fa-00.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-mip4-nemov4-fa-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-mip4-nemov4-fa-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-3-28120419.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-mip4-nemov4-fa-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-mip4-nemov4-fa-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-28120419.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 Mar 28 16:14:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeXT-0004W6-G6; Wed, 28 Mar 2007 16:14:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeXS-0004VJ-Bk for mip4@ietf.org; Wed, 28 Mar 2007 16:14:34 -0400 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWeXO-0006wJ-Di for mip4@ietf.org; Wed, 28 Mar 2007 16:14:34 -0400 Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JFM00CN7QFIUK@usaga01-in.huawei.com> for mip4@ietf.org; Wed, 28 Mar 2007 13:04:30 -0700 (PDT) Received: from N737011 (pool-71-112-126-182.sttlwa.dsl-w.verizon.net [71.112.126.182]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JFM003ZKQFCQW@usaga01-in.huawei.com> for mip4@ietf.org; Wed, 28 Mar 2007 13:04:30 -0700 (PDT) Date: Wed, 28 Mar 2007 13:04:25 -0700 From: Madjid Nakhjiri Subject: RE: [Mip4] Minutes from Prague In-reply-to: To: 'McCann Peter-A001034' , 'Mobile IPv4 Mailing List' Message-id: <008d01c77174$4b5e3a40$2f01a8c0@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdxTUrnSG74d5ijQJaqLtgrD6LYBAAJm87w X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: 'Madjid Nakhjiri' , kleung@cisco.com, "'Chowdhury, Kuntal'" , 'Henrik Levkowetz' , 'Avi Lior' X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Chairs, draft-ietf-mip4-radius-requirements Active - Needs review!!! Peter: Will go outside the WG to find reviewers. This document was actually produced as a response to the outside (AD and RADEXT chairs) reviews on the draft-nakhjiri-radius-mip4-02. Is it possible to do a last call on this requirement document? Thanks, Madjid -----Original Message----- From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] Sent: Wednesday, March 28, 2007 8:25 AM To: Mobile IPv4 Mailing List Subject: [Mip4] Minutes from Prague Attached are the draft minutes from the mip4 meeting at IETF 68 in Prague. Please review and send comments and corrections to the list. Thanks to Vidya Narayanan and Nicolas Montavont for taking notes during the meeting. -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 Wed Mar 28 16:39:26 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWevW-00083j-9R; Wed, 28 Mar 2007 16:39:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVFAT-0005EI-L3 for mip4@ietf.org; Sat, 24 Mar 2007 18:57:01 -0400 Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVFAS-0001TZ-A4 for mip4@ietf.org; Sat, 24 Mar 2007 18:57:01 -0400 Received: from saffron.ece.neu.edu (saffron.ece.neu.edu [129.10.60.111]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id l2OMun00022678 for ; Sat, 24 Mar 2007 18:57:00 -0400 (EDT) Received: from ECE.NEU.EDU ([129.10.60.216]) by saffron.ece.neu.edu (SMSSMTP 4.1.5.31) with SMTP id M2007032418510902297 for ; Sat, 24 Mar 2007 18:51:09 -0500 Received: from localhost (basagni@localhost) by ECE.NEU.EDU (8.12.8/8.12.5/Submit) with ESMTP id l2OMuHnS029639 for ; Sat, 24 Mar 2007 17:56:17 -0500 Date: Sat, 24 Mar 2007 17:56:17 -0500 (EST) From: Stefano Basagni To: mip4@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8 X-Mailman-Approved-At: Wed, 28 Mar 2007 16:39:22 -0400 Subject: [Mip4] CfP: 18th Tyrrhenian Workshop on Digital Communications X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org (Apologies for multiple reception of this CfP) *** DEADLINE APPROACHING *** ============================================================ PRELIMINARY ANNOUNCEMENT and CALL FOR PAPERS 18th Tyrrhenian Workshop on Digital Communications Ischia island, Naples, Italy September 9-12, 2007 Workshop theme WIRELESS COMMUNICATIONS * OVERVIEW The Tyrrhenian workshop on digital communications is each year devoted to a specific theme in the area of digital communications and its applications. After several years the theme of wireless communications return. The scope of the workshop is a friendly exchange of ideas on the main research lines in the field of the workshop theme. This year we have chosen five chapters, and to each of them a session has been devoted: -4G wireless systems -Sensor and ad hoc networks -Security in wireless networks -QoS and efficiency in multimedia heterogeneous wireless networks -Wireless system applications The five sessions are in some sense complementary and interlaced each other. Suggested Technical areas included in the sessions, but are not limited, are: modulation, coding, effects of system impairments, channel modeling, MIMO and smart antennas, cross layer and radio resource management, protocols, routing in wireless networks, cognitive radio, multimedia wireless communications, Quality of Service architectures, security, architectures for security, etc. Some sessions are specifically devoted to and we are looking for the most advanced solutions for security and for applications of wireless systems in many different environment, like multimedia communications, infomobility, health care, emergency situations, etc. Interested authors are invited to submit their papers. Authors could also submit papers yet open for discussion in the area of wireless communications and its applications to the poster session. All submitted papers will be carefully reviewed and, due to the limited space available in the sessions some of them could be proposed for the inclusion in the poster session. * PAPER SUBMISSION GUIDELINES Authors are invited to submit extended summary of the final manuscript of maximum length 5 pages including the main results (figures, tables) electronically in PDF format. Selection of the final manuscripts will be based on the extended summary. Final manuscripts to be considered as regular papers should be limited to 15 double-spaced pages. Final manuscripts to be considered for the poster session should be limited to 10 double-spaced pages. Any paper submitted to the Workshop must not have been published in or submitted to other technical conferences/journals. Proceedings of the Conference will be published as a book by Springer. The web page of the workshop will be ready soon at http://www.cnit.it/html/workshops/2007 * IMPORTANT DATES Deadline for extended abstract: March 31, 2007 Notification of acceptance: April 30, 2007 Final manuscript submission: June 1, 2007 Workshop co-chairs Shingo Ohmori, NiCT, Japan Silvano Pupolin, University of Padova and CNIT, Italy Technical Program Committee Hiroyo Ogawa, NiCT, Japan Anand Prasad, Docomo Euro-Labs, Germany Kato Shuzo, NiCT, Japan Michele Zorzi, University of Padova and CNIT, Italy Publicity Stefano Basagni, Northeastern University, Boston, MA, USA Publications Tomaso Erseghe, University of Padova and CNIT, Italy -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntington Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu *** http://www.ece.neu.edu/faculty/basagni/ *** -- 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 Mar 28 16:39:41 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWevk-0000fy-Me; Wed, 28 Mar 2007 16:39:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTIyA-0001oc-Cf for mip4@ietf.org; Mon, 19 Mar 2007 10:36:18 -0400 Received: from kronos.cti.gr ([150.140.1.25]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTIy2-000279-Nn for mip4@ietf.org; Mon, 19 Mar 2007 10:36:18 -0400 Received: (qmail 70881 invoked from network); 19 Mar 2007 14:36:13 -0000 Received: from comet.cti.gr (150.140.12.12) by kronos.cti.gr with SMTP; 19 Mar 2007 14:36:13 -0000 Received: (qmail 15722 invoked from network); 19 Mar 2007 14:36:01 -0000 Received: from comet.cti.gr (HELO localhost) (150.140.12.12) by comet.cti.gr with SMTP; 19 Mar 2007 14:36:01 -0000 Received: from kallioph.ceid.upatras.gr (kallioph.ceid.upatras.gr [150.140.141.24]) by nts.cti.gr (IMP) with HTTP for ; Mon, 19 Mar 2007 16:36:00 +0200 Message-ID: <1174314960.45fe9fd054dcd@nts.cti.gr> Date: Mon, 19 Mar 2007 16:36:00 +0200 From: Christos Bouras To: bouras@cti.gr MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 X-Originating-IP: 150.140.141.24 X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f X-Mailman-Approved-At: Wed, 28 Mar 2007 16:39:37 -0400 Cc: Subject: [Mip4] ACM WMuNeP'07 Workshop Call for Papers X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org *Apologies for cross posting. Please forward to interested people* -------------------------------------------------------------------------- THE THIRD ACM INTERNATIONAL WORKSHOP ON WIRELESS MULTIMEDIA NETWORKING AND PERFORMANCE MODELING (WMUNEP'07) 22-26 October 2007, Chania, Creta Island, Greece http://wmunep2007.cti.gr/ (To be held jointly with the 10-th ACM/IEEE International Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems http://www.cs.unibo.it/projects/mswim2007/) -------------------------------------------------------------------------- -------------------------------------------------------------------------- SCOPE -------------------------------------------------------------------------- The Third ACM International Workshop on Wireless Multimedia Networking and Performance Modeling (WMuNeP'07) will be a one-day workshop, held in conjunction with the 10th Annual ACM Symposium on Modeling, Analysis and Simulation of Wireless and Mobile Systems (MSWiM´07). The demand for wireless multimedia communications thrives in today's consumer and corporate market. The need to evolve multimedia applications and services, and their associated protocols for emerging networks is at a critical point given the proliferation and integration of wireless systems to intelligent and broadband networks, mobility of people, data/voice convergence and the integration of computing and communication in mobile devices. This workshop is devoted to cover different aspects of wireless multimedia networking and performance modeling for WLANs, WPANs, WMANs, WWANs, MANETs and sensor networks such as wireless video and wireless streaming, systematic design methodologies, algorithms, synchronization, analysis and performance modeling. The workshop will provide a forum for researchers and practitioners to present their contributions related to the above high-level aspects. -------------------------------------------------------------------------- TOPICS -------------------------------------------------------------------------- Topics of interest include (but are not limited to): -Wireless multimedia network management -Wireless multimedia traffic modeling -Middleware and reflective systems support for wireless multimedia -Proxy-based systems for video transcoding and content distribution -Performance modeling, monitoring and evaluation of wireless multimedia networks and systems -Multipoint, multicast wireless multimedia services -Deployment of wireless multimedia applications, services and networks -Protocols for wireless multimedia networks -QoS and Resource Allocation in wireless multimedia networks -Integration of wireless multimedia networks to broadband networks -End-to-end IP multimedia wireless communications -Coding and transmission for wireless multimedia networks -Distributed wireless multimedia services -Content-based wireless multimedia information retrieval tools -Video, streaming, real-time wireless multimedia communications and applications Security in wireless multimedia networks -Wireless multimedia right protection and watermarking -Pricing mechanisms for wireless multimedia networks -E-Commerce and related applications for wireless multimedia networks -Multimedia evaluation and processing for wireless networks -Cross layer design for wireless multimedia networks -Software tools for system performance and evaluation of wireless multimedia networks -Case studies showing the role of evaluation in the design of systems -------------------------------------------------------------------------- SUBMISSIONS, REVIEW AND PROCEEDINGS -------------------------------------------------------------------------- Authors are invited to submit research contributions representing original, previously unpublished work. Submitted papers will be carefully evaluated based on originality, significance, technical soundness, and clarity of exposition. Accepted papers will appear on the workshop proceedings that will be published by ACM press. At least one of the authors of accepted papers must attend the conference to present his/her paper. Paper length should be no more than 10 pages, double column, ACM style including tables and figures. More information about the submission template can be found in the workshop web site (http://wmunep2007.cti.gr/). Only Postscript and PDF formats are accepted. -------------------------------------------------------------------------- COMMITTEES --------------------------------------------------------------------------Program committee of the workshop can be found in the following URL: http://wmunep2007.cti.gr/committees.php -------------------------------------------------------------------------- IMPORTANT DATES -------------------------------------------------------------------------- Paper Submission June 1, 2007 Author Notification July 5, 2007 Author Registration TBA Camera-ready Paper TBA -------------------------------------------------------------------------- SPONSORS -------------------------------------------------------------------------- Sponsored by the Association for Computer Machinery (ACM) -------------------------------------------------------------------------- CONTACT -------------------------------------------------------------------------- For any question related to WMuNeP 2007, please contact the Program Co-Chairs (Regina Araujo: regina at dc.ufscar.br and/or Christos Bouras: bouras at cti.gr) -------------------------------------------------------------------------------- Christos Bouras, Associate Professor Department of Computer Engineering and Informatics, University of Patras and Research Academic Computer Technology Institute GR-26500 Rion, PATRA, GREECE Tel:+30-2610-960375, +30-2610-996951 Mobile:+30-694-4-988434 Fax:+30-2610-969016 e-mail: bouras@cti.gr, bouras@ceid.upatras.gr URL:ru6.cti.gr/bouras Skype ID: christos.bouras -------------------------------------------------------------------------------- -- 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 Mar 28 16:42:58 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeyw-0000j9-97; Wed, 28 Mar 2007 16:42:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWeyt-0000Xp-6j for mip4@ietf.org; Wed, 28 Mar 2007 16:42:56 -0400 Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWeyr-0004qX-L3 for mip4@ietf.org; Wed, 28 Mar 2007 16:42:55 -0400 Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502) id D925038C6D; Wed, 28 Mar 2007 22:42:50 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id BFE6C384D4; Wed, 28 Mar 2007 22:42:50 +0200 (CEST) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id B7D0037E48; Wed, 28 Mar 2007 22:42:49 +0200 (CEST) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.63) (envelope-from ) id 1HWeyn-00017K-B7; Wed, 28 Mar 2007 22:42:49 +0200 Message-ID: <460AD34C.7020206@levkowetz.com> Date: Wed, 28 Mar 2007 22:42:52 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: Madjid Nakhjiri Subject: Re: [Mip4] Minutes from Prague References: <008d01c77174$4b5e3a40$2f01a8c0@china.huawei.com> In-Reply-To: <008d01c77174$4b5e3a40$2f01a8c0@china.huawei.com> X-Enigmail-Version: 0.94.2.0 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: mnakhjiri@huawei.com, pete.mccann@motorola.com, mip4@ietf.org, kleung@cisco.com, kchowdhury@starentnetworks.com, avi@bridgewatersystems.com, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: "'Chowdhury, Kuntal'" , kleung@cisco.com, 'Mobile IPv4 Mailing List' , 'McCann Peter-A001034' , 'Avi Lior' X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0325183880==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0325183880== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig074C3248EF5CD0F8A046998D" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig074C3248EF5CD0F8A046998D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Madjid, on 2007-03-28 22:04 Madjid Nakhjiri said the following: > Hi Chairs, >=20 >=20 > draft-ietf-mip4-radius-requirements Active > - Needs review!!! > Peter: Will go outside the WG to find reviewers. >=20 > This document was actually produced as a response to the outside (AD an= d > RADEXT chairs) reviews on the draft-nakhjiri-radius-mip4-02. >=20 > Is it possible to do a last call on this requirement document? We may have to do that. But as also said in the meeting; if the document has had no reviews and no comments, the AD and RADEXT chairs are going to say "So, this has been reviewed and accepted by the WG, yes?" and we'll have to say "No". Henrik --------------enig074C3248EF5CD0F8A046998D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGCtNMeVhrtTJkXCMRAtaKAKCMvpjwRo0d30PBxg4/8U8PQwjo8QCeIdWg kNPrzJbS++E3duGFDT88uiA= =fHnh -----END PGP SIGNATURE----- --------------enig074C3248EF5CD0F8A046998D-- --===============0325183880== 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/ --===============0325183880==-- From mip4-bounces@ietf.org Wed Mar 28 16:43:20 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWezH-0001sG-Vh; Wed, 28 Mar 2007 16:43:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTNJm-0001Kz-GZ for mip4@ietf.org; Mon, 19 Mar 2007 15:14:54 -0400 Received: from a2s13.a2hosting.com ([69.39.88.160]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTNJN-00076N-0i for mip4@ietf.org; Mon, 19 Mar 2007 15:14:54 -0400 Received: from a2s13.a2hosting.com ([69.39.88.160] helo=[127.0.0.1]) by a2s13.a2hosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52) id 1HTNIx-0004Sl-1g for mip4@ietf.org; Mon, 19 Mar 2007 15:14:03 -0400 Message-ID: <45FEE0F7.7090503@umich.edu> Date: Mon, 19 Mar 2007 15:13:59 -0400 From: Ken Laberteaux User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: mip4@ietf.org X-Enigmail-Version: 0.94.2.0 Content-Type: multipart/mixed; boundary="------------030006080302030605080902" X-A2hosting-MailScanner-Information: Please contact the ISP for more information X-A2hosting-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-A2hosting-MailScanner-SpamCheck: X-A2hosting-MailScanner-From: klaberte@umich.edu X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s13.a2hosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - umich.edu X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 X-Mailman-Approved-At: Wed, 28 Mar 2007 16:43:16 -0400 Subject: [Mip4] CFP--Vehicular Ad Hoc Networks (VANET) 2007 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org This is a multi-part message in MIME format. --------------030006080302030605080902 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit --------------030006080302030605080902 Content-Type: text/plain; name="VANET-2007-CFP.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="VANET-2007-CFP.txt" ANNOUNCEMENT and CALL FOR PAPERS VANET 2007 The Fourth ACM International Workshop on Vehicular Ad Hoc Networks In conjunction with ACM MobiCom 2007 September 14, 2007 Montréal, QC, Canada Sponsored by ACM SIGMOBILE http://www.sigmobile.org/workshops/vanet2007/ Important Dates: Paper Submission Deadline: May 14, 2007, 11:59 p.m. GMT Notification of Acceptance: June 18, 2007 Camera-Ready Deadline: July 16, 2007 The goal of this workshop is to present and discuss recent advances in the development of wireless vehicular ad hoc networking (VANET) technologies. Based on short- to medium-range communication systems (vehicle-to-vehicle and vehicle-to-roadside), vehicular ad hoc networks 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, and secure 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 ad hoc networks in terms of mobility behavior and applications scenarios and requirements makes VANET research an exciting and demanding application- and purpose-driven sub-discipline of wireless networking. Following the successes of VANET 2004 held in Philadelphia, VANET 2005 held in Cologne, Germany, and VANET 2006 in Los Angeles, CA, the Fourth ACM International Workshop on Vehicular Ad Hoc Networks (VANET) will be held in Montréal, QC, Canada September 14, 2007, in conjunction with MobiCom 2007. Authors are invited to submit papers presenting new research related to the theory or practice of vehicular ad hoc networks (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: - Safety and non-safety applications - Roadside-to-vehicle and vehicle-to-vehicle communication - Communication protocol design - Channel modeling - Modulation and coding - Power control and scalability issues - Multi-channel organization and operation - Security issues and countermeasures - Privacy issues - Network management - Simulation frameworks & real-world testbeds VANET present a highly active field of research, development, standardization and field trials. Throughout the world, there are many national/international projects in government, industry, and academia devoted to VANET. These include the 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. 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 2007 web page at: http://www.sigmobile.org/workshops/vanet2007/. General Co-Chairs: Wieland Holfelder, DaimlerChrysler REDNA Paolo Santi, Italian Natl. Research Council Technical Program Co-Chairs: Yih-Chun Hu, University of Illinois at Urbana-Champaign Jean-Pierre Hubaux, EPFL Web Chair: Ken Laberteaux, Toyota Technical Center Technical Program Committee (partial list): Fan Bai, General Motors Tracy Camp, Colorado School of Mines Eylem Ekici, Ohio State University Tamer ElBatt, San Diego Research Center Andreas Festag, NEC Europe Ltd Hannes Hartenstein, University of Karlsruhe Wieland Holfelder, DaimlerChrysler REDNA Yih-Chun Hu, University of Illinois at Urbana-Champaign Jean-Pierre Hubaux, EPFL Markus Jakobsson, Indiana University Daniel Jiang, DaimlerChrysler REDNA Frank Kargl, Ulm University Timo Kosch, BMW Ken Laberteaux, Toyota Technical Center Panos Papadimitratos, EPFL Adrian Perrig, Carnegie Mellon University Maxim Raya, EPFL Paolo Santi, CNR --------------030006080302030605080902 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/ --------------030006080302030605080902-- From mip4-bounces@ietf.org Wed Mar 28 16:43:28 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWezQ-00029i-HF; Wed, 28 Mar 2007 16:43:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSiNP-0003jV-DJ for mip4@ietf.org; Sat, 17 Mar 2007 19:31:55 -0400 Received: from borg.ece.uprm.edu ([136.145.57.24] helo=ece.uprm.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSiNI-0000FO-U6 for mip4@ietf.org; Sat, 17 Mar 2007 19:31:55 -0400 Received: from kejielupc (perazzamac2.ece.uprm.edu [136.145.57.158]) by ece.uprm.edu (Postfix) with SMTP id F267C558C8 for ; Sat, 17 Mar 2007 19:31:39 -0400 (AST) Organization: UPR-Mayaguez Message-ID: <8319050de51436f8ae816a1100151b47@ece.uprm.edu> From: "Kejie Lu" To: Date: Sat, 17 Mar 2007 19:31:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba X-Mailman-Approved-At: Wed, 28 Mar 2007 16:43:26 -0400 Subject: [Mip4] CFP MILCOM 2007 (Abstracts Due on Mar. 30) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lukejie@ece.uprm.edu List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ** Apologies if you receive multiple copies of this message ** ** The deadline for submitting abstracts is 30 March 2007 (hard deadline) ** ** The link for submitting the unclassified papers is: = https://wams.jspargo.com/milcom07/login.asp ** =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL for PAPERS MILCOM 2007 October 29=9631, 2007 Gaylord Palms Convention Center Orlando, Florida USA Conference Theme:=20 Interoperability: Policy to Performance MILCOM 2007 is soliciting both unclassified and classified papers (up to = DoD Secret) relevant to communications and information processing system = technologies and capabilities that address the 21st century challenges of = National Defense, Homeland Security, Disaster Response and = Interoperability. Industry, academic, and government organizations from = both the U.S. and countries around the globe are invited and encouraged to = participate=2E Important Dates: Abstracts Due: 30 March 2007 Draft Papers Due: 20 April 2007 Author Notification: 25 May 2007 Final Camera Ready Papers Due: 6 July 2007 Suggested technical areas of general interest include but are not limited to: =95 Interoperability =96 Policies and Standards =96 DoD and Federal Agencies =96 State and Local Governments =96 Emergency Grid Communications =96 Coalition Partners =96 Disaster Response =95 Service Oriented Architectures =95 Advanced Communications Technologies =95 Network Management =95 Mobile and Wireless Technologies =95 Radio Systems and Technologies =95 Network Centric Systems and Technologies =95 Applications and Operational Concepts =95 Systems, Programs and Initiatives =95 Information Management and Dissemination =95 Digital Signal Processing =95 Coding =95 Modulation =95 Advanced Waveforms =95 Next Generation Networks and Systems =95 Internet Protocols =95 Link Layer and Cross-Layer Protocols =95 Network Architectures and Routing =95 Transport Protocols and Performance =95 Quality of Service Architectures =95 Design Modeling and Simulation =95 Digital Video Broadcasting and Standards =95 IF/RF Technologies and Techniques =95 Advanced SATCOM systems =95 Airborne Technologies =95 Standards Based Datalinks =95 Mobile Satellite Systems =95 Space Networks and Protocols =95 Wireless Communications =95 Mobile Ad Hoc Networks =95 Computer and Network Security Systems =95 Software Defined Radios and Cognitive Radios =95 Sensor Networks =95 Advanced Antenna Technologies =95 Laser Communications and Optical Networks =95 Tests and Measurements =95 Ultra Wideband =95 Multimedia Communications and Management Technical Program Committee Technical Program Chair Dr. Vitas Mikenas Harris Corporation 321-729-7748 mikenas.milcom2007@harris.com Unclassified Program Chair Dr. Sastri Kota Harris Corporation 408-990-8301 kota.milcom2007@harris.com Classified Program Chair Terry Casto Harris Corporation 321-984-5600 casto.milcom2007@harris.com Panels Program Chair Leo deCardenas Harris Corporation 321-727-6202 decardenas.milcom2007@harris.com Tutorial Program Chair Rich Folio Harris Corporation 321-729-3629 folio.milcom2007@harris.com Unclassified Technical Program Submission Process:=20 The Web-based Abstract Management System (WAMS) (www.milcom.org) is used = to submit abstracts, full papers, and final camera ready papers. During = the abstract submission process, author and password information will need = to be entered and a Paper ID# will be assigned. This Paper ID# and = password will be used to upload papers. The abstract must NOT contain any = ITAR-related, classified, or proprietary information=2E Abstracts will only be used to help define the sessions. The Unclassified = Author=92s Kit provides instructions to authors for preparation of the = full and final manuscripts and the required forms. Full papers will be = reviewed for acceptance only when all appropriate forms have been = completed and received=2E Classified Technical Program Submission Process: All persons wishing to attend and/or participate in the Classified = Technical Program must, at a minimum, possess a current Secret personnel = security clearance and be a U.S. citizen. Non-U.S. originated papers will = NOT be accepted for the Classified Technical Program. All abstracts for = the Classified Technical Program must be unclassified. Please submit a = title and a brief unclassified abstract (up to 2000 characters) of your = intended paper via email to: casto.milcom2007@harris.com. Each submission = requires author name, affiliation, citizenship, address, phone and fax = numbers, email address, and the applicable area. For papers with more than = one author, indicate the point of contact. Do NOT use WAMS to submit = abstracts, full papers, or the final papers for the Classified Technical = Program. All papers for the Classified Technical Program must be prepared = following the instructions and formatting guidelines in the Classified = Author=92s Kit=2E Proposals for Tutorials and Panels:=20 MILCOM 2007 solicits proposals for unclassified half-day tutorials, and = unclassified and classified panels on state-of-the art communications, = networking, and interoperability technologies. The tutorial proposals = should include a brief outline of the tutorial, instructor biography, and = relevant instructor experience. The Unclassified Tutorials Kit provides the applicable forms and the formatting guidelines for the = tutorial material. Please forward your proposals to the MILCOM 2007 = Tutorial Program Chair, Rich Folio, at folio.milcom2007@harris.com=2E Proposals for Panels:=20 The proposals for panels should include a brief outline of the panel = discussion topics, panel participants, and panel moderator along with = their bios. A Panels Kit provides the information about the applicable = forms and the guidelines for the preparation of the panel material. Please = forward your proposals to the MILCOM 2007 Panels Program Chair, Leo = deCardenas, at decardenas.milcom2007@harris.com=2E Tutorials and Panels Important Dates: Proposals Due: 16 March 2007 Notification: 20 April 2007 Material Due: 13 July 2007 For further details and information about MILCOM 2007 please visit = www.milcom.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 Mar 28 16:43:31 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWezT-0002CV-2s; Wed, 28 Mar 2007 16:43:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVVV8-00015Y-Kj for mip4@ietf.org; Sun, 25 Mar 2007 12:23:26 -0400 Received: from ece.uprm.edu ([136.145.57.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVVV3-00074K-7X for mip4@ietf.org; Sun, 25 Mar 2007 12:23:26 -0400 Received: from kejielupc (perazzamac2.ece.uprm.edu [136.145.57.158]) by ece.uprm.edu (Postfix) with SMTP id BF49356085 for ; Sun, 25 Mar 2007 12:23:18 -0400 (AST) Organization: UPR-Mayaguez Message-ID: <2223be45cba2d99a2c876fb20012f8fa@ece.uprm.edu> From: "Kejie Lu" To: Date: Sun, 25 Mar 2007 12:23:16 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba X-Mailman-Approved-At: Wed, 28 Mar 2007 16:43:26 -0400 Subject: [Mip4] CFP MILCOM 2007 (Abstracts Due on Mar. 30) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lukejie@ece.uprm.edu List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org ** Apologies if you receive multiple copies of this message ** ** The deadline for submitting abstracts is 30 March 2007 (hard deadline) ** ** The link for submitting the unclassified papers is: = https://wams.jspargo.com/milcom07/login.asp ** =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL for PAPERS MILCOM 2007 October 29=9631, 2007 Gaylord Palms Convention Center Orlando, Florida USA Conference Theme:=20 Interoperability: Policy to Performance MILCOM 2007 is soliciting both unclassified and classified papers (up to = DoD Secret) relevant to communications and information processing system = technologies and capabilities that address the 21st century challenges of = National Defense, Homeland Security, Disaster Response and = Interoperability. Industry, academic, and government organizations from = both the U.S. and countries around the globe are invited and encouraged to = participate=2E Important Dates: Abstracts Due: 30 March 2007 Draft Papers Due: 20 April 2007 Author Notification: 25 May 2007 Final Camera Ready Papers Due: 6 July 2007 Suggested technical areas of general interest include but are not limited to: =95 Interoperability =96 Policies and Standards =96 DoD and Federal Agencies =96 State and Local Governments =96 Emergency Grid Communications =96 Coalition Partners =96 Disaster Response =95 Service Oriented Architectures =95 Advanced Communications Technologies =95 Network Management =95 Mobile and Wireless Technologies =95 Radio Systems and Technologies =95 Network Centric Systems and Technologies =95 Applications and Operational Concepts =95 Systems, Programs and Initiatives =95 Information Management and Dissemination =95 Digital Signal Processing =95 Coding =95 Modulation =95 Advanced Waveforms =95 Next Generation Networks and Systems =95 Internet Protocols =95 Link Layer and Cross-Layer Protocols =95 Network Architectures and Routing =95 Transport Protocols and Performance =95 Quality of Service Architectures =95 Design Modeling and Simulation =95 Digital Video Broadcasting and Standards =95 IF/RF Technologies and Techniques =95 Advanced SATCOM systems =95 Airborne Technologies =95 Standards Based Datalinks =95 Mobile Satellite Systems =95 Space Networks and Protocols =95 Wireless Communications =95 Mobile Ad Hoc Networks =95 Computer and Network Security Systems =95 Software Defined Radios and Cognitive Radios =95 Sensor Networks =95 Advanced Antenna Technologies =95 Laser Communications and Optical Networks =95 Tests and Measurements =95 Ultra Wideband =95 Multimedia Communications and Management Technical Program Committee Technical Program Chair Dr. Vitas Mikenas Harris Corporation 321-729-7748 mikenas.milcom2007@harris.com Unclassified Program Chair Dr. Sastri Kota Harris Corporation 408-990-8301 kota.milcom2007@harris.com Classified Program Chair Terry Casto Harris Corporation 321-984-5600 casto.milcom2007@harris.com Panels Program Chair Leo deCardenas Harris Corporation 321-727-6202 decardenas.milcom2007@harris.com Tutorial Program Chair Rich Folio Harris Corporation 321-729-3629 folio.milcom2007@harris.com Unclassified Technical Program Submission Process:=20 The Web-based Abstract Management System (WAMS) (www.milcom.org) is used = to submit abstracts, full papers, and final camera ready papers. During = the abstract submission process, author and password information will need = to be entered and a Paper ID# will be assigned. This Paper ID# and = password will be used to upload papers. The abstract must NOT contain any = ITAR-related, classified, or proprietary information=2E Abstracts will only be used to help define the sessions. The Unclassified = Author=92s Kit provides instructions to authors for preparation of the = full and final manuscripts and the required forms. Full papers will be = reviewed for acceptance only when all appropriate forms have been = completed and received=2E Classified Technical Program Submission Process: All persons wishing to attend and/or participate in the Classified = Technical Program must, at a minimum, possess a current Secret personnel = security clearance and be a U.S. citizen. Non-U.S. originated papers will = NOT be accepted for the Classified Technical Program. All abstracts for = the Classified Technical Program must be unclassified. Please submit a = title and a brief unclassified abstract (up to 2000 characters) of your = intended paper via email to: casto.milcom2007@harris.com. Each submission = requires author name, affiliation, citizenship, address, phone and fax = numbers, email address, and the applicable area. For papers with more than = one author, indicate the point of contact. Do NOT use WAMS to submit = abstracts, full papers, or the final papers for the Classified Technical = Program. All papers for the Classified Technical Program must be prepared = following the instructions and formatting guidelines in the Classified = Author=92s Kit=2E Proposals for Tutorials and Panels:=20 MILCOM 2007 solicits proposals for unclassified half-day tutorials, and = unclassified and classified panels on state-of-the art communications, = networking, and interoperability technologies. The tutorial proposals = should include a brief outline of the tutorial, instructor biography, and = relevant instructor experience. The Unclassified Tutorials Kit provides the applicable forms and the formatting guidelines for the = tutorial material. Please forward your proposals to the MILCOM 2007 = Tutorial Program Chair, Rich Folio, at folio.milcom2007@harris.com=2E Proposals for Panels:=20 The proposals for panels should include a brief outline of the panel = discussion topics, panel participants, and panel moderator along with = their bios. A Panels Kit provides the information about the applicable = forms and the guidelines for the preparation of the panel material. Please = forward your proposals to the MILCOM 2007 Panels Program Chair, Leo = deCardenas, at decardenas.milcom2007@harris.com=2E Tutorials and Panels Important Dates: Proposals Due: 16 March 2007 Notification: 20 April 2007 Material Due: 13 July 2007 For further details and information about MILCOM 2007 please visit = www.milcom.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 Mar 28 16:43:36 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWezY-0002Vn-Gv; Wed, 28 Mar 2007 16:43:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU6Kx-0003aC-KN for mip4@ietf.org; Wed, 21 Mar 2007 15:19:07 -0400 Received: from pcvs68.informatik.uni-stuttgart.de ([129.69.210.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HU6Kv-0004EN-QF for mip4@ietf.org; Wed, 21 Mar 2007 15:19:07 -0400 Received: from pcvs68.informatik.uni-stuttgart.de (localhost [127.0.0.1]) by pcvs68.informatik.uni-stuttgart.de (8.13.6/8.13.6) with ESMTP id l2LJM0hS013921 for ; Wed, 21 Mar 2007 20:22:00 +0100 Received: (from pjmarron@localhost) by pcvs68.informatik.uni-stuttgart.de (8.13.7/8.13.7/Submit) id l2LJM0XK013917 for mip4@ietf.org; Wed, 21 Mar 2007 20:22:00 +0100 Date: Wed, 21 Mar 2007 20:22:00 +0100 Message-Id: <200703211922.l2LJM0XK013917@pcvs68.informatik.uni-stuttgart.de> To: mip4@ietf.org From: marronpo@informatik.uni-stuttgart.de X-Spam-Score: 0.7 (/) X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f X-Mailman-Approved-At: Wed, 28 Mar 2007 16:43:34 -0400 Subject: [Mip4] Call for Participation: 8th IEEE Mobile Data Management Conference (MDM 2007) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org CALL FOR PARTICIPATION 8th International Conference on Mobile Data Management (MDM'07) Mannheim, Germany, May 7 - 11, 2007 http://mdm2007.uni-mannheim.de Sponsored by the IEEE CS and Infos In Cooperation with the VLDB Endowment SCOPE: The rapid advances in computing and wireless communication technologies along with their integration into commodity devices such as personal digital assistants, mobile phones, and portable computers provide a technical infrastructure that enables a wealth of mobile services and applications. These include scenarios where seamless access to a computing infrastructure is provided, scenarios where interaction and data sharing among mobile users occur in mobile ad-hoc networks, and hybrid scenarios that combine these two. The continued miniaturization of computing devices along with improvements in the performance/price ratio enable new services and applications, e.g., in environmental monitoring and transportation. Although substantial research has been conducted, this area remains ripe with open research challenges, e.g., in relation to context-aware computing, including location-based services; ubiquitous computing; mobile applications in hybrid networks; and data management in sensor networks. This year's conference has an exciting program: * Keynotes by: - Karl Aberer, professor for distributed information systems at the EPFL and Director of the Swiss National Centre for Mobile Information and Communication Systems - Ralf Hartmut Güting, professor for database systems at the University of Hagen, Germany * Presentations of 26 technical papers * Presentations of 7 demos * 3 advanced technology seminars: - Research Issues in Location-Aware Wireless Sensor Networks - Privacy in Location-Based Services: State-of-the-Art and Research Directions - Location-Aware Query Processing and Optimization * 5 one-day workshops on important topics in data management, mobility, sensor networks, etc. The workshops will be held the day before and after the main conference (see program below). Registration is now open: http://mdm2007.uni-mannheim.de/ The cut-off date for early registration is April 1, 2007. Please register today to guarantee the best rates. The entire team of organizers looks forward to seeing you at MDM in Mannheim! Pedro Jose Marron MDM2007 General Chair ========================================= ** -------- Technical Program -------- ** ========================================= Monday, 07.05.07: Workshops * Workshop 1: Second International Workshop on Managing Context Information and Semantics in Mobile Environments (MCISME) * Workshop 2: Tools and Applications for Mobile Contents (TAMC 07) Tuesday, 08.05.07: Opening and Keynote 1, 9:00-10:30 Session 1: Mobile P2P and Sensor Networks, 11:00-12:40 * 11:00 Phenomenon-aware Stream Query Processing M. H. Ali, Mohamed F. Mokbel, Walid G. Aref, Purdue University * 11:30 Mobile Peer-to-peer Data Dissemination with Resource Constraints Ouri Wolfson, Bo Xu, University of Illinois * 12:00 Optimizing Energy-Efficient Query Processing in Wireless Sensor Networks Ross Rosemark, Wang-Chien Lee, Bhuvan Urgaonkar, Pennsylvania State University * 12:20 Collaboratively Querying Sensor Networks through Handheld Devices TszWai Chiu, Qiong Luo, Hong Kong University of Science and Technology Session 2: Query Processing for moving objects, 14:30-16:00 * 14:30 BORA: Routing and aggregation for distributed processing of spatio-temporal range queries Goce Trajcevski, Hui Ding, Peter Scheuermann, Northwestern University, Isabel Cruz, University of Illinois * 15:00 PLACE*: A Distributed Spatio-temporal Data Stream Management System for Moving Objects Xiaopeng Xiong, Hicham G. Elmongui, Xiaoyong Chai, Walid G. Aref, Purdue University * 15:30 Semantics of Spatially-aware Windows over Streaming Moving Objects Kostas Patroumpas, Timos Sellis, National Technical University of Athens Session 3: Privacy and Security, 16:30-18:00 * 16:30 Privacy-Preserving Data Mining on Moving Object Trajectories Gyozo Gidofalvi, Geomatic ApS, Xuegang Huang, Torben Bach Pedersen, Aalborg University * 17:00 Anonymity in Location-based Services: towards a General Framework Claudio Bettini, Sergio Mascetti, University of Milan, X. Sean Wang, University of Vermont * 17:30 Enforcing Data Integrity in Very Large Ad Hoc Networks Daniela Gavidia, Maarten van Steen, Vrije Universiteit Amsterdam Seminar 1, 14:30-16:00 & 16:30-18:00 Research Issues in Location-Aware Wireless Sensor Networks Yingqi Xu and Wang-Chien Lee Wednesday, 09.05.07: Keynote 2, 9:00-10:30 Session 4: Broadcast Environments, 11:00-12:30 * 11:00 An Adaptive Control Method in the Hybrid Wireless Broadcast Environment Jing CAI, Tsutomu Terada, Takahiro Hara, Shojiro Nishio, Osaka University * 11:30 Variant Bandwidth Channel Allocation in the Data Broadcasting Environment Chung-Hua Chu, Hao-Ping Hung, Ming-Syan Chen, National Taiwan University * 12:00 Multi-Resolution Data Management for Opportunistic Networking Iacopo Carreras, David Tacconi, Daniele Miorandi, Imrich Chlamtac, CREATE-NET Session 5: Replication, 14:30-16:00 * 14:30 Exploiting Our Computational Surroundings for Better Mobile Collaboration Joao Barreto, Paulo Ferreira, Technical University of Lisbon * 15:00 Data Replication Considering Power Consumption in Ad Hoc Networks Masako Shinohara, Takahiro Hara, Shojiro Nishio, Osaka University * 15:30 Group Anti-Entropy - Achieving Eventual Consistency in Mobile Service Environments Klaus Herrmann, University of Stuttgart Demonstration Session, 16:30-18:00 Invited Seminar, 11:00-12:30 Location-Aware Query Processing and Optimization Mohamed Mokbel and Walid Aref Seminar 2, 14:30-16:00 & 16:30-18:00 Privacy in Location-Based Services: State-of-the-Art and Research Directions Mohamed Mokbel Thursday, 10.05.07: Session 6: Query Processing and Data Management, 9:00-10:20 * 9:00 ConQuer: A Peer Group-based Incentive Model for Constraint Querying in Mobile-P2P Networks Anirban Mondal, University of Tokyo, Sanjay Kumar Madria, University of Missouri-Rolla, Masaru Kitsuregawa, University of Tokyo * 9:20 Integrated Data Modeling for Querying Physical Objects in RFID-enabled Pervasive Computing Shaorong Liu, IBM Silicon Valley Lab, Fusheng Wang, Peiya Liu, Siemens Corporate Research * 9:40 Advanced Evasive Data Storage in Sensor Networks Zinaida Benenson, University of Mannheim, Peter M. Cholewinski, SAP, Felix C. Freiling, University of Mannheim * 10:00 Distributed Histograms for Processing Aggregate Data from Moving Objects Hairuo Xie, Egemen Tanin, Lars Kulik, University of Melbourne Panel: Location-based services: hype, fiction or future?, 11:00-12:30 Session 7: Data Management for Ad Hoc and Sensor Networks, 14:00-16:00 * 14:00 A Failure Tolerating Atomic Commit Protocol for Mobile Environments Stefan Böttcher, University of Paderborn, Le Gruenwald, University of Oklahoma, Sebastian Obermeier, University of Paderborn * 14:30 Quantifying Network Partitioning in Mobile Ad Hoc Networks Jörg Hähner, Leibniz Universität Hannover, Dominique Dudkowski, Pedro Jose Marron, Kurt Rothermel, Universität Stuttgart Session 8: Query Processing in Sensor Networks, 14:00-16:00 * 14:00 MINT Views: Materialized In-Network Top-k Views in Sensor Networks Demetrios Zeinalipour-Yazti, Panayiotis Andreou, University of Cyprus, Panos K. Chrysanthis, University of Pittsburgh, George Samaras, University of Cyprus * 14:30 On Join Location in Sensor Networks Alexandru Coman, Mario A. Nascimento, Joerg Sander, University of Alberta * 15:00 Infrastructure for Data Processing in Large-Scale Interconnected Sensor Networks Karl Aberer, EPFL, Manfred Hauswirth, National University of Ireland, Ali Salehi, EPFL Closing Remarks, 16:00 Friday, 11.05.07: Workshops * The International Workshop on Privacy-Aware Location-based Mobile Services (PALMS) * Mobile Services-oriented Architectures and Ontologies (MoSO 2007) * International Workshop on Data Intensive Sensor Networks 2007 (DISN 07) ============================= ** ------ Demos ------ ** ============================= Audio and Image Data Browser for Mobile Devices Tommi Lahti, Nokia Research Center, Finland, Paavo Pietarila, VTT Electronics, Finland Liu Yingfei, Timo Pylvänäinen, Nokia Research Center, Finland, Olli Vuorinen, VTT Electronics, Finland A Sensed-Point-Oriented Geographic Routing for Camera Networks Hiroki Ishizuka, Yoshito Tobe, Tokyo Denki University, Japan iPDA: Enabling Privacy-Preserving Location-Based Services Jing DU, Jianliang XU, Hong Kong Baptist Univ., China Xueyan TANG, Nanyang Technological Univ., Singapore Haibo HU, Hong Kong Baptist Univ., China Moppy: Mobile Object Position Prediction Application Lukasz Rosikiewicz, Logos sp.z o.o., Poznan, Poland Mikolaj Morzy, Poznan University of Technology, Poland CADD: The Context-ADDICT Designer tool for context modeling and data tailoring C. Bolchini, C. A. Curino, G. Orsi, E. Quintarelli, F. A. Schreiber, L. Tanca Politecnico di Milano, Italy Distribution of Fingerprints for 802.11-based Positioning Systems Thomas King, Thomas Butter, Matthias Brantner, Stephan Kopf, Thomas Haenselmann, Alexander Biskop, Andreas Färber, Wolfgang Effelsberg, University of Mannheim, Germany A Testbed for the Exploration of Novel Concepts in Mobile Service Delivery Rico Wind, Christian S. Jensen, Kristian Torp, Aalborg University, Denmark -- 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 Mar 28 16:43:45 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWezh-0002iV-2y; Wed, 28 Mar 2007 16:43:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUhIY-0001Jk-Of for mip4@ietf.org; Fri, 23 Mar 2007 06:47:06 -0400 Received: from mail.di.uniroma1.it ([151.100.17.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUhIF-0005iG-CS for mip4@ietf.org; Fri, 23 Mar 2007 06:47:06 -0400 Received: from [151.100.17.90] (unknown [151.100.17.90]) by mail.di.uniroma1.it (Postfix) with ESMTP id CFB351BD621 for ; Fri, 23 Mar 2007 11:37:24 +0100 (CET) Message-ID: <4603B010.7000400@di.uniroma1.it> Date: Fri, 23 Mar 2007 11:46:40 +0100 From: Gaia Maselli User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: it, it-it, en-us, en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 X-Mailman-Approved-At: Wed, 28 Mar 2007 16:43:40 -0400 Subject: [Mip4] CFP: ACM/SIGMOBILE HealthNet 2007 (extended deadline: April 6) X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: maselli@di.uniroma1.it List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Please apologize if you receive multiple copies. ------------------------------------------------------------ **** EXTENDED SUBMISSION DEADLINE **** APRIL 6, 2007 (5PM US EST) ------------------------------------------------------------ Call for Papers HealthNet 2007 The 1st International Workshop on Systems and Networking Support for Healthcare and Assisted Living Environments Sponsored by ACM/SIGMOBILE In conjunction with MobiSys 2007 http://healthnet07.cs.uiuc.edu June 11, 2007 Puerto Rico, USA ------------------------------------------------------------ WORKSHOP SCOPE: ================ As the world's population grows older, healthcare and high-tech companies are joining forces. New technologies are being used to provide improved support for elderly and home bound people in their homes and in assisted living environments. The overall goal of these initiatives is to improve the quality of life by providing customized support to people in need of assistance. The main challenge is to provide this support according to the user's own specific situation in a non-intrusive and respectful way. These new technologies enable the automation of the observation and support for elderly and home bound people through the use of sensors, actuators, distributed intelligence, databases, ubiquitous connectivity and friendly adaptive interfaces, all connected mainly via a variety of wireless networking technologies. The ultimate goal is a system that can adapt to the users needs, helping them get through their daily routine in a way that is effective in providing support where needed without making them feel humiliated by excessive attention. To provide such support, it will be necessary to combine efforts from many areas of computer science, including networking, distributed systems, security, data management, HCI, AI and middleware. Given the inherent use of mobile and wireless communication and the need for comprehensive distributed systems as well as the multi-disciplinary nature of solutions for healthcare and assisted living environments, the goal of HealthNet is to provide a forum for the cross-area interactions that will be necessary for successful systems and applications. The specific focus of HealthNet will be on understanding what it takes to provide effective systems and communication support for healthcare and assisted living environments. Although the systems and networking community is very good at providing effective solutions to satisfying application requirements, they require input from experts in other disciples, including HCI, middleware, security, privacy and social networking, to provide a more accurate understanding of the specific requirements for these environments. Therefore, HealthNet aims to attract researchers working on cross-disciplinary projects, with a focus on understanding and supporting the requirements of these complex applications. Authors are invited to submit papers presenting new research related to the support of healthcare and assisted living environments. 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: * Enabling technologies * Service and device discovery * Security and privacy * Reliability and fault tolerance * User and device localization * Resource management architecture * User data management * Middleware for heterogeneous networks * Mobility and connectivity management * Cross-layer system architecture design * Human-centered Computing * Task and behavior analysis * Impact of user interface design on system design and management * Test-beds and simulations environments IMPORTANT DATES: ================ Paper submission deadline: March 23, 2007 ***** EXTENDED TO APRIL 6, 2007 (5PM US EST) ****** Notification of acceptance: April 27, 2007 Camera ready version due: May 17, 2007 Workshop date: June 11, 2007 PAPER SUBMISSION INSTRUCTIONS: =============================== All paper submissions will be handled electronically. Papers must be in PDF format, no longer than 6 pages, double-column, with a font size no smaller than 10 points, and must fit properly on US Letter-sized paper (8.5 inch x 11 inch) with reasonable margins. The first page of each paper should include the names and affiliations of the authors, i.e., the submissions should not be anonymous and reviewing is single-blind. Submissions will be judged on based on technical content and correctness, relevance to the workshop, as well as presentation of the research. Extended versions of selected workshop papers will be considered for fast track publication in a special issue of ACM Monet. ORGANIZING COMMITTEE ==================== WORKSHOP Co-Chairs: * Robin Kravets, University of Illinois, USA * Chiara Petrioli, Rome University "La Sapienza," Italy PUBLICITY Co-Chairs: * Stefano Basagni, Northeastern University, USA * Gaia Maselli, Rome University "La Sapienza," Italy TECHNICAL PROGRAM COMMITTEE * Amy Murphy, IRST-ITC * Archan Misra, IBM * Gene Tsudik, ISI * Hans Gellersen, Lancaster University * Henry Kautz, University of Rochester * Jack Stankovic, University of Virginia * Jean-Pierre Ebert, IHP Microelectronics * Karrie Karahalios, University of Illinois * Kay Connelly, Indiana University * Maria Ebling, IBM * Martha Pollack, University of Michigan * Nigel Davies, Lancaster University * Sunny Consolvo, Intel * Taieb Znati, University of Pittsburgh * Tarek Abdelzaher, University of Illinois * Wendi Heinzelman, University of Rochester * Yih-Chun Hu, University of Illinois Please email questions related to paper submission or the technical program to: healthnet07@cs.uiuc.edu. Organized by UIUC and Rome University "La Sapienza". -- Gaia Maselli, PhD HealthNet 2007 Publicity Chair -- 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 Mar 28 16:45:09 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWf13-0003sB-FT; Wed, 28 Mar 2007 16:45:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HU41c-0000He-FC; Wed, 21 Mar 2007 12:51:00 -0400 Received: from ozzie.acm.org ([63.118.7.46]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HU41X-00053B-OY; Wed, 21 Mar 2007 12:51:00 -0400 Received: from ozzie (localhost) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <1.002E7238@ozzie.acm.org>; Wed, 21 Mar 2007 12:56:25 -0400 Received: by LISTSERV.ACM.ORG (LISTSERV-TCP/IP release 14.3) with spool id 21052926 for SENSORNET@LISTSERV.ACM.ORG; Wed, 21 Mar 2007 12:56:13 -0400 Received: from psmtp.com (exprod7mx83.postini.com) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <1.002E7237@ozzie.acm.org>; Wed, 21 Mar 2007 12:56:12 -0400 Received: from source ([63.118.7.109]) (using SSLv3) by exprod7mx83.postini.com ([64.18.6.14]) with SMTP; Wed, 21 Mar 2007 09:50:32 PDT Received: from psmtp.com ([64.18.2.109]) by acm26-4.acm.org (ACM Email Forwarding Service) with SMTP id ATH39031 for ; Wed, 21 Mar 2007 12:38:31 -0400 Received: from source ([13.1.64.93]) by exprod7mx59.postini.com ([64.18.6.14]) with SMTP; Wed, 21 Mar 2007 09:38:30 PDT Received: from [13.2.19.35] ([13.2.19.35]) by alpha.xerox.com with SMTP id <172909(2)>; Wed, 21 Mar 2007 09:38:14 PDT User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-pstn-levels: (S: 8.61488/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 5 (2.0000:0.0000) s gt3 gt2 GT1 r p m c X-pstn-addresses: from [36/2] X-pstn-levels: (S: 8.61488/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c X-pstn-addresses: from [141/11] Message-ID: <46015F75.5000006@parc.com> Date: Wed, 21 Mar 2007 09:38:13 PDT From: Ying Zhang X-To: sensornet@acm.org To: SENSORNET@LISTSERV.ACM.ORG Precedence: list X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 X-Mailman-Approved-At: Wed, 28 Mar 2007 16:45:04 -0400 Cc: Subject: [Mip4] IPSN07: book your hotel soon X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Reply-To: Ying Zhang List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hotel cutoff dates are approaching: Hotel @ MIT Reservation Cut-Off Date: Sunday, March 25, 2007 Cambridge Marriott Reservation Cut-Off Date: Tuesday, April 03, 2007 Conference schedule: http://www.cse.wustl.edu/~lu/ipsn07.html -- 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 Mar 28 16:45:13 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWf17-0003xN-0Z; Wed, 28 Mar 2007 16:45:13 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUY3s-000779-Uf; Thu, 22 Mar 2007 20:55:21 -0400 Received: from ozzie.acm.org ([63.118.7.46]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUXz6-00013e-GL; Thu, 22 Mar 2007 20:50:27 -0400 Received: from ozzie (localhost) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <4.002E92CC@ozzie.acm.org>; Thu, 22 Mar 2007 20:55:56 -0400 Received: by LISTSERV.ACM.ORG (LISTSERV-TCP/IP release 14.3) with spool id 21075488 for SENSORNET@LISTSERV.ACM.ORG; Thu, 22 Mar 2007 20:55:44 -0400 Received: from psmtp.com (exprod7mx91.postini.com) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <6.002E8908@ozzie.acm.org>; Thu, 22 Mar 2007 20:55:44 -0400 Received: from source ([63.118.7.108]) (using SSLv3) by exprod7mx91.postini.com ([64.18.6.14]) with SMTP; Thu, 22 Mar 2007 17:50:02 PDT Received: from psmtp.com ([64.18.2.93]) by acm26-3.acm.org (ACM Email Forwarding Service) with SMTP id CDV17201 for ; Thu, 22 Mar 2007 20:50:01 -0400 Received: from source ([13.1.64.93]) by exprod7mx98.postini.com ([64.18.6.14]) with SMTP; Thu, 22 Mar 2007 17:50:01 PDT Received: from [13.2.19.35] ([13.2.19.35]) by alpha.xerox.com with SMTP id <385844(1)>; Thu, 22 Mar 2007 17:49:53 PDT User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-pstn-levels: (S:19.77903/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 5 (2.0000:0.0000) s gt3 gt2 GT1 r p m c X-pstn-addresses: from [36/2] X-pstn-levels: (S:19.77903/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c X-pstn-addresses: from [141/11] Message-ID: <46032430.5080805@parc.com> Date: Thu, 22 Mar 2007 17:49:52 PDT From: Ying Zhang X-To: sensornet@acm.org X-cc: tianhe@cs.umn.edu To: SENSORNET@LISTSERV.ACM.ORG Precedence: list X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad X-Mailman-Approved-At: Wed, 28 Mar 2007 16:45:10 -0400 Cc: Subject: [Mip4] IPSN07: Travel Grant Deadline Approaching X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Reply-To: Ying Zhang List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org *IPSN07 Travel Grant Deadline: March 28* Again Hotel cutoff dates are approaching: Hotel @ MIT Reservation Cut-Off Date: Sunday, March 25, 2007 Cambridge Marriott Reservation Cut-Off Date: Tuesday, April 03, 2007 Conference schedule: http://www.cse.wustl.edu/~lu/ipsn07.html -- 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 Mar 28 16:46:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWf2T-0005wG-Nr; Wed, 28 Mar 2007 16:46:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HW4dV-0006hb-Jd; Tue, 27 Mar 2007 01:54:25 -0400 Received: from ozzie.acm.org ([63.118.7.46]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HW4dR-00081B-8Y; Tue, 27 Mar 2007 01:54:25 -0400 Received: from ozzie (localhost) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <6.002ECAFF@ozzie.acm.org>; Tue, 27 Mar 2007 1:59:57 -0400 Received: by LISTSERV.ACM.ORG (LISTSERV-TCP/IP release 14.3) with spool id 21134892 for SENSORNET@LISTSERV.ACM.ORG; Tue, 27 Mar 2007 01:59:45 -0400 Received: from psmtp.com (exprod7mx99.postini.com) by ozzie.acm.org (LSMTP for Windows NT v1.1b) with SMTP id <4.002ED671@ozzie.acm.org>; Tue, 27 Mar 2007 1:59:44 -0400 Received: from source ([131.107.115.215]) (using TLSv1) by exprod7mx99.postini.com ([64.18.6.14]) with SMTP; Mon, 26 Mar 2007 22:53:56 PDT Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.56.116.111) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.0.685.24; Mon, 26 Mar 2007 22:53:53 -0700 Received: from NA-EXMSG-C105.redmond.corp.microsoft.com ([157.54.52.48]) by tk1-exhub-c101.redmond.corp.microsoft.com ([157.56.116.111]) with mapi; Mon, 26 Mar 2007 22:53:52 -0700 Thread-Topic: IPSN'07 Call for Participation Thread-Index: Acdbai843T0n47h2SV+QeVW6/m6HZgUwv1mg Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-pstn-levels: (S:99.90000/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c X-pstn-addresses: from [141/11] Message-ID: <55E173F65C36D94DBCC89D904E3CB21D478FF426B1@NA-EXMSG-C105.redmond.corp.microsoft.com> Date: Mon, 26 Mar 2007 22:53:42 -0700 From: Feng Zhao To: SENSORNET@LISTSERV.ACM.ORG Precedence: list X-Spam-Score: 0.0 (/) X-Scan-Signature: a83e8b750067501be8b56bf02fb6582d X-Mailman-Approved-At: Wed, 28 Mar 2007 16:46:36 -0400 Cc: Subject: [Mip4] FW: IPSN'07 Call for Participation X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Reply-To: Feng Zhao List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1881635547==" Errors-To: mip4-bounces@ietf.org --===============1881635547== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_55E173F65C36D94DBCC89D904E3CB21D478FF426B1NAEXMSGC105re_" --_000_55E173F65C36D94DBCC89D904E3CB21D478FF426B1NAEXMSGC105re_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'd like to encourage you to consider attending IPSN'07 (http://ipsn.acm.or= g) and several co-located events on the MIT campus (Cambridge, MA) next mon= th. The organizers of the conference has done a wonderful job in putting to= gether a top notch and very exciting program for Wednesday-Friday April 25-= 27. Here are a few other highlights: * Bob Metcalfe, inventor of Ethernet, will give a keynote on "Ether= net is the Answer; What is the question?" Wednesday afternoon. * Continuing the tradition, there will be a demo session, together = with the poster session, for students and practitioners to showcase the lat= est experimental systems. * An open "Extreme Sensing Competition" will be held next to the de= mo area. The goal is for participating teams to test people sensing/detecti= on algorithms on the noisy demo floor. And the winner will get one of the l= atest gaming console! * Two workshops, one on "Wireless sensor network architecture", and= another on "Data sharing and interoperability on world wide sensor web", w= ill be held on Tuesday, right before the main conference. * A hands-on tutorial on acoustic and seismic sensing will be offer= ed on Tuesday, and another on SensorMap for wide-area sensornet on Saturday= . * The 4th International TinyOS Technology Exchange (TTX4) will also= co-locate with IPSN on Saturday, April 28. As a reminder, the early registration deadline is April 3. I hope to see ma= ny of you in Cambridge! Feng --------- Feng Zhao, Microsoft Research, One Microsoft Way, Redmond, WA 98052, USA. http://resea= rch.microsoft.com/~zhao -----Original Message----- From: ACM SIGBED SensorNet List [mailto:SENSORNET@LISTSERV.ACM.ORG] On Beha= lf Of Ying Zhang Sent: Wednesday, February 28, 2007 10:55 AM To: SENSORNET@LISTSERV.ACM.ORG Subject: IPSN'07 Call for Participation *Advance Registration Deadline: 4/3/07* *Program Schedule and Registration in Website:* http://www.cse.wustl.edu/ipsn07.html ----------------------------------------------------------------------- CALL FOR PARTICIPATION The Sixth International Conference on Information Processing in Sensor Networks (IPSN'07) April 25 - 27, 2007 - Cambridge, Massachusetts, USA The sixth International Conference on Information Processing in Sensor Networks (IPSN 2007) will continue the success of previous five symposia to bring together researchers from academia, industry, and government to present and discuss recent work in sensor network research and applications. IPSN draws upon many disciplines including signal and image processing, information and coding theory, networking and protocols, distributed algorithms, wireless communications, machine learning, embedded systems design, and databases and information management. To further foster the collaboration between theory and practice, this conference will feature two interleaving tracks: IPSN, focusing more on information processing algorithms,and SPOTS, focusing on platform tools and design methods for network embedded sensors. In addition, IPSN'07 will feature a competition; details for rules and participation will be announced in the IPSN'07 competition website http://www.cs.virginia.edu/~whitehouse/ipsn07competition/. Topics covered in IPSN sessions include, but are not limited to, the following: - Distributed & collaborative signal processing - Network protocols for sensor networks - Coding, compression & information theory - Distributed query processing - Detection, classification, estimation, tracking - Sensor tasking and control - Networked sensing and control - In-network processing and aggregation - Distributed control & actuation - Distributed inference & fusion - Fault tolerance - Network coverage, connectivity & longevity - Data storage in sensor networks - Location and time services - Energy and resource management - Programming models and languages - Real-time scheduling - Security - Application & demonstration of sensor networks Topics covered in SPOTS sessions include, but are not limited to, the following: - Embedded networked sensor system platforms, platform modeling and analysis tools - Architectural design, modeling and optimization tools for sensor nodes and networks - Sensor node components and interfaces, middleware and system services - Applications of embedded networked sensing with actual field deployments that highlight new themes in the design and operation of these complete systems. Organization Committee General Chair: Tarek Abdelzaher (University of Illinois at Urbana-Champaign), IPSN co-Chairs: Leo Guibas (Stanford University) and Matt Welsh (Harvard University), SPOTS co-Chairs: Bill Kaiser (University of California at Los Angles) and Ralph Kling (Crossbow), Competition Chair: Kamin Whitehouse (University of Virginia), Demos Chair: Phil Levis (Stanford University), Finance Chair: John Heidemann (University of Southern California), Industry Sponsorship Chair: Joe Hellerstein (University of California at Berkeley), Local Arrangements: Seth Teller (Massachusetts Institute of Technology), Poster Chair: Haiyun Luo (University of Illinois at Urbana-Champaign), Publications Chair: Bhaskar Krishnamachari (University of Southern California), Publicity Chair: Ying Zhang (Palo Alto Research Center), Registration Chair: Jie Liu (Microsoft Research), Web Chair: Chenyang Lu (Washington University in St. Louis) --_000_55E173F65C36D94DBCC89D904E3CB21D478FF426B1NAEXMSGC105re_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I'd like to encourage you to consider attending IPS= N'07 (http://ipsn.acm.org) and several co-locate= d events on the MIT campus (Cambridge, MA) next month. The organizers of the = conference has done a wonderful job in putting together a top notch and very exciting = program for Wednesday-Friday April 25-27. Here are a few other highlights:

 

·      =    Bob Metcalfe, inventor of Ethernet, will giv= e a keynote on "Ethernet is the Answer; What is the question?" Wednes= day afternoon.

 

·      =    Continuing the tradition, there will be a de= mo session, together with the poster session, for students and practitioners t= o showcase the latest experimental systems.

 

·      =    An open "Extreme Sensing Competition&qu= ot; will be held next to the demo area. The goal is for participating teams to = test people sensing/detection algorithms on the noisy demo floor. And the winner will get one of the latest gaming console!

 

·      =    Two workshops, one on "Wireless sensor network architecture", and another on "Data sharing and interoperability on world wide sensor web", will be held on Tuesday, r= ight before the main conference.

 

·      =    A hands-on tutorial on acoustic and seismic = sensing will be offered on Tuesday, and another on SensorMap for wide-area sensorne= t on Saturday.

 

·      =    The 4th International TinyOS Technology Exch= ange (TTX4) will also co-locate with IPSN on Saturday, April 28.

 

As a reminder, the early registration deadline is A= pril 3. I hope to see many of you in Cambridge!

 

 

Feng

 

---------

Feng Zhao,

Microsoft Research, One Microsoft Way, Redmond, WA = 98052, USA. http://research.microsoft.com/~zhao

 

 

-----Original Message-----
From: ACM SIGBED SensorNet List [mailto:SENSORNET@LISTSERV.ACM.ORG] On Beha= lf Of Ying Zhang
Sent: Wednesday, February 28, 2007 10:55 AM
To: SENSORNET@LISTSERV.ACM.ORG
Subject: IPSN'07 Call for Participation

 

*Advance Registration Deadline: 4/3/07*<= /p>

*Program Schedule and Registration in Website:*

 

http://www.cse.wustl.edu/ipsn07.html

 

---------------------------------------------------= --------------------

 

CALL FOR PARTICIPATION

The Sixth International Conference on

Information Processing in Sensor Networks (IPSNR= 17;07)

 

April 25 - 27, 2007 – Cambridge, Massachusett= s, USA

 

The sixth International Conference on Information Processing in

Sensor Networks (IPSN 2007) will continue the succe= ss of previous

five symposia to bring together researchers from academia, industry,

and government to present and discuss recent work i= n sensor network

research and applications. IPSN draws upon many disciplines including

signal and image processing, information and coding theory, networking

and protocols, distributed algorithms, wireless communications,

machine learning, embedded systems design, and data= bases and information

management.

 

To further foster the collaboration between theory = and practice,

this conference will feature two interleaving track= s: IPSN, focusing

more on information processing algorithms,and SPOTS= , focusing on

platform tools and design methods for network embed= ded sensors.

In addition, IPSN'07 will feature a competition; de= tails for rules

and participation will be announced in the IPSN'07 competition website

http://www.cs.virginia.edu/~whitehouse/ipsn07compet= ition/.

 

Topics covered in IPSN sessions include, but are no= t limited to,

the following:

 

- Distributed & collaborative signal processing=

- Network protocols for sensor networks<= /p>

- Coding, compression & information theory=

- Distributed query processing

- Detection, classification, estimation, tracking

- Sensor tasking and control

- Networked sensing and control

- In-network processing and aggregation<= /p>

- Distributed control & actuation

- Distributed inference & fusion

- Fault tolerance

- Network coverage, connectivity & longevity

- Data storage in sensor networks

- Location and time services

- Energy and resource management

- Programming models and languages

- Real-time scheduling

- Security

- Application & demonstration of sensor network= s

 

Topics covered in SPOTS sessions include, but are n= ot limited to,

the following:

 

- Embedded networked sensor system platforms, platf= orm modeling

and analysis tools

- Architectural design, modeling and optimization t= ools for sensor

nodes and networks

- Sensor node components and interfaces, middleware= and system services

- Applications of embedded networked sensing with a= ctual field deployments

that highlight new themes in the design and operati= on of these complete

systems.

 

Organization Committee

 

General Chair: Tarek Abdelzaher (University of Illi= nois at

Urbana-Champaign),

IPSN co-Chairs: Leo Guibas (Stanford University) an= d Matt Welsh (Harvard

University),

SPOTS co-Chairs: Bill Kaiser (University of Califor= nia at Los Angles)

and Ralph Kling

(Crossbow),

Competition Chair: Kamin Whitehouse (University of Virginia),

Demos Chair: Phil Levis (Stanford University),=

Finance Chair: John Heidemann (University of Southe= rn California),

Industry Sponsorship Chair: Joe Hellerstein (Univer= sity of California at

Berkeley),

Local Arrangements: Seth Teller (Massachusetts Inst= itute of Technology),

Poster Chair: Haiyun Luo (University of Illinois at Urbana-Champaign),

Publications Chair: Bhaskar Krishnamachari (Univers= ity of Southern

California),

Publicity Chair: Ying Zhang (Palo Alto Research Cen= ter),

Registration Chair: Jie Liu (Microsoft Research),

Web Chair: Chenyang Lu (Washington University in St= . Louis)

--_000_55E173F65C36D94DBCC89D904E3CB21D478FF426B1NAEXMSGC105re_-- --===============1881635547== 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/ --===============1881635547==-- From mip4-bounces@ietf.org Wed Mar 28 16:49:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWf4r-0008EH-0y; Wed, 28 Mar 2007 16:49:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWf4o-0008DA-S3 for mip4@ietf.org; Wed, 28 Mar 2007 16:49:02 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWf4m-00066d-Hv for mip4@ietf.org; Wed, 28 Mar 2007 16:49:02 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-5.tower-128.messagelabs.com!1175114939!13700337!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [144.189.100.105] Received: (qmail 20168 invoked from network); 28 Mar 2007 20:48:59 -0000 Received: from motgate5.mot.com (HELO motgate5.mot.com) (144.189.100.105) by server-5.tower-128.messagelabs.com with SMTP; 28 Mar 2007 20:48:59 -0000 Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234]) by motgate5.mot.com (8.12.11/Motorola) with ESMTP id l2SKmwNu023872 for ; Wed, 28 Mar 2007 13:48:58 -0700 (MST) Received: from az10vts03 (az10vts03.mot.com [10.64.251.244]) by az33exr04.mot.com (8.13.1/Vontu) with SMTP id l2SKmv1W006074 for ; Wed, 28 Mar 2007 15:48:57 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id l2SKmujM006059 for ; Wed, 28 Mar 2007 15:48:56 -0500 (CDT) 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] Minutes from Prague Date: Wed, 28 Mar 2007 16:48:55 -0400 Message-ID: In-Reply-To: <008d01c77174$4b5e3a40$2f01a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minutes from Prague Thread-Index: AcdxTUrnSG74d5ijQJaqLtgrD6LYBAAJm87wAAGnbXA= References: <008d01c77174$4b5e3a40$2f01a8c0@china.huawei.com> From: "McCann Peter-A001034" To: "Madjid Nakhjiri" , "Mobile IPv4 Mailing List" X-Vontu: Pass X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: kleung@cisco.com, "Chowdhury, Kuntal" , Henrik Levkowetz , Avi Lior X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, Madjid, Would it be possible to get the reviews sent to the list, and some description from you of how they were addressed? -Pete Madjid Nakhjiri wrote: > Hi Chairs, >=20 >=20 > draft-ietf-mip4-radius-requirements Active > - Needs review!!! > Peter: Will go outside the WG to find reviewers. >=20 > This document was actually produced as a response to the outside (AD > and RADEXT chairs) reviews on the draft-nakhjiri-radius-mip4-02.=20 >=20 > Is it possible to do a last call on this requirement document? >=20 > Thanks, >=20 > Madjid >=20 > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] > Sent: Wednesday, March 28, 2007 8:25 AM > To: Mobile IPv4 Mailing List > Subject: [Mip4] Minutes from Prague >=20 > Attached are the draft minutes from the mip4 meeting at IETF 68 in > Prague. Please review and send comments and corrections to the list.=20 >=20 > Thanks to Vidya Narayanan and Nicolas Montavont for taking notes > during the meeting.=20 >=20 > -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 Wed Mar 28 18:01:06 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWgCJ-00054l-VQ; Wed, 28 Mar 2007 18:00:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWgCI-00054g-M0 for mip4@ietf.org; Wed, 28 Mar 2007 18:00:50 -0400 Received: from usaga01-in.huawei.com ([206.16.17.211]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWgCH-0007rU-Dk for mip4@ietf.org; Wed, 28 Mar 2007 18:00:50 -0400 Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JFM00C0BVTCUK@usaga01-in.huawei.com> for mip4@ietf.org; Wed, 28 Mar 2007 15:00:49 -0700 (PDT) Received: from N737011 (pool-71-112-126-182.sttlwa.dsl-w.verizon.net [71.112.126.182]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JFM00JVPVT79Z@usaga01-in.huawei.com> for mip4@ietf.org; Wed, 28 Mar 2007 15:00:48 -0700 (PDT) Date: Wed, 28 Mar 2007 15:00:47 -0700 From: Madjid Nakhjiri Subject: RE: [Mip4] Minutes from Prague In-reply-to: To: 'McCann Peter-A001034' , 'Mobile IPv4 Mailing List' Message-id: <00e401c77184$8b49cd80$2f01a8c0@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdxTUrnSG74d5ijQJaqLtgrD6LYBAAJm87wAAGnbXAAAlZ+EA== X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: 'Madjid Nakhjiri' , kleung@cisco.com, "'Chowdhury, Kuntal'" , 'Henrik Levkowetz' , 'Avi Lior' X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi Pete, As I said the reviews were on the nakhjiri-radius-mip4-02 and mainly around how/whether Mobile IP is extending RADIUS beyond its limit or not and that is why we wrote the ietf-mip4-radius-requirement as a response to those reviews to show that we are not stressing RADIUS in any way. Part of the issue was also that RADEXT has been working on its attribute space extension. The requirement doc has not been reviewed, since 00 was presumably expired before a review. My suggestion was to force a review through last call. If you are interested in the comments on nakhjiri-radius-mip4, I can send it. R, Madjid -----Original Message----- From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] Sent: Wednesday, March 28, 2007 1:49 PM To: Madjid Nakhjiri; Mobile IPv4 Mailing List Cc: Chowdhury, Kuntal; kleung@cisco.com; Avi Lior; Henrik Levkowetz Subject: RE: [Mip4] Minutes from Prague Hi, Madjid, Would it be possible to get the reviews sent to the list, and some description from you of how they were addressed? -Pete Madjid Nakhjiri wrote: > Hi Chairs, > > > draft-ietf-mip4-radius-requirements Active > - Needs review!!! > Peter: Will go outside the WG to find reviewers. > > This document was actually produced as a response to the outside (AD > and RADEXT chairs) reviews on the draft-nakhjiri-radius-mip4-02. > > Is it possible to do a last call on this requirement document? > > Thanks, > > Madjid > > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] > Sent: Wednesday, March 28, 2007 8:25 AM > To: Mobile IPv4 Mailing List > Subject: [Mip4] Minutes from Prague > > Attached are the draft minutes from the mip4 meeting at IETF 68 in > Prague. Please review and send comments and corrections to the list. > > Thanks to Vidya Narayanan and Nicolas Montavont for taking notes > during the meeting. > > -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 Wed Mar 28 18:51:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWgzU-0006IC-KM; Wed, 28 Mar 2007 18:51:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWgzS-0006I2-NE for mip4@ietf.org; Wed, 28 Mar 2007 18:51:38 -0400 Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWgzR-0000vd-AZ for mip4@ietf.org; Wed, 28 Mar 2007 18:51:38 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-13.tower-153.messagelabs.com!1175122293!6240405!1 X-StarScan-Version: 5.5.10.7.1; banners=-,-,- X-Originating-IP: [144.189.100.103] Received: (qmail 1852 invoked from network); 28 Mar 2007 22:51:33 -0000 Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-13.tower-153.messagelabs.com with SMTP; 28 Mar 2007 22:51:33 -0000 Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l2SMpWea004474 for ; Wed, 28 Mar 2007 15:51:32 -0700 (MST) Received: from az10vts03 (az10vts03.mot.com [10.64.251.244]) by az33exr03.mot.com (8.13.1/Vontu) with SMTP id l2SMpURF025230 for ; Wed, 28 Mar 2007 17:51:31 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l2SMpTei025219 for ; Wed, 28 Mar 2007 17:51:30 -0500 (CDT) 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] Minutes from Prague Date: Wed, 28 Mar 2007 18:51:29 -0400 Message-ID: In-Reply-To: <00e401c77184$8b49cd80$2f01a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Minutes from Prague Thread-Index: AcdxTUrnSG74d5ijQJaqLtgrD6LYBAAJm87wAAGnbXAAAlZ+EAABpHwQ References: <00e401c77184$8b49cd80$2f01a8c0@china.huawei.com> From: "McCann Peter-A001034" To: "Madjid Nakhjiri" , , X-Vontu: Pass X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Cc: "Chowdhury, Kuntal" , Mobile IPv4 Mailing List , kleung@cisco.com, Henrik Levkowetz , Avi Lior X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi, Madjid, Sorry, I missed the distinction between nakhjiri-radius-mip4-02 and ietf-mip4-radius-requirement. My mistake. >From our charter: 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been proposed for MIPv4. The working group will first produce a requirements specification, describing how the work differs from the requirements in RFC 2977 and the functionality provided by RFC 4004 (the MIPv4 Diameter App). The reason why this first step is required is that RFC 3127 shows that full RFC 2977 functionality can't be provided by even a considerably extended RADIUS, so we need to match the requirements to what can be done within RADIUS. Provided the requirements work finds approval with ADs and RADEXT WG, the workgroup will complete the specification of MIPv4 RADIUS attributes, solicit feedback from the RADEXT WG, adjust, and submit this for publication. Note that the work may require extensions to the RADIUS attribute space which will be handled outside the MIP4 WG. RADEXT chairs: could one of you (or someone you designate) please review the draft-ietf-mip4-radius-requirements-01.txt, and let us know whether it answers your concerns? Thanks, -Pete Madjid Nakhjiri wrote: > Hi Pete, >=20 > As I said the reviews were on the nakhjiri-radius-mip4-02 and mainly > around how/whether Mobile IP is extending RADIUS beyond its limit or > not and that is why we wrote the ietf-mip4-radius-requirement as a > response to those reviews to show that we are not stressing RADIUS in > any way. Part of the issue was also that RADEXT has been working on > its attribute space extension. =20 >=20 > The requirement doc has not been reviewed, since 00 was presumably > expired before a review. My suggestion was to force a review through > last call. =20 >=20 > If you are interested in the comments on nakhjiri-radius-mip4, I can > send it.=20 >=20 > R, >=20 > Madjid >=20 >=20 >=20 > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] > Sent: Wednesday, March 28, 2007 1:49 PM > To: Madjid Nakhjiri; Mobile IPv4 Mailing List > Cc: Chowdhury, Kuntal; kleung@cisco.com; Avi Lior; Henrik Levkowetz > Subject: RE: [Mip4] Minutes from Prague >=20 > Hi, Madjid, >=20 > Would it be possible to get the reviews sent to the list, and some > description from you of how they were addressed?=20 >=20 > -Pete >=20 > Madjid Nakhjiri wrote: >> Hi Chairs, >>=20 >>=20 >> draft-ietf-mip4-radius-requirements Active - >> Needs review!!! Peter: Will go outside the WG to find reviewers. >>=20 >> This document was actually produced as a response to the outside (AD >> and RADEXT chairs) reviews on the draft-nakhjiri-radius-mip4-02. >>=20 >> Is it possible to do a last call on this requirement document? >>=20 >> Thanks, >>=20 >> Madjid >>=20 >> -----Original Message----- >> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] >> Sent: Wednesday, March 28, 2007 8:25 AM >> To: Mobile IPv4 Mailing List >> Subject: [Mip4] Minutes from Prague >>=20 >> Attached are the draft minutes from the mip4 meeting at IETF 68 in >> Prague. Please review and send comments and corrections to the list. >>=20 >> Thanks to Vidya Narayanan and Nicolas Montavont for taking notes >> during the meeting.=20 >>=20 >> -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 Thu Mar 29 03:07:17 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWoj0-0002AG-Qw; Thu, 29 Mar 2007 03:07:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWoiy-0002AA-P2 for mip4@ietf.org; Thu, 29 Mar 2007 03:07:08 -0400 Received: from wr-out-0506.google.com ([64.233.184.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWoiw-0005jT-Hl for mip4@ietf.org; Thu, 29 Mar 2007 03:07:08 -0400 Received: by wr-out-0506.google.com with SMTP id 71so102271wri for ; Thu, 29 Mar 2007 00:07:06 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=SDUoJd1KHp0UEhhd+tL1u3AvOhzEIshvCLWjVJ2o1b050Wnws1XNLS0dnUVJlg9IEpUbGK2gzcjf7OIqqwbcRnFYiwogTEEBPwwtMuSVg6F7sgdyV0myF6iWs39boD7jaKBms7X/2v5uJofwucyHnuuIz2Ei2kMDX1HXke3AnJU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QnjzfxyBGVSco/FF26P1cCl46Xd2de4QjN6548C9sWR90woJWven2jljVyWI85DfSVVFz15H8GD2InpVuOfHeGTpy5FwdgoEP+s4Cla9CnVUpu9e7Tzrmp3iLHzJRDy0gcmusaLWY/rMKP5EoUj0GnXnUSGEhK8Y8+c3q1Ir63Y= Received: by 10.115.60.1 with SMTP id n1mr134873wak.1175152025446; Thu, 29 Mar 2007 00:07:05 -0700 (PDT) Received: by 10.114.193.6 with HTTP; Thu, 29 Mar 2007 00:07:05 -0700 (PDT) Message-ID: <88bc8c7a0703290007r72f45cf9w73958f789bd131e7@mail.gmail.com> Date: Thu, 29 Mar 2007 10:07:05 +0300 From: "Bjorn Andersson" To: "Arun SG" Subject: Re: [Mip4] Minor issue with MN advertisement sequence number handling In-Reply-To: <653F3CF58193744C9DE59C217C072B58CFC634@nilgiri.india.wirelessworld.airvananet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <653F3CF58193744C9DE59C217C072B58CFC634@nilgiri.india.wirelessworld.airvananet.com> X-Google-Sender-Auth: 706680afd80a9f0e X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: mip4@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: mip4-bounces@ietf.org Hi. On 3/26/07, Arun SG wrote: > This takes care of the control plane and maybe one additional line in > data plane is needeed too? Below is an edited version of Bjorn's > original sequence below: [...] > 6.a The MN has continued to send packets as per its original > registration. Should there be an addition line in section 4.2.2 , para > 3, stating that the datagram from unregistered MN's must be silently > discarded? Such a description exists in the reverse path towards the MN. If I understood you correctly you would like to change 4.2.2. para 3 to something like: The foreign agent MUST route datagrams it receives from registered mobile nodes and MUST silently discard datagrams it receives from unregistered mobile nodes. Adding this restriction may prevent the FA from acting as a normal router as well, so I feel that would be a little bit too restrictive. It should be up to the operator policy which packets the FA forwards. Bjorn -- 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 Mar 29 10:51:03 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWvxh-0002Ck-3o; Thu, 29 Mar 2007 10:50:49 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWvxR-0001wP-Q1; Thu, 29 Mar 2007 10:50:33 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HWvxQ-0004Ls-DD; Thu, 29 Mar 2007 10:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 545DF2ACA4; Thu, 29 Mar 2007 14:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HWvww-0004yF-3O; Thu, 29 Mar 2007 10:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 29 Mar 2007 10:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-nemov4-fa-00.txt X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-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 : FA extensions to NEMOv4 Base Author(s) : G. Tsirtsis, et al. Filename : draft-ietf-mip4-nemov4-fa-00.txt Pages : 14 Date : 2007-3-28 The base NEMOv4 specification defines extensions to Mobile IPv4 for mobile networks. NEMOv4 extensions are defined for use only by the mobile node and the home agent. This specification introduces extensions for NEMO support on the foreign agent. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-nemov4-fa-00.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-nemov4-fa-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-nemov4-fa-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --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: <2007-3-29081856.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-nemov4-fa-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-nemov4-fa-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-29081856.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--