From mip4-bounces@ietf.org Tue Jul 03 10:43:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jbf-0001UG-PM; Tue, 03 Jul 2007 10:43:55 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I5jbc-0001Tk-Sv for mip4-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 10:43:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jbc-0001TZ-J6; Tue, 03 Jul 2007 10:43:52 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5jbW-0007ZI-RW; Tue, 03 Jul 2007 10:43:52 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 03 Jul 2007 07:43:46 -0700 X-IronPort-AV: i="4.16,492,1175497200"; d="scan'208"; a="176118510:sNHT71788500" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l63Ehkg8011410; Tue, 3 Jul 2007 07:43:46 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l63Ehjvv000004; Tue, 3 Jul 2007 14:43:45 GMT Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 3 Jul 2007 07: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] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt Date: Tue, 3 Jul 2007 07:44:09 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB03F25533@xmb-sjc-236.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egEEv1oA From: "Parviz Yegani \(pyegani\)" To: "Ralph Droms \(rdroms\)" , , "DHC WG" X-OriginalArrivalTime: 03 Jul 2007 14:43:45.0777 (UTC) FILETIME=[8F1BB610:01C7BD80] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1912; t=1183473826; x=1184337826; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pyegani@cisco.com; z=From:=20=22Parviz=20Yegani=20\(pyegani\)=22=20 |Subject:=20RE=3A=20[Mip4]=20EXTENDED=3A=20mip4=20and=20dhc=20WG=20joint= 20last=20call=20on=20draft-ietf-mip4-gen-ext-03.txt |Sender:=20; bh=y3+vKPqzlfywqZOiHDMm+jo6yYWosTrx0GdsbDpzi10=; b=GAf7ljw8xN0/J5G/xf8C/VDeWIKg7GcO3WXaOcaCGsxD2+GlRU8AeMn6HToicIaugU4gsjFE qRlKmbz7y5jVNuuOckreeDMWHrWjWXpLzMBa9+x8OyviwGsmKZ+Tw0/s; Authentication-Results: sj-dkim-3; header.From=pyegani@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 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 I support advancing this draft to an RFC. Rgds, Parviz=20 -----Original Message----- From: Ralph Droms (rdroms)=20 Sent: Thursday, June 28, 2007 3:18 AM To: mip4@ietf.org; DHC WG Subject: [Mip4] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt There has been no response to this WG last call, so the deadline will be extended to 1700EDT, 07/05/07. =3D=3D=3D=3D=3D This message announces a joint WG last call for the mip4 and dhc WGs on "Mobile IPv4 Extension for Configuration Options Exchange" . The last call will conclude at 1700EDT, Monday, 06/25/07. The dhc WG is asked to review the use of DHCP options in this draft to pass configuration information to a mobile node. Please respond to this joint WG last call. Responses may be sent to either mip4@ietf.org or dhcwg@ietf.org. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. Lack of discussion does not represent positive support. If there is no expression of support for acceptance during the WG last call, the document will not be advanced to the IESG. draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing the host configuration information during Mobile IP registration. One or more Configuration Options Exchange Extensions may be included in the registration message to provide the Mobile Node the configuration parameters needed for network service (e.g. DNS). This draft is available as http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt - Stig Venaas, Ralph Droms dhc WG chairs -- 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 Tue Jul 03 13:03: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 1I5lmr-0007ap-PU; Tue, 03 Jul 2007 13:03:37 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I5lmq-0007YU-Qo for mip4-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 13:03:36 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5lmq-0007YD-Eq for mip4@ietf.org; Tue, 03 Jul 2007 13:03:36 -0400 Received: from zrtps0kn.nortel.com ([47.140.192.55]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5lmq-000889-4n for mip4@ietf.org; Tue, 03 Jul 2007 13:03:36 -0400 Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com [47.103.123.73]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l63H2eU28272 for ; Tue, 3 Jul 2007 17:02:41 GMT 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_01C7BD93.EC46F060" Date: Tue, 3 Jul 2007 12:02:18 -0500 Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA437115597A12@zrc2hxm2.corp.nortel.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-muhanna-diameter-mip4-performance-00.txt thread-index: Ace9gDJ7/TBveY8vTGWCH4BSxG4kUgAC4GOA From: "Ahmad Muhanna" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f Cc: Mohamed Khalil , Ahmad Muhanna Subject: [Mip4] FW: I-D ACTION:draft-muhanna-diameter-mip4-performance-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 This is a multi-part message in MIME format. ------_=_NextPart_001_01C7BD93.EC46F060 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Hello folks, We tried to make some comparison between the Diameter Mobile IPv4 Application and RADIUS based MIPv4 authentication and authorization procedures and their impact on the initial MIPv4 session setup. We tried to cover all scenarios but for sure we are looking forward for your feedback and comments to enhance this humble study. Many thanks in advance for your feedback. Regards, Ahmad -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 Sent: Tuesday, July 03, 2007 9:15 AM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-muhanna-diameter-mip4-performance-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : MIPv4 Authentication Performance Using RADIUS and Diameter MIPv4 Author(s) : A. Muhanna, M. Khalil Filename : draft-muhanna-diameter-mip4-performance-00.txt Pages : 16 Date : 2007-7-3 =09 Current Mobile IPv4 deployments use RADIUS based MIPv4 user authentication and authorization. Diameter Mobile IPv4 Application [RFC4004] offers another method for MIPv4 authentication, authorization, and dynamic mobility security association allocation, e.g. MN-HA SA allocation. Some SDOs are considering the use of Diameter Mobile IPv4 Application to replace RADIUS based mechanism. This document presents an analysis of the performance and impact of Diameter MIPv4 Application and RADIUS based solutions on the time the mobile node uses during the initial session setup. Some common MIPv4 scenarios which require the mobile node to retransmit its initial RRQ message have been identified and used. The set of assumptions and requirements used for this study has been clearly documented under section 5. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-muhanna-diameter-mip4-performa nce-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-muhanna-diameter-mip4-performance-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-muhanna-diameter-mip4-performance-00.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. ------_=_NextPart_001_01C7BD93.EC46F060 Content-Type: application/octet-stream; name="ATT2461726.TXT" Content-Transfer-Encoding: base64 Content-Description: ATT2461726.TXT Content-Disposition: attachment; filename="ATT2461726.TXT" Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNy03LTMwOTIyMzMuSS1EQGlldGYub3JnPg0KDQpFTkNP RElORyBtaW1lDQpGSUxFIC9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbXVoYW5uYS1kaWFtZXRlci1t aXA0LXBlcmZvcm1hbmNlLTAwLnR4dA0K ------_=_NextPart_001_01C7BD93.EC46F060 Content-Type: application/octet-stream; name="draft-muhanna-diameter-mip4-performance-00.URL" Content-Transfer-Encoding: base64 Content-Description: draft-muhanna-diameter-mip4-performance-00.URL Content-Disposition: attachment; filename="draft-muhanna-diameter-mip4-performance-00.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1tdWhhbm5hLWRpYW1ldGVyLW1pcDQtcGVyZm9ybWFuY2UtMDAudHh0DQo= ------_=_NextPart_001_01C7BD93.EC46F060 Content-Type: text/plain; name="ATT2461727.txt" Content-Transfer-Encoding: base64 Content-Description: ATT2461727.txt Content-Disposition: attachment; filename="ATT2461727.txt" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C7BD93.EC46F060 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_01C7BD93.EC46F060-- From mip4-bounces@ietf.org Tue Jul 03 13:36:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5mIN-0002GW-5Q; Tue, 03 Jul 2007 13:36:11 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I5mII-0001t8-Os for mip4-confirm+ok@megatron.ietf.org; Tue, 03 Jul 2007 13:36:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5mG1-00062A-VS; Tue, 03 Jul 2007 13:33:46 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5m6Y-0003fs-7w; Tue, 03 Jul 2007 13:24:30 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id D63B4328FA; Tue, 3 Jul 2007 15:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I5k5l-0007O4-Op; Tue, 03 Jul 2007 11:15:01 -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: Tue, 03 Jul 2007 11:15:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-generic-notification-message-01.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-01.txt Pages : 24 Date : 2007-7-3 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-01.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-01.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-01.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-7-3100916.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-generic-notification-message-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-generic-notification-message-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-3100916.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 Jul 05 04:15: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 1I6MUi-0002yl-Dq; Thu, 05 Jul 2007 04:15:20 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I6MUh-0002uJ-LF for mip4-confirm+ok@megatron.ietf.org; Thu, 05 Jul 2007 04:15:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6MUh-0002tB-4n for mip4@ietf.org; Thu, 05 Jul 2007 04:15:19 -0400 Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6MUd-00041S-G6 for mip4@ietf.org; Thu, 05 Jul 2007 04:15:19 -0400 Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.160]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l658FDIb023923 for ; Thu, 5 Jul 2007 17:15:13 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l658FDZ28919 for mip4@ietf.org; Thu, 5 Jul 2007 17:15:13 +0900 (JST) Received: from kuichi.jp.nec.com (kuichi.jp.nec.com [10.26.220.17]) by mailsv.nec.co.jp (8.11.7/3.7W-MAILSV-NEC) with ESMTP id l658FDB24179 for ; Thu, 5 Jul 2007 17:15:13 +0900 (JST) Received: from atenza ([10.56.131.18] [10.56.131.18]) by mail.jp.nec.com with ESMTP; Thu, 5 Jul 2007 17:15:13 +0900 To: mip4@ietf.org Message-Id: <20070705171747j-awano@mail.jp.nec.com> Mime-Version: 1.0 X-Mailer: WeMail32[2.51] ID:1D0034 From: j-awano@az.jp.nec.com Date: Thu, 5 Jul 2007 17:17:47 +0900 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.2 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Subject: [Mip4] flag bit conflict in Mobility Agent Advertisement Extension 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 Each RFC3543 "Registration Revocation in Mobile IPv4" and RFC4857 "Mobile IPv4 Regional Registration" defines a new flag for Mobility Agent Advertisement Extension. These are X bit and I bit, respectively. But these bits is the same position in Mobility Agent Advertisement Extension! In this case, what should we do? I'm not sure but I guess RFC3543 is more frequently used than RFC4857. (e.g. WiMAX forum refers to RFC3543.) So, I wish RFC3543 could keep the position of X bit. I hope this decision which RFC to be changed is made as soon as possible. ---------------------------------------------------------------------------- RFC3543 "Registration Revocation in Mobile IPv4" 3.1. Advertising Registration Revocation Support Mobility agents can advertise their support of registration revocation with a modification to the Mobility Agent Advertisement extension described in [1]. An 'X' bit is introduced to indicate an agent's support for Registration Revocation. 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 | Sequence Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Registration Lifetime |R|B|H|F|M|G|r|T|U|X| reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | zero or more Care-of Addresses | | ... | X The mobility agent supports Registration Revocation ---------------------------------------------------------------------------- RFC4857 "Mobile IPv4 Regional Registration" 8.1. Regional Registration Flag Regional Registration flag: 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 | Sequence Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Lifetime |R|B|H|F|M|G|r|T|U|I| reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | zero or more Care-of Addresses | | ... | The flag is defined as follows: Type 16 (Mobility Agent Advertisement) I Regional Registration. This domain supports regional registration as specified in this document. ---------------------------------------------------------------------------- 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 Sat Jul 07 09:07: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 1I7A0G-0004o8-PN; Sat, 07 Jul 2007 09:07:12 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I4Mvp-0002AM-CZ for mip4-confirm+ok@megatron.ietf.org; Fri, 29 Jun 2007 16:19:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Mvp-000290-1N; Fri, 29 Jun 2007 16:19:05 -0400 Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4MvS-0002bH-8L; Fri, 29 Jun 2007 16:19:05 -0400 Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 16:18:41 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAB8GhUZAZnmf/2dsb2JhbAA X-IronPort-AV: i="4.16,476,1175486400"; d="scan'208"; a="64043355:sNHT39304278" Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5TKIfxo011734; Fri, 29 Jun 2007 16:18:41 -0400 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TKIf6a001047; Fri, 29 Jun 2007 20:18:41 GMT Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 16:18:41 -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 Date: Fri, 29 Jun 2007 16:18:40 -0400 Message-ID: <8E296595B6471A4689555D5D725EBB2104619B99@xmb-rtp-20a.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egBG+QRQ From: "Bernie Volz \(volz\)" To: "Ralph Droms \(rdroms\)" , , "DHC WG" X-OriginalArrivalTime: 29 Jun 2007 20:18:41.0720 (UTC) FILETIME=[AF924380:01C7BA8A] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2250; t=1183148321; x=1184012321; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20\(volz\)=22=20 |Subject:=20RE=3A=20[dhcwg]=20EXTENDED=3A=20mip4=20and=20dhc=20WG=20joint =20last=20call=20on=20draft-ietf-mip4-gen-ext-03.txt |Sender:=20 |To:=20=22Ralph=20Droms=20\(rdroms\)=22=20, =20,=0A=20=20=20=20=20=20=20=20=22DHC=20WG=22=20; bh=cD3gSgNOpPI5MSFuLXKK6KZDhsz5GPWRSo5l2ntT4w0=; b=MDs9NreN/oS3W8mSeC3SQN8YHn7m78BLf3qaF1pPEuIM0hZrSnLnPkFygslf6p+5vU+URDHZ Sr9IzjV9S/WI7M6avutv4hoyrRCq6hEsqNJP4SaAhRD9QdvoIW4daXfw; Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim2001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 X-Mailman-Approved-At: Sat, 07 Jul 2007 09:07:11 -0400 Cc: Subject: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-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 Ralph, et al: This document only references DHCP and does not alter or extend it, so I see no strong need for wide review by the DHC WG. One suggestion is to add the "Note that DHCP option codes (OpCode) referenced by this document are defined in [RFC2132].", that is in the IANA Considerations, earlier because the IANA Considerations are usually dropped when the RFC is produced. So, this might get lost (and isn't really an IANA Considerations issue anyway). - Bernie -----Original Message----- From: Ralph Droms (rdroms)=20 Sent: Thursday, June 28, 2007 6:18 AM To: mip4@ietf.org; DHC WG Subject: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt There has been no response to this WG last call, so the deadline will be extended to 1700EDT, 07/05/07. =3D=3D=3D=3D=3D This message announces a joint WG last call for the mip4 and dhc WGs on "Mobile IPv4 Extension for Configuration Options Exchange" . The last call will conclude at 1700EDT, Monday, 06/25/07. The dhc WG is asked to review the use of DHCP options in this draft to pass configuration information to a mobile node. Please respond to this joint WG last call. Responses may be sent to either mip4@ietf.org or dhcwg@ietf.org. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. Lack of discussion does not represent positive support. If there is no expression of support for acceptance during the WG last call, the document will not be advanced to the IESG. draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing the host configuration information during Mobile IP registration. One or more Configuration Options Exchange Extensions may be included in the registration message to provide the Mobile Node the configuration parameters needed for network service (e.g. DNS). This draft is available as http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt - Stig Venaas, Ralph Droms dhc WG chairs _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg -- 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 Jul 09 18:43: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 1I81wm-0002ei-Hg; Mon, 09 Jul 2007 18:43:12 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I81wl-0002ed-Iw for mip4-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 18:43:11 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I81wk-0002eQ-QH for mip4@ietf.org; Mon, 09 Jul 2007 18:43:10 -0400 Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I81wX-00048S-By for mip4@ietf.org; Mon, 09 Jul 2007 18:43:10 -0400 Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l69MgQAO020099; Tue, 10 Jul 2007 01:42:34 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Jul 2007 01:42:33 +0300 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 17:42:31 -0500 Received: from [172.18.141.131] ([172.18.141.131]) by daebe101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 17:42:31 -0500 Message-ID: <4692B9D6.2040506@nokia.com> Date: Mon, 09 Jul 2007 15:42:30 -0700 From: "Charles E. Perkins" User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jul 2007 22:42:31.0180 (UTC) FILETIME=[6F42DCC0:01C7C27A] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: ext Vijay Devarapalli Subject: [Mip4] New revision for draft-ietf-mip4-rfc3344bis 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 Hello folks, Many thanks to Vijay Devarapalli. By his efforts, draft-ietf-mip4-rfc3344bis has been converted to XML. I managed to get a revised draft completed and sent to the Internet Drafts folks last night. I did incorporate new text as suggested by Kent Leung, which I will detail shortly in a follow-on message. Regards, Charlie P. -- 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 Jul 09 18:50: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 1I823Q-0007fx-3p; Mon, 09 Jul 2007 18:50:05 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I823O-0007fk-RG for mip4-confirm+ok@megatron.ietf.org; Mon, 09 Jul 2007 18:50:02 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I823O-0007fc-FZ for mip4@ietf.org; Mon, 09 Jul 2007 18:50:02 -0400 Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8238-0004FX-O5 for mip4@ietf.org; Mon, 09 Jul 2007 18:50:02 -0400 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l69Mn7ku004663; Tue, 10 Jul 2007 01:49:35 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Jul 2007 01:49:29 +0300 Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 17:49:19 -0500 Received: from [172.18.141.131] ([172.18.141.131]) by daebe101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Jul 2007 17:49:18 -0500 Message-ID: <4692BB6E.1040502@nokia.com> Date: Mon, 09 Jul 2007 15:49:18 -0700 From: "Charles E. Perkins" User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: "ext Kent Leung (kleung)" Subject: Re: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-03.txt References: <2979E38DD6FC6544B789C8DAD7BAFC52037BC836@xmb-sjc-235.amer.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC52037BC836@xmb-sjc-235.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jul 2007 22:49:18.0838 (UTC) FILETIME=[623E8960:01C7C27B] X-Nokia-AV: Clean X-Spam-Score: 0.0 (/) X-Scan-Signature: 3971661e40967acfc35f708dd5f33760 Cc: mip4@ietf.org, Ahmad Muhanna 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 Hello Kent, I re-read through this old thread. Your concerns seem valid to me, and I have incorporated some text inspired by your suggestion into the new Internet Draft which I sent in last night. I should have responded to this earlier, but it sort of dropped out of sight after your follow-up to Ahmad, and I didn't remember to do anything about it until just this last weekend. Here is what I have revised: In section 3.7.1, I changed the paragraph following the bullets to read: > If there is an NAI extension in the Registration Request message > (often, for example, when the mobile node's Home Address is zero), > 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 such a zero Home Address for the > mobile node, the foreign agent MUST return a Registration Reply with > Code indicating NONZERO_HOMEADDR_REQD (see [2]). In section 3.7.3.1, the second paragraph now reads as follows: > 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 there > are multiple entries with the same home address, and if the > Registration Reply has the Mobile Node NAI extension [2], the foreign > agent MUST use the NAI to disambiguate the pending Registration > Requests with the same home address. If no matching 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 found a mistake in the appendix, which I will fix soon but is not part of any normative text, sigh... Please let me know if you agree with these changes. Since I can now use xml2rfc for document production (thanks, Vijay!) my turnaround time for new revisions will be quite fast. Regards, Charlie P. ext Kent Leung (kleung) wrote: > > 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 > 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) > 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 > > > -- 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 Jul 10 16:15:32 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8M7Q-0006ZX-BI; Tue, 10 Jul 2007 16:15:32 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I8M6y-0005n8-Ee for mip4-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 16:15:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8M6x-0005mv-ON; Tue, 10 Jul 2007 16:15:03 -0400 Received: from ns1.neustar.com ([156.154.16.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8M6w-0008Kx-7X; Tue, 10 Jul 2007 16:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id C2CB426EBA; Tue, 10 Jul 2007 20:15:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I8M6v-0004WE-Ij; Tue, 10 Jul 2007 16:15:01 -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: Tue, 10 Jul 2007 16:15:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-04.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-04.txt Pages : 108 Date : 2007-7-10 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-04.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-04.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-04.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-7-10152546.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-rfc3344bis-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-10152546.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 Jul 11 12:30:39 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8f5L-0002oH-5P; Wed, 11 Jul 2007 12:30:39 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I8f5K-0002o8-Ed for mip4-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 12:30:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8f5K-0002o0-4m for mip4@ietf.org; Wed, 11 Jul 2007 12:30:38 -0400 Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I8f5G-0005mM-QA for mip4@ietf.org; Wed, 11 Jul 2007 12:30:38 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-8.tower-128.messagelabs.com!1184171432!13183184!1 X-StarScan-Version: 5.5.12.11; banners=-,-,- X-Originating-IP: [129.188.136.9] Received: (qmail 8371 invoked from network); 11 Jul 2007 16:30:32 -0000 Received: from ftpbox.mot.com (HELO ftpbox.mot.com) (129.188.136.9) by server-8.tower-128.messagelabs.com with SMTP; 11 Jul 2007 16:30:32 -0000 Received: from az33exr02.mot.com ([10.64.251.232]) by ftpbox.mot.com (8.12.11/Motorola) with ESMTP id l6BGUWF9002169 for ; Wed, 11 Jul 2007 11:30:32 -0500 (CDT) Received: from az10vts04 (az10vts04.mot.com [10.64.251.245]) by az33exr02.mot.com (8.13.1/Vontu) with SMTP id l6BGUV7f008818 for ; Wed, 11 Jul 2007 11:30:31 -0500 (CDT) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id l6BGUTBV008783 for ; Wed, 11 Jul 2007 11:30: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 Date: Wed, 11 Jul 2007 12:30:27 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Meeting Agenda Thread-Index: AcfD2MpVi6xMoBPfS6mQgiIFnTpTng== From: "McCann Peter-A001034" To: X-Vontu: Pass X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Subject: [Mip4] Meeting Agenda 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 mip4 working group will be meeting for 1 hour in Chicago, on Wednesday July 25 from 1510 to 1610. Please send any requests for agenda time to me and Henrik as soon as possible. -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 Jul 11 15:37: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 1I8hzo-0002yI-Kq; Wed, 11 Jul 2007 15:37:08 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I8hzm-0002xY-MT for mip4-confirm+ok@megatron.ietf.org; Wed, 11 Jul 2007 15:37:06 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8hzm-0002xA-40; Wed, 11 Jul 2007 15:37:06 -0400 Received: from mx0.starentnetworks.com ([12.38.223.203]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8hzl-0006dw-Or; Wed, 11 Jul 2007 15:37:06 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by mx0.starentnetworks.com (Postfix) with ESMTP id 2340790020; Wed, 11 Jul 2007 15:35:53 -0400 (EDT) Received: from mx0.starentnetworks.com ([127.0.0.1]) by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28908-12; Wed, 11 Jul 2007 15:35:49 -0400 (EDT) Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com [10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP; Wed, 11 Jul 2007 15:35:49 -0400 (EDT) Received: from exchtewks2.starentnetworks.com ([10.2.4.27]) by exchtewks1.starentnetworks.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Jul 2007 15:36:04 -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] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call ondraft-ietf-mip4-gen-ext-03.txt Date: Wed, 11 Jul 2007 15:35:30 -0400 Message-ID: <7CCD07160348804497EF29E9EA5560D7024DA2B4@exchtewks2.starentnetworks.com> In-Reply-To: <8E296595B6471A4689555D5D725EBB2104619B99@xmb-rtp-20a.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call ondraft-ietf-mip4-gen-ext-03.txt Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egBG+QRQAlo3tcA= From: "Chowdhury, Kuntal" To: "Bernie Volz (volz)" , "Ralph Droms (rdroms)" , , "DHC WG" X-OriginalArrivalTime: 11 Jul 2007 19:36:04.0616 (UTC) FILETIME=[B8602880:01C7C3F2] X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc 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 Bernie, Thanks for the review. I think your suggestion to add the note is good for clarification purpose. So, I see no issue adding such note in the document. BR, Kuntal > -----Original Message----- > From: Bernie Volz (volz) [mailto:volz@cisco.com] > Sent: Friday, June 29, 2007 3:19 PM > To: Ralph Droms (rdroms); mip4@ietf.org; DHC WG > Subject: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call > ondraft-ietf-mip4-gen-ext-03.txt >=20 > Ralph, et al: >=20 > This document only references DHCP and does not alter or extend it, so I > see no strong need for wide review by the DHC WG. >=20 > One suggestion is to add the "Note that DHCP option codes (OpCode) > referenced by this document are defined in [RFC2132].", that is in the > IANA Considerations, earlier because the IANA Considerations are usually > dropped when the RFC is produced. So, this might get lost (and isn't > really an IANA Considerations issue anyway). >=20 > - Bernie >=20 > -----Original Message----- > From: Ralph Droms (rdroms) > Sent: Thursday, June 28, 2007 6:18 AM > To: mip4@ietf.org; DHC WG > Subject: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on > draft-ietf-mip4-gen-ext-03.txt >=20 > There has been no response to this WG last call, so the deadline will be > extended to 1700EDT, 07/05/07. >=20 > =3D=3D=3D=3D=3D > This message announces a joint WG last call for the mip4 and dhc WGs > on "Mobile IPv4 Extension for Configuration Options Exchange" > . The last call will conclude at > 1700EDT, Monday, 06/25/07. >=20 > The dhc WG is asked to review the use of DHCP options in this draft to > pass configuration information to a mobile node. >=20 > Please respond to this joint WG last call. Responses may be sent to > either mip4@ietf.org or dhcwg@ietf.org. If you support acceptance of > the document without change, respond with a simple acknowledgment, so > that support for the document can be assessed. Lack of discussion > does not represent positive support. If there is no expression of > support for acceptance during the WG last call, the document will not > be advanced to the IESG. >=20 > draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing > the host configuration information during Mobile IP registration. One > or more Configuration Options Exchange Extensions may be included in > the registration message to provide the Mobile Node the configuration > parameters needed for network service (e.g. DNS). This draft is > available as > http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt >=20 > - Stig Venaas, Ralph Droms > dhc WG chairs >=20 >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=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 Jul 12 15:15: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 1I948r-0000D7-6T; Thu, 12 Jul 2007 15:15:57 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1I948n-00008E-03 for mip4-confirm+ok@megatron.ietf.org; Thu, 12 Jul 2007 15:15:53 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I948m-000086-LI; Thu, 12 Jul 2007 15:15:52 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I948m-0004ch-DZ; Thu, 12 Jul 2007 15:15:52 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 3F8962AC79; Thu, 12 Jul 2007 19:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1I947x-0005xo-Vb; Thu, 12 Jul 2007 15:15:01 -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, 12 Jul 2007 15:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-rfc3344bis-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 : IP Mobility Support for IPv4, revised Author(s) : C. Perkins Filename : draft-ietf-mip4-rfc3344bis-05.txt Pages : 108 Date : 2007-7-12 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-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-rfc3344bis-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-rfc3344bis-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-7-12145155.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-rfc3344bis-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-rfc3344bis-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-12145155.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 Sun Jul 15 11:16: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 1IA5pa-0002Np-Ll; Sun, 15 Jul 2007 11:16:18 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IA5pZ-0002Ni-DU for mip4-confirm+ok@megatron.ietf.org; Sun, 15 Jul 2007 11:16:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IA5pZ-0002NZ-2F for mip4@ietf.org; Sun, 15 Jul 2007 11:16:17 -0400 Received: from gair.firstpr.com.au ([150.101.162.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IA5pT-0005LO-LP for mip4@ietf.org; Sun, 15 Jul 2007 11:16:16 -0400 Received: from [10.0.0.8] (zita.firstpr.com.au [10.0.0.8]) by gair.firstpr.com.au (Postfix) with ESMTP id 1D12159DA1; Mon, 16 Jul 2007 01:16:10 +1000 (EST) Message-ID: <469A3A2C.5050406@firstpr.com.au> Date: Mon, 16 Jul 2007 01:15:56 +1000 From: Robin Whittle Organization: First Principles User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 Subject: [Mip4] LISP or Ivip for IPv4/6 mobility support 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 am not directly involved with Mobile IP, but am working on a new routing and addressing architecture for the Internet, as are other people on the RAM list: http://www1.ietf.org/mailman/listinfo/ram in response to the IAB RAWS report: http://www.iab.org/about/workshops/routingandaddressing/ http://tools.ietf.org/html/draft-iab-raws-report A proposal called LISP (Locator/ID Separation Protocol): http://tools.ietf.org/html/draft-farinacci-lisp http://tools.ietf.org/html/draft-lear-lisp-nerd http://tools.ietf.org/html/draft-meyer-lisp-cons involves a global system of Ingress Tunnel Routers (ITRs) which intercept packets addressed to certain prefixes and tunnel them to one of many Egress Tunnel Routers (ETRs). The mapping between the original address (EID) and the tunnel endpoint (RLOC) is controlled, in one way or another, by a centralised or distributed database - in principle down to single IP address granularity for IPv4, and maybe /64 for IPv6. I have my own proposal - Ivip (Internet Vastly Improved Plumbing) which is based on some of LISP's principles. http://www.firstpr.com.au/ip/ivip/ An I-D draft-whittle-ivip-arch-00 is available there and should appear in the IETF system soon. I think Ivip is more incrementally deployable than LISP, because Ivip ITRs can be outside provider and AS-end-user networks, using anycast to attract packets which are addressed to Ivip-mapped addresses, without there needing to be an ITR in every such network (as with LISP) in order for hosts in those networks to be able to send packets to hosts with LISP/Ivip-mapped addresses. The current state of discussions on the RAM list indicates that the most likely solution to the problems with routing and addressing will be something like LISP or Ivip. Once such a system of ITRs exists, if it could be controlled rapidly (which it needs to be to fulfil its primary mission of supporting multihomed end-user networks without involving traditional PI address space or BGP), then this is a mighty powerful tool for directing packets sent by Correpsondent Hosts (CHs) towards what I call "Translating Tunnel Routers" (TTRs). Consider thousands of TTRs all around the Net, inside and outside provider and AS-end-user networks. Mobile Nodes (MNs - which have their own care-of-address in each network they connect to) find a topologically nearby TTR and create a two-way tunnel to it. If the MN has two network connections (eg. UMTS and WiFi), it can find two different TTRs, probably in each network, but also perhaps nearby but not associated with these networks. Then it can build two tunnels to these two TTRs. Now consider each TTR to be somewhat like a home-agent with a 2-way tunnel from the MN. However, the MN can (probably with help from a centralised monitoring system) change the LISP/Ivip mapping database to make all the ITRs tunnel packets to one TTR or another. The TTR decapsulates the packets from the tunnel it entered at any one of these ITRs around the Net. It then tunnels the packet to the MN. Packets from the MN are sent out one link or the other, where the TTR at the end of that 2-way tunnel forwards them to the rest of the Net. The MN has its own LISP/Ivip-mapped IP address - completely unrelated to the addresses of these ITRs or TTRs. This means it can make multiple connections via various networks as it moves around the world, directing the LISP/Ivip system to beam packets to whichever TTR is best at the time. The MN can maintain sessions on its Ivip-mapped IP address. ................ ............ . N1 . . N2 . . . . . . CN1----ITR1~~~~~BR~~~TR~~~BR~~~~~TTR1===PE==\ . . \ . . = ................ | ............ = | = | = | MN1 ......... | ........... = . N4 . / . N3 . = . ./ . . = . TTR2==BR======BR==========PE==/ . . . . ......... ........... ~~~~ 1-way Ivip tunnel ==== 2-way tunnel established by Mobile Node to TTR Figure 10: Mobile IP with two TTRs. >From TTRs and Mobility: http://www.firstpr.com.au/ip/ivip/draft-whittle-ivip-arch-00.html#anchor81 The paths taken by the packets are generally highly optimal, since they flow from the CH to a nearby ITR (which is probably in the shortest path anyway) and then to the TTR which is close to the MN. Packets in the reverse direction come out of the MN and go via ordinary BGP routing to the CH - unless the CH has a LISP/Ivip-mapped address, in which case they go via an ITR near the TTR (or integrated into the TTR) and then an ETR near the CH. All this should work fine for unmodified CHs. The MH needs special software, of course. This should work for both IPv4 and IPv6. - Robin -- 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 Jul 16 00:11: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 1IAHvX-0007Dm-IZ; Mon, 16 Jul 2007 00:11:15 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IAHvU-00077g-El for mip4-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 00:11:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAHvU-00077S-2o for mip4@ietf.org; Mon, 16 Jul 2007 00:11:12 -0400 Received: from cassius.ee.usyd.edu.au ([129.78.13.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAHvQ-0005X8-BM for mip4@ietf.org; Mon, 16 Jul 2007 00:11:12 -0400 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 l6G4A4wm007420 for ; Mon, 16 Jul 2007 14:10:05 +1000 (EST) From: Guo Qiang Mao Received: from 203.143.170.222 (SquirrelMail authenticated user guoqiang) by www.ee.usyd.edu.au with HTTP; Mon, 16 Jul 2007 14:10:05 +1000 (EST) Message-ID: <4221.203.143.170.222.1184559005.squirrel@www.ee.usyd.edu.au> Date: Mon, 16 Jul 2007 14:10:05 +1000 (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 l6G4A4wm007420 X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Subject: [Mip4] Call for Chapters on Localization in Wireless Sensor Networks 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 apologizes if you receive multiple copies of this CFC] [CFP] Call for Chapters on Localization in Wireless Sensor Networks Book Title: Localization Algorithms and Strategies for Wireless Sensor Networks: Monitoring and Surveillance Techniques for Target Tracking Book webpage: http://www.ee.usyd.edu.au/~guoqiang/Research/BookOnLocalizationAlgorithms= .htm Editors: Guoqiang Mao and Baris Fidan Publishing Details: This book will be published by IGI Global http://www.igi-pub.com/ in 2008. Introduction Wireless sensor networks (WSNs) constitute a significant technology of today, attracting considerable research interest from various disciplines. Self-localization capability is a highly desirable characteristic of wireless sensor networks. In environmental monitoring applications such a= s bush fire surveillance, water quality monitoring and precision agriculture, the measurement data are meaningless without knowing the location from where the data are obtained. Moreover, location estimation may enable a myriad of applications such as inventory management, intrusion detection, road traffic monitoring, health monitoring, reconnaissance and surveillance. This book intends to cover the fundamental theories, the state-of-the-art research findings, and experimental studies and applications of WSN localization techniques. We expect the book to serve as a valuable and comprehensive reference for students, educators, researchers, and engineers who work in this rapidly evolving field. Recommended topics (not limited to) =95 Measurements techniques used in WSN localization =95 WSN localization algorithms =95 Fundamental theories in WSN localization =95 Graph theoretical analysis of characteristics of WSNs and application= of such analysis to WSN localization =95 Monitoring and surveillance techniques =95 Experimental studies =95 Applications of WSN localization techniques Invitation Prospective chapter authors are invited to submit, initially, a 1-2 page single column, single space proposal describing the proposed chapter in M= S Word or RTF format. The proposal should include the title, the abstract, the chapter organization, number of pages of the final manuscript intende= d to be submitted and contact authors. Each chapter is planned to fit 15-25 letter-size pages (single column, single space, 12 pt font). However, (only) fundamental chapter proposals of comprehensive review/survey style will be allowed to be up to 40 pages. Chapter templates will be provided once the proposals are submitted and acceptance decisions are made. Important Dates =95 Submission of Chapter Proposals: September 15, 2007 =95 Notification of Proposal Acceptance: October 15, 2007 =95 Full Chapter Submission: March 15, 2008 =95 Review Reports Due: May 15, 2008 =95 Final Version Submission: July 15, 2008 Contact =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D Please make correspondence and proposal submissions to: Dr Guoqiang Mao School of Electrical and Information Engineering The University of Sydney NSW 2006, Australia Email: guoqiang@ee.usyd.edu.au Dr Baris Fidan National ICT Australia Locked Bag 8001 Canberra ACT 2601, Australia Email: baris.fidan@nicta.com.au -- 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 Jul 16 17:13: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 1IAXsX-0005DV-99; Mon, 16 Jul 2007 17:13:13 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IAXsW-0005DP-7u for mip4-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 17:13:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAXsV-0005DH-BW for mip4@ietf.org; Mon, 16 Jul 2007 17:13:11 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAXsT-0002U6-J0 for mip4@ietf.org; Mon, 16 Jul 2007 17:13:11 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IAXry-0004cQ-VX; Mon, 16 Jul 2007 23:12:39 +0200 Message-ID: <469BDF3C.40609@levkowetz.com> Date: Mon, 16 Jul 2007 23:12:28 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Mobile IPv4 Mailing List X-Enigmail-Version: 0.95.2 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 merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] MIP4 agenda for IETF 69, 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="===============1386404271==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1386404271== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF89D8A13827B79B1337CC993" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF89D8A13827B79B1337CC993 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-69 in Chicago. 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, July 25, 2007 1510-1610 Afternoon Session II Adams =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 WG Documents: draft-ietf-mip4-dsmipv4 Active draft-ietf-mip4-generic-notification-message Active draft-ietf-mip4-nemo-v4-base Active draft-ietf-mip4-nemov4-dynamic Active draft-ietf-mip4-nemov4-fa Active draft-ietf-mip4-rfc2006bis Active draft-ietf-mip4-rfc3344bis Active draft-ietf-mip4-udptunnel-mib Active draft-ietf-mip4-vpn-problem-solution Waiting for writeup IESG Processing: draft-ietf-mip4-gen-ext AD Evaluation - Waiting on last call results from DHC WG draft-ietf-mip4-mobike-connectivity IESG Evaluation draft-ietf-mip4-radius-requirements IESG Evaluation - Discuss received, waiting on new document RFC-Editor's Queue: draft-ietf-mip4-fmipv4 RFC Ed Queue Published since IETF 68: draft-ietf-mip4-message-string-ext RFC 4917=09 draft-ietf-mip4-reg-tunnel RFC 4857=09 draft-ietf-mobileip-lowlatency-handoffs-v4 RFC 4881 3. Mobile IPv4, Revised 5 min Charles Perkin= s draft-ietf-mip4-3344bis 4. Proxy Mobile IPv4 10 min Kent Leung draft-leung-mip4-proxy-mode 5. Mobike Optimizations 10 min Vijay Devarapa= lli draft-meghana-mip4-mobike-optimizations 6. Diameter MIP4 Performance 5 min Ahmad Muhanna draft-muhanna-diameter-mip4-performance =3D=3D=3D=3D=3D =3D=3D=3D=3D= =3D=3D Total 55 min --------------enigF89D8A13827B79B1337CC993 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGm99EeVhrtTJkXCMRAiD+AJ0X5wK7UZP3ZyFj1g9r8AQfeIFltwCdHYWr 8TVy5lHebDIinV2Ezas0sjE= =Gr12 -----END PGP SIGNATURE----- --------------enigF89D8A13827B79B1337CC993-- --===============1386404271== 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/ --===============1386404271==-- From mip4-bounces@ietf.org Mon Jul 16 17:31:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAYA2-00067K-Uz; Mon, 16 Jul 2007 17:31:18 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IAYA2-000674-9z for mip4-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 17:31:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAYA1-00066l-6c for mip4@ietf.org; Mon, 16 Jul 2007 17:31:17 -0400 Received: from smtp2.song.fi ([194.100.2.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAY9w-00038W-SP for mip4@ietf.org; Mon, 16 Jul 2007 17:31:17 -0400 Received: from [84.240.69.182] (84-240-69-182.dsl.maxinetti.fi [84.240.69.182]) by smtp2.song.fi (Postfix) with ESMTP id 525844F4C6D; Tue, 17 Jul 2007 00:31:11 +0300 (EEST) Message-ID: <469BE39E.3010908@iki.fi> Date: Tue, 17 Jul 2007 00:31:10 +0300 From: Sami Vaarala User-Agent: Icedove 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: Henrik Levkowetz Subject: Re: [Mip4] MIP4 agenda for IETF 69, first draft References: <469BDF3C.40609@levkowetz.com> In-Reply-To: <469BDF3C.40609@levkowetz.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: mip4-chairs@tools.ietf.org, 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 Hi, Henrik Levkowetz wrote: > draft-ietf-mip4-vpn-problem-solution Waiting for writeup The (expired) -02 draft has incorporated feedback from Vijay, including a rewrite of the latency considerations section which was seen to be too complex. Apart from that I'm not aware of any open (technical) issues. If this is indeed the case, what are the writeup needs to version -02 before the draft can proceed forwards? BR, -Sami -- 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 Jul 16 18:15:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAYr9-0001Gu-Mq; Mon, 16 Jul 2007 18:15:51 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IAYr8-0001Gp-JB for mip4-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 18:15:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAYr8-0001Gh-9Y for mip4@ietf.org; Mon, 16 Jul 2007 18:15:50 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAYr6-0004I4-T2 for mip4@ietf.org; Mon, 16 Jul 2007 18:15:50 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IAYqa-00080A-U8; Tue, 17 Jul 2007 00:15:17 +0200 Message-ID: <469BEDF4.4020309@levkowetz.com> Date: Tue, 17 Jul 2007 00:15:16 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Sami Vaarala Subject: Re: [Mip4] MIP4 agenda for IETF 69, first draft References: <469BDF3C.40609@levkowetz.com> <469BE39E.3010908@iki.fi> In-Reply-To: <469BE39E.3010908@iki.fi> X-Enigmail-Version: 0.95.2 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: sami.vaarala@iki.fi, 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 merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: mip4-chairs@tools.ietf.org, 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="===============2115278064==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============2115278064== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4E23BA6EDCFEFA9E182055D4" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4E23BA6EDCFEFA9E182055D4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Sami, On 2007-07-16 23:31 Sami Vaarala said the following: > Hi, >=20 > Henrik Levkowetz wrote: >> draft-ietf-mip4-vpn-problem-solution Waiting for writeu= p >=20 > The (expired) -02 draft has incorporated feedback from Vijay, including= a > rewrite of the latency considerations section which was seen to be too > complex. Apart from that I'm not aware of any open (technical) issues.= >=20 > If this is indeed the case, what are the writeup needs to version -02 b= efore > the draft can proceed forwards? The writeup is the shepherding writeup needed for the submission for publication, and I'm responsible for not getting around to completing it, due to a very urgent and important project I've had to deal with. However, that's completed now, and I'm working on handling my backlog now, and getting back to completing this. Sorry for the delay. Henrik --------------enig4E23BA6EDCFEFA9E182055D4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGm+30eVhrtTJkXCMRApZaAJ95aIApyCrZPlu8YAZGpetWhvsPRQCgtnGX 8NQq6C6InHxTxaQEEKiv7hg= =9l4Z -----END PGP SIGNATURE----- --------------enig4E23BA6EDCFEFA9E182055D4-- --===============2115278064== 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/ --===============2115278064==-- From mip4-bounces@ietf.org Mon Jul 16 18:43:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAZID-0006rf-98; Mon, 16 Jul 2007 18:43:49 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IAZIC-0006ra-Ch for mip4-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 18:43:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAZIC-0006rS-2x for mip4@ietf.org; Mon, 16 Jul 2007 18:43:48 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAZIB-00057I-A6 for mip4@ietf.org; Mon, 16 Jul 2007 18:43:48 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IAZHj-0006Hq-PS; Tue, 17 Jul 2007 00:43:19 +0200 Message-ID: <469BF483.8000809@levkowetz.com> Date: Tue, 17 Jul 2007 00:43:15 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Mobile IPv4 Mailing List X-Enigmail-Version: 0.95.2 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 merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -2.8 (--) X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243 Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] MIP4 agenda for IETF 69, 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="===============2001883230==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============2001883230== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF598CC995CEC3927A1881935" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF598CC995CEC3927A1881935 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Below is the second draft of the agenda for the MIP4 working group meetin= g during IETF-69 in Chicago. The 60-minute meeting time is now filled, but if there are more requests for presentation slots we may try to see if some of the current 10-minute= slots can be reduced. Don't refrain from requesting slots if you feel you have something that needs presenting. 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=3D=3D=3D=3D= =3D=3D WEDNESDAY, July 25, 2007 1510-1610 Afternoon Session II Adams =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D [This is agenda rev -01, 17 Jul 2007 0:34:37] 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 WG Documents: draft-ietf-mip4-dsmipv4 Active draft-ietf-mip4-generic-notification-message Active draft-ietf-mip4-nemo-v4-base Active draft-ietf-mip4-nemov4-dynamic Active draft-ietf-mip4-nemov4-fa Active draft-ietf-mip4-rfc2006bis Active draft-ietf-mip4-rfc3344bis Active draft-ietf-mip4-udptunnel-mib Active draft-ietf-mip4-vpn-problem-solution Waiting for writeup IESG Processing: draft-ietf-mip4-gen-ext AD Evaluation - Waiting on last call results from DHC WG draft-ietf-mip4-mobike-connectivity IESG Evaluation draft-ietf-mip4-radius-requirements IESG Evaluation - Discuss received, waiting on new document RFC-Editor's Queue: draft-ietf-mip4-fmipv4 RFC Ed Queue Published since IETF 68: draft-ietf-mip4-message-string-ext RFC 4917=09 draft-ietf-mip4-reg-tunnel RFC 4857=09 draft-ietf-mobileip-lowlatency-handoffs-v4 RFC 4881 3. Mobile IPv4, Revised 5 min Charles Perkins draft-ietf-mip4-3344bis 4. Proxy Mobile IPv4 10 min Kent Leung draft-leung-mip4-proxy-mode 5. Mobike Optimizations 10 min Vijay Devarapalli draft-meghana-mip4-mobike-optimizations 6. Diameter MIP4 Performance 5 min Ahmad Muhanna draft-muhanna-diameter-mip4-performance 7. Selective use of encapsulated delivery style 5 min Samita Chakrabart= i draft-chakrabarti-mip4-mcbc =3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D Total 60 min --------------enigF598CC995CEC3927A1881935 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGm/SDeVhrtTJkXCMRAhvYAJ4qElblb6tefxLzrfIiE2TJgiZL7QCeJMGv FodR4aGKrgnN8i6RX7N8TYM= =0LF3 -----END PGP SIGNATURE----- --------------enigF598CC995CEC3927A1881935-- --===============2001883230== 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/ --===============2001883230==-- From mip4-bounces@ietf.org Thu Jul 19 06:31:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBTIZ-0006p8-19; Thu, 19 Jul 2007 06:31:55 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IBTIX-0006oN-Kn for mip4-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 06:31:53 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBTIX-0006mF-5m for mip4@ietf.org; Thu, 19 Jul 2007 06:31:53 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBTIW-0002xc-Jq for mip4@ietf.org; Thu, 19 Jul 2007 06:31:53 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l6JAVo2I030869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 19 Jul 2007 03:31:50 -0700 Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com [172.30.32.65]) by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l6JAVnsY001263; Thu, 19 Jul 2007 03:31:49 -0700 Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 19 Jul 2007 03:31:41 -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] MIP4 agenda for IETF 69, second draft Date: Thu, 19 Jul 2007 03:31:47 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF47A84B9@NAEX16.na.qualcomm.com> In-Reply-To: <469BF483.8000809@levkowetz.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] MIP4 agenda for IETF 69, second draft Thread-Index: AcfH/pIJyIl7cqa7SLmMlEv3vRyu3gB8V3vw References: <469BF483.8000809@levkowetz.com> From: "Tsirtsis, George" To: "Henrik Levkowetz" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 19 Jul 2007 10:31:41.0987 (UTC) FILETIME=[FF3C7F30:01C7C9EF] X-Spam-Score: 0.0 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 Cc: mip4-chairs@tools.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 Sorry for the late note on this but I can provide a 2-3min update on DSMIPv4 draft which is in WG last call. Thanks George -----Original Message----- From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20 Sent: Monday, July 16, 2007 11:43 PM To: Mobile IPv4 Mailing List Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] MIP4 agenda for IETF 69, second draft Hi, Below is the second draft of the agenda for the MIP4 working group meeting during IETF-69 in Chicago. The 60-minute meeting time is now filled, but if there are more requests for presentation slots we may try to see if some of the current 10-minute slots can be reduced. Don't refrain from requesting slots if you feel you have something that needs presenting. 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=3D =3D=3D=3D=3D=3D WEDNESDAY, July 25, 2007 1510-1610 Afternoon Session II Adams =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D [This is agenda rev -01, 17 Jul 2007 0:34:37] 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 WG Documents: draft-ietf-mip4-dsmipv4 Active draft-ietf-mip4-generic-notification-message Active draft-ietf-mip4-nemo-v4-base Active draft-ietf-mip4-nemov4-dynamic Active draft-ietf-mip4-nemov4-fa Active draft-ietf-mip4-rfc2006bis Active draft-ietf-mip4-rfc3344bis Active draft-ietf-mip4-udptunnel-mib Active draft-ietf-mip4-vpn-problem-solution Waiting for writeup IESG Processing: draft-ietf-mip4-gen-ext AD Evaluation - Waiting on last call results from DHC WG draft-ietf-mip4-mobike-connectivity IESG Evaluation draft-ietf-mip4-radius-requirements IESG Evaluation - Discuss received, waiting on new document RFC-Editor's Queue: draft-ietf-mip4-fmipv4 RFC Ed Queue Published since IETF 68: draft-ietf-mip4-message-string-ext RFC 4917=09 draft-ietf-mip4-reg-tunnel RFC 4857=09 draft-ietf-mobileip-lowlatency-handoffs-v4 RFC 4881 3. Mobile IPv4, Revised 5 min Charles Perkins draft-ietf-mip4-3344bis 4. Proxy Mobile IPv4 10 min Kent Leung draft-leung-mip4-proxy-mode 5. Mobike Optimizations 10 min Vijay Devarapalli draft-meghana-mip4-mobike-optimizations 6. Diameter MIP4 Performance 5 min Ahmad Muhanna draft-muhanna-diameter-mip4-performance 7. Selective use of encapsulated delivery style 5 min Samita Chakrabarti draft-chakrabarti-mip4-mcbc =3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D Total 60 min -- 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 Jul 19 11:47: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 1IBYEM-0006yE-E7; Thu, 19 Jul 2007 11:47:54 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IBYEL-0006y6-DE for mip4-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 11:47:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBYEL-0006xx-3L for mip4@ietf.org; Thu, 19 Jul 2007 11:47:53 -0400 Received: from smail5.alcatel.fr ([62.23.212.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBYEK-0002Ae-Gm for mip4@ietf.org; Thu, 19 Jul 2007 11:47:53 -0400 Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com [155.132.6.79]) by smail5.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6JFjvbW005301 for ; Thu, 19 Jul 2007 17:45:57 +0200 Received: from [172.27.205.222] ([172.27.205.222]) by FRVELSBHS07.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Thu, 19 Jul 2007 17:47:51 +0200 Message-ID: <469F87A6.6020003@alcatel-lucent.fr> Date: Thu, 19 Jul 2007 17:47:50 +0200 From: Bruno Mongazon-Cazavet User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Mobile IPv4 Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Jul 2007 15:47:51.0374 (UTC) FILETIME=[29DF3EE0:01C7CA1C] X-Scanned-By: MIMEDefang 2.51 on 155.132.188.13 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [Mip4] Question about draft-leung-mip4-proxy-mode 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 Hello, When a router implements this draft, how should it reacts to Router Solicitation? In particular: -should the router fill the Mobility Agent Advertisement extension in the reply? -should the FA capability be set if only PMIP is supported? Thanks, Bruno. -- 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 Jul 19 16:02: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 1IBcCQ-0000mk-F1; Thu, 19 Jul 2007 16:02:10 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IBcCP-0000lA-3k for mip4-confirm+ok@megatron.ietf.org; Thu, 19 Jul 2007 16:02:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IBcCO-0000l2-Pl for mip4@ietf.org; Thu, 19 Jul 2007 16:02:08 -0400 Received: from [2001:698:9:31:214:22ff:fe21:bb] (helo=merlot.tools.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBcCN-0000kR-U7 for mip4@ietf.org; Thu, 19 Jul 2007 16:02:08 -0400 Received: from localhost ([127.0.0.1] helo=marsanne.levkowetz.com ident=henrik) by merlot.tools.ietf.org with esmtp (Exim 4.67) (envelope-from ) id 1IBcBt-00014v-Rv; Thu, 19 Jul 2007 22:01:37 +0200 Message-ID: <469FC320.6090803@levkowetz.com> Date: Thu, 19 Jul 2007 22:01:36 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Mobile IPv4 Mailing List X-Enigmail-Version: 0.95.2 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 merlot.tools.ietf.org); SAEximRunCond expanded to false X-Spam-Score: -1.4 (-) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: mip4-chairs@tools.ietf.org Subject: [Mip4] MIP4 agenda for IETF 69, third 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="===============1261567779==" Errors-To: mip4-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1261567779== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFCDEFFF2406739B370A1BDCF" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFCDEFFF2406739B370A1BDCF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Below is the third draft of the agenda for the MIP4 working group meeting= during IETF-69 in Chicago. Let us know if any further adjustments are needed. 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, July 25, 2007 1510-1610 Afternoon Session II Adams =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 WG Documents: draft-ietf-mip4-dsmipv4 Last Call Done draft-ietf-mip4-generic-notification-message Active draft-ietf-mip4-nemo-v4-base Active draft-ietf-mip4-nemov4-dynamic Active draft-ietf-mip4-nemov4-fa Active draft-ietf-mip4-rfc2006bis Active draft-ietf-mip4-rfc3344bis Active draft-ietf-mip4-udptunnel-mib Active draft-ietf-mip4-vpn-problem-solution Waiting for writeup IESG Processing: draft-ietf-mip4-gen-ext AD Evaluation - Waiting on last call results from DHC WG draft-ietf-mip4-mobike-connectivity IESG Evaluation draft-ietf-mip4-radius-requirements IESG Evaluation - Discuss received, waiting on new document RFC-Editor's Queue: draft-ietf-mip4-fmipv4 RFC Ed Queue Published since IETF 68: draft-ietf-mip4-message-string-ext RFC 4917=09 draft-ietf-mip4-reg-tunnel RFC 4857=09 draft-ietf-mobileip-lowlatency-handoffs-v4 RFC 4881 3. Mobile IPv4, Revised 5 min Charles Perkins draft-ietf-mip4-3344bis 4. Proxy Mobile IPv4 10 min Kent Leung draft-leung-mip4-proxy-mode 5. Mobike Optimizations 5 min Vijay Devarapalli draft-meghana-mip4-mobike-optimizations 6. Diameter MIP4 Performance 5 min Ahmad Muhanna draft-muhanna-diameter-mip4-performance 7. Selective use of encapsulated delivery style 5 min Samita Chakrabart= i draft-chakrabarti-mip4-mcbc 8. Dual Stack MIPv4 draft-ietf-mip4-dsmipv4 5 min George Tsirtsis =3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D Total 60 min [This is agenda rev -02, 19 Jul 2007 21:55:47] --------------enigFCDEFFF2406739B370A1BDCF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iD8DBQFGn8MheVhrtTJkXCMRAusTAKDA8VU0hjBqA3AtefQiKz0j16tHhwCglh/6 0S4EqfLE7qLCh03pNOjvPkI= =QfbM -----END PGP SIGNATURE----- --------------enigFCDEFFF2406739B370A1BDCF-- --===============1261567779== 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/ --===============1261567779==-- From mip4-bounces@ietf.org Mon Jul 23 13:15: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 1ID1VV-0006Jx-Sq; Mon, 23 Jul 2007 13:15:41 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1ID1VT-0006Jd-Uh for mip4-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 13:15:39 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1VT-0006JM-J4 for mip4@ietf.org; Mon, 23 Jul 2007 13:15:39 -0400 Received: from mail.ece.gatech.edu ([143.215.151.200]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID1VT-0002si-3E for mip4@ietf.org; Mon, 23 Jul 2007 13:15:39 -0400 Received: from gc556bwnlap07 (c-71-56-60-21.hsd1.ga.comcast.net [71.56.60.21]) (authenticated bits=0) by mail.ece.gatech.edu (8.14.0/8.13.7) with ESMTP id l6NHCjd7004027 for ; Mon, 23 Jul 2007 13:12:45 -0400 (EDT) From: "Dario Pompili" To: Date: Mon, 23 Jul 2007 13:15:16 -0400 Message-ID: <007a01c7cd4d$0ce15ba0$6501a8c0@ece.gatech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: AcfNTFw3VgOXRKmbRnGhke/+E+TYxQAAD51wAAAKW0AAAANpMAAACARgAAAEdtA= X-PMX-Version: 5.3.2.304607, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.7.23.94933 X-PerlMx-Spam: Gauge=XXII, Probability=22%, Report='RELAY_IN_PBL_10 2.5, RDNS_BROADBAND 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, RELAY_IN_PBL 0, __C230066_P5 0, __CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RDNS_BROADBAND_4 0, __RDNS_POOLED_10 0, __SANE_MSGID 0, __USER_AGENT_MS_GENERIC 0' X-Spam-Score: 1.8 (+) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Subject: [Mip4] IEEE JSAC - 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 [We apologize in advance if you receive multiple copies of this CALL FOR PAPERS] IEEE JSAC - CALL FOR PAPERS Underwater Wireless Communications and Networks Wireless information transmission through the ocean is one of the enabling technologies for the development of future ocean-observation systems, whose applications include gathering of scientific data, pollution control, climate recording, detection of objects on the ocean floor, and transmission of images from remote sites. Implicitly, wireless signal transmission is crucial for control of autonomous vehicles which will serve as mobile nodes in the future information networks of distributed underwater sensors. Wireless communications underwater are usually established using acoustic waves, while electro-magnetic waves can be used over short distances. Acoustic communications are governed by three factors: limited bandwidth, time-varying multipath propagation, and low speed of sound underwater. Together, these factors result in a communication channel of poor quality and high latency, thus ironically combining the worst properties of terrestrial mobile radio and satellite channels. In addition, because acoustic propagation is best supported at low frequencies, high-rate underwater systems are inherently ultra-wideband. These facts necessitate dedicated design of communication algorithms and network protocols at all layers of the system architecture. The proposed JSAC special issue seeks original research papers that explicitly address the unique technical challenges encountered in underwater scenarios, including (but not limited to) the following areas: * Statistical channel modeling and estimation * Underwater channel and network capacity * Bandwidth-efficient modulation/detection methods * Acoustic modem design and performance * Coding for underwater channels * Optical and RF underwater systems * Network topology and architecture * Resource allocation and spatial reuse * Multiple access techniques * Medium access control protocols * Routing protocols * Transport protocols * Traffic characterization and modeling * Data aggregation, fusion, and storage * System integration and applications * Experimental platforms * Application experiences Prospective authors should follow the IEEE J-SAC manuscript format described in the Information for Authors at http://www.jsac.ucsd.edu/Guidelines/info.html and submit a PDF version of their complete manuscript to http://edas.info according to the following timetable: Manuscript Submission: FEBRUARY 15, 2008 Acceptance Notification: June 15, 2008 Final Manuscript Due: August 15, 2008 Publication: 4th Quarter 2008 For any additional request, please contact Michele Zorzi, zorzi@dei.unipd.it GUEST EDITORS John Heidemann, Information Sciences Institute (johnh@isi.edu) Urbashi Mitra, University of Southern California (ubli@usc.edu) James Preisig, Woods Hole Oceanographic Institute (jpreisig@whoi.edu) Milica Stojanovic, Massachusetts Inst. of Technology (millitsa@mit.edu) Michele Zorzi, University of Padova (zorzi@dei.unipd.it) Dario Pompili, Ph.D. School of Electrical & Computer Engineering Georgia Institute of Technology, Atlanta, GA Email: dario@ece.gatech.edu http://users.ece.gatech.edu/dario/ Mobile: (404) 324-2342 -- 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 Jul 23 13:16:02 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Vq-0006nv-Ck; Mon, 23 Jul 2007 13:16:02 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1ID1Vp-0006nq-CK for mip4-confirm+ok@megatron.ietf.org; Mon, 23 Jul 2007 13:16:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Vp-0006ni-2d for mip4@ietf.org; Mon, 23 Jul 2007 13:16:01 -0400 Received: from mail.ece.gatech.edu ([143.215.151.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID1Vl-00046q-Pm for mip4@ietf.org; Mon, 23 Jul 2007 13:16:01 -0400 Received: from gc556bwnlap07 (c-71-56-60-21.hsd1.ga.comcast.net [71.56.60.21]) (authenticated bits=0) by mail.ece.gatech.edu (8.14.0/8.13.7) with ESMTP id l6NHD3cd004056 for ; Mon, 23 Jul 2007 13:13:03 -0400 (EDT) From: "Dario Pompili" To: Date: Mon, 23 Jul 2007 13:15:34 -0400 Message-ID: <007b01c7cd4d$17fb4eb0$6501a8c0@ece.gatech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: Acesaz71Ija9ayMQR+GFz954WkxtXwAAB5SwCDgiywAAAC/hAAAAA7QgAAAJSfAAAAMm8AAACNyA X-PMX-Version: 5.3.2.304607, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.7.23.94933 X-PerlMx-Spam: Gauge=XXIIIIIIII, Probability=28%, Report='RELAY_IN_PBL_10 2.5, LINES_OF_YELLING_3 0.671, RDNS_BROADBAND 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, RELAY_IN_PBL 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RDNS_BROADBAND_4 0, __RDNS_POOLED_10 0, __SANE_MSGID 0, __USER_AGENT_MS_GENERIC 0' X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Subject: [Mip4] CALL FOR POSTERS & DEMOS: The Second ACM International Workshop on UnderWater Networks (WUWNet 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 [We apologize in advance if you receive multiple copies of this CALL FOR POSTERS & DEMOS] _______________________________________________________________ __________________________________________________________________________ The Second ACM International Workshop on UnderWater Networks (WUWNet 2007) http://wuwnet07.engr.uconn.edu/ In conjunction with ACM MobiCom 2007 September 14, 2007 Montreal, Quebec, Canada Sponsored by ACM SIGMOBILE __________________________________________________________________________ __________________________________________________________________________ ********************************* CALL FOR WORK-IN-PROGRESS POSTERS ********************************* The work-in-progress poster session will provide a forum for researchers to showcase new and emerging work and obtain feedback from others on ongoing research. Topics of interest include, but are not limited to: - Network architecture design - Efficient acoustic communications - Cooperative underwater communications - Medium access control - Routing and forwarding - Reliable data transfer - Security and robustness - Power management - Data storage and management - Localization, timing, and synchronization - Data fusion, dissemination, tracking - Network modeling and simulations - Capacity analysis - New techniques for aquatic applications - New applications for underwater networks - Acoustic propagation modeling - Underwater network simulations - Underwater acoustic and optical testbeds POSTER SUBMISSION INSTRUCTIONS Please submit an extended abstract (no more than 2 pages) of your poster as a PDF e-mail attachment to and with the subject line reading "WUWNet Poster Submission" before the deadline. Please be as specific as possible in describing what you will show. Accepted abstracts will be posted and maintained on the workshop website. IMPORTANT DATES Extended abstracts due: 11:59 pm (EST), August 17, 2007 Notification of acceptance: August 22, 2007 Web abstracts due: August 31, 2007 Workshop date: September 14, 2007 WORK-IN-PROGRESS POSTER COMMITTEE Volkan Rodoplu (University of California, Santa Barbara) Wei Ye (ISI, University of Southern California) ________________________________________________________________________ ************** CALL FOR DEMOS ************** Demonstrations of innovative research, applications, and hardware/software products are solicited. Demonstrations of technology, platforms, applications and products for all aspects of underwater networks are of strong interest. Submission from both industry and universities are encouraged. DEMO SUBMISSION INSTRUCTIONS Please submit an extended abstract (no more than 2 pages) of your demo as a PDF e-mail attachment to: and with the subject line reading "WUWNet Demo Submission" before the deadline. Please be as specific as possible in describing what you will demonstrate or exhibit. The extended abstract should include a short description of space and equipment requirements. Accepted abstracts will be posted and maintained on the workshop website. IMPORTANT DATES Extended abstracts due: 11:59 pm (EST), August 17, 2007 Notification of acceptance: August 22, 2007 Web abstracts due: August 31, 2007 Workshop date: September 14, 2007 DEMO COMMITTEE Payman Arabshahi (University of Washington) Geoffrey Xie (Naval Postgraduate School) __________________________________________________________________________ Dario Pompili, Ph.D. School of Electrical & Computer Engineering Georgia Institute of Technology, Atlanta, GA Email: dario@ece.gatech.edu http://users.ece.gatech.edu/dario/ -- 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 Jul 24 11:15: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 1IDM6y-0008FY-3f; Tue, 24 Jul 2007 11:15:44 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDM6p-0007wc-DU for mip4-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 11:15:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDM6o-0007vz-J1; Tue, 24 Jul 2007 11:15:34 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDM6m-00019X-HZ; Tue, 24 Jul 2007 11:15:34 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 671C43296B; Tue, 24 Jul 2007 15:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IDM6I-0002JC-95; Tue, 24 Jul 2007 11:15: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: Tue, 24 Jul 2007 11:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-gen-ext-04.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 Extension for Configuration Options Exchange Author(s) : J. Bharatia, et al. Filename : draft-ietf-mip4-gen-ext-04.txt Pages : 13 Date : 2007-7-24 This document describes the mechanism for providing the host configuration information during Mobile IP registration. One or more Configuration Options Exchange Extensions may be included in the registration message to provide the Mobile Node the configuration parameters needed for network service (e.g. DNS). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-04.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-gen-ext-04.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-gen-ext-04.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-7-24105051.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-gen-ext-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-gen-ext-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-24105051.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 Jul 25 08:50: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 1IDgKE-0001q2-BU; Wed, 25 Jul 2007 08:50:46 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDgKC-0001kc-H1 for mip4-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 08:50:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDgKA-0001g8-95 for mip4@ietf.org; Wed, 25 Jul 2007 08:50:42 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDgK8-0006oy-QM for mip4@ietf.org; Wed, 25 Jul 2007 08:50:42 -0400 Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l6PCocRm013289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 25 Jul 2007 05:50:38 -0700 Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com [172.30.36.175]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l6PCobYG016064; Wed, 25 Jul 2007 05:50:38 -0700 (PDT) Received: from NAEX16.na.qualcomm.com ([10.47.6.158]) by sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jul 2007 05:50:37 -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] Working Group Last call for draft-ietf-mip4-dsmipv4-02.txt Date: Wed, 25 Jul 2007 05:50:36 -0700 Message-ID: <2309978910A6A6478C2C7585692B0AF487107F@NAEX16.na.qualcomm.com> In-Reply-To: <4682E20B.40300@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Working Group Last call for draft-ietf-mip4-dsmipv4-02.txt Thread-Index: Ace5CQSadqqzuRmdQsGsmnCCkPao3AVsIV3g References: <46823665.7040801@gmail.com> <2309978910A6A6478C2C7585692B0AF46E1617@NAEX16.na.qualcomm.com> <4682C883.6030405@gmail.com> <2309978910A6A6478C2C7585692B0AF46E1643@NAEX16.na.qualcomm.com> <4682E20B.40300@gmail.com> From: "Tsirtsis, George" To: "Alexandru Petrescu" X-OriginalArrivalTime: 25 Jul 2007 12:50:37.0114 (UTC) FILETIME=[65D671A0:01C7CEBA] X-Spam-Score: 0.0 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 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 Sorry for the delay but here are some additional comments -----Original Message----- From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]=20 Sent: Wednesday, June 27, 2007 5:18 PM To: Tsirtsis, George Cc: mip4@ietf.org Subject: Re: [Mip4] Working Group Last call for draft-ietf-mip4-dsmipv4-02.txt :-) Tsirtsis, George wrote: > About implicit mode:=20 > Implicit mode, means that MIP signaling is NOT used to indicate the IPv6 > addresses/prefixes for a given MN. How these address/prefixes are known > by the MN and the HA is simply outside the scope of this specification. > The MN can use DHCP prefix delegation, or HA and MN could be > preconfigured with IPv6 prefixes, or some other mechanism that I do not > know about may be used. There is nothing we need to say about any of > this here. I think what one needs in DSMIPv4 implicit mode is HA to hold a new=20 table IPv4 HoA - IPv6 HoA. I don't think prefix delegation can offer=20 that association. GT> Yes, but my point is that how it does this is entirely an implementation issue and there is no protocol work that needs to be done for it. > About encapsulation methods:=20 > When IPv6 is tunneled to the MN's IPv4 HoA, you get IPv6-in-IPv4 i.e., For this IPv6-in-IPv4 - which RFC? rfc2529 (6over4 - IPv4 protocol 41)?=20 Shouldn't this be referred to? You thought another? GT> I think the obvious choice is RFC4213 > the HA encapsulates packets with destAddr=3D=3DMN's IPv6 HoA, to an = IPv4 > tunnel with destAddr=3D=3DMN's IPv4 HoA. Then, the IPv4 packets (with > destAddr=3D=3DMN's IPv4 HoA) are tunneled to the MN's CoA with = whatever > mechanism is negotiated in MIPv4 messages (IPinIP, Minimal Encapsulation > etc). I think this is clear and the DS support does not interfere with > the different MIPv4 tunnel types. > If IPv6 is tunneled to the MN's CoA, however, then only > IPv6-in-IPv4 is used i.e., the HA encapsulates packets with > destAddr=3D=3DMN's IPv6 HoA, in an IPv4 tunnel with destAddr=3D=3DMN's = IPv4 CoA. > In that case the different MIP4 tunnel types are not used for this. > I could add such clarification in the specification. Would that be > acceptable to you? Ok if one refers to rfc2529 (or another you may have thought), thanks. GT> again RFC4213 Alex >=20 > -----Original Message----- > From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]=20 > Sent: Wednesday, June 27, 2007 4:29 PM > To: Tsirtsis, George > Cc: mip4@ietf.org > Subject: Re: [Mip4] Working Group Last call for > draft-ietf-mip4-dsmipv4-02.txt >=20 > Tsirtsis, George wrote: >> Hi Alex, >> >> Thanks for the review. I think this is the 2nd or 3rd one you provide >> for this draft :-) I think most of the comments this time can be=20 >> resolved easily. >=20 > I get your point, but I don't quite understand how you solve the issue > of GRE, Minimal Encapsulation and IP-in-IP not supporting IPv6. Or how=20 > you assume HA to learn the IPv6 HoA in implicit mode by means outside=20 > this document. >=20 > Alex >=20 >=20 > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email=20 > ______________________________________________________________________ >=20 ______________________________________________________________________ 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/ From mip4-bounces@ietf.org Wed Jul 25 12:15:11 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDjW3-0004wZ-5g; Wed, 25 Jul 2007 12:15:11 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDjVv-0004qK-FS for mip4-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 12:15:03 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDjVv-0004q3-3K; Wed, 25 Jul 2007 12:15:03 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDjVu-0007zL-Mr; Wed, 25 Jul 2007 12:15:03 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 6A410175C9; Wed, 25 Jul 2007 16:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IDjVt-0005PH-VZ; Wed, 25 Jul 2007 12:15:01 -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, 25 Jul 2007 12:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-radius-requirements-04.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 RADIUS requirements Author(s) : M. Nakhjiri, et al. Filename : draft-ietf-mip4-radius-requirements-04.txt Pages : 10 Date : 2007-7-25 This document provides an applicability statement as well as a scope definition for specifying RADIUS extensions to support Mobile IPv4. The goal is to allow specification of RADIUS attributes to assist the Mobile IPv4 signaling procedures. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-radius-requirements-04.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-radius-requirements-04.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-radius-requirements-04.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-7-25111919.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-radius-requirements-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-radius-requirements-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-25111919.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 Jul 25 13:05: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 1IDkIe-0006cP-QB; Wed, 25 Jul 2007 13:05:24 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDkId-0006cA-NL for mip4-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 13:05:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDkId-0006c2-Bd for mip4@ietf.org; Wed, 25 Jul 2007 13:05:23 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDkIc-0005G5-36 for mip4@ietf.org; Wed, 25 Jul 2007 13:05:23 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 25 Jul 2007 10:05:13 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CANcfp0arR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,581,1175497200"; d="scan'208"; a="388115991:sNHT2362314770" 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 l6PH5Cqr031318; Wed, 25 Jul 2007 10:05:12 -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 l6PH56Sb022169; Wed, 25 Jul 2007 17:05:12 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); Wed, 25 Jul 2007 10:05:05 -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] Question about draft-leung-mip4-proxy-mode Date: Wed, 25 Jul 2007 10:04:24 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520440F6D1@xmb-sjc-235.amer.cisco.com> In-Reply-To: <469F87A6.6020003@alcatel-lucent.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Question about draft-leung-mip4-proxy-mode Thread-Index: AcfKHDVAvdBJC2YXQQSc1q3zvh7lPwEwUWlg From: "Kent Leung \(kleung\)" To: "Bruno Mongazon-Cazavet" , "Mobile IPv4 Mailing List" X-OriginalArrivalTime: 25 Jul 2007 17:05:05.0983 (UTC) FILETIME=[F2CAF4F0:01C7CEDD] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=891; t=1185383112; x=1186247112; 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]=20Question=20about=20draft-leung-mip4-proxy-mo de |Sender:=20; bh=5rXShpImz20GgkM0NKMUlXobNlUFJPaw6QBIi4Wvy2M=; b=ZHaQ6s1fOQbD4zVAAutGFKaGHA91mffS+YHMx7bWZA/sd4zOUQdQhrwVW2PmWvOFy3vnu+hH gD+Tlhz4Ql18Bcjao7XOVLQLG3OYWiWyCKfbIRs3qyrIT8TONvOJaTVf; Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 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 Bruno. Sorry, I missed this question. In this case, the Router Advertisement will not have the Mobility Agent Advertisement Extension. Kent=20 -----Original Message----- From: Bruno Mongazon-Cazavet [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr]=20 Sent: Thursday, July 19, 2007 8:48 AM To: Mobile IPv4 Mailing List Subject: [Mip4] Question about draft-leung-mip4-proxy-mode Hello, When a router implements this draft, how should it reacts to Router Solicitation? In particular: -should the router fill the Mobility Agent Advertisement extension in the reply? -should the FA capability be set if only PMIP is supported? Thanks, Bruno. -- 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 Jul 25 14:28: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 1IDlbV-0005dD-GU; Wed, 25 Jul 2007 14:28:57 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDlbU-0005d4-U8 for mip4-confirm+ok@megatron.ietf.org; Wed, 25 Jul 2007 14:28:56 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDlbU-0005cv-Jq for mip4@ietf.org; Wed, 25 Jul 2007 14:28:56 -0400 Received: from py-out-1112.google.com ([64.233.166.176]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDlbT-0000t7-Dc for mip4@ietf.org; Wed, 25 Jul 2007 14:28:56 -0400 Received: by py-out-1112.google.com with SMTP id f31so952720pyh for ; Wed, 25 Jul 2007 11:28: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:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=F2uD58QAHsVgihVEuH22q8rMGxgQ5ptr/D+1Z3gZzLOcoN3B4x6xve/Xpuo2UlCMdW2/9aYBaUFTvT3dj/pPqBkBJPkyRpsAKHZUp/wtTjV9R1BVkpJEb7LjSOka/mexwVMz/cXjjUVOlGR1eN6+CwlKWUOB45Wsu8Fwwehh68o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=bBMdg6lC9ZaQiebAKGU/5K6ndbW93TJezO1P0WM4CQ7/jrZW8c89kjOrsmWgj2NhpiYObp02pHYxv3rtnm4HzaoMioB/NSm/nrweGIeGUZmZKNYLm1RqS7UhSYI82T2FVUAojTZ/D6F/EM9w/PM5Rp/g/7xnO0XucQ2tbBMC7H0= Received: by 10.141.129.14 with SMTP id g14mr288380rvn.1185388134170; Wed, 25 Jul 2007 11:28:54 -0700 (PDT) Received: from ?130.129.19.220? ( [130.129.19.220]) by mx.google.com with ESMTPS id l32sm1399103rvb.2007.07.25.11.28.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 25 Jul 2007 11:28:53 -0700 (PDT) Message-ID: <46A79660.5050901@gmail.com> Date: Wed, 25 Jul 2007 13:28:48 -0500 From: Alexandru Petrescu User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: "Tsirtsis, George" Subject: Re: [Mip4] Working Group Last call for draft-ietf-mip4-dsmipv4-02.txt References: <46823665.7040801@gmail.com> <2309978910A6A6478C2C7585692B0AF46E1617@NAEX16.na.qualcomm.com> <4682C883.6030405@gmail.com> <2309978910A6A6478C2C7585692B0AF46E1643@NAEX16.na.qualcomm.com> <4682E20B.40300@gmail.com> <2309978910A6A6478C2C7585692B0AF487107F@NAEX16.na.qualcomm.com> In-Reply-To: <2309978910A6A6478C2C7585692B0AF487107F@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: 9ed51c9d1356100bce94f1ae4ec616a9 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 Tsirtsis, George wrote: > Sorry for the delay but here are some additional comments > > -----Original Message----- From: Alexandru Petrescu > [mailto:alexandru.petrescu@gmail.com] Sent: Wednesday, June 27, 2007 > 5:18 PM To: Tsirtsis, George Cc: mip4@ietf.org Subject: Re: [Mip4] > Working Group Last call for draft-ietf-mip4-dsmipv4-02.txt > > :-) > > Tsirtsis, George wrote: >> About implicit mode: Implicit mode, means that MIP signaling is NOT >> used to indicate the IPv6 addresses/prefixes for a given MN. How >> these address/prefixes are known by the MN and the HA is simply >> outside the scope of this specification. The MN can use DHCP prefix >> delegation, or HA and MN could be preconfigured with IPv6 prefixes, >> or some other mechanism that I do not know about may be used. There >> is nothing we need to say about any of this here. > > I think what one needs in DSMIPv4 implicit mode is HA to hold a new > table IPv4 HoA - IPv6 HoA. I don't think prefix delegation can offer > that association. > > GT> Yes, but my point is that how it does this is entirely an > implementation issue and there is no protocol work that needs to be > done for it. Ok... >> About encapsulation methods: When IPv6 is tunneled to the MN's IPv4 >> HoA, you get IPv6-in-IPv4 i.e., > > For this IPv6-in-IPv4 - which RFC? rfc2529 (6over4 - IPv4 protocol > 41)? Shouldn't this be referred to? You thought another? > > GT> I think the obvious choice is RFC4213 Ah I think rfc4213 "Basic Transition Mechanisms for IPv6 Hosts and Routers" is appropriate to be referenced in this draft for IPv6-in-IPv4 encapsulation. The RFC talks dual-stack and configured tunnelling as two different mechanisms. I think the DSMIP only needs the dual-stack part? Alex -- 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 Jul 26 03:54: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 1IDyAf-0002P3-JA; Thu, 26 Jul 2007 03:54:05 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IDyAe-0002Os-LA for mip4-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 03:54:04 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDyAe-0002OX-6C for mip4@ietf.org; Thu, 26 Jul 2007 03:54:04 -0400 Received: from cassius.ee.usyd.edu.au ([129.78.13.49]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDyAb-0004kT-GV for mip4@ietf.org; Thu, 26 Jul 2007 03:54:02 -0400 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 l6Q7qDbB024881 for ; Thu, 26 Jul 2007 17:52:13 +1000 (EST) From: Guo Qiang Mao Received: from 220.233.174.32 (SquirrelMail authenticated user guoqiang) by www.ee.usyd.edu.au with HTTP; Thu, 26 Jul 2007 17:52:13 +1000 (EST) Message-ID: <19402.220.233.174.32.1185436333.squirrel@www.ee.usyd.edu.au> Date: Thu, 26 Jul 2007 17:52:13 +1000 (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 l6Q7qDbB024881 X-Spam-Score: 0.0 (/) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Subject: [Mip4] =?iso-8859-1?q?SenSys_2007_Call_For_Demos_and_Posters_=96?= =?iso-8859-1?q?_Two_Days_Left?= 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 SenSys 2007 Call For Demos and Posters =96 Two Days Left =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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 POSTERS Posters showing exciting early work on sensor systems are solicited. Areas of interest are the same as those listed in the technical call for papers. While the poster need not describe completed work, it should report on research for which at least preliminary results are available. The poster session will provide a forum for researchers to showcase their work and obtain feedback on ongoing research from knowledgeable conferenc= e attendees. 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. We especially encourage submissions by students (that is, for which a student is the first author on the poster). POSTER SUBMISSION INSTRUCTIONS Poster proposals must be submitted as a single PDF file with no more than 3 pages. The first two pages should contain an abstract describing the research content of the poster, along with title, authors, institutional affiliations and contact information. The third page should contain a thumbnail draft of the poster's contents. Please submit your poster proposal as a PDF e-mail attachment to sensys07-poster-chairs AT cs.pdx.edu with the subject line reading "Sensys Poster Submission" before the deadline. Any questions for the Poster Co-chairs Nirupama Bulusu, Portlan= d State Rachel Cardell-Oliver, University of Western Australia may also be directed to this address. IMPORTANT DATES Three-page poster proposal: 11:59pm (PST), July 27, 2007 Notification of acceptance: August 10, 2007 Camera-ready abstract: August 24, 2007 Conference dates: November 6-9, 2007 BASIC INFORMATION ABOUT POSTERS Two-page poster abstracts will appear in the conference proceedings. Authors of accepted poster proposals will have a chance to present the poster to interested attendees during a special poster session at SenSys. Well-crafted posters will tell the story well by themselves, but authors of posters are expected to be available to describe and discuss the work in the poster during the session. The poster dimensions are 30" by 40", with poster contents mounted on rectangular poster board that we will provide. You may choose a layout consisting of individual sheets of paper, or a monolithic large piece of poster paper (which can be printed at document companies). Nirupama Bulusu, Portland State Rachel Cardell-Oliver, University of Western Australia SenSys 2007 Poster Chairs =3D=3D=3D=3D=3D=3D=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 DEMO Demonstrations showing innovative research and applications are solicited. SenSys'07 is very interested in demonstrations of technology, platforms, and applications of wireless sensor networks and their integration with the Web. The demo session of SenSys'07 will provide a forum for researchers to showcase their work and obtain feedback on ongoing researc= h from knowledgeable conference attendees. Areas of interest are the same a= s those listed in the technical call for papers. Two-page abstracts of accepted demos will be published in the SenSys conference proceedings. Submissions from both industries and universities are encouraged. There will be one Best Student Demo Award and one Best Industry Demo Award. DEMO SUBMISSION INSTRUCTIONS Please send a two-page description of your demo to sensys07-demo-chairs [AT] nicta.com.au with the subject line reading "Sensys Demo Submission" before the deadlin= e. Submissions should be in PDF format. An additional one page appendix can be included in the initial submission but will be removed in published proceedings. Be as specific as possible in describing what you will show. Any questions for the Demonstration Co-chairs Max Ott and Suman Nath may also be directed to this address: sensys07-demo-chairs [AT] nicta.com.au IMPORTANT DATES Demo proposal: 11:59pm (PST), July 27, 2007 Notification of acceptance: August 10, 2007 Camera-ready abstract: August 24, 2007 Conference dates: November 6-9, 2007 Suman Nath, Microsoft Research Max Ott, NICTA, Australia SenSys 2007 Demo Chairs -- 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 Jul 26 09:17: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 1IE3DV-0000Lc-MY; Thu, 26 Jul 2007 09:17:21 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IE3DU-0000LQ-3u for mip4-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 09:17:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IE3DT-0000LH-Pc for mip4@ietf.org; Thu, 26 Jul 2007 09:17:19 -0400 Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail6.alcatel.fr) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE3DS-000552-BF for mip4@ietf.org; Thu, 26 Jul 2007 09:17:19 -0400 Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com [155.132.6.77]) by smail6.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6QDHEI8020207; Thu, 26 Jul 2007 15:17:14 +0200 Received: from [172.27.205.222] ([172.27.205.222]) by FRVELSBHS05.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Thu, 26 Jul 2007 15:17:15 +0200 Message-ID: <46A89EDB.8050706@alcatel-lucent.fr> Date: Thu, 26 Jul 2007 15:17:15 +0200 From: Bruno Mongazon-Cazavet User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: "Kent Leung (kleung)" Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode References: <2979E38DD6FC6544B789C8DAD7BAFC520440F6D1@xmb-sjc-235.amer.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520440F6D1@xmb-sjc-235.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Jul 2007 13:17:15.0549 (UTC) FILETIME=[48FE04D0:01C7CF87] X-Scanned-By: MIMEDefang 2.51 on 155.132.188.84 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c 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 Kent Leung (kleung) wrote: > Hi Bruno. Sorry, I missed this question. > > In this case, the Router Advertisement will not have the Mobility Agent > Advertisement Extension. > Since a router implementing MIP4 proxy mode includes FA function, isn't it logical and consistent to include a Mobility Agent Advertisment extension in RA to indicate FA support? I would suggest this behaviour can be added to your draft, possibly extending the Mobility Agent Advertisment extension to indicate PMIP support (i think some place is left for RFU in the format). What do you think? Such addition is not intended to be processed (understandable) by simple IP terminals, but rather by terminals that might behave as simple IP or MIP and need to choose which protocol to use. Thanks in advance for your reply. Bruno. > Kent > > -----Original Message----- > From: Bruno Mongazon-Cazavet > [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] > Sent: Thursday, July 19, 2007 8:48 AM > To: Mobile IPv4 Mailing List > Subject: [Mip4] Question about draft-leung-mip4-proxy-mode > > Hello, > > When a router implements this draft, how should it reacts to Router > Solicitation? > In particular: > -should the router fill the Mobility Agent Advertisement extension in > the reply? > -should the FA capability be set if only PMIP is supported? > > Thanks, Bruno. > > > -- > 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 Jul 26 12:39: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 1IE6NE-0008GP-25; Thu, 26 Jul 2007 12:39:36 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IE6NB-0008Fw-Vd for mip4-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 12:39:35 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IE6NB-0008Fn-Kh for mip4@ietf.org; Thu, 26 Jul 2007 12:39:33 -0400 Received: from hiltonsmtp.worldspice.net ([216.37.94.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE6NB-0002Dk-8k for mip4@ietf.org; Thu, 26 Jul 2007 12:39:33 -0400 Received: (qmail 11049 invoked by uid 0); 26 Jul 2007 16:31:54 -0000 Received: by simscan 1.2.0 ppid: 11015, pid: 11043, t: 0.9508s scanners: clamav: 0.90.2/m: spam: 3.1.8 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on hiltonsmtp.worldspice.net X-Spam-Level: *** X-Spam-Status: No, score=3.8 required=6.2 tests=ALL_TRUSTED,BAYES_80, MIME_BASE64_BLANKS,MIME_BASE64_TEXT,MISSING_MID autolearn=disabled version=3.2.1 Received: from unknown (HELO jysb3104081524) (z49950@67.97.210.2) by hiltonsmtp.worldspice.net with ESMTPA; 26 Jul 2007 16:31:53 -0000 Date: Thu, 26 Jul 2007 11:39:05 -0500 From: "John.zhao" To: "kleung" , "bruno.mongazon-cazavet" Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode X-mailer: Foxmail 5.0 beta1 [cn] Mime-Version: 1.0 X-Spam-Score: 2.8 (++) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Message-Id: Cc: mip4 X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: john.zhao@huawei.com List-Id: Mobility for IPv4 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1920284369==" Errors-To: mip4-bounces@ietf.org --===============1920284369== Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksa2VudA0KDQoJQ291bGQgSSBhc2sgZm9yIHR3byBwcm9ibGVtcyBhYm91dCB0aGlzIGRyYWZ0 Pw0KCTEpV2hhdCBpcyB0aGUgZGVmaW5hdGlvbiBvZiB5b3UgaGF2ZSBqdXN0IG1lbnRpb25lZCB0 aGUgTW9iaWxpdHkgQWdlbnQgQWR2ZXJ0aXNlbWVudCBFeHRlbnNpb24/DQoJMilXaGF0IGlzIHRo ZSBvcmlnaW5hdGlvbiBvZiBwc2V1ZG8gTUFDIGFkZHJlc3M/DQoNCgkJCUJlc3QgUmdkcywNClRo YW5rcywNCg0KCaGhoaGhoaGhoaGhoaGhoaFKb2huLnpoYW8NCqGhCaGhCaGhoaGhoaGhoaFqb2hu LnpoYW9AaHVhd2VpLmNvbQ0KoaGhoaGhCaGhCaGhoaGhoaGhoaGhoTIwMDctMDctMjYNCj09PT09 PT0gMjAwNy0wNy0yNiAxMjowMDowMCBZb3UgaGF2ZSBzYWlkOj09PT09PT0NCj4NCj5LZW50IExl dW5nIChrbGV1bmcpIHdyb3RlOg0KPj4gSGkgQnJ1bm8uICBTb3JyeSwgSSBtaXNzZWQgdGhpcyBx dWVzdGlvbi4NCj4+DQo+PiBJbiB0aGlzIGNhc2UsIHRoZSBSb3V0ZXIgQWR2ZXJ0aXNlbWVudCB3 aWxsIG5vdCBoYXZlIHRoZSBNb2JpbGl0eSBBZ2VudA0KPj4gQWR2ZXJ0aXNlbWVudCBFeHRlbnNp b24uDQo+PiAgIA0KPlNpbmNlIGEgcm91dGVyIGltcGxlbWVudGluZyBNSVA0IHByb3h5IG1vZGUg aW5jbHVkZXMgRkEgZnVuY3Rpb24sIGlzbid0IA0KPml0IGxvZ2ljYWwgYW5kIGNvbnNpc3RlbnQg dG8gaW5jbHVkZSBhIE1vYmlsaXR5IEFnZW50IEFkdmVydGlzbWVudCANCj5leHRlbnNpb24gaW4g UkEgdG8gaW5kaWNhdGUgRkEgc3VwcG9ydD8NCj5JIHdvdWxkIHN1Z2dlc3QgdGhpcyBiZWhhdmlv dXIgY2FuIGJlIGFkZGVkIHRvIHlvdXIgZHJhZnQsIHBvc3NpYmx5IA0KPmV4dGVuZGluZyB0aGUg TW9iaWxpdHkgQWdlbnQgQWR2ZXJ0aXNtZW50IGV4dGVuc2lvbiB0byBpbmRpY2F0ZSBQTUlQIA0K PnN1cHBvcnQgKGkgdGhpbmsgc29tZSBwbGFjZSBpcyBsZWZ0IGZvciBSRlUgaW4gdGhlIGZvcm1h dCkuDQo+DQo+V2hhdCBkbyB5b3UgdGhpbms/DQo+DQo+U3VjaCBhZGRpdGlvbiBpcyBub3QgaW50 ZW5kZWQgdG8gYmUgcHJvY2Vzc2VkICh1bmRlcnN0YW5kYWJsZSkgYnkgc2ltcGxlIA0KPklQIHRl cm1pbmFscywgYnV0IHJhdGhlciBieSB0ZXJtaW5hbHMgdGhhdCBtaWdodCBiZWhhdmUgYXMgc2lt cGxlIElQIG9yIA0KPk1JUCBhbmQgbmVlZCB0byBjaG9vc2Ugd2hpY2ggcHJvdG9jb2wgdG8gdXNl Lg0KPg0KPlRoYW5rcyBpbiBhZHZhbmNlIGZvciB5b3VyIHJlcGx5Lg0KPkJydW5vLg0KPj4gS2Vu dCANCj4+DQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTogQnJ1bm8gTW9u Z2F6b24tQ2F6YXZldA0KPj4gW21haWx0bzpicnVuby5tb25nYXpvbi1jYXphdmV0QGFsY2F0ZWwt bHVjZW50LmZyXSANCj4+IFNlbnQ6IFRodXJzZGF5LCBKdWx5IDE5LCAyMDA3IDg6NDggQU0NCj4+ IFRvOiBNb2JpbGUgSVB2NCBNYWlsaW5nIExpc3QNCj4+IFN1YmplY3Q6IFtNaXA0XSBRdWVzdGlv biBhYm91dCBkcmFmdC1sZXVuZy1taXA0LXByb3h5LW1vZGUNCj4+DQo+PiBIZWxsbywNCj4+DQo+ PiBXaGVuIGEgcm91dGVyIGltcGxlbWVudHMgdGhpcyBkcmFmdCwgaG93IHNob3VsZCBpdCByZWFj dHMgdG8gUm91dGVyDQo+PiBTb2xpY2l0YXRpb24/DQo+PiBJbiBwYXJ0aWN1bGFyOg0KPj4gLXNo b3VsZCB0aGUgcm91dGVyIGZpbGwgdGhlIE1vYmlsaXR5IEFnZW50IEFkdmVydGlzZW1lbnQgZXh0 ZW5zaW9uIGluDQo+PiB0aGUgcmVwbHk/DQo+PiAtc2hvdWxkIHRoZSBGQSBjYXBhYmlsaXR5IGJl IHNldCBpZiBvbmx5IFBNSVAgaXMgc3VwcG9ydGVkPw0KPj4NCj4+IFRoYW5rcywgQnJ1bm8uDQo+ Pg0KDQo= --===============1920284369== 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/ --===============1920284369==-- From mip4-bounces@ietf.org Thu Jul 26 22:22:53 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEFTh-0001ZN-57; Thu, 26 Jul 2007 22:22:53 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IEFTf-0001WC-BQ for mip4-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 22:22:51 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEFTe-0001UL-Vl for mip4@ietf.org; Thu, 26 Jul 2007 22:22:51 -0400 Received: from tyo202.gate.nec.co.jp ([202.32.8.206]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEFTe-0006R1-6X for mip4@ietf.org; Thu, 26 Jul 2007 22:22:50 -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 l6R2Mlp4015181 for ; Fri, 27 Jul 2007 11:22:47 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l6R2MlE14775 for mip4@ietf.org; Fri, 27 Jul 2007 11:22:47 +0900 (JST) Received: from saigo.jp.nec.com (saigo.jp.nec.com [10.26.220.6]) by mailsv.nec.co.jp (8.11.7/3.7W-MAILSV-NEC) with ESMTP id l6R2Mle04244 for ; Fri, 27 Jul 2007 11:22:47 +0900 (JST) Received: from [10.87.72.34] ([10.87.72.34] [10.87.72.34]) by mail.jp.nec.com with ESMTP; Fri, 27 Jul 2007 11:22:41 +0900 Message-Id: <46A956F3.7030000@az.jp.nec.com> Date: Thu, 26 Jul 2007 21:22:43 -0500 From: Jun AWANO User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: mip4 Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question about draft-leung-mip4-proxy-mode) References: In-Reply-To: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by tyo202.gate.nec.co.jp id l6R2Mlp4015181 X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 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 let me ask about your draft. Your draft says, "This document describes WiMAX Forum and 3GPP2 solution for the base Proxy Mobile IPv4 function which enables another entity to provide mobility support on behalf of an unaltered and mobility-unaware IPv4 device." But, I think that the PMIPv4 described in your draft seems different from the one specified in WiMAX Forum spec (WiMAX Forum Network Architechture stage2/3). Do you plan to change the PMIPv4 spec of WiMAX Forum to match your draft? Best Regards, Jun John.zhao wrote: > Hi,kent >=20 > Could I ask for two problems about this draft? > 1)What is the defination of you have just mentioned the Mobility Agent= Advertisement Extension? > 2)What is the origination of pseudo MAC address? >=20 > Best Rgds, > Thanks, >=20 > =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1John.zhao > =A1=A1 =A1=A1 =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1john.zhao@huawei.com > =A1=A1=A1=A1=A1=A1 =A1=A1 =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12007-07-2= 6 > =3D=3D=3D=3D=3D=3D=3D 2007-07-26 12:00:00 You have said:=3D=3D=3D=3D=3D= =3D=3D >> Kent Leung (kleung) wrote: >>> Hi Bruno. Sorry, I missed this question. >>> >>> In this case, the Router Advertisement will not have the Mobility Age= nt >>> Advertisement Extension. >>> =20 >> Since a router implementing MIP4 proxy mode includes FA function, isn'= t=20 >> it logical and consistent to include a Mobility Agent Advertisment=20 >> extension in RA to indicate FA support? >> I would suggest this behaviour can be added to your draft, possibly=20 >> extending the Mobility Agent Advertisment extension to indicate PMIP=20 >> support (i think some place is left for RFU in the format). >> >> What do you think? >> >> Such addition is not intended to be processed (understandable) by simp= le=20 >> IP terminals, but rather by terminals that might behave as simple IP o= r=20 >> MIP and need to choose which protocol to use. >> >> Thanks in advance for your reply. >> Bruno. >>> Kent=20 >>> >>> -----Original Message----- >>> From: Bruno Mongazon-Cazavet >>> [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr]=20 >>> Sent: Thursday, July 19, 2007 8:48 AM >>> To: Mobile IPv4 Mailing List >>> Subject: [Mip4] Question about draft-leung-mip4-proxy-mode >>> >>> Hello, >>> >>> When a router implements this draft, how should it reacts to Router >>> Solicitation? >>> In particular: >>> -should the router fill the Mobility Agent Advertisement extension in >>> the reply? >>> -should the FA capability be set if only PMIP is supported? >>> >>> Thanks, Bruno. >>> >=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 Jul 27 11:45: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 1IES0I-0006sl-Ea; Fri, 27 Jul 2007 11:45:22 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IES0H-0006sb-9b for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 11:45:21 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IES0G-0006sS-Uw for mip4@ietf.org; Fri, 27 Jul 2007 11:45:21 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IES0G-0007XN-DT for mip4@ietf.org; Fri, 27 Jul 2007 11:45:20 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 27 Jul 2007 08:45:19 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAFKwqUarR7PE/2dsb2JhbAA X-IronPort-AV: i="4.16,589,1175497200"; d="scan'208"; a="10909299:sNHT19321518" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6RFjJOR028431; Fri, 27 Jul 2007 08:45:19 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6RFjAA0023409; Fri, 27 Jul 2007 15:45:19 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); Fri, 27 Jul 2007 08:45:10 -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] Question about draft-leung-mip4-proxy-mode Date: Fri, 27 Jul 2007 08:45:09 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520445EA5E@xmb-sjc-235.amer.cisco.com> In-Reply-To: <46A89EDB.8050706@alcatel-lucent.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Question about draft-leung-mip4-proxy-mode Thread-Index: AcfPh0pwplgWEYNbSTGas8RfCPDlSwACsxnw From: "Kent Leung \(kleung\)" To: "Bruno Mongazon-Cazavet" X-OriginalArrivalTime: 27 Jul 2007 15:45:10.0123 (UTC) FILETIME=[1D104BB0:01C7D065] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2968; t=1185551119; x=1186415119; c=relaxed/simple; s=sjdkim4002; 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]=20Question=20about=20draft-leung-mip4-proxy-mo de |Sender:=20; bh=JuvVwRTJlXoDWQHSWJGXhgquXUDu1UPl9UcvOaOWTVs=; b=bN0b1Ie3VdH2iB08TAZkOv3t9c8f6gbf2iEQY1vV3lEqL6TKe2erqw7MaVBmbgEDHH5K0pmv R6SB9803R2ZvK2X6FCw07Lh05EGbvMslwXogPp5PU6FqPl7xElka6hPM; Authentication-Results: sj-dkim-4; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 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 The router which implements the MIP4 proxy mode may not be enabled with FA service. In such case, collocated Care-of Address may be used for Mobile IP registration/tunneling. I think your question is based on the need for the mobile terminal to learn if the network supports PMIP and/or MIP. Is this in the context of WiMAX or just generic MIP? For generic MIP, a MIP-enabled terminal also supports simple IP. If the terminal is using the MIP Home Address, then it must register with its HA via FA CoA or CCoA to maintain its communications. If a CCoA address is available, the terminal may use that IP address as well. Not clear if the terminal needs to know if this IP address is provided mobility by the network? For PMIP, this is suppose to be transparent to the mobile terminal. Of course, the terminal can detect if the CCoA is still usable after handover via DHCP, ARP, and/or ICMP mechanisms without having to know what the network is doing. For WiMAX case, we should probably discuss this on the NWG alias. Kent -----Original Message----- From: Bruno Mongazon-Cazavet [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr]=20 Sent: Thursday, July 26, 2007 6:17 AM To: Kent Leung (kleung) Cc: Mobile IPv4 Mailing List Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode Kent Leung (kleung) wrote: > Hi Bruno. Sorry, I missed this question. > > In this case, the Router Advertisement will not have the Mobility=20 > Agent Advertisement Extension. > =20 Since a router implementing MIP4 proxy mode includes FA function, isn't it logical and consistent to include a Mobility Agent Advertisment extension in RA to indicate FA support? I would suggest this behaviour can be added to your draft, possibly extending the Mobility Agent Advertisment extension to indicate PMIP support (i think some place is left for RFU in the format). What do you think? Such addition is not intended to be processed (understandable) by simple IP terminals, but rather by terminals that might behave as simple IP or MIP and need to choose which protocol to use. Thanks in advance for your reply. Bruno. > Kent > > -----Original Message----- > From: Bruno Mongazon-Cazavet > [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] > Sent: Thursday, July 19, 2007 8:48 AM > To: Mobile IPv4 Mailing List > Subject: [Mip4] Question about draft-leung-mip4-proxy-mode > > Hello, > > When a router implements this draft, how should it reacts to Router=20 > Solicitation? > In particular: > -should the router fill the Mobility Agent Advertisement extension in=20 > the reply? > -should the FA capability be set if only PMIP is supported? > > Thanks, Bruno. > > > -- > 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 Jul 27 11:54: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 1IES9P-0005Vr-1q; Fri, 27 Jul 2007 11:54:47 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IES9N-0005Vh-5B for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 11:54:45 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IES9M-0005VZ-Qd for mip4@ietf.org; Fri, 27 Jul 2007 11:54:44 -0400 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IES9M-0007mk-E3 for mip4@ietf.org; Fri, 27 Jul 2007 11:54:44 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 27 Jul 2007 08:54:44 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAH+xqUarR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,589,1175497200"; d="scan'208"; a="507771345:sNHT101492500" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6RFsh3M027804; Fri, 27 Jul 2007 08:54:43 -0700 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 l6RFsUTx013563; Fri, 27 Jul 2007 15:54:43 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); Fri, 27 Jul 2007 08:54:31 -0700 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Subject: RE: [Mip4] Question about draft-leung-mip4-proxy-mode Date: Fri, 27 Jul 2007 08:54:30 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520445EA6C@xmb-sjc-235.amer.cisco.com> In-Reply-To: <5v3llb$rjn96@sj-inbound-a.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] Question about draft-leung-mip4-proxy-mode Thread-Index: AcfPo5CW8QiFVfNkR1eK/PbBxR+xkgAwZbLA From: "Kent Leung \(kleung\)" To: , "bruno.mongazon-cazavet" X-OriginalArrivalTime: 27 Jul 2007 15:54:31.0018 (UTC) FILETIME=[6B6214A0:01C7D066] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=830; t=1185551683; x=1186415683; 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]=20Question=20about=20draft-leung-mip4-proxy-mo de |Sender:=20; bh=1PNplwbISL6SlDCZdlx/+vlV1VRXVukCTskUuNOnD5A=; b=VmrKXN5skuWSsVq7GNgjDlJrEi2SAbz6XLPx59d+45sf9NgChpns/wO1U20BYl9VG0JpgyWG RdATpIStks/IRi8TWVR3J9HDH/GbTv+ekph18FQCoc55jvxXjPERyDQL; 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: 2409bba43e9c8d580670fda8b695204a Cc: mip4 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 John. The Mobility Agent Advertisement Extension that I mentioned is defined in RFC 3344 section 2.1.1. The pseudo MAC address is learned via ARP. This address can be set by configuration. Kent -----Original Message----- From: John.zhao [mailto:john.zhao@huawei.com] Sent: Thursday, July 26, 2007 9:39 AM To: Kent Leung (kleung); bruno.mongazon-cazavet Cc: mip4 Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode Hi,kent Could I ask for two problems about this draft? 1)What is the defination of you have just mentioned the Mobility Agent Advertisement Extension? 2)What is the origination of pseudo MAC address? Best Rgds, Thanks, 　　　　　　　　John.zhao 　 　 　　　　　john.zhao@huawei.com 　　　 　 　　　　　　2007-07-26 -- 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 Jul 27 12:28: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 1IESgA-00055d-7Y; Fri, 27 Jul 2007 12:28:38 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IESg8-00054G-88 for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 12:28:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IESg7-000548-Uu for mip4@ietf.org; Fri, 27 Jul 2007 12:28:35 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IESg7-0008O4-Bq for mip4@ietf.org; Fri, 27 Jul 2007 12:28:35 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-4.cisco.com with ESMTP; 27 Jul 2007 09:28:34 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CALK5qUarR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,589,1175497200"; d="scan'208"; a="7379701:sNHT21660000" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6RGSYsw018770; Fri, 27 Jul 2007 09:28:34 -0700 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 l6RGSE6c008106; Fri, 27 Jul 2007 16:28:34 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); Fri, 27 Jul 2007 09:28:32 -0700 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] Question aboutdraft-leung-mip4-proxy-mode) Date: Fri, 27 Jul 2007 09:28:31 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520445EAA2@xmb-sjc-235.amer.cisco.com> In-Reply-To: <46A956F3.7030000@az.jp.nec.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pmipv4 of WiMAX forum (Re: [Mip4] Question aboutdraft-leung-mip4-proxy-mode) Thread-Index: AcfP9RTgSQLyB53JQkqB34Jrwl6AwAAdb5sQ From: "Kent Leung ¥(kleung¥)" To: "Jun AWANO" , "mip4" X-OriginalArrivalTime: 27 Jul 2007 16:28:32.0153 (UTC) FILETIME=[2BFE9090:01C7D06B] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3152; t=1185553714; x=1186417714; 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=20pmipv4=20of=20WiMAX=20forum=20(Re=3A=20[Mip4]=20Quest ion=20aboutdraft-leung-mip4-proxy-mode) |Sender:=20; bh=aREMTxLvwYXdrpcYMP1rQHrkQf154Ho2ipdclPs+Ajg=; b=THSW8zPoMuWqFrVn6gLI6guYNjRkR7ksqerodC0mR9/DY5IyoRHDnUluxtsnaVr0/9U8HfrY 5NwZcFlr4cvj+2x2V3mLCgl94TqPNUGoGeU0KAzDkrQ/arGnbvZD7uBL; Authentication-Results: sj-dkim-3; header.From=kleung@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 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. We are working with WiMAX Forum members to address the technical gaps in the draft. Currently, we are collecting the review comments and will update the draft accordingly. Kent -----Original Message----- From: Jun AWANO [mailto:j-awano@az.jp.nec.com] Sent: Thursday, July 26, 2007 7:23 PM To: mip4 Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question aboutdraft-leung-mip4-proxy-mode) Hi, kent Please let me ask about your draft. Your draft says, "This document describes WiMAX Forum and 3GPP2 solution for the base Proxy Mobile IPv4 function which enables another entity to provide mobility support on behalf of an unaltered and mobility-unaware IPv4 device." But, I think that the PMIPv4 described in your draft seems different from the one specified in WiMAX Forum spec (WiMAX Forum Network Architechture stage2/3). Do you plan to change the PMIPv4 spec of WiMAX Forum to match your draft? Best Regards, Jun John.zhao wrote: > Hi,kent > > Could I ask for two problems about this draft? > 1)What is the defination of you have just mentioned the Mobility Agent Advertisement Extension? > 2)What is the origination of pseudo MAC address? > > Best Rgds, > Thanks, > > 　　　　　　　　John.zhao > 　 　 　　　　　john.zhao@huawei.com > 　　　 　 　　　　　　2007-07-26 > ======= 2007-07-26 12:00:00 You have said:======= >> Kent Leung (kleung) wrote: >>> Hi Bruno. Sorry, I missed this question. >>> >>> In this case, the Router Advertisement will not have the Mobility >>> Agent Advertisement Extension. >>> >> Since a router implementing MIP4 proxy mode includes FA function, >> isn't it logical and consistent to include a Mobility Agent >> Advertisment extension in RA to indicate FA support? >> I would suggest this behaviour can be added to your draft, possibly >> extending the Mobility Agent Advertisment extension to indicate PMIP >> support (i think some place is left for RFU in the format). >> >> What do you think? >> >> Such addition is not intended to be processed (understandable) by >> simple IP terminals, but rather by terminals that might behave as >> simple IP or MIP and need to choose which protocol to use. >> >> Thanks in advance for your reply. >> Bruno. >>> Kent >>> >>> -----Original Message----- >>> From: Bruno Mongazon-Cazavet >>> [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] >>> Sent: Thursday, July 19, 2007 8:48 AM >>> To: Mobile IPv4 Mailing List >>> Subject: [Mip4] Question about draft-leung-mip4-proxy-mode >>> >>> Hello, >>> >>> When a router implements this draft, how should it reacts to Router >>> Solicitation? >>> In particular: >>> -should the router fill the Mobility Agent Advertisement extension >>> in the reply? >>> -should the FA capability be set if only PMIP is supported? >>> >>> Thanks, Bruno. >>> > -- 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 Jul 27 12:31: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 1IESiv-0007eK-At; Fri, 27 Jul 2007 12:31:29 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IESiu-0007eD-1j for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 12:31:28 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IESit-0007e5-ND for mip4@ietf.org; Fri, 27 Jul 2007 12:31:27 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IESit-0000Jr-AF for mip4@ietf.org; Fri, 27 Jul 2007 12:31:27 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-5.cisco.com with ESMTP; 27 Jul 2007 09:31:26 -0700 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAN66qUarR7PD/2dsb2JhbAA X-IronPort-AV: i="4.16,589,1175497200"; d="scan'208"; a="168468883:sNHT41558256" Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l6RGVQPe023788; Fri, 27 Jul 2007 09:31:26 -0700 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 l6RGVQ6E011149; Fri, 27 Jul 2007 16:31:26 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); Fri, 27 Jul 2007 09:31:26 -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: pmipv4 of WiMAX forum (Re: [Mip4] Questionaboutdraft-leung-mip4-proxy-mode) Date: Fri, 27 Jul 2007 09:31:25 -0700 Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC520445EAAA@xmb-sjc-235.amer.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520445EAA2@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pmipv4 of WiMAX forum (Re: [Mip4] Questionaboutdraft-leung-mip4-proxy-mode) Thread-Index: AcfP9RTgSQLyB53JQkqB34Jrwl6AwAAdb5sQAAAl9oA= From: "Kent Leung ¥(kleung¥)" To: "Jun AWANO" , "mip4" X-OriginalArrivalTime: 27 Jul 2007 16:31:26.0164 (UTC) FILETIME=[93B68940:01C7D06B] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1305; t=1185553886; x=1186417886; 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=20pmipv4=20of=20WiMAX=20forum=20(Re=3A=20[Mip4]=20Quest ionaboutdraft-leung-mip4-proxy-mode) |Sender:=20; bh=KzX3S0VrI2lHDvf38YsKJBvhjeopjIGWvy6BVlSA+ms=; b=O9VrY8KuDINEnK9fgDuetGq7mgGdl/nogIgvCVWil4ax+qfwZqH2PVaMR+4aIyVF8fRK9AkA 4fB7sMXhHT4otQWiLeo30dKEIWYR5oy1QOLmYlFd22wVquCOxA3xzPZL; 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: 4adaf050708fb13be3316a9eee889caa 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 Let me clarify that we will be updating our draft, draft-leung-mip4-proxy-mode, accordingly to address the gaps. Kent=20 -----Original Message----- From: Kent Leung (kleung)=20 Sent: Friday, July 27, 2007 9:29 AM To: Jun AWANO; mip4 Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] Questionaboutdraft-leung-mip4-proxy-mode) Hi Jun. We are working with WiMAX Forum members to address the technical gaps in the draft. Currently, we are collecting the review comments and will update the draft accordingly. Kent=20 -----Original Message----- From: Jun AWANO [mailto:j-awano@az.jp.nec.com] Sent: Thursday, July 26, 2007 7:23 PM To: mip4 Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question aboutdraft-leung-mip4-proxy-mode) Hi, kent Please let me ask about your draft. Your draft says, "This document describes WiMAX Forum and 3GPP2 solution for the base Proxy Mobile IPv4 function which enables another entity to provide mobility support on behalf of an unaltered and mobility-unaware IPv4 device." But, I think that the PMIPv4 described in your draft seems different from the one specified in WiMAX Forum spec (WiMAX Forum Network Architechture stage2/3). Do you plan to change the PMIPv4 spec of WiMAX Forum to match your draft? 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 Fri Jul 27 13:28: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 1IETbp-0004Ih-3r; Fri, 27 Jul 2007 13:28:13 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IETbn-0004Fd-8k for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 13:28:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IETbm-0004FU-VJ for mip4@ietf.org; Fri, 27 Jul 2007 13:28:10 -0400 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IETbm-0001Qi-17 for mip4@ietf.org; Fri, 27 Jul 2007 13:28:10 -0400 Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by ind-iport-1.cisco.com with ESMTP; 28 Jul 2007 12:05:26 +0530 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAIfHqUYKS+ej/2dsb2JhbAA X-IronPort-AV: i="4.16,589,1175452200"; d="scan'208"; a="84868261:sNHT39956232" Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6RHS20P029934; Sat, 28 Jul 2007 01:28:02 +0800 Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6RHS1CK025207; Fri, 27 Jul 2007 17:28:02 GMT Received: from xmb-hkg-416.apac.cisco.com ([64.104.123.88]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Jul 2007 01:28:01 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) Date: Sat, 28 Jul 2007 01:27:37 +0800 Message-ID: <35912544FC930E49BF20EF16C3EF2765027A4819@xmb-hkg-416.apac.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520445EAAA@xmb-sjc-235.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) Thread-Index: AcfP9RTgSQLyB53JQkqB34Jrwl6AwAAdb5sQAAAl9oAAATvVIA== From: "Yoshi Tsuda ¥(yotsuda¥)" To: "Kent Leung ¥(kleung¥)" , "Jun AWANO" X-OriginalArrivalTime: 27 Jul 2007 17:28:01.0179 (UTC) FILETIME=[7B4CB6B0:01C7D073] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2310; t=1185557282; x=1186421282; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=yotsuda@cisco.com; z=From:=20=22Yoshi=20Tsuda=20¥(yotsuda¥)=22=20 |Subject:=20RE=3A=20pmipv4=20of=20WiMAX=20forum=20(Re=3A=20[Mip4]Question aboutdraft-leung-mip4-proxy-mode) |Sender:=20; bh=0jvf9puuiUSA1L5dOtBg2PK6mhDt7t+VMoDoNt6XHNk=; b=XsqbvkkeodKCX+PjjNouJfeD1uQZVMI21r2AjVr9vSgIo5PEkYhpeEW7jP2BcKnadc147Q3q 5Vqu7SE8EIoyOuH0i98OcuBnJ91Xsuo3vXmbK6r15A27OwHqJM+gVn5D7QpPSti2Ax6U9nSBKX PNtE2BtsJ91+d4yM1efzPkGJc=; Authentication-Results: hkg-dkim-2; header.From=yotsuda@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); X-Spam-Score: -4.0 (----) X-Scan-Signature: 25620135586de10c627e3628c432b04a Cc: mip4 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 Awano-san, What do you think the major technical differences between current Kent's draft and the current WiMAX spec? You know, most people in this MIP4 mailinglist doesn't have enough time to check the specific WiMAX spec. So, we would appreciate, if you point out the MIPv4-related technical differences instead of just saying different. =20 Thanks in advance. -Yoshi > -----Original Message----- > From: Kent Leung (kleung)=20 > Sent: Friday, July 27, 2007 9:31 AM > To: Jun AWANO; mip4 > Subject: RE: pmipv4 of WiMAX forum (Re:=20 > [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) >=20 > Let me clarify that we will be updating our draft,=20 > draft-leung-mip4-proxy-mode, accordingly to address the gaps. >=20 > Kent=20 >=20 > -----Original Message----- > From: Kent Leung (kleung) > Sent: Friday, July 27, 2007 9:29 AM > To: Jun AWANO; mip4 > Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] > Questionaboutdraft-leung-mip4-proxy-mode) >=20 > Hi Jun. >=20 > We are working with WiMAX Forum members to address the=20 > technical gaps in the draft. Currently, we are collecting=20 > the review comments and will update the draft accordingly. >=20 > Kent=20 >=20 > -----Original Message----- > From: Jun AWANO [mailto:j-awano@az.jp.nec.com] > Sent: Thursday, July 26, 2007 7:23 PM > To: mip4 > Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question > aboutdraft-leung-mip4-proxy-mode) >=20 > Hi, kent >=20 > Please let me ask about your draft. >=20 > Your draft says, > "This document describes WiMAX Forum and 3GPP2 solution for=20 > the base Proxy Mobile IPv4 function which enables another=20 > entity to provide mobility support on behalf of an unaltered=20 > and mobility-unaware IPv4 device." >=20 > But, I think that the PMIPv4 described in your draft seems=20 > different from the one specified in WiMAX Forum spec (WiMAX=20 > Forum Network Architechture stage2/3). >=20 > Do you plan to change the PMIPv4 spec of WiMAX Forum to match=20 > your draft? >=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 Fri Jul 27 16:57:56 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWsm-0007DX-A0; Fri, 27 Jul 2007 16:57:56 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IEWsl-0007DL-Bj for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 16:57:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWsl-0007DC-2C for mip4@ietf.org; Fri, 27 Jul 2007 16:57:55 -0400 Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEWsk-00074a-Cs for mip4@ietf.org; Fri, 27 Jul 2007 16:57:55 -0400 Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.197]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l6RKvrer020221 for ; Sat, 28 Jul 2007 05:57:53 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l6RKvrC15381 for mip4@ietf.org; Sat, 28 Jul 2007 05:57:53 +0900 (JST) Received: from saigo.jp.nec.com (saigo.jp.nec.com [10.26.220.6]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id l6RKvqP28074 for ; Sat, 28 Jul 2007 05:57:52 +0900 (JST) Received: from [10.87.72.34] ([10.87.72.34] [10.87.72.34]) by mail.jp.nec.com with ESMTP; Sat, 28 Jul 2007 05:57:51 +0900 Message-Id: <46AA5C53.8030907@az.jp.nec.com> Date: Fri, 27 Jul 2007 15:57:55 -0500 From: Jun AWANO User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: mip4 Subject: Re: pmipv4 of WiMAX forum (Re: [Mip4] Questionaboutdraft-leung-mip4-proxy-mode) References: <2979E38DD6FC6544B789C8DAD7BAFC520445EAAA@xmb-sjc-235.amer.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520445EAAA@xmb-sjc-235.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da 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, Thank you for your early reply. I've understood your intention. I'll wait for your updated draft.:) Best Regards, Jun Kent Leung (kleung) wrote: > Let me clarify that we will be updating our draft, > draft-leung-mip4-proxy-mode, accordingly to address the gaps. > > Kent > > -----Original Message----- > From: Kent Leung (kleung) > Sent: Friday, July 27, 2007 9:29 AM > To: Jun AWANO; mip4 > Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] > Questionaboutdraft-leung-mip4-proxy-mode) > > Hi Jun. > > We are working with WiMAX Forum members to address the technical gaps in > the draft. Currently, we are collecting the review comments and will > update the draft accordingly. > > Kent > > -----Original Message----- > From: Jun AWANO [mailto:j-awano@az.jp.nec.com] > Sent: Thursday, July 26, 2007 7:23 PM > To: mip4 > Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question > aboutdraft-leung-mip4-proxy-mode) > > Hi, kent > > Please let me ask about your draft. > > Your draft says, > "This document describes WiMAX Forum and 3GPP2 solution for the base > Proxy Mobile IPv4 function which enables another entity to provide > mobility support on behalf of an unaltered and mobility-unaware IPv4 > device." > > But, I think that the PMIPv4 described in your draft seems different > from the one specified in WiMAX Forum spec (WiMAX Forum Network > Architechture stage2/3). > > Do you plan to change the PMIPv4 spec of WiMAX Forum to match your > draft? > > Best Regards, > Jun > -- ----------------------------------------------- Jun AWANO NEC System Platforms Research Laboratories Tel:+81 44 431 7638, FAX:+81 44 431 7609 -- 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 Jul 27 19:13: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 1IEZ03-0000qw-0p; Fri, 27 Jul 2007 19:13:35 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IEZ02-0000qr-0W for mip4-confirm+ok@megatron.ietf.org; Fri, 27 Jul 2007 19:13:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEZ01-0000qj-N0 for mip4@ietf.org; Fri, 27 Jul 2007 19:13:33 -0400 Received: from tyo202.gate.nec.co.jp ([202.32.8.206]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEYzz-000272-PW for mip4@ietf.org; Fri, 27 Jul 2007 19:13:33 -0400 Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.197]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l6RNDS2F004018; Sat, 28 Jul 2007 08:13:28 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l6RNDSX09643; Sat, 28 Jul 2007 08:13:28 +0900 (JST) Received: from saigo.jp.nec.com (saigo.jp.nec.com [10.26.220.6]) by mailsv5.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id l6RNDSP03977; Sat, 28 Jul 2007 08:13:28 +0900 (JST) Received: from [10.87.72.34] ([10.87.72.34] [10.87.72.34]) by mail.jp.nec.com with ESMTP; Sat, 28 Jul 2007 08:13:26 +0900 Message-Id: <46AA7C18.3040101@az.jp.nec.com> Date: Fri, 27 Jul 2007 18:13:28 -0500 From: Jun AWANO User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: "Yoshi Tsuda (yotsuda)" , mip4 Subject: Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) References: <35912544FC930E49BF20EF16C3EF2765027A4819@xmb-hkg-416.apac.cisco.com> In-Reply-To: <35912544FC930E49BF20EF16C3EF2765027A4819@xmb-hkg-416.apac.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Cc: "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 Hi Tsuda-san, O.K. Tsuda-san. I think I couldn't pick up all of differences. But I try to enumerate them. The differences are as following. 1. Terminologies draft-leung-mip4-proxy-mode says LMA,MAG,PRRQ,PRRP. But WiMAX spec doesn't use such terminologies. Just, HA, FA & PMIP Client, RRQ, RRP,respectively. 2. New extensions draft-leung-mip4-proxy-mode defines new MIPv4 extensions, Proxy Mobile IPv4 Mode Extension and PMIPv4 Per-Node Authentication Method Extension. And enfocing to use them. But WiMAX spec doesn't support them. 3. New error codes draft-leung-mip4-proxy-mode defines new error codes, PMIP_UNSUPPORTED and PMIP_DISALLOWED. But WiMAX spec doesn't use them. 4. How to use Registration Revocation When a MN moves to a new MAG. Registration Revocation message is sent to the previous MAG according to draft-leung-mip4-proxy-mode. I'm not sure it's different or not. But at least WiMAX spec doesn't say explicitly that a LMA(HA) uses Registration Revocation in this case. 5. Processing Proxy Registration Request Whole sentence described at "8.1. Processing Proxy Registration Requests" is different from WiMAX spec. A HA specified in WiMAX performs as per RFC3344. So the HA doesn't perform like described at "8.1.". i.e. The HA doen't use Sequence Number and doesn't send error RRP like described at "8.1.". 6. Moving to a New MAG I think draft-leung-mip4-proxy-mode assumes that the MAG which sends RRQ on behalf of a MN is relocated when the MN has moved to a new MAG. But In WiMAX spec, PMIP client which sends RRQ on behalf of a MN is anchored even when the MN has moved to a new FA. Are you following the proceeding of netlmm WG? And do you know Ajoy's PMIPv6 draft? http://tools.ietf.org/wg/netlmm/draft-singh-netlmm-protocol-03.txt The MAG described in the draft is anchored while moving. The PMIP client specified in WiMAX is similar to it. So, WiMAX PMIP client isn't required to transfer any MN's contexts(e.g. MN-HA key) when the MN has moved. Best Regard, Jun Yoshi Tsuda (yotsuda) wrote: > Hi Awano-san, > > What do you think the major technical differences between current > Kent's draft and the current WiMAX spec? > You know, most people in this MIP4 mailinglist doesn't have enough > time to check the specific WiMAX spec. So, we would appreciate, > if you point out the MIPv4-related technical differences instead of > just > saying different. > > Thanks in advance. > -Yoshi > >> -----Original Message----- >> From: Kent Leung (kleung) >> Sent: Friday, July 27, 2007 9:31 AM >> To: Jun AWANO; mip4 >> Subject: RE: pmipv4 of WiMAX forum (Re: >> [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) >> >> Let me clarify that we will be updating our draft, >> draft-leung-mip4-proxy-mode, accordingly to address the gaps. >> >> Kent >> >> -----Original Message----- >> From: Kent Leung (kleung) >> Sent: Friday, July 27, 2007 9:29 AM >> To: Jun AWANO; mip4 >> Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] >> Questionaboutdraft-leung-mip4-proxy-mode) >> >> Hi Jun. >> >> We are working with WiMAX Forum members to address the >> technical gaps in the draft. Currently, we are collecting >> the review comments and will update the draft accordingly. >> >> Kent >> >> -----Original Message----- >> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] >> Sent: Thursday, July 26, 2007 7:23 PM >> To: mip4 >> Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question >> aboutdraft-leung-mip4-proxy-mode) >> >> Hi, kent >> >> Please let me ask about your draft. >> >> Your draft says, >> "This document describes WiMAX Forum and 3GPP2 solution for >> the base Proxy Mobile IPv4 function which enables another >> entity to provide mobility support on behalf of an unaltered >> and mobility-unaware IPv4 device." >> >> But, I think that the PMIPv4 described in your draft seems >> different from the one specified in WiMAX Forum spec (WiMAX >> Forum Network Architechture stage2/3). >> >> Do you plan to change the PMIPv4 spec of WiMAX Forum to match >> your draft? >> >> 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 System Platforms Research Laboratories Tel:+81 44 431 7638, FAX:+81 44 431 7609 -- 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 Jul 28 01:26: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 1IEep2-0004uj-6z; Sat, 28 Jul 2007 01:26:36 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IEeoz-0004ud-Vc for mip4-confirm+ok@megatron.ietf.org; Sat, 28 Jul 2007 01:26:33 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IEeoz-0004uT-2t for mip4@ietf.org; Sat, 28 Jul 2007 01:26:33 -0400 Received: from tyo201.gate.nec.co.jp ([202.32.8.193]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEeox-0001F0-T7 for mip4@ietf.org; Sat, 28 Jul 2007 01:26:32 -0400 Received: from mailgate3.nec.co.jp (mailgate54.nec.co.jp [10.7.69.193]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id l6S5QOgC014120; Sat, 28 Jul 2007 14:26:24 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id l6S5QOu14691; Sat, 28 Jul 2007 14:26:24 +0900 (JST) Received: from kuichi.jp.nec.com (kuichi.jp.nec.com [10.26.220.17]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id l6S5QNX27529; Sat, 28 Jul 2007 14:26:23 +0900 (JST) Received: from [10.87.72.34] ([10.87.72.34] [10.87.72.34]) by mail.jp.nec.com with ESMTP; Sat, 28 Jul 2007 14:26:21 +0900 Message-Id: <46AAD381.2080401@az.jp.nec.com> Date: Sat, 28 Jul 2007 00:26:25 -0500 From: Jun AWANO User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: "Yoshi Tsuda (yotsuda)" , mip4 Subject: Re: pmipv4 of WiMAX forum (Re: [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) References: <35912544FC930E49BF20EF16C3EF2765027A4819@xmb-hkg-416.apac.cisco.com> <46AA7C18.3040101@az.jp.nec.com> In-Reply-To: <46AA7C18.3040101@az.jp.nec.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e Cc: "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 Hi Tsuda-san and Kent, I forgot to say about supporting IPv6/DS host. Of cource, draft-leung-mip4-proxy-mode could include the feature to support IPv6/DS host although WiMAX spec PMIPv4 doesn't have such a feature (at least so far). But I think there are issues about this. The first issue: The draft refers to draft-navali-ip6-over-netmip4-00 (I found out -02 ver.) to achieve support for dual stack feature. You know, mip4 WG already have dsmipv4 draft. It's draft-ietf-mip4-dsmipv4. Although some modifications might be needed to adapt draft-ietf-mip4-dsmipv4 to proxy mode. (e.g. RRQ MUST include IPv6 Tunneling Mode Ext.) Extensions defined at draft-ietf-mip4-dsmipv4 can be reused. The draft defines IPv4 Prefix Ext and IPv6 Code Ext to request, bind and get IPv6 HoA. OTOH, draft-navali-ip6-over-netmip4 defines IPv6 Home Address Request Ext and IPv6 Home Address Extension for the same aims. IMO, I don't want to have different extension to achieve the same effect. I want to reuse extensions and procedures described in draft-navali-ip6-over-netmip4 as much as possible. The second issue: I think there might be an argument about necessity of PMIPv4 DS support. Because PMIPv6 draft + IPv4 support draft can cover almost the same scenario as PMIPv4 DS can. What do you think? Thanks, Jun Jun AWANO wrote: > Hi Tsuda-san, > > O.K. Tsuda-san. > I think I couldn't pick up all of differences. > But I try to enumerate them. > > The differences are as following. > > 1. Terminologies > draft-leung-mip4-proxy-mode says > LMA,MAG,PRRQ,PRRP. > But WiMAX spec doesn't use such terminologies. > Just, HA, FA & PMIP Client, RRQ, RRP,respectively. > > 2. New extensions > draft-leung-mip4-proxy-mode defines new MIPv4 extensions, > Proxy Mobile IPv4 Mode Extension and PMIPv4 Per-Node > Authentication Method Extension. And enfocing to use them. > But WiMAX spec doesn't support them. > > 3. New error codes > draft-leung-mip4-proxy-mode defines new error codes, > PMIP_UNSUPPORTED and PMIP_DISALLOWED. > But WiMAX spec doesn't use them. > > 4. How to use Registration Revocation > When a MN moves to a new MAG. > Registration Revocation message is sent to the > previous MAG according to draft-leung-mip4-proxy-mode. > I'm not sure it's different or not. > But at least WiMAX spec doesn't say explicitly that > a LMA(HA) uses Registration Revocation in this case. > > 5. Processing Proxy Registration Request > Whole sentence described at "8.1. Processing Proxy > Registration Requests" is different from WiMAX spec. > A HA specified in WiMAX performs as per RFC3344. > So the HA doesn't perform like described at "8.1.". > i.e. The HA doen't use Sequence Number and doesn't > send error RRP like described at "8.1.". > > 6. Moving to a New MAG > I think draft-leung-mip4-proxy-mode assumes that > the MAG which sends RRQ on behalf of a MN is relocated > when the MN has moved to a new MAG. > But In WiMAX spec, PMIP client which sends RRQ on behalf > of a MN is anchored even when the MN has moved to a new FA. > Are you following the proceeding of netlmm WG? > And do you know Ajoy's PMIPv6 draft? > http://tools.ietf.org/wg/netlmm/draft-singh-netlmm-protocol-03.txt > The MAG described in the draft is anchored while moving. > The PMIP client specified in WiMAX is similar to it. > So, WiMAX PMIP client isn't required to transfer any MN's > contexts(e.g. MN-HA key) when the MN has moved. > > Best Regard, > Jun > > > Yoshi Tsuda (yotsuda) wrote: >> Hi Awano-san, >> >> What do you think the major technical differences between current >> Kent's draft and the current WiMAX spec? >> You know, most people in this MIP4 mailinglist doesn't have enough >> time to check the specific WiMAX spec. So, we would appreciate, >> if you point out the MIPv4-related technical differences instead of >> just >> saying different. >> >> Thanks in advance. >> -Yoshi >> >>> -----Original Message----- >>> From: Kent Leung (kleung) Sent: Friday, July 27, 2007 9:31 AM >>> To: Jun AWANO; mip4 >>> Subject: RE: pmipv4 of WiMAX forum (Re: >>> [Mip4]Questionaboutdraft-leung-mip4-proxy-mode) >>> >>> Let me clarify that we will be updating our draft, >>> draft-leung-mip4-proxy-mode, accordingly to address the gaps. >>> >>> Kent >>> -----Original Message----- >>> From: Kent Leung (kleung) >>> Sent: Friday, July 27, 2007 9:29 AM >>> To: Jun AWANO; mip4 >>> Subject: RE: pmipv4 of WiMAX forum (Re: [Mip4] >>> Questionaboutdraft-leung-mip4-proxy-mode) >>> >>> Hi Jun. >>> >>> We are working with WiMAX Forum members to address the technical gaps >>> in the draft. Currently, we are collecting the review comments and >>> will update the draft accordingly. >>> >>> Kent >>> -----Original Message----- >>> From: Jun AWANO [mailto:j-awano@az.jp.nec.com] >>> Sent: Thursday, July 26, 2007 7:23 PM >>> To: mip4 >>> Subject: pmipv4 of WiMAX forum (Re: [Mip4] Question >>> aboutdraft-leung-mip4-proxy-mode) >>> >>> Hi, kent >>> >>> Please let me ask about your draft. >>> >>> Your draft says, >>> "This document describes WiMAX Forum and 3GPP2 solution for the base >>> Proxy Mobile IPv4 function which enables another entity to provide >>> mobility support on behalf of an unaltered and mobility-unaware IPv4 >>> device." >>> >>> But, I think that the PMIPv4 described in your draft seems different >>> from the one specified in WiMAX Forum spec (WiMAX Forum Network >>> Architechture stage2/3). >>> >>> Do you plan to change the PMIPv4 spec of WiMAX Forum to match your >>> draft? >>> >>> 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 System Platforms Research Laboratories Tel:+81 44 431 7638, FAX:+81 44 431 7609 -- 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 Jul 30 04:40:19 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFQnb-0005gX-NI; Mon, 30 Jul 2007 04:40:19 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFQna-0005gS-Ob for mip4-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 04:40:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFQna-0005gK-F8 for mip4@ietf.org; Mon, 30 Jul 2007 04:40:18 -0400 Received: from smail5.alcatel.fr ([62.23.212.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFQnZ-000551-Jd for mip4@ietf.org; Mon, 30 Jul 2007 04:40:18 -0400 Received: from FRVELSBHS07.ad2.ad.alcatel.com (frvelsbhs07.ad2.ad.alcatel.com [155.132.6.79]) by smail5.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l6U8e7gZ004098; Mon, 30 Jul 2007 10:40:07 +0200 Received: from [172.27.205.222] ([172.27.205.222]) by FRVELSBHS07.ad2.ad.alcatel.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.2499); Mon, 30 Jul 2007 10:40:14 +0200 Message-ID: <46ADA3EE.5090306@alcatel-lucent.fr> Date: Mon, 30 Jul 2007 10:40:14 +0200 From: Bruno Mongazon-Cazavet User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: "Kent Leung (kleung)" Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode References: <2979E38DD6FC6544B789C8DAD7BAFC520445EA5E@xmb-sjc-235.amer.cisco.com> In-Reply-To: <2979E38DD6FC6544B789C8DAD7BAFC520445EA5E@xmb-sjc-235.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Jul 2007 08:40:14.0606 (UTC) FILETIME=[3FCA62E0:01C7D285] X-Scanned-By: MIMEDefang 2.51 on 155.132.188.13 X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 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 Kent Leung (kleung) wrote: > The router which implements the MIP4 proxy mode may not be enabled with > FA service. In such case, collocated Care-of Address may be used for > Mobile IP registration/tunneling. > > I think your question is based on the need for the mobile terminal to > learn if the network supports PMIP and/or MIP. Is this in the context > of WiMAX or just generic MIP? > Generic MIP. > For generic MIP, a MIP-enabled terminal also supports simple IP. If the > terminal is using the MIP Home Address, then it must register with its > HA via FA CoA or CCoA to maintain its communications. If a CCoA address > is available, the terminal may use that IP address as well. Not clear > if the terminal needs to know if this IP address is provided mobility by > the network? For PMIP, this is suppose to be transparent to the mobile > terminal. Of course, the terminal can detect if the CCoA is still > usable after handover via DHCP, ARP, and/or ICMP mechanisms without > having to know what the network is doing. > Of course such mechanisms can be used. I am just wondering if a simple and common mechanism can be used to do so. Would be more simple and direct to send a RS and get back the answer in a RA. This does not impact existing simple IP terminals that would not send RS, but only MIP capable. Just to ease the job, not contradicting MIP philosophy i guess. > For WiMAX case, we should probably discuss this on the NWG alias. > > Kent > > -----Original Message----- > From: Bruno Mongazon-Cazavet > [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] > Sent: Thursday, July 26, 2007 6:17 AM > To: Kent Leung (kleung) > Cc: Mobile IPv4 Mailing List > Subject: Re: [Mip4] Question about draft-leung-mip4-proxy-mode > > Kent Leung (kleung) wrote: > >> Hi Bruno. Sorry, I missed this question. >> >> In this case, the Router Advertisement will not have the Mobility >> Agent Advertisement Extension. >> >> > Since a router implementing MIP4 proxy mode includes FA function, isn't > it logical and consistent to include a Mobility Agent Advertisment > extension in RA to indicate FA support? > I would suggest this behaviour can be added to your draft, possibly > extending the Mobility Agent Advertisment extension to indicate PMIP > support (i think some place is left for RFU in the format). > > What do you think? > > Such addition is not intended to be processed (understandable) by simple > IP terminals, but rather by terminals that might behave as simple IP or > MIP and need to choose which protocol to use. > > Thanks in advance for your reply. > Bruno. > >> Kent >> >> -----Original Message----- >> From: Bruno Mongazon-Cazavet >> [mailto:bruno.mongazon-cazavet@alcatel-lucent.fr] >> Sent: Thursday, July 19, 2007 8:48 AM >> To: Mobile IPv4 Mailing List >> Subject: [Mip4] Question about draft-leung-mip4-proxy-mode >> >> Hello, >> >> When a router implements this draft, how should it reacts to Router >> Solicitation? >> In particular: >> -should the router fill the Mobility Agent Advertisement extension in >> the reply? >> -should the FA capability be set if only PMIP is supported? >> >> Thanks, Bruno. >> >> >> -- >> 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 Mon Jul 30 06:40: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 1IFSfT-0000Ty-MS; Mon, 30 Jul 2007 06:40:03 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFSfR-0000TW-UJ for mip4-confirm+ok@megatron.ietf.org; Mon, 30 Jul 2007 06:40:02 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFSfR-0000TK-Im; Mon, 30 Jul 2007 06:40:01 -0400 Received: from [202.99.23.227] (helo=people.com.cn) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IFSfQ-0000MU-J2; Mon, 30 Jul 2007 06:40:01 -0400 Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm5746adc77c; Mon, 30 Jul 2007 18:51:52 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id jm2246a77910; Wed, 25 Jul 2007 19:59:38 +0800 Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC 2.9.5.8) with SMTP id AISP action; Wed, 25 Jul 2007 19:59:38 +0800 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDM6x-00089I-Jq; Tue, 24 Jul 2007 11:15:43 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDM6o-0007vz-J1; Tue, 24 Jul 2007 11:15:34 -0400 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDM6m-00019X-HZ; Tue, 24 Jul 2007 11:15:34 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 671C43296B; Tue, 24 Jul 2007 15:15:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1IDM6I-0002JC-95; Tue, 24 Jul 2007 11:15: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: Tue, 24 Jul 2007 11:15:02 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Archive: X-AIMC-AUTH: (null) X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org X-AIMC-AUTH: (null) X-AIMC-MAILFROM: Internet-Drafts@ietf.org X-Auto-Forward: jaglee@people.com.cn jag@kw.com.cn X-Spam-Score: 2.8 (++) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: mip4@ietf.org Subject: [Mip4] I-D ACTION:draft-ietf-mip4-gen-ext-04.txt X-BeenThere: mip4@ietf.org Reply-To: internet-drafts@ietf.org 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 Extension for Configuration Options Exchange Author(s) : J. Bharatia, et al. Filename : draft-ietf-mip4-gen-ext-04.txt Pages : 13 Date : 2007-7-24 This document describes the mechanism for providing the host configuration information during Mobile IP registration. One or more Configuration Options Exchange Extensions may be included in the registration message to provide the Mobile Node the configuration parameters needed for network service (e.g. DNS). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-04.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-gen-ext-04.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-gen-ext-04.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-7-24105051.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-gen-ext-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-gen-ext-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-7-24105051.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/ --NextPart-- From mip4-bounces@ietf.org Tue Jul 31 10:05: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 1IFsLm-0003jV-E5; Tue, 31 Jul 2007 10:05:26 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFsLk-0003it-93 for mip4-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 10:05:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFsLi-0003ia-H0; Tue, 31 Jul 2007 10:05:23 -0400 Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IFsLi-0001EA-4M; Tue, 31 Jul 2007 10:05:22 -0400 X-VirusChecked: Checked X-Env-Sender: pete.mccann@motorola.com X-Msg-Ref: server-11.tower-153.messagelabs.com!1185890720!4908425!1 X-StarScan-Version: 5.5.12.11; banners=-,-,- X-Originating-IP: [144.189.100.102] Received: (qmail 27136 invoked from network); 31 Jul 2007 14:05:20 -0000 Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102) by server-11.tower-153.messagelabs.com with SMTP; 31 Jul 2007 14:05:20 -0000 Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232]) by motgate4.mot.com (8.12.11/Motorola) with ESMTP id l6VE5KpC012757; Tue, 31 Jul 2007 07:05:20 -0700 (MST) Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18]) by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id l6VE1JID023983; Tue, 31 Jul 2007 09:01:19 -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: Tue, 31 Jul 2007 10:01:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-mip4-gen-ext-03.txt Thread-Index: AcfTe0Ke/BKsgd15SyWMrcjFTjhBOw== From: "McCann Peter-A001034" To: , X-Spam-Score: -4.0 (----) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: Subject: [Mip4] draft-ietf-mip4-gen-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 A question has arisen during the last call for=20 draft-ietf-mip4-gen-ext-03.txt. The draft includes the following text: There are mechanisms such as DHCP for the mobile node to configure information from the foreign network, but not from the home network when the mobile node is not attached to the home network. However, this may not be strictly true. In particular, it might be possible to use a DHCPINFORM message through the tunnel that was established with Mobile IP, thus eliminating the need to encode DHCP options inside Mobile IP messages. This would allow for a single configuration protocol to be used whether the MN is at home or visiting. I think we may have touched on this question during our last chartering discussion but we might not have explored all the ramifications. Please, if you have an opinion either way=20 express it now and give some background as to why you think so. It is possible that we might turn this draft into a BCP-like document for how to configure and run DHCP over the tunnel to the home network. -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 Tue Jul 31 12:39:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFuks-00083q-3L; Tue, 31 Jul 2007 12:39:30 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFukq-00083i-FD for mip4-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 12:39:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFukq-00083Z-5b; Tue, 31 Jul 2007 12:39:28 -0400 Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IFukn-0006sD-V2; Tue, 31 Jul 2007 12:39:28 -0400 Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com [47.103.123.72]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l6VGdNO29678; Tue, 31 Jul 2007 16:39:23 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] draft-ietf-mip4-gen-ext-03.txt Date: Tue, 31 Jul 2007 11:37:58 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Mip4] draft-ietf-mip4-gen-ext-03.txt Thread-Index: AcfTe0Ke/BKsgd15SyWMrcjFTjhBOwAFKorw From: "Jayshree Bharatia" To: "McCann Peter-A001034" X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: dhcwg@ietf.org, 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 Pete, The proposal in this draft was always considered as an alternative over DHCP. There was never an intent saying that the mechanism discussed in this draft is the only way to exchange configuration information between two Mobile IP entities. This draft has been there for a long time and honestly, I have lost track of who provided which comment which resulted in the statement you quoted. We have already gone through multiple WGLC on this draft and I don't necessary agree on the change of status at this time.=20 Regards, Jayshree -----Original Message----- From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20 Sent: Tuesday, July 31, 2007 9:01 AM To: mip4@ietf.org; dhcwg@ietf.org Subject: [Mip4] draft-ietf-mip4-gen-ext-03.txt A question has arisen during the last call for=20 draft-ietf-mip4-gen-ext-03.txt. The draft includes the following text: There are mechanisms such as DHCP for the mobile node to configure information from the foreign network, but not from the home network when the mobile node is not attached to the home network. However, this may not be strictly true. In particular, it might be possible to use a DHCPINFORM message through the tunnel that was established with Mobile IP, thus eliminating the need to encode DHCP options inside Mobile IP messages. This would allow for a single configuration protocol to be used whether the MN is at home or visiting. I think we may have touched on this question during our last chartering discussion but we might not have explored all the ramifications. Please, if you have an opinion either way=20 express it now and give some background as to why you think so. It is possible that we might turn this draft into a BCP-like document for how to configure and run DHCP over the tunnel to the home network. -Pete --=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 Tue Jul 31 13:19:30 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvNZ-00045f-UQ; Tue, 31 Jul 2007 13:19:29 -0400 Received: from mip4 by megatron.ietf.org with local (Exim 4.43) id 1IFvNX-00045A-Sb for mip4-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 13:19:27 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvNX-000450-Hf; Tue, 31 Jul 2007 13:19:27 -0400 Received: from mail2.azairenet.com ([207.47.15.6]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFvNW-0001Rm-Uq; Tue, 31 Jul 2007 13:19:27 -0400 Received: from [127.0.0.1] ([207.47.15.6]) by mail2.azairenet.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Jul 2007 10:19:25 -0700 Message-ID: <46AF6F1C.3000408@azairenet.com> Date: Tue, 31 Jul 2007 10:19:24 -0700 From: Vijay Devarapalli User-Agent: Thunderbird 2.0.0.5 (Windows/20070716) MIME-Version: 1.0 To: Jayshree Bharatia Subject: Re: [Mip4] draft-ietf-mip4-gen-ext-03.txt References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Jul 2007 17:19:25.0815 (UTC) FILETIME=[F1C56870:01C7D396] X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: dhcwg@ietf.org, mip4@ietf.org, McCann Peter-A001034 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 Well, the statement is still valid. There is no document that describes how to run DHCP over the Mobile IPv4 tunnel. (it may be obvious to some folks but not to all). I guess what we need to decide is whether we want a document that describes how to run DHCP over the Mobile IPv4 tunnel or still go with the mechanism described in draft-ietf-mip4-gen-ext. Vijay Jayshree Bharatia wrote: > Hi Pete, > > The proposal in this draft was always considered as an alternative over > DHCP. There was never an intent saying that the mechanism discussed in > this draft is the only way to exchange configuration information between > two Mobile IP entities. This draft has been there for a long time and > honestly, I have lost track of who provided which comment which resulted > in the statement you quoted. > > We have already gone through multiple WGLC on this draft and I don't > necessary agree on the change of status at this time. > > Regards, > Jayshree > > -----Original Message----- > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com] > Sent: Tuesday, July 31, 2007 9:01 AM > To: mip4@ietf.org; dhcwg@ietf.org > Subject: [Mip4] draft-ietf-mip4-gen-ext-03.txt > > > A question has arisen during the last call for > draft-ietf-mip4-gen-ext-03.txt. > > The draft includes the following text: > > There are mechanisms > such as DHCP for the mobile node to configure information from the > foreign network, but not from the home network when the mobile node > is not attached to the home network. > > However, this may not be strictly true. In particular, > it might be possible to use a DHCPINFORM message through > the tunnel that was established with Mobile IP, thus eliminating the > need to encode DHCP options inside Mobile IP messages. This would allow > for a single configuration protocol to be used whether the MN is at home > or visiting. > > I think we may have touched on this question during our last chartering > discussion but we might not have explored all the ramifications. > Please, if you have an opinion either way > express it now and give some background as to why you think so. It is > possible that we might turn this draft into a BCP-like document for how > to configure and run DHCP over the tunnel to the home network. > > -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/