From exim@www1.ietf.org Sat Jan 3 14:55:11 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10412 for ; Sat, 3 Jan 2004 14:55:11 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcrrA-0005VC-BR for mip4-archive@odin.ietf.org; Sat, 03 Jan 2004 14:54:44 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i03JsilH021146 for mip4-archive@odin.ietf.org; Sat, 3 Jan 2004 14:54:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcrrA-0005Uz-7y for mip4-web-archive@optimus.ietf.org; Sat, 03 Jan 2004 14:54:44 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10400 for ; Sat, 3 Jan 2004 14:54:41 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Acrr7-0007XP-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 14:54:41 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Acrp7-0007QP-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 14:52:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AcrnY-0007LJ-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 14:51:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Acrna-0005MR-80; Sat, 03 Jan 2004 14:51:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcrnF-0005Lc-F0 for mip4@optimus.ietf.org; Sat, 03 Jan 2004 14:50:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10321 for ; Sat, 3 Jan 2004 14:50:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcrnC-0007Jp-00 for mip4@ietf.org; Sat, 03 Jan 2004 14:50:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcrlN-0007ET-00 for mip4@ietf.org; Sat, 03 Jan 2004 14:48:45 -0500 Received: from apollo.tilted.net ([69.36.45.132]) by ietf-mx with esmtp (Exim 4.12) id 1Acrko-00079R-00 for mip4@ietf.org; Sat, 03 Jan 2004 14:48:10 -0500 Received: from internet5xupq7 (adsl-65-42-95-84.dsl.chcgil.ameritech.net [65.42.95.84]) (authenticated) by apollo.tilted.net (8.11.6/8.11.6) with ESMTP id i03Jm9H06610 for ; Sat, 3 Jan 2004 13:48:10 -0600 Message-Id: <200401031948.i03Jm9H06610@apollo.tilted.net> From: "Neil Barnett " To: Date: Sat, 3 Jan 2004 13:48:17 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C3D200.3FC00E50" X-Mailer: Microsoft Office Outlook, Build 11.0.5329 Thread-Index: AcPSMogYavT2/9jqRleUh+e6N2zlaA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: [Mip4] Is this List Active ? Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_60_70, HTML_FONT_FACE_BAD,HTML_MESSAGE,MISSING_OUTLOOK_NAME autolearn=no version=2.60 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C3D200.3FC00E50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Is this list active and operational ? Anyone ------=_NextPart_000_0006_01C3D200.3FC00E50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Is this List Active ?

Is this list active and operational ? Anyone  =


        

------=_NextPart_000_0006_01C3D200.3FC00E50-- -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Sat Jan 3 15:39:03 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12426 for ; Sat, 3 Jan 2004 15:39:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcsXa-0006wz-Cy for mip4-archive@odin.ietf.org; Sat, 03 Jan 2004 15:38:34 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i03KcY7G026711 for mip4-archive@odin.ietf.org; Sat, 3 Jan 2004 15:38:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcsXa-0006wk-5R for mip4-web-archive@optimus.ietf.org; Sat, 03 Jan 2004 15:38:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12416 for ; Sat, 3 Jan 2004 15:38:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcsXY-0001On-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 15:38:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcsVh-0001Km-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 15:36:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AcsUA-0001HF-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 15:35:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcsUB-0006ZY-1M; Sat, 03 Jan 2004 15:35:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcsTj-0006Ys-MI for mip4@optimus.ietf.org; Sat, 03 Jan 2004 15:34:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12321 for ; Sat, 3 Jan 2004 15:34:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcsTi-0001Fe-00 for mip4@ietf.org; Sat, 03 Jan 2004 15:34:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcsRp-0001CQ-00 for mip4@ietf.org; Sat, 03 Jan 2004 15:32:37 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AcsQa-00018z-00 for mip4@ietf.org; Sat, 03 Jan 2004 15:31:20 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AcsQW-0006wF-00; Sat, 03 Jan 2004 21:31:16 +0100 Date: Sat, 3 Jan 2004 21:31:12 +0100 From: Henrik Levkowetz To: "Neil Barnett " Cc: Subject: Re: [Mip4] Is this List Active ? Message-Id: <20040103213112.492eaad9.henrik@levkowetz.com> In-Reply-To: <200401031948.i03Jm9H06610@apollo.tilted.net> References: <200401031948.i03Jm9H06610@apollo.tilted.net> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Saturday 3 January 2004, Neil Barnett wrote: > Is this list active and operational ? Anyone Oh, yes. It's just the holiday quiet :-) Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Sat Jan 3 23:35:09 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23786 for ; Sat, 3 Jan 2004 23:35:09 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AczyL-0003lV-Kd for mip4-archive@odin.ietf.org; Sat, 03 Jan 2004 23:34:41 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i044YfnZ014469 for mip4-archive@odin.ietf.org; Sat, 3 Jan 2004 23:34:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AczyL-0003lI-Fo for mip4-web-archive@optimus.ietf.org; Sat, 03 Jan 2004 23:34:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23755 for ; Sat, 3 Jan 2004 23:34:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AczyJ-00039R-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 23:34:39 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AczwT-000360-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 23:32:45 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aczun-00032F-00 for mip4-web-archive@ietf.org; Sat, 03 Jan 2004 23:31:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aczun-0003ag-85; Sat, 03 Jan 2004 23:31:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aczua-0003aK-ME for mip4@optimus.ietf.org; Sat, 03 Jan 2004 23:30:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23654 for ; Sat, 3 Jan 2004 23:30:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AczuY-000314-00 for mip4@ietf.org; Sat, 03 Jan 2004 23:30:46 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aczsi-0002xJ-00 for mip4@ietf.org; Sat, 03 Jan 2004 23:28:52 -0500 Received: from apollo.tilted.net ([69.36.45.132]) by ietf-mx with esmtp (Exim 4.12) id 1AczrA-0002so-00 for mip4@ietf.org; Sat, 03 Jan 2004 23:27:16 -0500 Received: from internet5xupq7 (adsl-65-42-95-84.dsl.chcgil.ameritech.net [65.42.95.84]) (authenticated) by apollo.tilted.net (8.11.6/8.11.6) with ESMTP id i044RCH10540; Sat, 3 Jan 2004 22:27:13 -0600 Message-Id: <200401040427.i044RCH10540@apollo.tilted.net> From: "Neil Barnett " To: "'Henrik Levkowetz'" Cc: Subject: RE: [Mip4] Is this List Active ? Date: Sat, 3 Jan 2004 22:27:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5329 Thread-Index: AcPSORQthP1jQHX3TIG68mqlyTMtVQAQd5jQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <20040103213112.492eaad9.henrik@levkowetz.com> Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Cool Thanks, Just wondering. -----Original Message----- From: mip4-admin@ietf.org [mailto:mip4-admin@ietf.org] On Behalf Of Henrik Levkowetz Sent: Saturday, January 03, 2004 2:31 PM To: Neil Barnett Cc: mip4@ietf.org Subject: Re: [Mip4] Is this List Active ? Saturday 3 January 2004, Neil Barnett wrote: > Is this list active and operational ? Anyone Oh, yes. It's just the holiday quiet :-) Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 10:02:38 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13373 for ; Wed, 7 Jan 2004 10:02:37 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFCD-0007iB-H2 for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 10:02:10 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07F29WK029642 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 10:02:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFCD-0007i1-Ad for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 10:02:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13321 for ; Wed, 7 Jan 2004 10:02:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFCB-0007SP-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:02:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFAL-0007O9-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:00:13 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeF9B-0007K4-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 09:59:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeF9B-0007Zh-EU; Wed, 07 Jan 2004 09:59:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeF8F-0007Ya-MH for mip4@optimus.ietf.org; Wed, 07 Jan 2004 09:58:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13181 for ; Wed, 7 Jan 2004 09:58:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeF8D-0007Hx-00 for mip4@ietf.org; Wed, 07 Jan 2004 09:58:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeF6I-0007EB-00 for mip4@ietf.org; Wed, 07 Jan 2004 09:56:03 -0500 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1AeF4a-000787-00 for mip4@ietf.org; Wed, 07 Jan 2004 09:54:17 -0500 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jan 2004 09:53:46 -0500 Message-ID: <9E3BA3946476AD4EB94672712B12A85F03AB13@ftmail.lab.flarion.com> From: Tsirtsis George To: "'Henrik Levkowetz'" , Pete McCann Cc: Alpesh , mip4@ietf.org Subject: RE: [Mip4] WG adoption call on draft-patel-mobileip-experimental -messages-02.txt Date: Wed, 7 Jan 2004 09:53:43 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 All, Happy New Year... Did you guys consider Vendor Specific Mobile IP message Types as well as experimental types. Note that we currently have vendor specific extensions but no vendor specific message types. Thanks George -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 10:30:39 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15367 for ; Wed, 7 Jan 2004 10:30:39 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFdJ-0000Ul-Vi for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 10:30:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07FU92n001903 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 10:30:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFdJ-0000Uc-NG for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 10:30:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15291 for ; Wed, 7 Jan 2004 10:30:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFdH-0000nX-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:30:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFbO-0000iA-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:28:11 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeFaG-0000eB-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:27:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFaI-0000IL-0h; Wed, 07 Jan 2004 10:27:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFZV-0000HG-H8 for mip4@optimus.ietf.org; Wed, 07 Jan 2004 10:26:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15171 for ; Wed, 7 Jan 2004 10:26:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFZT-0000cT-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:26:11 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFXa-0000Y8-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:24:15 -0500 Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AeFWO-0000Tz-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:23:00 -0500 Received: from nwsgpa.ih.lucent.com (h135-1-121-22.lucent.com [135.1.121.22]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i07FLre09875; Wed, 7 Jan 2004 09:21:53 -0600 (CST) Received: from mccap-1.lucent.com by nwsgpa.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2) id i07FLpF19536; Wed, 7 Jan 2004 09:21:51 -0600 (CST) Received: from [127.0.0.1] (helo=MCCAP-1.lucent.com) by mccap-1.lucent.com with esmtp (Exim 4.04) id HR4LB1-0000QW-00; Wed, 07 Jan 2004 10:21:01 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16380.9176.533904.461330@gargle.gargle.HOWL> Date: Wed, 7 Jan 2004 09:20:56 -0600 From: Pete McCann To: Tsirtsis George Cc: "'Henrik Levkowetz'" , Alpesh , mip4@ietf.org Subject: RE: [Mip4] WG adoption call on draft-patel-mobileip-experimental -messages-02.txt In-Reply-To: <9E3BA3946476AD4EB94672712B12A85F03AB13@ftmail.lab.flarion.com> References: <9E3BA3946476AD4EB94672712B12A85F03AB13@ftmail.lab.flarion.com> X-Mailer: VM 7.14 under 21.5 (beta14) "cassava" XEmacs Lucid Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, George, I think this was discussed as part of the Experimental message types question, and there was a strong push from ADs that we NOT pursue vendor-specific messages. They would allow for too much uncontrolled protocol growth in unpredictable ways, with negative implications for interoperability. -Pete Tsirtsis George writes: > All, > > Happy New Year... > > > Did you guys consider Vendor Specific Mobile IP message Types as well as > experimental types. Note that we currently have vendor specific extensions > but no vendor specific message types. > > Thanks > George -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 10:32:51 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15484 for ; Wed, 7 Jan 2004 10:32:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFfT-0000Z6-3e for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 10:32:23 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07FWLId002156 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 10:32:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFfO-0000Yb-Sa for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 10:32:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15455 for ; Wed, 7 Jan 2004 10:32:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFfM-0000wi-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:32:16 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFdd-0000rJ-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:30:29 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeFcB-0000kh-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:28:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFcD-0000N9-1M; Wed, 07 Jan 2004 10:29:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFbK-0000MA-M2 for mip4@optimus.ietf.org; Wed, 07 Jan 2004 10:28:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15223 for ; Wed, 7 Jan 2004 10:28:03 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFbI-0000gu-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:28:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFZX-0000dB-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:26:15 -0500 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1AeFYG-0000Yv-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:24:56 -0500 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jan 2004 10:24:27 -0500 Message-ID: <9E3BA3946476AD4EB94672712B12A85F03AB15@ftmail.lab.flarion.com> From: Tsirtsis George To: "'Pete McCann'" Cc: "'Henrik Levkowetz'" , Alpesh , mip4@ietf.org Subject: RE: [Mip4] WG adoption call on draft-patel-mobileip-experimental -messages-02.txt Date: Wed, 7 Jan 2004 10:24:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 While now unpredictable growth will happen in a totally uncoordinated way (i.e.: people will just grab message types) which I am sure will help interoperability ....oh well ;-] George > -----Original Message----- > From: Pete McCann [mailto:mccap@lucent.com] > Sent: Wednesday, January 07, 2004 3:21 PM > To: Tsirtsis George > Cc: 'Henrik Levkowetz'; Alpesh; mip4@ietf.org > Subject: RE: [Mip4] WG adoption call on > draft-patel-mobileip-experimental -messages-02.txt > > > > Hi, George, > > I think this was discussed as part of the Experimental message types > question, and there was a strong push from ADs that we NOT pursue > vendor-specific messages. They would allow for too much uncontrolled > protocol growth in unpredictable ways, with negative implications for > interoperability. > > -Pete > > Tsirtsis George writes: > > All, > > > > Happy New Year... > > > > > > Did you guys consider Vendor Specific Mobile IP message > Types as well as > > experimental types. Note that we currently have vendor > specific extensions > > but no vendor specific message types. > > > > Thanks > > George > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 10:34:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15561 for ; Wed, 7 Jan 2004 10:34:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFh5-0000bJ-1L for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 10:34:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07FY2U0002303 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 10:34:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFh4-0000b4-8G for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 10:34:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15528 for ; Wed, 7 Jan 2004 10:33:58 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFh1-0000zp-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:34:00 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFf5-0000u5-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:32:00 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeFdA-0000mN-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:30:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFdB-0000RE-J2; Wed, 07 Jan 2004 10:30:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Advzd-0003e4-3C for mip4@optimus.ietf.org; Tue, 06 Jan 2004 13:31:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28057 for ; Tue, 6 Jan 2004 13:31:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Advza-0001pE-00 for mip4@ietf.org; Tue, 06 Jan 2004 13:31:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Advxn-0001k2-00 for mip4@ietf.org; Tue, 06 Jan 2004 13:29:59 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=shiraz.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1Advwo-0001eQ-00 for mip4@ietf.org; Tue, 06 Jan 2004 13:28:59 -0500 Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=shiraz) by shiraz.levkowetz.com with esmtp (Exim 3.35 #1 (Debian)) id 1Advwn-0003NH-00 for ; Tue, 06 Jan 2004 19:28:57 +0100 Content-Type: text/plain; charset=utf-8 To: mip4@ietf.org From: Alpesh Reply-To: Mip4 issue tracker Date: Tue, 06 Jan 2004 18:28:55 +0000 MIME-Version: 1.0 Message-Id: <1073413735.86.0.82505581673.issue43@mip4.org> X-Roundup-Name: Mip4 issue tracker X-Roundup-Loop: hello Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [Mip4] [issue43] Experimental (sub) option type for existing options? Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable This has been entered in the issue tracker as issue 43. owner: Alpesh : category: Technical draft: draft-ietf-mip4-experimental-messages priority: Should fix status: No discussion title: Experimental (sub) option type for existing options? Hi - We have one open issue for this draft -=20 Description: Should we define an experimental sub-type for existing options? One school of thought is that this is not needed as the experiemental exten= sion types permits us to achieve this. By using the experimental extension type,= one can use all the sub-types in that type for experimentation.=20 Other school of thought is that for existing options, if any experimentatio= n is needed we can use an experimental sub-type from that type. Once ready for standardization almost no code change is required to change that experiment= al sub-type to use a standard sub-type. We need the WG comments to resolve this issue and move on to the next level. Your prompt attention in this regards is highly appreciated. Please let me = know if you need further clarification. Thanks Alpesh _________________________________________________ Mip4 issue tracker _________________________________________________ -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 10:50:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16053 for ; Wed, 7 Jan 2004 10:50:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFwc-0001Lk-Lf for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 10:50:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Fo6PZ005182 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 10:50:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFwc-0001LV-ID for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 10:50:06 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16042 for ; Wed, 7 Jan 2004 10:50:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFwa-0001ut-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:50:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFuv-0001rI-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:48:22 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeFtc-0001lE-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 10:47:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFtd-00019G-5m; Wed, 07 Jan 2004 10:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeFtY-00018o-Vb for mip4@optimus.ietf.org; Wed, 07 Jan 2004 10:46:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15927 for ; Wed, 7 Jan 2004 10:46:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeFtW-0001kH-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:46:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeFrh-0001ZG-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:45:01 -0500 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1AeFqV-0001NH-00 for mip4@ietf.org; Wed, 07 Jan 2004 10:43:47 -0500 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jan 2004 10:43:19 -0500 Message-ID: <9E3BA3946476AD4EB94672712B12A85F03AB18@ftmail.lab.flarion.com> From: Tsirtsis George To: mip4@ietf.org Subject: RE: [Mip4] [issue43] Experimental (sub) option type for existing options? Date: Wed, 7 Jan 2004 10:43:15 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="utf-8" Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 How is this covering Vendor-specific types? It looks like it is about experimental sub-types....or am I missing the point? George > -----Original Message----- > From: mip4-admin@ietf.org [mailto:mip4-admin@ietf.org]On Behalf Of > Alpesh > Sent: Tuesday, January 06, 2004 6:29 PM > To: mip4@ietf.org > Subject: [Mip4] [issue43] Experimental (sub) option type for existing > options? > > > > This has been entered in the issue tracker as issue 43. > > owner: Alpesh : > > category: Technical > draft: draft-ietf-mip4-experimental-messages > priority: Should fix > status: No discussion > title: Experimental (sub) option type for existing options? > > Hi - > > We have one open issue for this draft - > > Description: Should we define an experimental sub-type for > existing options? > > One school of thought is that this is not needed as the > experiemental extension > types permits us to achieve this. By using the experimental > extension type, one > can use all the sub-types in that type for experimentation. > > Other school of thought is that for existing options, if any > experimentation is > needed we can use an experimental sub-type from that type. > Once ready for > standardization almost no code change is required to change > that experimental > sub-type to use a standard sub-type. > > We need the WG comments to resolve this issue and move on to > the next level. > Your prompt attention in this regards is highly appreciated. > Please let me know > if you need further clarification. > > Thanks > Alpesh > _________________________________________________ > Mip4 issue tracker > > _________________________________________________ > > -- > Mip4 mailing list > Mip4@ietf.org > https://www.ietf.org/mailman/listinfo/mip4 > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 12:12:36 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19332 for ; Wed, 7 Jan 2004 12:12:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHE0-0005G7-PP for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 12:12:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07HC8Ux020212 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 12:12:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHE0-0005Fv-FY for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 12:12:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19296 for ; Wed, 7 Jan 2004 12:12:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHDz-0006Et-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:12:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeHCO-00069W-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:10:29 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AeHB7-00062Y-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:09:10 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AeHB8-00031a-OY for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:09:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHAz-00056G-Dm; Wed, 07 Jan 2004 12:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHAS-00053M-CS for mip4@optimus.ietf.org; Wed, 07 Jan 2004 12:08:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19081 for ; Wed, 7 Jan 2004 12:08:25 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHAR-0005yU-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:08:27 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeH8U-0005rb-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:06:27 -0500 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AeH7C-0005k9-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:05:07 -0500 Received: from nwsgpa.ih.lucent.com (h135-1-121-22.lucent.com [135.1.121.22]) by hoemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i07H4Ka25738; Wed, 7 Jan 2004 11:04:21 -0600 (CST) Received: from mccap-1.lucent.com by nwsgpa.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2) id i07H4JF21593; Wed, 7 Jan 2004 11:04:19 -0600 (CST) Received: from [127.0.0.1] (helo=MCCAP-1.lucent.com) by mccap-1.lucent.com with esmtp (Exim 4.04) id HR4Q1T-0000IW-00; Wed, 07 Jan 2004 12:03:29 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16380.15328.327904.809869@gargle.gargle.HOWL> Date: Wed, 7 Jan 2004 11:03:28 -0600 From: Pete McCann To: Tsirtsis George Cc: "'Henrik Levkowetz'" , Alpesh , mip4@ietf.org Subject: RE: [Mip4] WG adoption call on draft-patel-mobileip-experimental -messages-02.txt In-Reply-To: <9E3BA3946476AD4EB94672712B12A85F03AB15@ftmail.lab.flarion.com> References: <9E3BA3946476AD4EB94672712B12A85F03AB15@ftmail.lab.flarion.com> X-Mailer: VM 7.14 under 21.5 (beta14) "cassava" XEmacs Lucid Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Perhaps true, but everyone should realize that this happens without the blessing of IANA and the numbers are still available for use by IETF consensus documents. -Pete Tsirtsis George writes: > While now unpredictable growth will happen in a totally uncoordinated way > (i.e.: people will just grab message types) which I am sure will help > interoperability ....oh well ;-] > > George > > > -----Original Message----- > > From: Pete McCann [mailto:mccap@lucent.com] > > Sent: Wednesday, January 07, 2004 3:21 PM > > To: Tsirtsis George > > Cc: 'Henrik Levkowetz'; Alpesh; mip4@ietf.org > > Subject: RE: [Mip4] WG adoption call on > > draft-patel-mobileip-experimental -messages-02.txt > > > > > > > > Hi, George, > > > > I think this was discussed as part of the Experimental message types > > question, and there was a strong push from ADs that we NOT pursue > > vendor-specific messages. They would allow for too much uncontrolled > > protocol growth in unpredictable ways, with negative implications for > > interoperability. > > > > -Pete > > > > Tsirtsis George writes: > > > All, > > > > > > Happy New Year... > > > > > > > > > Did you guys consider Vendor Specific Mobile IP message > > Types as well as > > > experimental types. Note that we currently have vendor > > specific extensions > > > but no vendor specific message types. > > > > > > Thanks > > > George > > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 12:46:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22134 for ; Wed, 7 Jan 2004 12:46:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHkq-0007qs-GE for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 12:46:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07Hk4bv030176 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 12:46:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHkq-0007qd-BP for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 12:46:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22006 for ; Wed, 7 Jan 2004 12:46:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHko-0002Hq-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:46:02 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeHis-00028a-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:44:03 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AeHgw-0001nu-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:42:02 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AeHgx-0006HS-9n for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:42:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHgu-0007QY-RY; Wed, 07 Jan 2004 12:42:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHg7-0007Lr-PA for mip4@optimus.ietf.org; Wed, 07 Jan 2004 12:41:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21248 for ; Wed, 7 Jan 2004 12:41:08 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHg6-0001fn-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:41:10 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeHcz-00011d-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:37:57 -0500 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1AeHaF-0000MY-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:35:08 -0500 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72) id ; Wed, 7 Jan 2004 12:34:36 -0500 Message-ID: <9E3BA3946476AD4EB94672712B12A85F03AB1A@ftmail.lab.flarion.com> From: Tsirtsis George To: "'Kent Leung'" Cc: mip4@ietf.org Subject: RE: [Mip4] [issue43] Experimental (sub) option type for existing options? Date: Wed, 7 Jan 2004 12:34:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 OK, this is clear enough. Thanks George > -----Original Message----- > From: Kent Leung [mailto:kleung@cisco.com] > Sent: Wednesday, January 07, 2004 5:05 PM > To: Tsirtsis George > Cc: mip4@ietf.org > Subject: RE: [Mip4] [issue43] Experimental (sub) option type for > existing options? > > > This is not about vendor specific types. Here's a quick summary of > the goals of the experimental and vendor specific drafts/RFC. > > 1) Experimental messages and extensions (only type defined) to support > research and experimentation. > > The issue here is should there be a universal > experimental subtype > for extensions as well (this means the same subtype number is > reserved for experiments in all extension types)? I > don't think we > need this since experimental type should suffice from > the functional > perspective. > > 2) Vendor specific extensions are defined to support vendor > capabilities > to standard messages. > > If vendors need messages, the experimental messages > would be ideal > to use for experimentation and inter-operation. Once > the idea has been > baked and determined to be useful for deployment, then > it should be > proposed to WG to obtain IANA message types for real > world deployment. > > Just my perception of the differences and objectives of the > experimental > and vendor draft/RFC. > > Kent > > At 10:43 AM 1/7/2004 -0500, Tsirtsis George wrote: > >How is this covering Vendor-specific types? It looks like it is about > >experimental sub-types....or am I missing the point? > > > >George > > > > > -----Original Message----- > > > From: mip4-admin@ietf.org [mailto:mip4-admin@ietf.org]On Behalf Of > > > Alpesh > > > Sent: Tuesday, January 06, 2004 6:29 PM > > > To: mip4@ietf.org > > > Subject: [Mip4] [issue43] Experimental (sub) option type > for existing > > > options? > > > > > > > > > > > > This has been entered in the issue tracker as issue 43. > > > > > > owner: Alpesh : > > > > > > category: Technical > > > draft: draft-ietf-mip4-experimental-messages > > > priority: Should fix > > > status: No discussion > > > title: Experimental (sub) option type for existing options? > > > > > > Hi - > > > > > > We have one open issue for this draft - > > > > > > Description: Should we define an experimental sub-type for > > > existing options? > > > > > > One school of thought is that this is not needed as the > > > experiemental extension > > > types permits us to achieve this. By using the experimental > > > extension type, one > > > can use all the sub-types in that type for experimentation. > > > > > > Other school of thought is that for existing options, if any > > > experimentation is > > > needed we can use an experimental sub-type from that type. > > > Once ready for > > > standardization almost no code change is required to change > > > that experimental > > > sub-type to use a standard sub-type. > > > > > > We need the WG comments to resolve this issue and move on to > > > the next level. > > > Your prompt attention in this regards is highly appreciated. > > > Please let me know > > > if you need further clarification. > > > > > > Thanks > > > Alpesh > > > _________________________________________________ > > > Mip4 issue tracker > > > > > > _________________________________________________ > > > > > > -- > > > Mip4 mailing list > > > Mip4@ietf.org > > > https://www.ietf.org/mailman/listinfo/mip4 > > > > > > >-- > >Mip4 mailing list > >Mip4@ietf.org > >https://www.ietf.org/mailman/listinfo/mip4 > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 13:00:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19333 for ; Wed, 7 Jan 2004 12:12:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHE1-0005GS-4a for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 12:12:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07HC9xl020228 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 12:12:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHE0-0005GB-VM for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 12:12:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19299 for ; Wed, 7 Jan 2004 12:12:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHDz-0006Ey-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:12:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeHCP-00069e-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:10:30 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AeHB7-00062Z-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:09:10 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AeHB8-00031b-Ob for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 12:09:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHAz-00056V-SV; Wed, 07 Jan 2004 12:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeHAZ-00055V-7K for mip4@optimus.ietf.org; Wed, 07 Jan 2004 12:08:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19096 for ; Wed, 7 Jan 2004 12:08:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeHAX-0005zS-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:08:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeH8Z-0005sF-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:06:32 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AeH7M-0005ky-00 for mip4@ietf.org; Wed, 07 Jan 2004 12:05:16 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 07 Jan 2004 09:12:26 +0000 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i07H4hVM012799; Wed, 7 Jan 2004 09:04:44 -0800 (PST) Received: from kleung-w2k01.cisco.com (sjc-vpn3-763.cisco.com [10.21.66.251]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APA44845; Wed, 7 Jan 2004 09:04:42 -0800 (PST) Message-Id: <4.3.2.7.2.20040107085259.02825578@mira-sjcm-2.cisco.com> X-Sender: kleung@mira-sjcm-2.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 07 Jan 2004 09:04:42 -0800 To: Tsirtsis George From: Kent Leung Subject: RE: [Mip4] [issue43] Experimental (sub) option type for existing options? Cc: mip4@ietf.org In-Reply-To: <9E3BA3946476AD4EB94672712B12A85F03AB18@ftmail.lab.flarion. com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 This is not about vendor specific types. Here's a quick summary of the goals of the experimental and vendor specific drafts/RFC. 1) Experimental messages and extensions (only type defined) to support research and experimentation. The issue here is should there be a universal experimental subtype for extensions as well (this means the same subtype number is reserved for experiments in all extension types)? I don't think we need this since experimental type should suffice from the functional perspective. 2) Vendor specific extensions are defined to support vendor capabilities to standard messages. If vendors need messages, the experimental messages would be ideal to use for experimentation and inter-operation. Once the idea has been baked and determined to be useful for deployment, then it should be proposed to WG to obtain IANA message types for real world deployment. Just my perception of the differences and objectives of the experimental and vendor draft/RFC. Kent At 10:43 AM 1/7/2004 -0500, Tsirtsis George wrote: >How is this covering Vendor-specific types? It looks like it is about >experimental sub-types....or am I missing the point? > >George > > > -----Original Message----- > > From: mip4-admin@ietf.org [mailto:mip4-admin@ietf.org]On Behalf Of > > Alpesh > > Sent: Tuesday, January 06, 2004 6:29 PM > > To: mip4@ietf.org > > Subject: [Mip4] [issue43] Experimental (sub) option type for existing > > options? > > > > > > > > This has been entered in the issue tracker as issue 43. > > > > owner: Alpesh : > > > > category: Technical > > draft: draft-ietf-mip4-experimental-messages > > priority: Should fix > > status: No discussion > > title: Experimental (sub) option type for existing options? > > > > Hi - > > > > We have one open issue for this draft - > > > > Description: Should we define an experimental sub-type for > > existing options? > > > > One school of thought is that this is not needed as the > > experiemental extension > > types permits us to achieve this. By using the experimental > > extension type, one > > can use all the sub-types in that type for experimentation. > > > > Other school of thought is that for existing options, if any > > experimentation is > > needed we can use an experimental sub-type from that type. > > Once ready for > > standardization almost no code change is required to change > > that experimental > > sub-type to use a standard sub-type. > > > > We need the WG comments to resolve this issue and move on to > > the next level. > > Your prompt attention in this regards is highly appreciated. > > Please let me know > > if you need further clarification. > > > > Thanks > > Alpesh > > _________________________________________________ > > Mip4 issue tracker > > > > _________________________________________________ > > > > -- > > Mip4 mailing list > > Mip4@ietf.org > > https://www.ietf.org/mailman/listinfo/mip4 > > > >-- >Mip4 mailing list >Mip4@ietf.org >https://www.ietf.org/mailman/listinfo/mip4 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 15:50:53 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00437 for ; Wed, 7 Jan 2004 15:50:53 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeKdE-0008WT-5R for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 15:50:24 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i07KoOwP032755 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 15:50:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeKdE-0008WE-0t for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 15:50:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00414 for ; Wed, 7 Jan 2004 15:50:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeKdC-0002m5-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 15:50:22 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeKbM-0002hj-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 15:48:29 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeKZx-0002cH-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 15:47:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeKZx-0008Mn-Gk; Wed, 07 Jan 2004 15:47:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeKZG-0008LD-KV for mip4@optimus.ietf.org; Wed, 07 Jan 2004 15:46:20 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00179 for ; Wed, 7 Jan 2004 15:46:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeKZF-0002Yw-00 for mip4@ietf.org; Wed, 07 Jan 2004 15:46:17 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeKXN-0002Tp-00 for mip4@ietf.org; Wed, 07 Jan 2004 15:44:22 -0500 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AeKWD-0002Oy-00 for mip4@ietf.org; Wed, 07 Jan 2004 15:43:09 -0500 Received: from nwsgpa.ih.lucent.com (h135-1-121-22.lucent.com [135.1.121.22]) by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i07Kf0e01888; Wed, 7 Jan 2004 14:41:15 -0600 (CST) Received: from mccap-1.lucent.com by nwsgpa.ih.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2) id i07KecF00926; Wed, 7 Jan 2004 14:40:55 -0600 (CST) Received: from [127.0.0.1] (helo=MCCAP-1.lucent.com) by mccap-1.lucent.com with esmtp (Exim 4.04) id HR502C-0000BG-00; Wed, 07 Jan 2004 15:39:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16380.28307.706904.249774@gargle.gargle.HOWL> Date: Wed, 7 Jan 2004 14:39:47 -0600 From: Pete McCann To: Alexandru Petrescu Cc: Tsirtsis George , "'Henrik Levkowetz'" , mip4@ietf.org Subject: Re: [Mip4] WG adoption call on draft-kulkarni-mobileip-dynamic-assignment-02.txt In-Reply-To: <3FDA1B7C.8010906@nal.motlabs.com> References: <9E3BA3946476AD4EB94672712B12A85F03AA5A@ftmail.lab.flarion.com> <3FDA1B7C.8010906@nal.motlabs.com> X-Mailer: VM 7.14 under 21.5 (beta14) "cassava" XEmacs Lucid Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, all, I wanted to summarize/checkpoint the discussion on draft-kulkarni-mobileip-dynamic-assignment-02.txt that took place before the holidays. It seems that we have enough consensus to take this on as a working group item so I've asked Milind to submit draft-ietf-mip4-dynamic-assignment-00.txt. We have had some discussion of dynamic load balancing of ongoing sessions that might need further consideration; however, the majority of responses seem to indicate that this could be addressed with a separate draft. -Pete -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 7 23:38:59 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23435 for ; Wed, 7 Jan 2004 23:38:59 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeRwF-0006Nl-39 for mip4-archive@odin.ietf.org; Wed, 07 Jan 2004 23:38:31 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i084cVkM024532 for mip4-archive@odin.ietf.org; Wed, 7 Jan 2004 23:38:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeRwE-0006Nb-Sb for mip4-web-archive@optimus.ietf.org; Wed, 07 Jan 2004 23:38:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23394 for ; Wed, 7 Jan 2004 23:38:28 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeRwC-0007Qs-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 23:38:28 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeRuQ-0007Ke-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 23:36:38 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AeRsr-0007EC-00 for mip4-web-archive@ietf.org; Wed, 07 Jan 2004 23:35:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeRsr-0005np-NL; Wed, 07 Jan 2004 23:35:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeRsJ-0005lz-2Q for mip4@optimus.ietf.org; Wed, 07 Jan 2004 23:34:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23202 for ; Wed, 7 Jan 2004 23:34:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeRsG-0007AJ-00 for mip4@ietf.org; Wed, 07 Jan 2004 23:34:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeRqI-00072u-00 for mip4@ietf.org; Wed, 07 Jan 2004 23:32:23 -0500 Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au) by ietf-mx with esmtp (Exim 4.12) id 1AeRmI-0006uD-00 for mip4@ietf.org; Wed, 07 Jan 2004 23:28:14 -0500 Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26]) by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id PAA542740 for ; Thu, 8 Jan 2004 15:27:07 +1100 (EST) From: paul van den bergen To: mip4@ietf.org Date: Thu, 8 Jan 2004 15:27:06 +1100 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401081527.06914.pvandenbergen@swin.edu.au> Content-Transfer-Encoding: 7bit Subject: [Mip4] which implementations. Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all. I am wondering what mobile IP implementations there are out there. Specifically I am most interested in Open Source - *BSD and linux implementations for IPv4 and/or IPv6. I am aware of KAME for *BSD/ IPv6. If you know of a mobile IP implementation, could you drop me an email with; Mobile IP implementation name Operating system(s) - e.g. windows, MacOS, *BSD, linux distro IPv4 or IPv6. state... e.g. Commercial or Open Source; Experimental, Beta or Stable/Mature... thanks. -- Dr Paul van den Bergen Centre for Advanced Internet Architectures caia.swin.edu.au pvandenbergen@swin.edu.au IM:bulwynkl2002 "And some run up hill and down dale, knapping the chucky stones to pieces wi' hammers, like so many road makers run daft. They say it is to see how the world was made." Sir Walter Scott, St. Ronan's Well 1824 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Thu Jan 8 05:39:13 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16225 for ; Thu, 8 Jan 2004 05:39:13 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeXYr-0007iT-Tl for mip4-archive@odin.ietf.org; Thu, 08 Jan 2004 05:38:46 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i08AcjDK029660 for mip4-archive@odin.ietf.org; Thu, 8 Jan 2004 05:38:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeXYr-0007iJ-Kv for mip4-web-archive@optimus.ietf.org; Thu, 08 Jan 2004 05:38:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16222 for ; Thu, 8 Jan 2004 05:38:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeXYo-0007mL-00 for mip4-web-archive@ietf.org; Thu, 08 Jan 2004 05:38:42 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeXX1-0007ea-00 for mip4-web-archive@ietf.org; Thu, 08 Jan 2004 05:36:52 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AeXWI-0007Vu-00 for mip4-web-archive@ietf.org; Thu, 08 Jan 2004 05:36:06 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AeXWK-0005GC-WF for mip4-web-archive@ietf.org; Thu, 08 Jan 2004 05:36:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeXWE-0007Ci-7t; Thu, 08 Jan 2004 05:36:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AeXW0-0007Ae-0I for mip4@optimus.ietf.org; Thu, 08 Jan 2004 05:35:48 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15936 for ; Thu, 8 Jan 2004 05:35:44 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AeXVw-0007PP-00 for mip4@ietf.org; Thu, 08 Jan 2004 05:35:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AeXP2-000745-00 for mip4@ietf.org; Thu, 08 Jan 2004 05:28:37 -0500 Received: from sam.comnets.uni-bremen.de ([134.102.186.10] helo=bugs.comnets.uni-bremen.de) by ietf-mx with esmtp (Exim 4.12) id 1AeXLw-0006oM-00 for mip4@ietf.org; Thu, 08 Jan 2004 05:25:25 -0500 Received: from scoobydoo (scoobydoo.comnets.uni-bremen.de [134.102.155.152]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id i08AP0Q00737; Thu, 8 Jan 2004 11:25:00 +0100 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host scoobydoo.comnets.uni-bremen.de [134.102.155.152] claimed to be scoobydoo From: "Koojana Kuladinithi" To: "'paul van den bergen'" , Subject: AW: [Mip4] which implementations. Date: Thu, 8 Jan 2004 11:27:00 +0100 Message-ID: <000001c3d5d1$f3af77f0$989b6686@scoobydoo> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal In-Reply-To: <200401081527.06914.pvandenbergen@swin.edu.au> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: quoted-printable Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Paul We are maintaining an implementation, originally developed by Sun Labs = for Mobile IPv4. It was modified to support the simultaneous use of multiple interfaces. For more details at www.mobileip.org. You can find other Mobile IP implementations for IPv4 on Linux at=20 http://www.hpl.hp.com/personal/Jean_Tourrilhes/MobileIP/mip.html For IPv6, http://www.mipl.mediapoli.com/, MIPL from HUT, Finland. Hope, this helps Koojana > -----Urspr=FCngliche Nachricht----- > Von: mip4-admin@ietf.org [mailto:mip4-admin@ietf.org] Im Auftrag von = paul > van den bergen > Gesendet: Donnerstag, 8. Januar 2004 05:27 > An: mip4@ietf.org > Betreff: [Mip4] which implementations. >=20 > Hi all. >=20 > I am wondering what mobile IP implementations there are out there. >=20 > Specifically I am most interested in Open Source - *BSD and linux > implementations for IPv4 and/or IPv6. >=20 > I am aware of KAME for *BSD/ IPv6. >=20 > If you know of a mobile IP implementation, could you drop me an email > with; >=20 > Mobile IP implementation name > Operating system(s) - e.g. windows, MacOS, *BSD, linux distro > IPv4 or IPv6. > state... e.g. Commercial or Open Source; Experimental, Beta or > Stable/Mature... >=20 > thanks. >=20 > -- > Dr Paul van den Bergen > Centre for Advanced Internet Architectures > caia.swin.edu.au > pvandenbergen@swin.edu.au > IM:bulwynkl2002 > "And some run up hill and down dale, knapping the chucky stones > to pieces wi' hammers, like so many road makers run daft. > They say it is to see how the world was made." > Sir Walter Scott, St. Ronan's Well 1824 >=20 >=20 > -- > Mip4 mailing list > Mip4@ietf.org > https://www.ietf.org/mailman/listinfo/mip4 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 13 13:49:28 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03197 for ; Tue, 13 Jan 2004 13:49:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgTb1-0004LY-Tx for mip4-archive@odin.ietf.org; Tue, 13 Jan 2004 13:49:00 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DImx8P016708 for mip4-archive@odin.ietf.org; Tue, 13 Jan 2004 13:48:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgTb1-0004LP-Qe for mip4-web-archive@optimus.ietf.org; Tue, 13 Jan 2004 13:48:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03151 for ; Tue, 13 Jan 2004 13:48:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgTaz-0004p1-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 13:48:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgTZa-0004hy-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 13:47:31 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgTY9-0004WQ-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 13:46:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgTYB-0004EX-6U; Tue, 13 Jan 2004 13:46:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgKmT-0005IK-N4 for mip4@optimus.ietf.org; Tue, 13 Jan 2004 04:24:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02457 for ; Tue, 13 Jan 2004 04:24:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgKmQ-0002JE-00 for mip4@ietf.org; Tue, 13 Jan 2004 04:24:10 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgKka-0002HB-00 for mip4@ietf.org; Tue, 13 Jan 2004 04:22:17 -0500 Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx with esmtp (Exim 4.12) id 1AgKk0-0002Ej-00; Tue, 13 Jan 2004 04:21:41 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id i0CMmYRv003838; Mon, 12 Jan 2004 17:48:34 -0500 (EST) Received: from bibbiena.ece.neu.edu ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2004011217483424330 ; Mon, 12 Jan 2004 17:48:34 -0500 Received: from localhost (basagni@localhost) by bibbiena.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id i0CMmYF11174; Mon, 12 Jan 2004 17:48:34 -0500 (EST) X-Authentication-Warning: bibbiena.ece.neu.edu: basagni owned process doing -bs Date: Mon, 12 Jan 2004 17:48:34 -0500 (EST) From: Stefano Basagni X-X-Sender: basagni@bibbiena To: "Prof. Stefano Basagni" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Mip4] MobiQuitous 2004, Call for Papers (New deadlines!) Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=LINES_OF_YELLING autolearn=no version=2.60 Dear Colleagues, please, find below the Call for Papers for MobiQuitous 04. Notice that the paper submission deadline has been postponed to February 13 (with paper registration due on February 6). We *TRULY* apologize if you receive multiple copies of this Call for Papers. *********************************************************************** PRELIMINARY ANNOUNCEMENT and CALL FOR PAPERS MobiQuitous 2004 http://www.mobiquitous.org The First Annual International Conference on Mobile and Ubiquitous Systems: Networking and Services August 22-25, 2004 Boston, Massachusetts, USA (ACM sponsorship pending) *********************************************************************** The combination of mobile and ubiquitous computing is emerging as a promising new paradigm with the goal to provide computing and communication services all the time, everywhere, transparently and invisibly to the user, using devices embedded in the surrounding physical environment. In this context, the communication devices, the objects with which they interact, or both may be mobile. The implementation of such a paradigm requires advances in wireless network technologies and devices, development of infrastructures supporting cognitive environments, and discovery and identification of ubiquitous computing applications and services. The first ACM Annual International Conference on Mobile and Ubiquitous Systems: networking and services (Mobiquitous 04) will cover all these aspects, representing a forum where practitioners and researchers coming from the many areas involved in ubiquitous solutions design and deployment will be able to interact exchanging the cross-layer experiences needed to build the overall ubiquitous systems. Areas addressed by the conference include: applications, service-oriented computing, middleware, networking, agents, knowledge management and databases. PAPERS: Technical papers describing original, previously unpublished research, not currently under review by another conference or journal, are solicited. The conference is interested in contributions addressing all the areas associated with mobile and ubiquitous architectures, infrastructure and services. Technical works clearly identifying how the specific contributions fit to an overall working solution are particularly of interest. Topics include, but are not limited to, the following feature topics: * Ubiquitous architectures and systems * Wearable computing and personal area network * Wireless technologies for mobile and ubiquitous communications (Bluetooth, ZigBee, 802.15.x, WiFi) * Wireless Internet access in ubiquitous systems * Reconfigurability and personalization of wireless network * Service discovery mechanisms, knowledge discovery, matching and composition mechanisms * Wireless/mobile service management and delivery * Security, privacy and social issues of mobile and ubiquitous systems * Peer-to-peer knowledge management * Emerging industrial/business scenarios * Multimodal interfaces (speech, video kinetic, tactile) * Smart spaces * Ad hoc and sensor networking * Localization and tracking * Context and location aware application * Multimedia encoding and transcoding * Middleware services * Agent technologies in ubiquitous, wearable, and mobile systems * Hardware and software platforms for ubiquitous systems, and testbeds * User interfaces * Toolkits, development environments, and languages for ubiquitous computing * Ontologies for mobile and ubiquitous computing SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically (see the conference web page for details). Authors should prepare a Portable Document Format (PDF) or postscript version of their full paper. Papers must not exceed 8 pages double column (US Letter size, 8.5 x 11 inches) including text, figures and references. The font size must be at least 10 points. PUBLICATION: All submitted papers will be rigorously reviewed by technical program committee members. Accepted papers will be published in the conference proceedings. Papers of particular merit will be proposed for publication in the ACM/Kluwer Wireless Networks journal. TUTORIALS: Proposals for tutorials are solicited. Evaluation of tutorial proposals will be based on the expertise and experience of the instructors, and on the relevance of the subject matter. Potential instructors are requested to submit a tutorial proposal of at most 5 pages, including a biographical sketch, to the Tutorial Chair by March 1, 2004. DEMOS: Proposals for research and industrial demos are solicited. A maximum of 3 pages should be submitted which include a description of the demo and needed equipment. Proposals should be submitted to the Demo Chair by March 1, 2004 (responses will be given by April 30, 2004). *********************************************************************** IMPORTANT DATES *********************************************************************** Paper registration deadline: FEBRUARY 6 2004, 11:59pm PST Paper submission deadline: FEBRUARY 13 2004, 11:59pm PST Notification of acceptance: APRIL 30 2004 Camera-ready version due: MAY 15 2004 ********************************************************************** Papers submitted to MobiQuitous 2004 must be registered with EDAS by 11:59pm, PST, February 6, 2004. The deadline for submitting a registered paper is 11:59pm, PST, February 13, 2004. *** ORGANIZING COMMITTEE * General Co-Chairs Imrich Chlamtac University of Texas at Dallas, U.S.A. chlamtac@utdallas.edu Fausto Giunchiglia Universita` di Trento, Italy fausto@dit.unitn.it * General Vice Co-Chairs Michele Zorzi Universita` di Padova, Italy zorzi@dei.unipd.it Valentina Tamma University of Liverpool, U.K. valli@csc.liv.ac.uk * Program Co-Chairs * NETWORKING Tom La Porta Penn State University, U.S.A. tlp@cse.psu.edu Chiara Petrioli Universita` di Roma "La Sapienza," Italy petrioli@dsi.uniroma1.it * SERVICES Tim Finin Univ. of Maryland Baltimore County, U.S.A. finin@cs.umbc.edu Chiara Ghidini ITC-IRST, Trento, Italy ghidini@itc.it * Tutorial Chair Mani Srivastava Univ. of California Los Angeles, U.S.A. mbs@ucla.edu * Publicity Co-Chairs Stefano Basagni Northeastern University, U.S.A. Ilya Zaihrayeu Universita` di Trento, Italy * Registration Chair Robin Kravets Univ. of Illinois Urbana-Champaign, U.S.A. * Demo Chair Yannis Labrou Fujitsu Labs of America, U.S.A. yannis@fla.fujitsu.com * Local Arrangements Chair Prithwish Basu BBN Technologies, U.S.A. * Publication Chair Roger Whitaker Cardiff University, U.K. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 13 15:54:53 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12450 for ; Tue, 13 Jan 2004 15:54:53 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVYP-0002VM-9N for mip4-archive@odin.ietf.org; Tue, 13 Jan 2004 15:54:25 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DKsP3b009622 for mip4-archive@odin.ietf.org; Tue, 13 Jan 2004 15:54:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVYP-0002V7-4t for mip4-web-archive@optimus.ietf.org; Tue, 13 Jan 2004 15:54:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12428 for ; Tue, 13 Jan 2004 15:54:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgVYN-0004Uk-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 15:54:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgVWY-0004Sf-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 15:52:31 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgVW6-0004QL-00 for mip4-web-archive@ietf.org; Tue, 13 Jan 2004 15:52:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVW4-0002Ig-TY; Tue, 13 Jan 2004 15:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVVy-0002IV-Av for mip4@optimus.ietf.org; Tue, 13 Jan 2004 15:51:55 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12303; Tue, 13 Jan 2004 15:51:51 -0500 (EST) Message-Id: <200401132051.PAA12303@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip4@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 13 Jan 2004 15:51:51 -0500 Subject: [Mip4] I-D ACTION:draft-ietf-mip4-dynamic-assignment-00.txt Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --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 Dynamic Home Agent Assignment Author(s) : M. Kulkarni, K. Leung Filename : draft-ietf-mip4-dynamic-assignment-00.txt Pages : 21 Date : 2004-1-13 Mobile IP (RFC 3344) uses the Home Agent (HA) to anchor sessions of a roaming Mobile Node (MN). This draft proposes a messaging mechanism for dynamic home agent assignment and HA redirection. The goal is to provide a mechanism to assign an optimal HA for a Mobile IP session while allowing any suitable method for HA selection. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip4-dynamic-assignment-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mip4-dynamic-assignment-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mip4-dynamic-assignment-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-1-13160051.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip4-dynamic-assignment-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip4-dynamic-assignment-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-13160051.I-D@ietf.org> --OtherAccess-- --NextPart-- -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 14 18:30:42 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21328 for ; Wed, 14 Jan 2004 18:30:41 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguSl-00080r-F0 for mip4-archive@odin.ietf.org; Wed, 14 Jan 2004 18:30:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0ENUF7p030795 for mip4-archive@odin.ietf.org; Wed, 14 Jan 2004 18:30:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguSl-00080c-AL for mip4-web-archive@optimus.ietf.org; Wed, 14 Jan 2004 18:30:15 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21302 for ; Wed, 14 Jan 2004 18:30:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AguSa-0001RV-00 for mip4-web-archive@ietf.org; Wed, 14 Jan 2004 18:30:04 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AguSD-0001Nr-00 for mip4-web-archive@ietf.org; Wed, 14 Jan 2004 18:29:41 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AguQY-0001I6-00 for mip4-web-archive@ietf.org; Wed, 14 Jan 2004 18:27:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguQa-0007mL-RA; Wed, 14 Jan 2004 18:28:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AguQ5-0007lz-SH for mip4@optimus.ietf.org; Wed, 14 Jan 2004 18:27:29 -0500 Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21129 for ; Wed, 14 Jan 2004 18:27:25 -0500 (EST) Received: from apache by asgard.ietf.org with local (Exim 4.14) id 1AguPB-0001PU-0N; Wed, 14 Jan 2004 18:26:33 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce:; Cc: Internet Architecture Board , RFC Editor , Message-Id: Date: Wed, 14 Jan 2004 18:26:33 -0500 Subject: [Mip4] Protocol Action: 'Mobile IPv4 Extension for AAA Network Access Identifiers' to Proposed Standard Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 The IESG has approved the following document: - 'Mobile IPv4 Extension for AAA Network Access Identifiers ' as a Proposed Standard This document is the product of the Mobility for IPv4 Working Group. The IESG contact persons are Thomas Narten and Margaret Wasserman. Technical Summary When a mobile node moves from one foreign networks to another, it has to be reauthenticated at the new foreign network. If the home network has multiple AAA servers the reauthentication request may not be directed to the same AAAH that processed previous authentication requests. In order for the new Home AAA server to be able to forward the request to the appropriate Home Agent, it has to know the identity of the Home Agent the mobile node is using. This document defines an extension that enables the HA to pass its identity to the mobile node which can in turn pass it to the AAA server when changing point of attachment. This document specifies a Mobile IP NAI extension that can carry these NAIs. Working Group Summary There was consensus in the WG for this extension. Protocol Quality The specification has been reviewed for the IESG by Thomas Narten. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Mon Jan 19 22:50:28 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26784 for ; Mon, 19 Jan 2004 22:50:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aimto-00077Y-AW for mip4-archive@odin.ietf.org; Mon, 19 Jan 2004 22:49:57 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K3nu6e027367 for mip4-archive@odin.ietf.org; Mon, 19 Jan 2004 22:49:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aimti-00077C-Tt for mip4-web-archive@optimus.ietf.org; Mon, 19 Jan 2004 22:49:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26759 for ; Mon, 19 Jan 2004 22:49:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aimta-0000YW-00 for mip4-web-archive@ietf.org; Mon, 19 Jan 2004 22:49:42 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AimqH-0000Jd-00 for mip4-web-archive@ietf.org; Mon, 19 Jan 2004 22:46:19 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AimmR-000063-00 for mip4-web-archive@ietf.org; Mon, 19 Jan 2004 22:42:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AimmA-0006eS-0W; Mon, 19 Jan 2004 22:42:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AimlR-0006dB-4K for mip4@optimus.ietf.org; Mon, 19 Jan 2004 22:41:43 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26501 for ; Mon, 19 Jan 2004 22:41:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AimlF-00000J-00 for mip4@ietf.org; Mon, 19 Jan 2004 22:41:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AimiB-0007hJ-00 for mip4@ietf.org; Mon, 19 Jan 2004 22:37:56 -0500 Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au) by ietf-mx with esmtp (Exim 4.12) id 1AimgU-0007aw-00; Mon, 19 Jan 2004 22:36:10 -0500 Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26]) by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id OAA864336; Tue, 20 Jan 2004 14:35:18 +1100 (EST) From: paul van den bergen To: mip6@ietf.org, , , snap-users@kame.net, users@freenet6.net Date: Tue, 20 Jan 2004 14:35:17 +1100 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401201435.17642.pvandenbergen@swin.edu.au> Content-Transfer-Encoding: 7bit Subject: [Mip4] for your information - Mobile IP v4 and v6 implementations. Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, a few weeks ago I asked for mobile IP implementations... just thought you'd all be interested to see what I found... IP Operating Systems Name Source and Comments 6 FreeBSD 4.9 KAME http://www.kame.net/ NetBSD 1.6.1 Stable, MIP code experimental, actively updated OpenBSD 3.3 4 NetBSD 1.1 Monarch http://www.monarch.cs.cmu.edu/software.html FreeBSD 2.2.2 Rich University, old 6 INRIA's IPv6 code and FreeBSD 2.2.2 4 linux Secure Mobile Net http://www.cs.pdx.edu/research/SMN/ FreeBSD 2.2.8, 4.6 actively updated 4.8, 4.9, 5.2 4 Linux Dynamics Helsinki University of Technology Windows client http://dynamics.sourceforge.net/ 6 Linux MIPL http://www.mipl.mediapoli.com/ GPL, stable 4 Linux UoB-NOMAD http://www.mobileip.org/ SPL, based on NOMADv4 6 Linux HMIPv6 http://www.ctie.monash.edu.au/ipv6/hmipv6.htm 4 Windows SEGCO http://www.secgo.com/ Linux commercial 4 Linux kernel 2.2.16 MosquitoNet http://mosquitonet.stanford.edu/mip/ 4 Windows IPunplugged http://www.ipunplugged.com/ commercial 4 Windows Birdstep http://www.birdstep.com/ embedded systems commercial 4 & 6 embedded Elmic Systems http://www.elmic.com/ OS independant commercial, now Treck Inc. 4 Userland MobileIP (platform independent) (linux 2.0.3) http://www.hpl.hp.com/personal/Jean_Tourrilhes/MobileIP/index.html -- Dr Paul van den Bergen Centre for Advanced Internet Architectures caia.swin.edu.au pvandenbergen@swin.edu.au IM:bulwynkl2002 "And some run up hill and down dale, knapping the chucky stones to pieces wi' hammers, like so many road makers run daft. They say it is to see how the world was made." Sir Walter Scott, St. Ronan's Well 1824 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 20 04:04:44 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19483 for ; Tue, 20 Jan 2004 04:04:44 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Airny-0005xd-Kj for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 04:04:15 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0K94EuG022912 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 04:04:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Airnx-0005xO-A6 for mip4-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 04:04:13 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19475 for ; Tue, 20 Jan 2004 04:04:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Airnu-0000ST-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 04:04:10 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Airmw-0000Qm-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 04:03:11 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Airmo-0000Ot-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 04:03:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Airmn-0005tv-WB; Tue, 20 Jan 2004 04:03:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aioox-0004jD-Rn for mip4@optimus.ietf.org; Tue, 20 Jan 2004 00:53:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02527 for ; Tue, 20 Jan 2004 00:52:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aioov-0000TA-00 for mip4@ietf.org; Tue, 20 Jan 2004 00:53:01 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aionw-0000Pb-00 for mip4@ietf.org; Tue, 20 Jan 2004 00:52:00 -0500 Received: from 203.141.155.85.user.ca.il24.net ([203.141.155.85] helo=doller.momose.org) by ietf-mx with esmtp (Exim 4.12) id 1AionF-0000It-00; Tue, 20 Jan 2004 00:51:17 -0500 Received: from [IPv6:2001:200:182:2000:20a:95ff:fef1:1836] ([IPv6:2001:200:182:2000:20a:95ff:fef1:1836]) (authenticated (0 bits)) by doller.momose.org (8.12.10/8.11.4) with ESMTP id i0K5oW4N092360; Tue, 20 Jan 2004 14:50:35 +0900 (JST) (envelope-from t-momose@kame.net) In-Reply-To: <200401201435.17642.pvandenbergen@swin.edu.au> References: <200401201435.17642.pvandenbergen@swin.edu.au> Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8D867402-4B0C-11D8-8C16-000A959836B2@kame.net> Content-Transfer-Encoding: 7bit Cc: "" , mip6@ietf.org, users@freenet6.net, "" From: Tsuyoshi MOMOSE Date: Tue, 20 Jan 2004 14:50:29 +0900 To: snap-users@kame.net X-Mailer: Apple Mail (2.609) Content-Transfer-Encoding: 7bit Subject: [Mip4] Re: (KAME-snap 8240) for your information - Mobile IP v4 and v6 implementations. Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, On 2004/01/20, at 12:35, paul van den bergen wrote: > IP Operating Systems Name Source and Comments > 6 FreeBSD 4.9 KAME http://www.kame.net/ > NetBSD 1.6.1 Stable, MIP code experimental, actively updated > OpenBSD 3.3 Current KAME MIP6 doesn't support OpenBSD yet. I'm now working to port it. --- MOMOSE Tsuyoshi NEC Corporation KAME Project http://www.kame.net/ Nautilus Project http://www.nautilus6.org/ -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 20 05:07:26 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21636 for ; Tue, 20 Jan 2004 05:07:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aismf-00011n-F4 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 05:06:58 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KA6vJU003951 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 05:06:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aisme-00011e-N1 for mip4-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 05:06:57 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21535 for ; Tue, 20 Jan 2004 05:06:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aismb-0003o4-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 05:06:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AislU-0003en-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 05:05:45 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aisko-0003X1-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 05:05:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aiskq-0000q3-BS; Tue, 20 Jan 2004 05:05:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AiskE-0000pL-Hm for mip4@optimus.ietf.org; Tue, 20 Jan 2004 05:04:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21284 for ; Tue, 20 Jan 2004 05:04:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AiskB-0003WW-00 for mip4@ietf.org; Tue, 20 Jan 2004 05:04:23 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aisj9-0003Sm-00 for mip4@ietf.org; Tue, 20 Jan 2004 05:03:19 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1Aisis-0003Pd-00; Tue, 20 Jan 2004 05:03:02 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1Aisio-00024j-00; Tue, 20 Jan 2004 11:02:58 +0100 Date: Tue, 20 Jan 2004 11:02:49 +0100 From: Henrik Levkowetz To: paul van den bergen Cc: mip6@ietf.org, , , snap-users@kame.net, users@freenet6.net Subject: Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. Message-Id: <20040120110249.461dfeea.henrik@levkowetz.com> In-Reply-To: <200401201435.17642.pvandenbergen@swin.edu.au> References: <200401201435.17642.pvandenbergen@swin.edu.au> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Paul, Tuesday 20 January 2004, paul van den bergen wrote: > Hi all, > a few weeks ago I asked for mobile IP implementations... > > just thought you'd all be interested to see what I found... Useful and interesting indeed. I've taken the liberty of duplicating the information here: Thanks, Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 20 15:45:08 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20912 for ; Tue, 20 Jan 2004 15:45:08 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2ji-00087Y-9I for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 15:44:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KKiY3G031215 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 15:44:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2jg-00085h-S1 for mip4-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 15:44:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20683 for ; Tue, 20 Jan 2004 15:44:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj2jf-0000U5-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 15:44:31 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj2ij-0000RL-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 15:43:34 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aj2iF-0000PZ-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 15:43:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj2iC-0007t2-KM; Tue, 20 Jan 2004 15:43:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj0dw-0007GU-FA for mip4@optimus.ietf.org; Tue, 20 Jan 2004 13:30:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15248 for ; Tue, 20 Jan 2004 13:30:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj0du-0002MI-00 for mip4@ietf.org; Tue, 20 Jan 2004 13:30:26 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj0cw-0002Ki-00 for mip4@ietf.org; Tue, 20 Jan 2004 13:29:27 -0500 Received: from web12823.mail.yahoo.com ([216.136.174.204]) by ietf-mx with smtp (Exim 4.12) id 1Aj0cK-0002JK-00 for mip4@ietf.org; Tue, 20 Jan 2004 13:28:48 -0500 Message-ID: <20040120182737.20338.qmail@web12823.mail.yahoo.com> Received: from [66.208.42.117] by web12823.mail.yahoo.com via HTTP; Tue, 20 Jan 2004 10:27:37 PST Date: Tue, 20 Jan 2004 10:27:37 -0800 (PST) From: Qiang zhang Reply-To: qiangieee@yahoo.com Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. To: paul van den bergen Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net, users@freenet6.net In-Reply-To: <20040120110249.461dfeea.henrik@levkowetz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Dr. Paul Bergen, I know there are several other commercials, such as ecutel.com Qiang --- Henrik Levkowetz wrote: > Hello Paul, > > Tuesday 20 January 2004, paul van den bergen wrote: > > Hi all, > > a few weeks ago I asked for mobile IP > implementations... > > > > just thought you'd all be interested to see what I > found... > > > > Useful and interesting indeed. I've taken the > liberty of duplicating > the information here: > > > > > Thanks, > Henrik > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 20 16:40:08 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26666 for ; Tue, 20 Jan 2004 16:40:08 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj3b2-0003Oj-JP for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 16:39:40 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0KLde6t013055 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 16:39:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj3b2-0003OU-D6 for mip4-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 16:39:40 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26587 for ; Tue, 20 Jan 2004 16:39:37 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj3b0-0006yz-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 16:39:38 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj3a5-0006pp-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 16:38:42 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Aj3ZV-0006mf-01 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 16:38:05 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1Aj3Ud-0005Wu-Io for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 16:33:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj3Uc-0002mG-Cc; Tue, 20 Jan 2004 16:33:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj3UH-0002g1-4a for mip4@optimus.ietf.org; Tue, 20 Jan 2004 16:32:41 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26398 for ; Tue, 20 Jan 2004 16:32:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj3UF-0006cC-00 for mip4@ietf.org; Tue, 20 Jan 2004 16:32:39 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj3TL-0006Zg-00 for mip4@ietf.org; Tue, 20 Jan 2004 16:31:44 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1Aj3Ss-0006W5-00; Tue, 20 Jan 2004 16:31:15 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1Aj3Sk-0002Jy-00; Tue, 20 Jan 2004 22:31:06 +0100 Date: Tue, 20 Jan 2004 22:31:01 +0100 From: Henrik Levkowetz To: qiangieee@yahoo.com Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net, users@freenet6.net Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. Message-Id: <20040120223101.1634dc64.henrik@levkowetz.com> In-Reply-To: <20040120182737.20338.qmail@web12823.mail.yahoo.com> References: <20040120110249.461dfeea.henrik@levkowetz.com> <20040120182737.20338.qmail@web12823.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Qiang Tuesday 20 January 2004, Qiang Zhang wrote: > I know there are several other commercials, such as > ecutel.com As more implementations are mentioned on the mailing list, I'll put them into the table at . I would need a bit more information to do so, though. Would you be kind enough to provide / IP version / OS / Name / URL / status / for the implementations you know of? Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 20 19:57:23 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04630 for ; Tue, 20 Jan 2004 19:57:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj6fq-0003yy-Eq for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 19:56:54 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0L0uoTH015307 for mip4-archive@odin.ietf.org; Tue, 20 Jan 2004 19:56:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj6fq-0003yo-0v for mip4-web-archive@optimus.ietf.org; Tue, 20 Jan 2004 19:56:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04612 for ; Tue, 20 Jan 2004 19:56:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj6fo-00036K-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 19:56:48 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj6ew-000325-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 19:55:55 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aj6e7-0002wf-00 for mip4-web-archive@ietf.org; Tue, 20 Jan 2004 19:55:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj6e7-0003ko-1v; Tue, 20 Jan 2004 19:55:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aj6dp-0003jy-2a for mip4@optimus.ietf.org; Tue, 20 Jan 2004 19:54:45 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04382 for ; Tue, 20 Jan 2004 19:54:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aj6dm-0002tW-00 for mip4@ietf.org; Tue, 20 Jan 2004 19:54:42 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aj6co-0002kC-00 for mip4@ietf.org; Tue, 20 Jan 2004 19:53:42 -0500 Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au) by ietf-mx with esmtp (Exim 4.12) id 1Aj6bn-0002Yl-00; Tue, 20 Jan 2004 19:52:39 -0500 Received: from pvdbergen.caia.swin.edu.au (pvdbergen.caia.swin.edu.au [136.186.229.26]) by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA985290; Wed, 21 Jan 2004 11:51:23 +1100 (EST) From: paul van den bergen To: Henrik Levkowetz , qiangieee@yahoo.com Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. Date: Wed, 21 Jan 2004 11:51:22 +1100 User-Agent: KMail/1.5 Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net, users@freenet6.net References: <20040120110249.461dfeea.henrik@levkowetz.com> <20040120182737.20338.qmail@web12823.mail.yahoo.com> <20040120223101.1634dc64.henrik@levkowetz.com> In-Reply-To: <20040120223101.1634dc64.henrik@levkowetz.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401211151.23317.pvandenbergen@swin.edu.au> Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hey Henrik, thanks for that! I'm glad this information has a home! (I might steal your page and duplicate it at wikipedia too, if I get a moment.) FYI, I am winding up here this week, so this email address will disappear. but anyone who wants to talk to the people who will no doubt follow after me (I speak of the researcher who is greater than me, whos very operational parameters I am unworthy to even calculate) can go to www.caia.swin.edu.au and have a look around there... :-) On Wed, 21 Jan 2004 08:31 am, Henrik Levkowetz wrote: > Hi Qiang > > Tuesday 20 January 2004, Qiang Zhang wrote: > > I know there are several other commercials, such as > > ecutel.com > > As more implementations are mentioned on the mailing list, I'll put them > into the table at . > > I would need a bit more information to do so, though. Would you be kind > enough to provide / IP version / OS / Name / URL / status / for the > implementations you know of? > > Henrik IP OS Name URL Comments 4 Windows client/server Viatores www.ecutel.com/ commercial Linux server -- Dr Paul van den Bergen Centre for Advanced Internet Architectures caia.swin.edu.au pvandenbergen@swin.edu.au IM:bulwynkl2002 "And some run up hill and down dale, knapping the chucky stones to pieces wi' hammers, like so many road makers run daft. They say it is to see how the world was made." Sir Walter Scott, St. Ronan's Well 1824 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Thu Jan 22 12:44:26 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01014 for ; Thu, 22 Jan 2004 12:44:26 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ajis2-0001fe-RG for mip4-archive@odin.ietf.org; Thu, 22 Jan 2004 12:43:59 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0MHhwtG006418 for mip4-archive@odin.ietf.org; Thu, 22 Jan 2004 12:43:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ajis2-0001fR-HU for mip4-web-archive@optimus.ietf.org; Thu, 22 Jan 2004 12:43:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00964 for ; Thu, 22 Jan 2004 12:43:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ajis0-0000GQ-00 for mip4-web-archive@ietf.org; Thu, 22 Jan 2004 12:43:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ajiow-00005M-00 for mip4-web-archive@ietf.org; Thu, 22 Jan 2004 12:40:47 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Ajild-0007gS-00 for mip4-web-archive@ietf.org; Thu, 22 Jan 2004 12:37:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AjilJ-0000qX-8D; Thu, 22 Jan 2004 12:37:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AjikN-0000pF-Us for mip4@optimus.ietf.org; Thu, 22 Jan 2004 12:36:29 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00601 for ; Thu, 22 Jan 2004 12:36:00 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AjikH-0007bQ-00 for mip4@ietf.org; Thu, 22 Jan 2004 12:35:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ajig7-0007OC-00 for mip4@ietf.org; Thu, 22 Jan 2004 12:31:40 -0500 Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Ajicw-0007AE-00; Thu, 22 Jan 2004 12:28:22 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 22 Jan 2004 09:31:53 +0000 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0MHRVff007001; Thu, 22 Jan 2004 09:27:31 -0800 (PST) Received: from kleung-w2k01.cisco.com (sjc-vpn3-722.cisco.com [10.21.66.210]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APN31133; Thu, 22 Jan 2004 09:27:30 -0800 (PST) Message-Id: <4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com> X-Sender: kleung@mira-sjcm-2.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 22 Jan 2004 09:27:29 -0800 To: Henrik Levkowetz From: Kent Leung Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. Cc: qiangieee@yahoo.com, mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net, users@freenet6.net In-Reply-To: <20040120223101.1634dc64.henrik@levkowetz.com> References: <20040120182737.20338.qmail@web12823.mail.yahoo.com> <20040120110249.461dfeea.henrik@levkowetz.com> <20040120182737.20338.qmail@web12823.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Hi Henrik. Here's Cisco's info: IP: 4 & 6 OS: Cisco IOS Name: Cisco Systems (URL: http://www.cisco.com/go/mobile_ip) Comments: MIPv4 commercial, MIPv6 technology preview Kent At 10:31 PM 1/20/2004 +0100, Henrik Levkowetz wrote: >As more implementations are mentioned on the mailing list, I'll put them >into the table at . > >I would need a bit more information to do so, though. Would you be kind >enough to provide / IP version / OS / Name / URL / status / for the >implementations you know of? > > Henrik > >-- >Mip4 mailing list >Mip4@ietf.org >https://www.ietf.org/mailman/listinfo/mip4 -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Sat Jan 24 10:50:02 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12545 for ; Sat, 24 Jan 2004 10:50:02 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AkQ2Q-00054M-Kw for mip4-archive@odin.ietf.org; Sat, 24 Jan 2004 10:49:36 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0OFnYxd019482 for mip4-archive@odin.ietf.org; Sat, 24 Jan 2004 10:49:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AkQ2Q-000549-EV for mip4-web-archive@optimus.ietf.org; Sat, 24 Jan 2004 10:49:34 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12532 for ; Sat, 24 Jan 2004 10:49:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AkQ2O-0003tv-00 for mip4-web-archive@ietf.org; Sat, 24 Jan 2004 10:49:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AkQ1Q-0003sC-00 for mip4-web-archive@ietf.org; Sat, 24 Jan 2004 10:48:33 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AkQ0u-0003qW-00 for mip4-web-archive@ietf.org; Sat, 24 Jan 2004 10:48:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AkQ0u-0004xL-Sz; Sat, 24 Jan 2004 10:48:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AkQ0V-0004we-0t for mip4@optimus.ietf.org; Sat, 24 Jan 2004 10:47:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12512 for ; Sat, 24 Jan 2004 10:47:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AkQ0S-0003qM-00 for mip4@ietf.org; Sat, 24 Jan 2004 10:47:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AkPzZ-0003or-00 for mip4@ietf.org; Sat, 24 Jan 2004 10:46:38 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AkPzI-0003mK-00; Sat, 24 Jan 2004 10:46:20 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AkPz7-0000gl-00; Sat, 24 Jan 2004 16:46:09 +0100 Date: Sat, 24 Jan 2004 16:45:50 +0100 From: Henrik Levkowetz To: Kent Leung Cc: mip6@ietf.org, mip4@ietf.org, users@ipv6.org, snap-users@kame.net, users@freenet6.net Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6 implementations. Message-Id: <20040124164550.422cb64e.henrik@levkowetz.com> In-Reply-To: <4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com> References: <20040120182737.20338.qmail@web12823.mail.yahoo.com> <20040120110249.461dfeea.henrik@levkowetz.com> <20040120182737.20338.qmail@web12823.mail.yahoo.com> <4.3.2.7.2.20040122092132.0256a9b8@mira-sjcm-2.cisco.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw" Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 --Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Thursday 22 January 2004, Kent Leung wrote: > Here's Cisco's info: > > IP: 4 & 6 > OS: Cisco IOS > Name: Cisco Systems (URL: http://www.cisco.com/go/mobile_ip) > Comments: MIPv4 commercial, MIPv6 technology preview > > Kent Thanks, Kent. I've added this to the page at . If there are any updates, let me know. Regards, Henrik --Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAEpM3eVhrtTJkXCMRAkHlAJ0Z11lIp82HGb/EUKv9v8EO5NqvowCg528T NhdqfohqmHAL3JNnQI8RzCo= =OixS -----END PGP SIGNATURE----- --Signature=_Sat__24_Jan_2004_16_45_50_+0100_CnA_7QrvTfWN_aHw-- -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 27 19:35:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05123 for ; Tue, 27 Jan 2004 19:35:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aldfb-0006gB-GV for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 19:35:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S0Z321025646 for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 19:35:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldfY-0006es-UO for mip4-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 19:35:02 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05041 for ; Tue, 27 Jan 2004 19:34:57 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AldfX-0001l2-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:34:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlddP-0001FB-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:32:48 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AldcZ-00012I-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:31:55 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AldRe-00062U-O0 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:20:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldGo-0001Bw-Aw; Tue, 27 Jan 2004 19:09:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlCNe-000333-2K for mip4@optimus.ietf.org; Mon, 26 Jan 2004 14:27:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16643 for ; Mon, 26 Jan 2004 14:26:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlCNR-0007GA-00 for mip4@ietf.org; Mon, 26 Jan 2004 14:26:29 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlCL6-00079V-00 for mip4@ietf.org; Mon, 26 Jan 2004 14:24:05 -0500 Received: from palrel11.hp.com ([156.153.255.246]) by ietf-mx with esmtp (Exim 4.12) id 1AlCJg-00073E-00; Mon, 26 Jan 2004 14:22:36 -0500 Received: from strtio1.cup.hp.com (strtio1.cup.hp.com [15.13.129.245]) by palrel11.hp.com (Postfix) with ESMTP id 5A48D1C012E5; Mon, 26 Jan 2004 21:28:05 -0800 (PST) Received: (from jlau@localhost) by strtio1.cup.hp.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.02) id LAA13756; Mon, 26 Jan 2004 11:20:15 -0800 (PST) Date: Mon, 26 Jan 2004 11:20:15 -0800 (PST) From: Joe Lau Message-Id: <200401261920.LAA13756@strtio1.cup.hp.com> To: mip4@ietf.org, mip6@ietf.org Cc: clemenj@cup.hp.com, henrik@levkowetz.com, jlau@cup.hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] Re: Mobile IP v4 and v6 implementations. Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: Re: Mobile IP v4 and v6 implementations. Hello, Please add the following Mobile IP implementation from HP to your Mobile-IP Implementions List. IP = 4 Operating Systems = HP-UX 11.11 Name = HP-UX Mobile IPv4 License = commercial Comments = Mobile IPv4 HA/CN, Reverse Tunneling, Route Optimization and AAA support URL = www.software.hp.com ----------------- IP = 6 Operating Systems = HP-UX 11.11 and HP-UX 11.23 Name = HP-UX Mobile IPv6 License = commercial Comments = Mobile IPv6 HA/CN, draft-24 URL = www.software.hp.com Thank you. Regards, Joe Lau Mobile IP Project SNSL, HP -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 27 19:39:36 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06039 for ; Tue, 27 Jan 2004 19:39:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldjZ-0007S9-EY for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 19:39:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S0d9Zf028633 for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 19:39:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldjZ-0007Rf-1L for mip4-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 19:39:09 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05813 for ; Tue, 27 Jan 2004 19:39:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AldjX-0002ko-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:39:07 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aldge-00021o-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:36:09 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Alddx-0001OZ-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:33:21 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AldRV-00062U-96 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 19:20:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldJb-0002Ry-3t; Tue, 27 Jan 2004 19:12:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlEdW-0002T6-CR for mip4@optimus.ietf.org; Mon, 26 Jan 2004 16:51:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21240 for ; Mon, 26 Jan 2004 16:51:11 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlEdU-0005zq-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:51:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlEcX-0005xm-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:50:13 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AlEbt-0005wD-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:49:33 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AlEbs-0000ZC-00 for ; Mon, 26 Jan 2004 22:49:32 +0100 Date: Mon, 26 Jan 2004 22:49:32 +0100 From: Henrik Levkowetz To: mip4@ietf.org Subject: Re: [Mip4] [issue43] draft-ietf-mip4-experimental-messages Message-Id: <20040126224932.6dd9a0f5.henrik@levkowetz.com> In-Reply-To: <1073413735.86.0.82505581673.issue43@mip4.org> References: <1073413735.86.0.82505581673.issue43@mip4.org> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit We would like to move forward with draft-ietf-mip4-experimental-messages. There is currently one open issue, reflected here: The possible positions seems to be either of: * "Yes, add experimental sub-type number" * "No, do not add experimental sub-type number" I'd like to get a little bit more feedback from the list on this issue, please comment on this, indicating your preference. Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Tue Jan 27 21:12:18 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10966 for ; Tue, 27 Jan 2004 21:12:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlfBG-000479-EO for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 21:11:50 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0S2BoY4015811 for mip4-archive@odin.ietf.org; Tue, 27 Jan 2004 21:11:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlfBG-00046w-5X for mip4-web-archive@optimus.ietf.org; Tue, 27 Jan 2004 21:11:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10794 for ; Tue, 27 Jan 2004 21:11:47 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlfBD-0002cW-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 21:11:47 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alf9i-0002J1-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 21:10:14 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Alf7m-00024J-00 for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 21:08:14 -0500 Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1Alf7n-0004dX-1n for mip4-web-archive@ietf.org; Tue, 27 Jan 2004 21:08:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AldIg-00024W-4E; Tue, 27 Jan 2004 19:11:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlEPy-0001mf-Ug for mip4@optimus.ietf.org; Mon, 26 Jan 2004 16:37:14 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21016 for ; Mon, 26 Jan 2004 16:37:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlEPw-0005V7-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:37:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlEP8-0005SO-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:36:22 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AlEOO-0005PM-00 for mip4@ietf.org; Mon, 26 Jan 2004 16:35:36 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AlEOI-0000YL-00 for ; Mon, 26 Jan 2004 22:35:30 +0100 Date: Mon, 26 Jan 2004 22:35:27 +0100 From: Henrik Levkowetz To: mip4@ietf.org Message-Id: <20040126223527.5957444c.henrik@levkowetz.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] Request for reviewer Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Request for reviewer: The person with both MIP and MIB experience who had promised to review the rfc2006bis ("The Definitions of Managed Objects for IP Mobility Support using SMIv2, revised") is currently so overloaded with work that we don't expect him to be able to make progress on this. Accordingly, we will need another reviewer who is both knowledgeable in MIP and MIBs to do a review, with focus on the MIP specific aspects. We really would like to get this done, so we can send the document on to the MIB doctors for MIB doctor review. Regards, Henrik and Pete -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 09:50:03 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02482 for ; Wed, 28 Jan 2004 09:50:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alr0a-0003SJ-0t for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 09:49:36 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SEnZ6Z013277 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 09:49:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alr0Z-0003S4-S5 for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 09:49:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02476 for ; Wed, 28 Jan 2004 09:49:32 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alr0Y-0007NK-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 09:49:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alqzc-0007J4-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 09:48:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Alqz2-0007En-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 09:48:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alqz2-0003KA-Qe; Wed, 28 Jan 2004 09:48:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlqcO-0001NY-QT for mip4@optimus.ietf.org; Wed, 28 Jan 2004 09:24:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01789 for ; Wed, 28 Jan 2004 09:24:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlqcN-0005JZ-00 for mip4@ietf.org; Wed, 28 Jan 2004 09:24:35 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlqbZ-0005Ev-00 for mip4@ietf.org; Wed, 28 Jan 2004 09:23:45 -0500 Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14]) by ietf-mx with esmtp (Exim 4.12) id 1Alqam-0005Aa-00 for mip4@ietf.org; Wed, 28 Jan 2004 09:22:56 -0500 Received: from fokus.fraunhofer.de (dale [193.175.135.167]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with ESMTP id i0SEMsL02902; Wed, 28 Jan 2004 15:22:54 +0100 (MET) Message-ID: <4017C5BC.3000208@fokus.fraunhofer.de> Date: Wed, 28 Jan 2004 15:22:52 +0100 From: Reinhard Ruppelt Reply-To: Reinhard.Ruppelt@fokus.fraunhofer.de Organization: Fraunhofer Institut Fokus User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] RoamIn Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, even though the implementations available from http://www.mobile-ip.de are pretty aged and W-NT and W-98 are falling into oblivion there are still many downloads indicating interest in the implementation. Regards, Reinhard Ruppelt -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 10:06:04 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03252 for ; Wed, 28 Jan 2004 10:06:04 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlrG5-0007Mm-1z for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 10:05:37 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SF5bfq028308 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 10:05:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlrG4-0007MO-R3 for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 10:05:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03196 for ; Wed, 28 Jan 2004 10:05:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlrG2-0000p4-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:05:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlrF7-0000kU-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:04:38 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AlrEV-0000g4-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:03:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlrEW-0006vl-Ry; Wed, 28 Jan 2004 10:04:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlrEA-0006pr-G1 for mip4@optimus.ietf.org; Wed, 28 Jan 2004 10:03:38 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02978 for ; Wed, 28 Jan 2004 10:03:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlrE8-0000ex-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:03:36 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlrDA-0000Zv-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:02:36 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AlrCG-0000VT-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:01:40 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AlrC7-000209-00; Wed, 28 Jan 2004 16:01:31 +0100 Date: Wed, 28 Jan 2004 16:01:30 +0100 From: Henrik Levkowetz To: Reinhard.Ruppelt@fokus.fraunhofer.de Cc: mip4@ietf.org Subject: Re: [Mip4] RoamIn Message-Id: <20040128160130.78ff63be.henrik@levkowetz.com> In-Reply-To: <4017C5BC.3000208@fokus.fraunhofer.de> References: <4017C5BC.3000208@fokus.fraunhofer.de> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Wednesday 28 January 2004, Reinhard Ruppelt wrote: > even though the implementations available from http://www.mobile-ip.de > are pretty aged and W-NT and W-98 are falling into oblivion there are > still many downloads indicating interest in the implementation. Thanks Reinhard, I've added it to the table at http://mip4.org/2004/implementations/ . However, it isn't quite clear to me whether this is a commercial offering or something else (and in that case what kind of distribution and licence it has), and when the implementation is from. Do you have that information available? Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 10:41:02 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05052 for ; Wed, 28 Jan 2004 10:41:02 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alrnw-00046I-8H for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 10:40:36 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SFeaYs015756 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 10:40:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alrnv-000463-UD for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 10:40:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05038 for ; Wed, 28 Jan 2004 10:40:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alrnt-0003im-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:40:33 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alrn0-0003ee-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:39:39 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AlrmO-0003aL-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 10:39:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlrmP-0003xZ-F5; Wed, 28 Jan 2004 10:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alrlz-0003xG-9A for mip4@optimus.ietf.org; Wed, 28 Jan 2004 10:38:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04998 for ; Wed, 28 Jan 2004 10:38:31 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alrlw-0003Z7-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:38:33 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alrkz-0003VL-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:37:34 -0500 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=chardonnay.local.levkowetz.com) by ietf-mx with esmtp (Exim 4.12) id 1AlrkU-0003Rb-00 for mip4@ietf.org; Wed, 28 Jan 2004 10:37:02 -0500 Received: from chardonnay ([127.0.0.1] helo=chardonnay.local.levkowetz.com) by chardonnay.local.levkowetz.com with smtp (Exim 3.36 #1 (Debian)) id 1AlrkT-00022o-00 for ; Wed, 28 Jan 2004 16:37:01 +0100 Date: Wed, 28 Jan 2004 16:36:58 +0100 From: Henrik Levkowetz To: mip4@ietf.org Message-Id: <20040128163658.095a4634.henrik@levkowetz.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] WG Last call on draft-ietf-mip4-dynamic-assignment-00.txt Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit This message announces a WG last call on "Mobile IPv4 Dynamic Home Agent Assignment" . The last call will conclude at 24:00 UTC on Friday, 13th Feb 2004. Please respond to this WG last call. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. draft-ietf-mip4-dynamic-assignment-00.txt proposes a messaging mechanism for dynamic home agent assignment and HA redirection. The goal is to provide a mechanism to assign an optimal HA for a Mobile IP session while allowing any suitable method for HA selection. This draft is available as Henrik -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 16:28:27 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00519 for ; Wed, 28 Jan 2004 16:28:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlxE7-0002HA-Ui for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 16:27:59 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SLRxoT008748 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 16:27:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlxE7-0002H1-RH for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 16:27:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00379 for ; Wed, 28 Jan 2004 16:27:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlxE6-0006WR-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 16:27:58 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlxD9-0006JR-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 16:27:00 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AlxCN-0006CY-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 16:26:11 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1Alx5S-0002bN-4g for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 16:19:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alx5R-0001Io-2A; Wed, 28 Jan 2004 16:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alx5C-0001IN-4i for mip4@optimus.ietf.org; Wed, 28 Jan 2004 16:18:46 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29888 for ; Wed, 28 Jan 2004 16:18:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alx5A-0005OP-00 for mip4@ietf.org; Wed, 28 Jan 2004 16:18:44 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alx4C-0005GN-00 for mip4@ietf.org; Wed, 28 Jan 2004 16:17:45 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Alx3B-0004vZ-00 for mip4@ietf.org; Wed, 28 Jan 2004 16:16:42 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0SLGBI18337 for ; Wed, 28 Jan 2004 13:16:11 -0800 X-mProtect: <200401282116> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpduDDnf0; Wed, 28 Jan 2004 13:16:07 PST Message-ID: <4018268D.1E4B7D17@iprg.nokia.com> Date: Wed, 28 Jan 2004 13:15:57 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 22] Section 3.4 para 1 is too simplified Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue22 as necessary. Here is a proposed new paragraph, utilizing the word "typically" along with some other minor improvement. A mobility agent typically returns a Registration Reply message to a mobile node which has sent a Registration Request (Section 3.3) message. If the mobile node is requesting service from a foreign agent, that foreign agent will typically receive the Reply from the home agent and subsequently relay it to the mobile node. Reply messages contain the necessary codes to inform the mobile node about the status of its Request, along with the lifetime granted by the home agent, which MAY be smaller than the original Request. Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 17:19:17 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02945 for ; Wed, 28 Jan 2004 17:19:17 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly1K-0006C4-SZ for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 17:18:50 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SMIoAL023805 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 17:18:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly1K-0006Bs-K5 for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 17:18:50 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02824 for ; Wed, 28 Jan 2004 17:18:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aly1I-00041H-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:18:48 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aly0I-0003pk-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:17:47 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AlxzK-0003fk-01 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:16:46 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1AlxmB-0005Wo-Ao for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:03:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alxm6-0004nY-Kc; Wed, 28 Jan 2004 17:03:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alxlt-0004jj-Sm for mip4@optimus.ietf.org; Wed, 28 Jan 2004 17:02:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02382 for ; Wed, 28 Jan 2004 17:02:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alxlr-0002Yj-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:02:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alxky-0002Nz-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:01:56 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Alxji-0002Ap-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:00:38 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0SM05D03979 for ; Wed, 28 Jan 2004 14:00:05 -0800 X-mProtect: <200401282200> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdKot4Dl; Wed, 28 Jan 2004 14:00:04 PST Message-ID: <401830D9.CED2FA09@iprg.nokia.com> Date: Wed, 28 Jan 2004 13:59:53 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 21] MN-AAA extension not considered in FA to HA forwarding rules Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,NEW_DOMAIN_EXTENSIONS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue21 as necessary. The problem with this text results from the previous change to Mobile IP whereby registrations can be authorized by including alternative "authorization-enabling" extensions, for instance the "MN-AAA Authentication" extension. I fixed this by rewording the bullet item as suggested at the working group meeting. OLD: - It MUST process and remove any Extensions following the Mobile-Home Authentication Extension, NEW: - It MUST process and remove any Extensions which do not precede any authorization-enabling extension. I _think_ this also takes care of the case where a foreign agent doesn't recognize the authorization-enabling extension. Perhaps we should designate new Extension with subtypes that would take care of all future authentication-enabling extensions. That would be the clearest resolution of this problem. Comments? Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 17:22:21 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03082 for ; Wed, 28 Jan 2004 17:22:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly4J-0006if-7T for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 17:21:55 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SMLtOM025823 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 17:21:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly4J-0006iQ-1J for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 17:21:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03075 for ; Wed, 28 Jan 2004 17:21:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aly4G-0004M8-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:21:52 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aly3I-0004GZ-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:20:53 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Aly2g-0004BQ-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 17:20:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly2g-0006Kq-8I; Wed, 28 Jan 2004 17:20:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aly1u-0006GY-7k for mip4@optimus.ietf.org; Wed, 28 Jan 2004 17:19:26 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02987 for ; Wed, 28 Jan 2004 17:19:22 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aly1r-000463-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:19:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aly1B-0003wt-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:18:41 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Alxzb-0003fi-00 for mip4@ietf.org; Wed, 28 Jan 2004 17:17:03 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0SMGWS05532 for ; Wed, 28 Jan 2004 14:16:32 -0800 X-mProtect: <200401282216> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdLPgYmg; Wed, 28 Jan 2004 14:16:30 PST Message-ID: <401834B5.B0438217@iprg.nokia.com> Date: Wed, 28 Jan 2004 14:16:21 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 20] Missing description - FA rejection code when MN-HA auth.ext.invalid Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue20 as necessary. The suggestion was to mandate some action on the part of a foreign agent if no MN-HA authentication extension is present. Presumably, this really means, to reject in case there is no authorization-enabling extension. But this should anyway be a rare case, and there is little danger since the home agent or other authorizing agent will reject the Request. I propose that no action be taken, and that the suggestion to change the specification be rejected. Comments? Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 18:56:16 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08125 for ; Wed, 28 Jan 2004 18:56:16 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzXD-0002eQ-Ei for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 18:55:51 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0SNtppO010185 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 18:55:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzXD-0002eB-97 for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 18:55:51 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08111 for ; Wed, 28 Jan 2004 18:55:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlzXA-0006Av-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 18:55:48 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlzWD-00066b-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 18:54:50 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AlzVO-00062V-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 18:53:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzVQ-0002aR-MK; Wed, 28 Jan 2004 18:54:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzVQ-0002aG-6O for mip4@optimus.ietf.org; Wed, 28 Jan 2004 18:54:00 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08082 for ; Wed, 28 Jan 2004 18:53:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlzVN-00062K-00 for mip4@ietf.org; Wed, 28 Jan 2004 18:53:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlzUT-0005x4-00 for mip4@ietf.org; Wed, 28 Jan 2004 18:53:02 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AlzTu-0005pm-00 for mip4@ietf.org; Wed, 28 Jan 2004 18:52:26 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0SNpsW21094 for ; Wed, 28 Jan 2004 15:51:54 -0800 X-mProtect: <200401282351> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdAKIySp; Wed, 28 Jan 2004 15:51:53 PST Message-ID: <40184B0F.F7199D88@iprg.nokia.com> Date: Wed, 28 Jan 2004 15:51:43 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [issue 19] Multiple authorization-enabling extensions should be permitted Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,NEW_DOMAIN_EXTENSIONS autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue19 as necessary. Discussion at IETF58 was not wholly conclusive. I have taken the suggested wording changes, and incorporated the mandate that the home agent must insure that all verifications have taken place. The home agent is sometimes unable to make the verification directly, so some of the suggested wording changes required slight additional modification. ============================================================================= Section 3.5.2 Existing Text: Exactly one authorization-enabling extension MUST be present in all Registration Requests, and also in all Registration Replies generated by the Home Agent. The Mobile-Home Authentication Extension is always an authorization-enabling for registration messages specified in this document. This requirement is intended to eliminate problems [2] which result from the uncontrolled propagation of remote redirects in the Internet. The location of the extension marks the end of the authenticated data. New Text: At least one authorization-enabling extension MUST be present in all Registration Requests, and also in all Registration Replies generated by the Home Agent. The Mobile-Home Authentication Extension is always an authorization-enabling for registration messages specified in this document. This requirement is intended to eliminate problems [2] which result from the uncontrolled propagation of remote redirects in the Internet. The location of the authorization-enabling extension marks the end of the data to be authenticated by the authorizing agent interpreting that authorization-enabling extension. ============================================================================= Section 3.6.1.3 Note in the discussion about revised text for section 3.6.1.3, that the Mobile-Foreign authentication extension was never intended to be an authorization-enabling extension. The only new extension, defined after RFC 2002, which is specified to be an authorization-enabling extension is the MN-AAA extension. Finally, I did not see why item (c) in 3.6.1.3 was changed back to be MN-HA, since that position in the ordering of extensions was previously enabled to contain the MN-AAA authentication extension. Moreover, the previously suggested wording would not allow the foreign agent to remove extensions that were only meant for its own use, since presumably the AAA or other authorizing agent is somewhere external to the foreign agent. If the foreign agent is intended to be the authorizing agent, then the new text below takes that into account. Existing Text: This section describes the ordering of any mandatory and any optional Extensions that a mobile node appends to a Registration Request. This following ordering MUST be followed: a) The IP header, followed by the UDP header, followed by the fixed-length portion of the Registration Request, followed by b) If present, any non-authentication Extensions expected to be used by the home agent (which may or may not also be useful to the foreign agent), followed by c) An authorization-enabling extension, followed by d) If present, any non-authentication Extensions used only by the foreign agent, followed by e) The Mobile-Foreign Authentication Extension, if present. Note that items (a) and (c) MUST appear in every Registration Request sent by the mobile node. Items (b), (d), and (e) are optional. However, item (e) MUST be included when the mobile node and the foreign agent share a mobility security association. New text: This section describes the ordering of any mandatory and any optional Extensions that a mobile node appends to a Registration Request. This ordering is REQUIRED: a) The IP header, followed by the UDP header, followed by the fixed-length portion of the Registration Request, followed by b) If present, any non-authentication Extensions expected to be used by the home agent or other authorizing agent (which may or may not also be useful to the foreign agent), followed by c) All authorization-enabling extensions, followed by d) If present, any non-authentication Extensions used only by the foreign agent, followed by e) The Mobile-Foreign Authentication Extension, if present. Note that items (a) and (c) MUST appear in every Registration Request sent by the mobile node. Items (b), (d), and (e) are optional. However, item (e) MUST be included when the mobile node and the foreign agent share a mobility security association. ============================================================================= section 3.8.2.1 Existing text: a) The home agent MUST check for the presence of an authorization-enabling extension, and perform the indicated authentication. Exactly one authorization-enabling extension MUST be present in the Registration Request; and the home agent MUST either check the Authenticator value in the extension or verify that the authenticator value has been checked by another agent with which it has a security association. If no authorization-enabling extension is found, or if more than one authorization-enabling extension is found, or if the Authenticator is invalid, the home agent MUST reject the mobile node's registration and SHOULD send a Registration Reply to the mobile node with Code 131. The home agent MUST then discard the Request and SHOULD log the error as a security exception. b) The home agent MUST check that the registration Identification field is correct using the context selected by the SPI within the authorization-enabling extension. See Section 5.7 for a description of how this is performed. If incorrect, the home agent MUST reject the Request and SHOULD send a Registration Reply to the mobile node with Code 133, including an Identification field computed in accordance with the rules specified in Section 5.7. The home agent MUST do no further processing with such a Request, though it SHOULD log the error as a security exception. New text: a) The home agent MUST check for the presence of an authorization-enabling extension, and perform the indicated authentication. Exactly one authorization-enabling extension MUST be present in the Registration Request; and the home agent MUST either check the Authenticator value in the extension or verify that the authenticator value has been checked by another agent with which it has a security association. If no authorization-enabling extension is found, or if more than one authorization-enabling extension is found, or if the Authenticator is invalid, the home agent MUST reject the mobile node's registration and SHOULD send a Registration Reply to the mobile node with Code 131. The home agent MUST then discard the Request and SHOULD log the error as a security exception. b) The home agent MUST check that the registration Identification field is correct using the context selected by the SPI within the authorization-enabling extension. See Section 5.7 for a description of how this is performed. If incorrect, the home agent MUST reject the Request and SHOULD send a Registration Reply to the mobile node with Code 133, including an Identification field computed in accordance with the rules specified in Section 5.7. The home agent MUST do no further processing with such a Request, though it SHOULD log the error as a security exception. ============================================================================= Section: 3.8.2.3. I wonder how long this mistake has been sitting there unnoticed!!! Existing text: If the Registration Reply does not satisfy all of the validity checks in Section 3.8.2.1 ........ New text: If the Registration Reply does not satisfy all of the validity checks in Section 3.8.2.1 ........ ============================================================================= Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 19:16:22 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08581 for ; Wed, 28 Jan 2004 19:16:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzqd-0004C5-E8 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:15:55 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T0FtHn016115 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:15:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzqd-0004Bq-AP for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 19:15:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08571 for ; Wed, 28 Jan 2004 19:15:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alzqb-0000ET-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:15:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alzpc-00007i-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:14:53 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Alzol-00001o-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:13:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzom-00047g-38; Wed, 28 Jan 2004 19:14:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzof-00047V-SI for mip4@optimus.ietf.org; Wed, 28 Jan 2004 19:13:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08538 for ; Wed, 28 Jan 2004 19:13:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alzoe-00001G-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:13:52 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alznj-0007jX-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:12:55 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Alzn5-0007YN-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:12:15 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0T0Bic02810 for ; Wed, 28 Jan 2004 16:11:44 -0800 X-mProtect: <200401290011> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdafJho2; Wed, 28 Jan 2004 16:11:42 PST Message-ID: <40184FB5.B1EBB40A@iprg.nokia.com> Date: Wed, 28 Jan 2004 16:11:33 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Subject: Re: [Mip4] [issue 19] Multiple authorization-enabling extensions should bepermitted References: <40184B0F.F7199D88@iprg.nokia.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, It was pointed out (thanks, Alan!) that I still didn't properly illustrate the needed change in 3.8.2.3: "Charles E. Perkins" wrote: > ============================================================================= > > Section: 3.8.2.3. > > I wonder how long this mistake has been sitting there unnoticed!!! > > Existing text: > If the Registration Reply does not satisfy all of the validity checks > in Section 3.8.2.1 ........ > > New text: > If the Registration Reply does not satisfy all of the validity checks > in Section 3.8.2.1 ........ > > ============================================================================= That new text should be: If the Registration Request does not satisfy all of the validity checks in Section 3.8.2.1 ........ It has been corrected in the revised document for sure now. Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 19:19:19 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08714 for ; Wed, 28 Jan 2004 19:19:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlztU-0004Oz-Ep for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:18:52 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T0IqOF016915 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:18:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlztU-0004Ok-BC for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 19:18:52 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08703 for ; Wed, 28 Jan 2004 19:18:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlztS-0000YP-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:18:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlzsX-0000Sb-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:17:54 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Alzrg-0000MZ-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:17:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzrg-0004HJ-Ri; Wed, 28 Jan 2004 19:17:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Alzrc-0004Gg-84 for mip4@optimus.ietf.org; Wed, 28 Jan 2004 19:16:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08630 for ; Wed, 28 Jan 2004 19:16:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Alzra-0000LV-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:16:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Alzqi-0000FS-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:16:00 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AlzqI-00008m-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:15:34 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0T0F4c11941 for ; Wed, 28 Jan 2004 16:15:04 -0800 X-mProtect: <200401290015> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdaoZx9d; Wed, 28 Jan 2004 16:15:01 PST Message-ID: <4018507B.A4881E58@iprg.nokia.com> Date: Wed, 28 Jan 2004 16:14:51 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 18] The FA is rejecting with Error Code 136 which is meant for the home agent Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue18 as necessary. The proposed solution: create a new error code. Existing text: if the foreign agent does not serve the mobile node as a home agent, the foreign agent rejects the Registration Request with code 136 (unknown home agent address). New text: if the foreign agent does not serve the mobile node as a home agent, the foreign agent rejects the Registration Request with code TBD-IANA (Invalid Home Agent Address). New text in IANA Considerations: In this revised specification, a new Code value (for the field in the Registration Request message) is needed within the range typically used for Foreign Agent messages. This error code is needed to indicate the status "Invalid Home Agent Address". See section 3.7.2 for details. Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 19:27:20 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09001 for ; Wed, 28 Jan 2004 19:27:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am01F-00057C-9I for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:26:53 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T0QrqF019655 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:26:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am01F-00056w-4f for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 19:26:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08991 for ; Wed, 28 Jan 2004 19:26:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Am01D-0001NS-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:26:51 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Am00J-0001IQ-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:25:55 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AlzzR-0001D5-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:25:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzzR-00051Q-8B; Wed, 28 Jan 2004 19:25:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AlzzL-00050w-JH for mip4@optimus.ietf.org; Wed, 28 Jan 2004 19:24:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08909 for ; Wed, 28 Jan 2004 19:24:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AlzzJ-0001Bv-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:24:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AlzyM-00015q-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:23:55 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AlzxS-0000uc-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:22:58 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0T0MRN25045 for ; Wed, 28 Jan 2004 16:22:27 -0800 X-mProtect: <200401290022> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdMu0jFy; Wed, 28 Jan 2004 16:22:26 PST Message-ID: <40185238.F883A5F2@iprg.nokia.com> Date: Wed, 28 Jan 2004 16:22:16 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 17] Enhanced Registration Request processing at the Home Agent. Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue17 and: http://www.ietf.org/proceedings/03nov/142.htm as necessary. This issue has to deal with what the home agent might do if it gets a Registration Request to an unknown unicast address. Nobody presented sufficient reasons for the home agent to take any useful action other than rejecting the Request. I don't think that any changes to the specification are yet warranted by discussion up until now. Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 19:30:22 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09098 for ; Wed, 28 Jan 2004 19:30:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am04B-0005Cf-Kx for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:29:55 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T0Ttit019995 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 19:29:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am04B-0005CQ-GK for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 19:29:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09084 for ; Wed, 28 Jan 2004 19:29:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Am049-0001e1-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:29:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Am03A-0001Yh-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:28:53 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Am02K-0001Ts-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 19:28:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am02L-00058n-BZ; Wed, 28 Jan 2004 19:28:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am02F-00057z-BA for mip4@optimus.ietf.org; Wed, 28 Jan 2004 19:27:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09053 for ; Wed, 28 Jan 2004 19:27:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Am02D-0001TF-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:27:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Am01J-0001OL-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:26:57 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Am00l-0001I5-00 for mip4@ietf.org; Wed, 28 Jan 2004 19:26:23 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0T0Pqa32089 for ; Wed, 28 Jan 2004 16:25:52 -0800 X-mProtect: <200401290025> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdYn320c; Wed, 28 Jan 2004 16:25:51 PST Message-ID: <40185305.A8CE2E24@iprg.nokia.com> Date: Wed, 28 Jan 2004 16:25:41 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip4@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [Issue 9] Why Allowing FA to reject RRQ with error code 136 Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Please refer to previous discussion at the following URL: http://www.mip4.org/issues/tracker/mip4/issue9 and: http://www.ietf.org/proceedings/03nov/142.htm as necessary. There was some problems with wording in the existing specification, revolving around allowing the foreign agent to use Code 136. This will be resolved, if the proposed solution to issue 18 is adopted. Regards, Charlie P. -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Wed Jan 28 21:10:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11919 for ; Wed, 28 Jan 2004 21:10:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am1d1-0005S5-R8 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 21:10:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0T29xFA020951 for mip4-archive@odin.ietf.org; Wed, 28 Jan 2004 21:09:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am1d1-0005Rq-AD for mip4-web-archive@optimus.ietf.org; Wed, 28 Jan 2004 21:09:59 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11899 for ; Wed, 28 Jan 2004 21:09:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Am1cy-00032E-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 21:09:56 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Am1c1-0002wt-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 21:08:58 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Am1b8-0002rW-00 for mip4-web-archive@ietf.org; Wed, 28 Jan 2004 21:08:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am1b9-00050E-CF; Wed, 28 Jan 2004 21:08:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Am1b3-0004xb-8l for mip4@optimus.ietf.org; Wed, 28 Jan 2004 21:07:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11812 for ; Wed, 28 Jan 2004 21:07:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Am1b0-0002qD-00 for mip4@ietf.org; Wed, 28 Jan 2004 21:07:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Am1a2-0002kV-00 for mip4@ietf.org; Wed, 28 Jan 2004 21:06:54 -0500 Received: from [202.106.187.158] (helo=sina.com) by ietf-mx with smtp (Exim 4.12) id 1Am1Z8-0002ej-00 for mip4@ietf.org; Wed, 28 Jan 2004 21:05:58 -0500 Received: (qmail 71807 invoked from network); 29 Jan 2004 02:05:51 -0000 Received: from unknown (HELO wym-pc) (210.42.103.237) by 202.106.187.158 with SMTP; 29 Jan 2004 02:05:51 -0000 Date: Thu, 29 Jan 2004 10:07:15 +0800 From: "Yuming Wang" To: "Henrik Levkowetz" , "pvandenbergen" Cc: "Mip6" , "mip4" , "users" , "snap-users" , "users" Subject: Re: [Mip6] Re: [Mip4] for your information - Mobile IP v4 and v6implementations. X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Henrik and Paul, That's a good summary, a useful list. Thanks! >Hello Paul, > >Tuesday 20 January 2004, paul van den bergen wrote: >> Hi all, >> a few weeks ago I asked for mobile IP implementations... >> >> just thought you'd all be interested to see what I found... > > > >Useful and interesting indeed. I've taken the liberty of duplicating >the information here: > > > > > Thanks, > Henrik > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > > >. Yuming 2004-01-29 ---------------- Yuming Wang ----------------- NGIT Research Group, ITEC R&D Center, EI Dpt., HuaZhong University of Science and Technology. Email: acer_wym@sina.com Home Page: http://itec.hust.edu.cn/wym.htm TEL: +86-27-87453207 FAX: +86-27-87456436 ---- -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Fri Jan 30 11:53:13 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27214 for ; Fri, 30 Jan 2004 11:53:13 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambsf-00019i-15 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 11:52:33 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UGqWUA004443 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 11:52:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambse-00019a-Px for mip4-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 11:52:32 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27159 for ; Fri, 30 Jan 2004 11:52:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ambsd-0006MB-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:52:31 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ambrl-0006Do-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:51:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AmbrH-000652-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:51:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmbrF-0000Yv-7T; Fri, 30 Jan 2004 11:51:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambqs-0000Wa-Kl for mip4@optimus.ietf.org; Fri, 30 Jan 2004 11:50:42 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26948; Fri, 30 Jan 2004 11:50:39 -0500 (EST) Message-Id: <200401301650.LAA26948@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip4@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 30 Jan 2004 11:50:39 -0500 Subject: [Mip4] I-D ACTION:draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 --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 : Low latency Handoffs in Mobile IPv4 Author(s) : K. Malki Filename : draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt Pages : 52 Date : 2004-1-29 Mobile IPv4 describes how a Mobile Node can perform IP-layer handoffs between subnets served by different Foreign Agents. In certain cases, the latency involved in these handoffs can be above the threshold required for the support of delay-sensitive or real-time services. The aim of this document is to present two methods to achieve low- latency Mobile IP handoffs. In addition, a combination of these two methods is described. The described techniques allow greater support for real-time services on a Mobile IPv4 network by minimising the period of time when a Mobile Node is unable to send or receive IP packets due to the delay in the Mobile IP Registration process. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-1-30121129.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mobileip-lowlatency-handoffs-v4-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-30121129.I-D@ietf.org> --OtherAccess-- --NextPart-- -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Fri Jan 30 11:54:02 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27390 for ; Fri, 30 Jan 2004 11:54:02 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambtd-0001QE-U4 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 11:53:34 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UGrXJh005460 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 11:53:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambtd-0001Pz-Pg for mip4-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 11:53:33 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27301 for ; Fri, 30 Jan 2004 11:53:30 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ambtc-0006XN-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:53:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ambsj-0006N6-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:52:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Ambs8-0006EE-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 11:52:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ambs8-0000w4-QX; Fri, 30 Jan 2004 11:52:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmbrR-0000dF-3u for mip4@optimus.ietf.org; Fri, 30 Jan 2004 11:51:17 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26985 for ; Fri, 30 Jan 2004 11:51:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmbrP-0006Ak-00 for mip4@ietf.org; Fri, 30 Jan 2004 11:51:16 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmbqP-00061I-00 for mip4@ietf.org; Fri, 30 Jan 2004 11:50:13 -0500 Received: from [47.81.138.65] (helo=zsc3s004.nortelnetworks.com) by ietf-mx with esmtp (Exim 4.12) id 1AmbpT-0005mt-00 for mip4@ietf.org; Fri, 30 Jan 2004 11:49:15 -0500 Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zsc3s004.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0UGmbi01761; Fri, 30 Jan 2004 08:48:38 -0800 (PST) Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 30 Jan 2004 10:48:37 -0600 Message-ID: <870397D7C140C84DB081B88396458DAF746CDD@zrc2c000.us.nortel.com> From: "Jayshree Bharatia" To: "'Charles E. Perkins'" Cc: mip4@ietf.org Subject: RE: [Mip4] [Issue 18] The FA is rejecting with Error Code 136 whi ch is meant for the home agent Date: Fri, 30 Jan 2004 10:48:36 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Hello Charlie, I would think that this new code value you are defining will be for the Registration Reply message (and not for Registration Request). My suggestion is inline... Thanks, Jayshree > -----Original Message----- > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > Sent: Wednesday, January 28, 2004 6:15 PM > To: mip4@ietf.org > Subject: [Mip4] [Issue 18] The FA is rejecting with Error > Code 136 which is meant for the home agent > > > > Hello folks, > > Please refer to previous discussion at the following URL: > http://www.mip4.org/issues/tracker/mip4/issue18 > as necessary. > > The proposed solution: create a new error code. > > Existing text: > if the foreign agent does not serve the mobile node as a > home agent, > the foreign agent rejects the Registration Request with code 136 > (unknown home agent address). > > New text: > if the foreign agent does not serve the mobile node as a > home agent, > the foreign agent rejects the Registration Request with code > TBD-IANA (Invalid Home Agent Address). > > New text in IANA Considerations: > In this revised specification, a new Code value (for the > field in the > Registration Request message) is needed within the range typically > used for Foreign Agent messages. This error code is needed to > indicate the status "Invalid Home Agent Address". See > section 3.7.2 > for details. > [JB] New text in IANA Considerations: In this revised specification, a new Code value (for the field in the Registration Reply message) is needed within ... > > Regards, > Charlie P. > > -- > Mip4 mailing list > Mip4@ietf.org > https://www.ietf.org/mailman/listinfo/mip4 > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Fri Jan 30 12:10:47 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28717 for ; Fri, 30 Jan 2004 12:10:47 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amc9r-0003Yw-Qo for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 12:10:20 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UHAJF4013688 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 12:10:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amc9r-0003Yh-F0 for mip4-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 12:10:19 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28704 for ; Fri, 30 Jan 2004 12:10:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Amc9q-0001Fo-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 12:10:18 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Amc91-00019K-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 12:09:28 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1Amc8a-00012F-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 12:09:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amc8a-0003Sg-84; Fri, 30 Jan 2004 12:09:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amc84-0003MK-3a for mip4@optimus.ietf.org; Fri, 30 Jan 2004 12:08:28 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28573 for ; Fri, 30 Jan 2004 12:08:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Amc81-0000z0-00 for mip4@ietf.org; Fri, 30 Jan 2004 12:08:25 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Amc7B-0000nf-00 for mip4@ietf.org; Fri, 30 Jan 2004 12:07:33 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Amc6F-0000VT-00 for mip4@ietf.org; Fri, 30 Jan 2004 12:06:35 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0UH5YE29029; Fri, 30 Jan 2004 09:05:34 -0800 X-mProtect: <200401301705> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdNCRvny; Fri, 30 Jan 2004 09:05:32 PST Message-ID: <401A8ED2.CAC5E6AA@iprg.nokia.com> Date: Fri, 30 Jan 2004 09:05:22 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jayshree Bharatia CC: mip4@ietf.org Subject: Re: [Mip4] [Issue 18] The FA is rejecting with Error Code 136 which is meant for the home agent References: <870397D7C140C84DB081B88396458DAF746CDD@zrc2c000.us.nortel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Jayshree, Yes, you are quite correct. I have changed it within the revised document now -- thanks! Regards, Charlie P. Jayshree Bharatia wrote: > > Hello Charlie, > > I would think that this new code value you are defining will be for the > Registration Reply message (and not for Registration Request). My suggestion > is inline... > > Thanks, > Jayshree > > > -----Original Message----- > > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > > Sent: Wednesday, January 28, 2004 6:15 PM > > To: mip4@ietf.org > > Subject: [Mip4] [Issue 18] The FA is rejecting with Error > > Code 136 which is meant for the home agent > > > > > > > > Hello folks, > > > > Please refer to previous discussion at the following URL: > > http://www.mip4.org/issues/tracker/mip4/issue18 > > as necessary. > > > > The proposed solution: create a new error code. > > > > Existing text: > > if the foreign agent does not serve the mobile node as a > > home agent, > > the foreign agent rejects the Registration Request with code 136 > > (unknown home agent address). > > > > New text: > > if the foreign agent does not serve the mobile node as a > > home agent, > > the foreign agent rejects the Registration Request with code > > TBD-IANA (Invalid Home Agent Address). > > > > New text in IANA Considerations: > > In this revised specification, a new Code value (for the > > field in the > > Registration Request message) is needed within the range typically > > used for Foreign Agent messages. This error code is needed to > > indicate the status "Invalid Home Agent Address". See > > section 3.7.2 > > for details. > > > [JB] New text in IANA Considerations: > In this revised specification, a new Code value (for the field in the > Registration Reply message) is needed within ... > > > > Regards, > > Charlie P. > > > > -- > > Mip4 mailing list > > Mip4@ietf.org > > https://www.ietf.org/mailman/listinfo/mip4 > > -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Fri Jan 30 13:47:55 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07967 for ; Fri, 30 Jan 2004 13:47:55 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amdfr-0005Y1-7J for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 13:47:27 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UIlRxx021315 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 13:47:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amdfr-0005Xe-36 for mip4-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 13:47:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07951 for ; Fri, 30 Jan 2004 13:47:24 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Amdfo-0002pr-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 13:47:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Amdf0-0002j8-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 13:46:34 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AmdeR-0002bV-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 13:46:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmdeT-0005QF-IT; Fri, 30 Jan 2004 13:46:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Amdds-0005N0-MY for mip4@optimus.ietf.org; Fri, 30 Jan 2004 13:45:24 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07817 for ; Fri, 30 Jan 2004 13:45:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Amddq-0002Ya-00 for mip4@ietf.org; Fri, 30 Jan 2004 13:45:22 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Amdcm-0002P0-00 for mip4@ietf.org; Fri, 30 Jan 2004 13:44:17 -0500 Received: from [47.81.138.65] (helo=zsc3s004.nortelnetworks.com) by ietf-mx with esmtp (Exim 4.12) id 1Amdbn-00029B-00 for mip4@ietf.org; Fri, 30 Jan 2004 13:43:15 -0500 Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zsc3s004.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0UIggi20959; Fri, 30 Jan 2004 10:42:43 -0800 (PST) Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 30 Jan 2004 12:42:42 -0600 Message-ID: <870397D7C140C84DB081B88396458DAF746CE1@zrc2c000.us.nortel.com> From: "Jayshree Bharatia" To: "'Charles E. Perkins'" Cc: mip4@ietf.org Subject: RE: [Mip4] [issue 19] Multiple authorization-enabling extensions should be permitted Date: Fri, 30 Jan 2004 12:42:42 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Hello Charlie, Looks like there is no change shown in the "Existing Text" and "New Text" for section 3.8.2.1. We need changes in this paragraph to allow multiple authorization-enabling extensions in the Registration Request. I believe there was some text proposed earlier on the mailing list for this. Regards, Jayshree > -----Original Message----- > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > Sent: Wednesday, January 28, 2004 5:52 PM > To: mip4@ietf.org > Subject: [Mip4] [issue 19] Multiple authorization-enabling > extensions should be permitted > > [...] > ============================================================== > =============== > > section 3.8.2.1 > > Existing text: > > a) The home agent MUST check for the presence of an > authorization-enabling extension, and perform the indicated > authentication. Exactly one authorization-enabling extension > MUST be present in the Registration Request; and the > home agent > MUST either check the Authenticator value in the extension or > verify that the authenticator value has been checked > by another > agent with which it has a security association. If no > authorization-enabling extension is found, or if > more than one > authorization-enabling extension is found, or if the > Authenticator is invalid, the home agent MUST reject > the mobile > node's registration and SHOULD send a Registration > Reply to the > mobile node with Code 131. The home agent MUST then discard > the Request and SHOULD log the error as a security exception. > > b) The home agent MUST check that the registration > Identification > field is correct using the context selected by the SPI within > the authorization-enabling extension. See Section 5.7 for a > description of how this is performed. If incorrect, the home > agent MUST reject the Request and SHOULD send a Registration > Reply to the mobile node with Code 133, including an > Identification field computed in accordance with the rules > specified in Section 5.7. The home agent MUST do no further > processing with such a Request, though it SHOULD log > the error > as a security exception. > > New text: > a) The home agent MUST check for the presence of an > authorization-enabling extension, and perform the indicated > authentication. Exactly one > authorization-enabling extension > MUST be present in the Registration Request; and the home > agent MUST either check the Authenticator value in the > extension or verify that the authenticator value has been > checked by another agent with which it has a security > association. If no authorization-enabling extension is > found, or if more than one authorization-enabling > extension > is found, or if the Authenticator is invalid, the > home agent > MUST reject the mobile node's registration and > SHOULD send > a Registration Reply to the mobile node with Code > 131. The > home agent MUST then discard the Request and > SHOULD log the > error as a security exception. > > b) The home agent MUST check that the registration > Identification field is correct using the context selected > by the SPI within the authorization-enabling > extension. See > Section 5.7 for a description of how this is performed. If > incorrect, the home agent MUST reject the Request > and SHOULD > send a Registration Reply to the mobile node with Code 133, > including an Identification field computed in > accordance with > the rules specified in Section 5.7. The home agent MUST do > no further processing with such a Request, though it SHOULD > log the error as a security exception. > [...] -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4 From exim@www1.ietf.org Fri Jan 30 14:28:19 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10584 for ; Fri, 30 Jan 2004 14:28:19 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmeIy-000060-AM for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 14:27:52 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0UJRqXk000368 for mip4-archive@odin.ietf.org; Fri, 30 Jan 2004 14:27:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AmeIx-00005m-UH for mip4-web-archive@optimus.ietf.org; Fri, 30 Jan 2004 14:27:52 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10457 for ; Fri, 30 Jan 2004 14:27:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AmeIv-0001Mx-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 14:27:49 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AmeH3-0000ti-00 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 14:25:53 -0500 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1AmeFp-0000iO-01 for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 14:24:37 -0500 Received: from [132.151.1.19] (helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1Ame3m-0007Xj-AJ for mip4-web-archive@ietf.org; Fri, 30 Jan 2004 14:12:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ame3g-0007m0-2Y; Fri, 30 Jan 2004 14:12:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ame3E-0007jv-IP for mip4@optimus.ietf.org; Fri, 30 Jan 2004 14:11:36 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10008 for ; Fri, 30 Jan 2004 14:11:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ame3C-00076f-00 for mip4@ietf.org; Fri, 30 Jan 2004 14:11:34 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ame2S-0006vb-00 for mip4@ietf.org; Fri, 30 Jan 2004 14:10:50 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1Ame0v-0006QV-00 for mip4@ietf.org; Fri, 30 Jan 2004 14:09:13 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i0UJ7LI32445; Fri, 30 Jan 2004 11:07:21 -0800 X-mProtect: <200401301907> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdeDPjBn; Fri, 30 Jan 2004 11:07:20 PST Message-ID: <401AAB5D.2D176864@iprg.nokia.com> Date: Fri, 30 Jan 2004 11:07:09 -0800 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jayshree Bharatia CC: mip4@ietf.org References: <870397D7C140C84DB081B88396458DAF746CE1@zrc2c000.us.nortel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip4] [issue 19] Multiple authorization-enabling extensions should be permitted Sender: mip4-admin@ietf.org Errors-To: mip4-admin@ietf.org X-BeenThere: mip4@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobility for IPv4 List-Post: List-Help: List-Subscribe: , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Jayshree, Yes, as it turns out it was a cut and paste error. The text I labeled as the "new text" was NOT the new text. Here is the actual new text that should have been pasted in: a) The home agent MUST check for the presence of at least one authorization-enabling extension, and ensure that all indicated authentications are carried out. At least one authorization-enabling extension MUST be present in the Registration Request; and the home agent MUST either check the Authenticator value in the extension or verify that the authenticator value has been checked by another agent with which it has a security association. If no authorization-enabling extension is found, or if the Authenticator is invalid, the home agent MUST reject the mobile node's registration and SHOULD send a Registration Reply to the mobile node with Code 131. The home agent MUST then discard the Request and SHOULD log the error as a security exception. If the home agent receives a Registration Request without a Mobile-Home Authentication extension from a Mobile Node that has a security association with this home agent, the home agent MUST discard the Mobile Node's Registration Request. b) The home agent MUST check that the registration Identification field is correct using the context selected by the SPI within the authorization-enabling extension that the home agent used to authenticate the Mobile Node's Registration Request. See Section 5.7 for a description of how this is performed. If incorrect, the home agent MUST reject the Request and SHOULD send a Registration Reply to the mobile node with Code 133, including an Identification field computed in accordance with the rules specified in Section 5.7. The home agent MUST do no further processing with such a Request, though it SHOULD log the error as a security exception. And, for convenience, here is the old text again: a) The home agent MUST check for the presence of an authorization-enabling extension, and perform the indicated authentication. Exactly one authorization-enabling extension MUST be present in the Registration Request; and the home agent MUST either check the Authenticator value in the extension or verify that the authenticator value has been checked by another agent with which it has a security association. If no authorization-enabling extension is found, or if more than one authorization-enabling extension is found, or if the Authenticator is invalid, the home agent MUST reject the mobile node's registration and SHOULD send a Registration Reply to the mobile node with Code 131. The home agent MUST then discard the Request and SHOULD log the error as a security exception. b) The home agent MUST check that the registration Identification field is correct using the context selected by the SPI within the authorization-enabling extension. See Section 5.7 for a description of how this is performed. If incorrect, the home agent MUST reject the Request and SHOULD send a Registration Reply to the mobile node with Code 133, including an Identification field computed in accordance with the rules specified in Section 5.7. The home agent MUST do no further processing with such a Request, though it SHOULD log the error as a security exception. Thanks again for pointing out the mistake; please let me know if you think it serves the intended purpose. Because of discussion at the last IETF, I thought that some of the changes from the earlier proposed text needed to be reformulated, so I didn't use it verbatim. Regards, Charlie P. Jayshree Bharatia wrote: > > Hello Charlie, > > Looks like there is no change shown in the "Existing Text" and "New Text" > for section 3.8.2.1. We need changes in this paragraph to allow multiple > authorization-enabling extensions in the Registration Request. > > I believe there was some text proposed earlier on the mailing list for this. > > Regards, > Jayshree ============================================================================ -- Mip4 mailing list Mip4@ietf.org https://www.ietf.org/mailman/listinfo/mip4