From exim@www1.ietf.org Thu Oct 2 10:51:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23343 for ; Thu, 2 Oct 2003 10:51:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54nP-0003iu-4L for mip6-archive@odin.ietf.org; Thu, 02 Oct 2003 10:51:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h92EpBGG014304 for mip6-archive@odin.ietf.org; Thu, 2 Oct 2003 10:51:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54nP-0003ia-09 for mip6-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 10:51:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23287 for ; Thu, 2 Oct 2003 10:50:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A54nL-0001VI-00 for mip6-web-archive@ietf.org; Thu, 02 Oct 2003 10:51:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A54nL-0001VD-00 for mip6-web-archive@ietf.org; Thu, 02 Oct 2003 10:51:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54nG-0003gC-7F; Thu, 02 Oct 2003 10:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A54mc-0003e3-5m for mip6@optimus.ietf.org; Thu, 02 Oct 2003 10:50:22 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23018; Thu, 2 Oct 2003 10:50:11 -0400 (EDT) Message-Id: <200310021450.KAA23018@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: mip6@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 02 Oct 2003 10:50:11 -0400 Subject: [Mip6] I-D ACTION:draft-haddad-mipv6-omipv6-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Optimizing Mobile IPv6 (OMIPv6) Author(s) : W. Haddad, S. Krishnan Filename : draft-haddad-mipv6-omipv6-00.txt Pages : 8 Date : 2003-10-2 Mobile IPv6 [1] is supposed to solve the mobility problem and offers a new mode, which allows the flows of data packets between a mobile node (MN) and a correspondent node (CN) to be exchanged via the direct path between them. However this efficiency comes at high price in terms of security needs and excessive mobility signaling messages. This draft introduces a proposal to make Mobile IPv6 more optimized with regards to security needs and less redundant in signaling messages. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-haddad-mipv6-omipv6-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-haddad-mipv6-omipv6-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-haddad-mipv6-omipv6-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: <2003-10-2105821.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-haddad-mipv6-omipv6-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-haddad-mipv6-omipv6-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-2105821.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 3 12:00:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13520 for ; Fri, 3 Oct 2003 12:00:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5SLi-0004Zp-G0 for mip6-archive@odin.ietf.org; Fri, 03 Oct 2003 12:00:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93G0AMl017586 for mip6-archive@odin.ietf.org; Fri, 3 Oct 2003 12:00:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5SLh-0004ZZ-Uz for mip6-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 12:00:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13485 for ; Fri, 3 Oct 2003 12:00:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5SLg-0002aZ-00 for mip6-web-archive@ietf.org; Fri, 03 Oct 2003 12:00:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A5SLg-0002aV-00 for mip6-web-archive@ietf.org; Fri, 03 Oct 2003 12:00:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5SLb-0004Yz-6x; Fri, 03 Oct 2003 12:00:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5SLD-0004YM-8Y for mip6@optimus.ietf.org; Fri, 03 Oct 2003 11:59:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13466 for ; Fri, 3 Oct 2003 11:59:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5SLB-0002aM-00 for mip6@ietf.org; Fri, 03 Oct 2003 11:59:37 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1A5SLB-0002aI-00 for mip6@ietf.org; Fri, 03 Oct 2003 11:59:37 -0400 Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h93FxY77022082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Oct 2003 08:59:35 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h93FxWDw015192; Fri, 3 Oct 2003 08:59:33 -0700 (PDT) Message-Id: <5.2.0.9.2.20031003085455.026a61f0@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 03 Oct 2003 08:59:30 -0700 To: mip6@ietf.org From: Frank Quick Cc: mobile-ip@sunroof.eng.sun.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Mip6] Comment on MIPv6 I-D Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , In section 10.3.1: "To begin processing the Binding Update, the home agent MUST perform the following sequence of tests: ... o A Home Address destination option MUST be present in the message. ..." 11.7.1 says essentially the same thing on page 131: " o The packet MUST contain a Home Address destination option, giving the mobile node's home address for the binding." This seems to moot some of the text in 11.7.1, page 132: "The mobile node MUST use its home address - either in the Home Address destination option or in the Source Address field of the IPv6 header - in Binding Updates sent to the home agent." This sentence implies that the node has the option of EITHER/OR whereas the preceding text would say the node MUST include the Home Address destination option, and (presumably) MAY also use the home address as the Source Address. I'd suggest that this sentence be deleted, or amended to reflect the fact that the home address as Source Address is allowed but the destination option is mandatory. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 3 22:55:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08773 for ; Fri, 3 Oct 2003 22:55:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5cZY-0001DU-Tf for mip6-archive@odin.ietf.org; Fri, 03 Oct 2003 22:55:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h942t8V2004672 for mip6-archive@odin.ietf.org; Fri, 3 Oct 2003 22:55:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5cZY-0001DH-Pc for mip6-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 22:55:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08770 for ; Fri, 3 Oct 2003 22:54:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5cZV-0002Ou-00 for mip6-web-archive@ietf.org; Fri, 03 Oct 2003 22:55:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A5cZU-0002Oq-00 for mip6-web-archive@ietf.org; Fri, 03 Oct 2003 22:55:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5cZS-0001Cp-2O; Fri, 03 Oct 2003 22:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5cZB-0001CP-IP for mip6@optimus.ietf.org; Fri, 03 Oct 2003 22:54:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08764 for ; Fri, 3 Oct 2003 22:54:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A5cZ7-0002Om-00 for mip6@ietf.org; Fri, 03 Oct 2003 22:54:42 -0400 Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx with esmtp (Exim 4.12) id 1A5cZ7-0002OM-00 for mip6@ietf.org; Fri, 03 Oct 2003 22:54:41 -0400 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HM700201PE4RH@mailout3.samsung.com> for mip6@ietf.org; Sat, 04 Oct 2003 11:54:04 +0900 (KST) Received: from ep_mmp2 (localhost [127.0.0.1]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HM7008EYPE49Q@mailout3.samsung.com> for mip6@ietf.org; Sat, 04 Oct 2003 11:54:04 +0900 (KST) Received: from daniel ([168.219.203.183]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HM700JI2PE3R6@mmp2.samsung.com> for mip6@ietf.org; Sat, 04 Oct 2003 11:54:04 +0900 (KST) Date: Sat, 04 Oct 2003 11:54:14 +0900 From: Soohong Daniel Park Subject: RE: [Mip6] Comment on MIPv6 I-D In-reply-to: <5.2.0.9.2.20031003085455.026a61f0@unixmail.qualcomm.com> To: mip6@ietf.org Cc: mobile-ip@sunroof.eng.sun.com Message-id: <016701c38a22$cbcf0890$b7cbdba8@daniel> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Content-Transfer-Encoding: 7BIT Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT One more editorial: P 71 o The node MUST be able validate a Home Address option using an existing Binding Cache entry, as described in Section 9.3.1. s/be able/be able to...:-) Soohong Daniel Park @SAMSUNG.COM > -----Original Message----- > From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On > Behalf Of Frank Quick > Sent: Saturday, October 04, 2003 1:00 AM > To: mip6@ietf.org > Cc: mobile-ip@sunroof.eng.sun.com > Subject: [Mip6] Comment on MIPv6 I-D > > > In section 10.3.1: > > "To begin processing the Binding Update, the home agent MUST > perform the > following sequence of tests: > > ... > > o A Home Address destination option MUST be present in > the message. > > ..." > > 11.7.1 says essentially the same thing on page 131: > > " o The packet MUST contain a Home Address destination > option, giving > the mobile node's home address for the binding." > > > This seems to moot some of the text in 11.7.1, page 132: > > "The mobile node MUST use its home address - either in the > Home Address > destination option or in the Source Address field of the > IPv6 header - in > Binding Updates sent to the home agent." > > This sentence implies that the node has the option of > EITHER/OR whereas the > preceding text would say the node MUST include the Home > Address destination > option, and (presumably) MAY also use the home address as the Source > Address. I'd suggest that this sentence be deleted, or > amended to reflect > the fact that the home address as Source Address is allowed but the > destination option is mandatory. > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 6 13:04:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12344 for ; Mon, 6 Oct 2003 13:04:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6YmE-0008A3-Py for mip6-archive@odin.ietf.org; Mon, 06 Oct 2003 13:04:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96H463s031369 for mip6-archive@odin.ietf.org; Mon, 6 Oct 2003 13:04:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6YmE-00089s-MR for mip6-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 13:04:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12321 for ; Mon, 6 Oct 2003 13:03:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6YmC-00013k-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 13:04:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6YmC-00013g-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 13:04:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Ym8-00089E-Nv; Mon, 06 Oct 2003 13:04:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Ylp-00088g-Jd for mip6@optimus.ietf.org; Mon, 06 Oct 2003 13:03:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12308 for ; Mon, 6 Oct 2003 13:03:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Yln-00013M-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:03:39 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1A6Yln-00013I-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:03:39 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96H3a77001318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 6 Oct 2003 10:03:37 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96H3Zia016628 for ; Mon, 6 Oct 2003 10:03:35 -0700 (PDT) Message-Id: <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 06 Oct 2003 10:03:34 -0700 To: mip6@ietf.org From: Frank Quick Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Mip6] more confusion Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Sorry for being a pest, but I have another issue with v24 of the I-D. If it's too late to change the I-D, some other means of clarification should be found. Section 11.3.2, page 115 says: o In addition, for all security associations bound to the mobile node's home address established by IKE, the mobile node MUST include an ISAKMP Identification Payload [8] in the IKE exchange, giving the mobile node's home address as the initiator of the Security Association [7]. From the email threads on this subject that I have seen, the mobile should not do this. Section 5.1, page 21 says: When IKE version 1 is used with preshared secret authentication between the mobile node and the home agent, aggressive mode MUST be used. Similarly, the ID_IPV6_ADDR Identity Payload MUST NOT be used in IKEv1 phase 1. It's hard to see what identity type other than ID_IPV6_ADDR might be used to comply with 11.3.2. I think the spirit of the email threads is that mobile must provide an Identification Payload that maps to the home address within the home agent, but it can't be the home address itself. If this holds, then Section 11.3.2 should be changed to reflect it. Further, given the spirit of the email threads, I would think Section 5.1 should be modified to make it clear that this prohibition is not restricted to preshared secret authentication. I believe that use of any ID type that includes one or more IP addresses or prefixes should similarly be discouraged. ----- The reasoning behind this, if I understand it correctly, is: IKE phase I doesn't protect the Source Address. This is believed to be a security flaw that may be fixed in IKEv2. Meanwhile, implementers have installed a poor-man's authentication by checking the Identification payload against the Source Address, and rejecting messages where they do not match. Thus, while it would seem that the certificate ID should match the Identification payload but the Source Address should be the care-of address, in practice this will fail. Can anyone point out email threads and/or an internet-drafts that discuss this issue? Frank Quick office +1-858-658-3608 fax +1-858-651-1940 portable +1-619-890-5749 paging fquick@pager.qualcomm.com RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 6 13:24:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13566 for ; Mon, 6 Oct 2003 13:24:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Z5Y-0000hR-RT for mip6-archive@odin.ietf.org; Mon, 06 Oct 2003 13:24:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96HO4G9002681 for mip6-archive@odin.ietf.org; Mon, 6 Oct 2003 13:24:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Z5Y-0000hA-Mo for mip6-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 13:24:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13554 for ; Mon, 6 Oct 2003 13:23:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Z5W-0001Lx-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 13:24:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6Z5W-0001Lu-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 13:24:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Z5V-0000fn-4m; Mon, 06 Oct 2003 13:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Z51-0000fS-KN for mip6@optimus.ietf.org; Mon, 06 Oct 2003 13:23:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13510 for ; Mon, 6 Oct 2003 13:23:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Z4z-0001LH-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:23:29 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1A6Z4y-0001Kr-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:23:28 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h96HMkE05697; Mon, 6 Oct 2003 10:22:46 -0700 X-mProtect: <200310061722> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdxrx9xw; Mon, 06 Oct 2003 10:22:45 PDT Message-ID: <3F81A525.9010107@iprg.nokia.com> Date: Mon, 06 Oct 2003 10:23:49 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank Quick CC: mip6@ietf.org Subject: Re: [Mip6] more confusion References: <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> In-Reply-To: <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I am not sure you have read the companion draft http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-ha-ipsec-06.txt I think sections 4.4 and 6.17 of this draft should answer your questions. Vijay > Sorry for being a pest, but I have another issue with v24 of the I-D. > If it's too late to change the I-D, some other means of clarification > should be found. > > Section 11.3.2, page 115 says: > > o In addition, for all security associations bound to the mobile > node's home address established by IKE, the mobile node MUST > include an ISAKMP Identification Payload [8] in the IKE exchange, > giving the mobile node's home address as the initiator of the > Security Association [7]. > > From the email threads on this subject that I have seen, the mobile > should not do this. Section 5.1, page 21 says: > > When IKE version 1 is used with preshared secret authentication > between the mobile node and the home agent, aggressive mode MUST be > used. Similarly, the ID_IPV6_ADDR Identity Payload MUST NOT be used > in IKEv1 phase 1. > > It's hard to see what identity type other than ID_IPV6_ADDR might be > used to comply with 11.3.2. I think the spirit of the email threads > is that mobile must provide an Identification Payload that maps to the > home address within the home agent, but it can't be the home address > itself. > > If this holds, then Section 11.3.2 should be changed to reflect it. > > Further, given the spirit of the email threads, I would think Section > 5.1 should be modified to make it clear that this prohibition is not > restricted to preshared secret authentication. > > I believe that use of any ID type that includes one or more IP > addresses or prefixes should similarly be discouraged. > > ----- > > The reasoning behind this, if I understand it correctly, is: IKE > phase I doesn't protect the Source Address. This is believed to be a > security flaw that may be fixed in IKEv2. Meanwhile, implementers > have installed a poor-man's authentication by checking the > Identification payload against the Source Address, and rejecting > messages where they do not match. Thus, while it would seem that the > certificate ID should match the Identification payload but the Source > Address should be the care-of address, in practice this will fail. > > Can anyone point out email threads and/or an internet-drafts that > discuss this issue? > > > > Frank Quick > office +1-858-658-3608 fax +1-858-651-1940 > portable +1-619-890-5749 > paging fquick@pager.qualcomm.com > RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 > D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 6 14:00:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14936 for ; Mon, 6 Oct 2003 14:00:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ZeR-00025i-UK for mip6-archive@odin.ietf.org; Mon, 06 Oct 2003 14:00:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96I07PM008032 for mip6-archive@odin.ietf.org; Mon, 6 Oct 2003 14:00:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ZeR-00025T-FS for mip6-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 14:00:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14897 for ; Mon, 6 Oct 2003 13:59:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6ZeP-0001hy-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 14:00:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6ZeO-0001hv-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 14:00:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ZeM-00024j-C5; Mon, 06 Oct 2003 14:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6Zdz-000234-Op for mip6@optimus.ietf.org; Mon, 06 Oct 2003 13:59:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14879 for ; Mon, 6 Oct 2003 13:59:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6Zdx-0001he-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:59:37 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx with esmtp (Exim 4.12) id 1A6Zdw-0001hR-00 for mip6@ietf.org; Mon, 06 Oct 2003 13:59:36 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96HxWHr000589; Mon, 6 Oct 2003 10:59:32 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96HxUia024806; Mon, 6 Oct 2003 10:59:30 -0700 (PDT) Message-Id: <5.2.0.9.2.20031006105021.02229df0@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 06 Oct 2003 10:59:28 -0700 To: Vijay Devarapalli From: Frank Quick Subject: Re: [Mip6] more confusion Cc: mip6@ietf.org In-Reply-To: <3F81A525.9010107@iprg.nokia.com> References: <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , At 10:23 AM 10/6/2003 -0700, Vijay Devarapalli wrote: >I am not sure you have read the companion draft > >http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-ha-ipsec-06.txt > >I think sections 4.4 and 6.17 of this draft should answer your questions. Thanks, I was aware if the other draft but I do appreciate the specific pointers. 4.4 says that the problem is that "unambiguous mapping of identities to keys is not possible" if the Identification payload is the ID_IPV6_ADDR type. This is a slightly different slant, but it seems the bottom line is the same: having two different addresses will confuse the implementations. The apparent conflict in the MIPv6 draft remains... unless I interpret all of this to mean the prohibition of the use of ID_IPV6_ADDR indeed applies *only* to the case of preshared secrets. The wording "security associations ... established by IKE" could mean that the paragraph of 11.3.2 of the MIPv6 draft applies only to dynamic keying. Is that the intent? If so, I'll withdraw my comments. >Vijay > >>Sorry for being a pest, but I have another issue with v24 of the I-D. >>If it's too late to change the I-D, some other means of clarification >>should be found. >> >>Section 11.3.2, page 115 says: >> >> o In addition, for all security associations bound to the mobile >> node's home address established by IKE, the mobile node MUST >> include an ISAKMP Identification Payload [8] in the IKE exchange, >> giving the mobile node's home address as the initiator of the >> Security Association [7]. >> >> From the email threads on this subject that I have seen, the mobile >> should not do this. Section 5.1, page 21 says: >> >> When IKE version 1 is used with preshared secret authentication >> between the mobile node and the home agent, aggressive mode MUST be >> used. Similarly, the ID_IPV6_ADDR Identity Payload MUST NOT be used >> in IKEv1 phase 1. >> >>It's hard to see what identity type other than ID_IPV6_ADDR might be used >>to comply with 11.3.2. I think the spirit of the email threads is that >>mobile must provide an Identification Payload that maps to the home >>address within the home agent, but it can't be the home address itself. >> >>If this holds, then Section 11.3.2 should be changed to reflect it. >> >>Further, given the spirit of the email threads, I would think Section 5.1 >>should be modified to make it clear that this prohibition is not >>restricted to preshared secret authentication. >> >>I believe that use of any ID type that includes one or more IP addresses >>or prefixes should similarly be discouraged. >> >>----- >> >>The reasoning behind this, if I understand it correctly, is: IKE phase I >>doesn't protect the Source Address. This is believed to be a security >>flaw that may be fixed in IKEv2. Meanwhile, implementers have installed >>a poor-man's authentication by checking the Identification payload >>against the Source Address, and rejecting messages where they do not >>match. Thus, while it would seem that the certificate ID should match >>the Identification payload but the Source Address should be the care-of >>address, in practice this will fail. >> >>Can anyone point out email threads and/or an internet-drafts that discuss >>this issue? >> >> >> >>Frank Quick >>office +1-858-658-3608 fax +1-858-651-1940 >>portable +1-619-890-5749 >>paging fquick@pager.qualcomm.com >>RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 >>D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D >> >> >>_______________________________________________ >>Mip6 mailing list >>Mip6@ietf.org >>https://www.ietf.org/mailman/listinfo/mip6 > > > Frank Quick office +1-858-658-3608 fax +1-858-651-1940 portable +1-619-890-5749 paging fquick@pager.qualcomm.com RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 6 14:32:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16164 for ; Mon, 6 Oct 2003 14:32:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6a9O-0003PJ-S6 for mip6-archive@odin.ietf.org; Mon, 06 Oct 2003 14:32:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96IW6mg013093 for mip6-archive@odin.ietf.org; Mon, 6 Oct 2003 14:32:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6a9O-0003P6-ME for mip6-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 14:32:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16150 for ; Mon, 6 Oct 2003 14:31:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6a9L-000242-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 14:32:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6a9L-00023z-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 14:32:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6a9J-0003OS-20; Mon, 06 Oct 2003 14:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6a8M-0003N5-Ch for mip6@optimus.ietf.org; Mon, 06 Oct 2003 14:31:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16085 for ; Mon, 6 Oct 2003 14:30:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6a8J-00022x-00 for mip6@ietf.org; Mon, 06 Oct 2003 14:30:59 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1A6a8I-00022i-00 for mip6@ietf.org; Mon, 06 Oct 2003 14:30:58 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h96IUMF01038; Mon, 6 Oct 2003 11:30:22 -0700 X-mProtect: <200310061830> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdVxjetw; Mon, 06 Oct 2003 11:30:21 PDT Message-ID: <3F81B4FE.6060005@iprg.nokia.com> Date: Mon, 06 Oct 2003 11:31:26 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank Quick CC: mip6@ietf.org Subject: Re: [Mip6] more confusion References: <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> <5.2.0.9.2.20031006105021.02229df0@unixmail.qualcomm.com> In-Reply-To: <5.2.0.9.2.20031006105021.02229df0@unixmail.qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit the main goal is to associate whatever security association created with the home address of the mobile node and not the CoA. the CoA changes and you have to re-key everytime the mobile node moves. in case of preshared secrets, the source address in phase 1 is used to look up the secret. the source address in phase 1 is CoA, therefore aggresive mode should be used. there is a more detailed response from Francis Dupont to a similar question at http://www.piuha.net/~jarkko/publications/mipv6/issues/issue305.txt Frank Quick wrote: > Thanks, I was aware if the other draft but I do appreciate the > specific pointers. > > 4.4 says that the problem is that "unambiguous mapping of identities > to keys is not possible" if the Identification payload is the > ID_IPV6_ADDR type. This is a slightly different slant, but it seems > the bottom line is the same: having two different addresses will > confuse the implementations. > > The apparent conflict in the MIPv6 draft remains... unless I interpret > all of this to mean the prohibition of the use of ID_IPV6_ADDR indeed > applies *only* to the case of preshared secrets. The wording > "security associations ... established by IKE" could mean that the > paragraph of 11.3.2 of the MIPv6 draft applies only to dynamic > keying. Is that the intent? If so, I'll withdraw my comments. yup. Vijay _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 6 15:09:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17634 for ; Mon, 6 Oct 2003 15:09:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ajA-0004s4-PZ for mip6-archive@odin.ietf.org; Mon, 06 Oct 2003 15:09:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h96J94jU018721 for mip6-archive@odin.ietf.org; Mon, 6 Oct 2003 15:09:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ajA-0004rs-IW for mip6-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 15:09:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17569 for ; Mon, 6 Oct 2003 15:08:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6aj7-0002M1-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 15:09:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6aj7-0002Ly-00 for mip6-web-archive@ietf.org; Mon, 06 Oct 2003 15:09:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6aj7-0004rM-I8; Mon, 06 Oct 2003 15:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6ais-0004qd-KW for mip6@optimus.ietf.org; Mon, 06 Oct 2003 15:08:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17530 for ; Mon, 6 Oct 2003 15:08:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6aip-0002Lk-00 for mip6@ietf.org; Mon, 06 Oct 2003 15:08:43 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx with esmtp (Exim 4.12) id 1A6aio-0002Lh-00 for mip6@ietf.org; Mon, 06 Oct 2003 15:08:42 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96J8dHr005682; Mon, 6 Oct 2003 12:08:39 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h96J8bia006254; Mon, 6 Oct 2003 12:08:37 -0700 (PDT) Message-Id: <5.2.0.9.2.20031006115556.02230158@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 06 Oct 2003 12:06:54 -0700 To: Vijay Devarapalli From: Frank Quick Subject: Re: [Mip6] more confusion Cc: mip6@ietf.org In-Reply-To: <3F81B4FE.6060005@iprg.nokia.com> References: <5.2.0.9.2.20031006105021.02229df0@unixmail.qualcomm.com> <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> <5.2.0.9.2.20031006094952.01ce5fc0@unixmail.qualcomm.com> <5.2.0.9.2.20031006105021.02229df0@unixmail.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Thanks again. I was aware of Dupont's answer cited below. However, Dupont's answer adds to the confusion: "Many implementations check the peer address (the address IKE runs over) and the address ID (and an address subject alternate name with signature based authentication) matches. This is the defense against some attacks because IKE doesn't protect the peer addresses at all (a known security flaw which should be fixed in IKEv2). Of course it doesn't work with NAT traversal (which can be considered intrinsicly insecure) or with an initiator using a dynamic address (a road warrior) but fortunately other ID types can (should in these cases) be used." This was the source of my thinking that the use of ID_IPV6_ADDR was prohibited in all cases including dynamic key agreement. However, the question in the email thread does seem to be related to preshared secrets, and perhaps the reply is in that context. Still looking for a definitive response: Can ID_IPV6_ADDR be used (and set to the home address) in phase I if dynamic key agreement is used (no preshared secret)? At 11:31 AM 10/6/2003 -0700, Vijay Devarapalli wrote: >the main goal is to associate whatever security association created with the >home address of the mobile node and not the CoA. the CoA changes and you >have to re-key everytime the mobile node moves. > >in case of preshared secrets, the source address in phase 1 is used to look >up the secret. the source address in phase 1 is CoA, therefore aggresive mode >should be used. > >there is a more detailed response from Francis Dupont to a similar question >at http://www.piuha.net/~jarkko/publications/mipv6/issues/issue305.txt > >Frank Quick wrote: > >>Thanks, I was aware if the other draft but I do appreciate the specific >>pointers. >> >>4.4 says that the problem is that "unambiguous mapping of identities to >>keys is not possible" if the Identification payload is the ID_IPV6_ADDR >>type. This is a slightly different slant, but it seems the bottom line >>is the same: having two different addresses will confuse the implementations. >> >>The apparent conflict in the MIPv6 draft remains... unless I interpret >>all of this to mean the prohibition of the use of ID_IPV6_ADDR indeed >>applies *only* to the case of preshared secrets. The wording "security >>associations ... established by IKE" could mean that the paragraph of >>11.3.2 of the MIPv6 draft applies only to dynamic keying. Is that the >>intent? If so, I'll withdraw my comments. > >yup. > >Vijay > Frank Quick office +1-858-658-3608 fax +1-858-651-1940 portable +1-619-890-5749 paging fquick@pager.qualcomm.com RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 7 04:18:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22867 for ; Tue, 7 Oct 2003 04:18:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6n2l-0004vo-Cw for mip6-archive@odin.ietf.org; Tue, 07 Oct 2003 04:18:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h978I7V3018950 for mip6-archive@odin.ietf.org; Tue, 7 Oct 2003 04:18:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6n2k-0004vZ-WB for mip6-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 04:18:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22850 for ; Tue, 7 Oct 2003 04:17:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6n2i-0002XC-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 04:18:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6n2h-0002X9-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 04:18:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6n2f-0004tn-4k; Tue, 07 Oct 2003 04:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6n2N-0004tO-J6 for mip6@optimus.ietf.org; Tue, 07 Oct 2003 04:17:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22846 for ; Tue, 7 Oct 2003 04:17:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6n2K-0002X0-00 for mip6@ietf.org; Tue, 07 Oct 2003 04:17:40 -0400 Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx with esmtp (Exim 4.12) id 1A6n2J-0002Wp-00 for mip6@ietf.org; Tue, 07 Oct 2003 04:17:40 -0400 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id h978H2N06485; Tue, 7 Oct 2003 10:17:02 +0200 Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id h978H1HN092999; Tue, 7 Oct 2003 10:17:02 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200310070817.h978H1HN092999@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Frank Quick cc: Vijay Devarapalli , mip6@ietf.org Subject: Re: [Mip6] more confusion In-reply-to: Your message of Mon, 06 Oct 2003 12:06:54 PDT. <5.2.0.9.2.20031006115556.02230158@unixmail.qualcomm.com> Date: Tue, 07 Oct 2003 10:17:01 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , In your previous mail you wrote: Thanks again. I was aware of Dupont's answer cited below. However, Dupont's answer adds to the confusion: => it seems some context lacks: there are two cases: IPsec between the mobile and its home agent, where the mobile should not use one of its addresses as an ID, and IPsec between the mobile and a correspondent node, where the mobile may use its home address as an ID. And all this discussion is about phase 1 IDs, not phase 2 IDs aka traffic selectors where a care-of address must never be used. "Many implementations check the peer address (the address IKE runs over) and the address ID (and an address subject alternate name with signature based authentication) matches. This is the defense against some attacks because IKE doesn't protect the peer addresses at all (a known security flaw which should be fixed in IKEv2). Of course it doesn't work with NAT traversal (which can be considered intrinsicly insecure) or with an initiator using a dynamic address (a road warrior) but fortunately other ID types can (should in these cases) be used." This was the source of my thinking that the use of ID_IPV6_ADDR was prohibited in all cases including dynamic key agreement. However, the question in the email thread does seem to be related to preshared secrets, and perhaps the reply is in that context. => preshared secrets have some additional issues with address based phase 1 ID payloads. Still looking for a definitive response: Can ID_IPV6_ADDR be used (and set to the home address) in phase I if dynamic key agreement is used (no preshared secret)? => only when the responder is not a home agent or with other words only when the apparent peer address of the mobile is its home address. Regards Francis.Dupont@enst-bretagne.fr _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 7 07:59:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28019 for ; Tue, 7 Oct 2003 07:59:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6qUb-00052X-Kd for mip6-archive@odin.ietf.org; Tue, 07 Oct 2003 07:59:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97Bx5dR019373 for mip6-archive@odin.ietf.org; Tue, 7 Oct 2003 07:59:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6qUb-00052O-GF for mip6-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 07:59:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28008 for ; Tue, 7 Oct 2003 07:58:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6qUa-0004U1-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 07:59:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6qUa-0004Ty-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 07:59:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6qUX-00051r-4p; Tue, 07 Oct 2003 07:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6qTg-0004yr-W1 for mip6@optimus.ietf.org; Tue, 07 Oct 2003 07:58:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27987 for ; Tue, 7 Oct 2003 07:58:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6qTg-0004TZ-00 for mip6@ietf.org; Tue, 07 Oct 2003 07:58:08 -0400 Received: from p2.piuha.net ([131.160.192.2]) by ietf-mx with esmtp (Exim 4.12) id 1A6qTf-0004TL-00 for mip6@ietf.org; Tue, 07 Oct 2003 07:58:07 -0400 Received: from kolumbus.fi (p4.piuha.net [131.160.192.4]) by p2.piuha.net (Postfix) with ESMTP id 4F01A6A906; Tue, 7 Oct 2003 14:58:00 +0300 (EEST) Message-ID: <3F82A960.2010204@kolumbus.fi> Date: Tue, 07 Oct 2003 14:54:08 +0300 From: Jari Arkko User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Al-Absi Ayman (AC/EED)" Cc: mip6@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Re: [mobile-ip] about MIPvs6 and HMIPvs6 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Al-Absi Ayman (AC/EED) wrote: > I would to ask the following questions please Re-directing the question to the mip6 list, mobile-ip list is going to be closed. > 1) in the MIPvs6, could the MN send the BU to the HA and the Home Test init. message to the CN in same time ? Good question. Section 11.7.2 says that you have to send the BU first, followed by the initiation of the correspondent binding procedure. There is no need to wait for the BA. So in essence, the home and the correspondent binding procedures are executed in parallel. This includes also sending home test init messages. (Some discussion of the way this works on the home agent side is also given in Section 3.2 of draft-mobileip-mipv6-ha-ipsec-06.txt.) When the messages are sent quickly after one another, there is a small risk of losing some of the RR packets. For instance, if the packets get reordered and the home test init goes through the HA to the CN and back before the BU is received by the home agent, then Home Test message would go to the previous location. However, the risk for this is small and it generally makes sense to send all the signaling messages as quickly as possible. If anyone has measurement data regarding message losses in this situation, please post them... --Jari _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 7 14:00:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14101 for ; Tue, 7 Oct 2003 14:00:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6w7y-0006P8-Ip for mip6-archive@odin.ietf.org; Tue, 07 Oct 2003 14:00:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h97I06nD024614 for mip6-archive@odin.ietf.org; Tue, 7 Oct 2003 14:00:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6w7y-0006Ov-3i for mip6-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 14:00:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14074 for ; Tue, 7 Oct 2003 13:59:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6w7v-0001WD-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 14:00:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A6w7v-0001W9-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 14:00:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6w7t-0006OG-J4; Tue, 07 Oct 2003 14:00:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6w6u-0006NH-2z for mip6@optimus.ietf.org; Tue, 07 Oct 2003 13:59:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14044 for ; Tue, 7 Oct 2003 13:58:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6w6r-0001VU-00 for mip6@ietf.org; Tue, 07 Oct 2003 13:58:57 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1A6w6r-0001VO-00 for mip6@ietf.org; Tue, 07 Oct 2003 13:58:57 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h97Hwj77029425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Oct 2003 10:58:46 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h97Hwhia019639; Tue, 7 Oct 2003 10:58:43 -0700 (PDT) Message-Id: <5.2.0.9.2.20031007102814.0276b020@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 07 Oct 2003 10:58:41 -0700 To: Francis Dupont From: Frank Quick Subject: Re: [Mip6] more confusion Cc: Vijay Devarapalli , mip6@ietf.org In-Reply-To: <200310070817.h978H1HN092999@givry.rennes.enst-bretagne.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , At 10:17 AM 10/7/2003 +0200, Francis Dupont wrote: > In your previous mail you wrote: > > Thanks again. I was aware of Dupont's answer cited below. However, > Dupont's answer adds to the confusion: > >=> it seems some context lacks: there are two cases: IPsec between >the mobile and its home agent, where the mobile should not use >one of its addresses as an ID, and IPsec between the mobile and >a correspondent node, where the mobile may use its home address >as an ID. And all this discussion is about phase 1 IDs, not phase 2 >IDs aka traffic selectors where a care-of address must never be used. Agreed that the context is very important. The particular context that I would like to address is phase 1, MN performing a Binding Update with its home agent. There seem to be two sub-contexts within that: 1. Where a preshared secret exists 2. Where public-key methods are used (typically via exchange of certificates) The water is muddied a bit by the use of terms like "IKE phase 1" at some places in the I-D, while in other places IKE appears alone and the context seems to be phase 2 only. 1. Where a preshared secret exists, the argument is that in phase 1: - aggressive mode must be used. In messages from the MN: - the Source Address must be the CoA because the phase 1 SA is with the CoA. - the Identification payload must uniquely identify the home address; but it can't be of type ID_IPV6_ADDR set to the home address because IPsec implementations will reject it (not equal to Source Address). In principle it would be possible to specify behavior for a home agent that would allow the ID payload to be the home address. My guess is that we do not do this because we want MIPv6 to run on IPsec from existing OS kernels without modification, and some/most/all of those perform the deadly consistency check. 2. For public-key-based phase 1 (presumably main mode?), the question is whether this same restriction on the ID payload exists. If it is truly an implementation issue, it would seem equally applicable to this case. Your response below suggests that this is a general problem, not specific to preshared keys. Yet both I-Ds seem to limit the requirement against use of ID-IPV6_ADDR to the preshared case. > "Many implementations check the peer address (the address IKE runs over) > and the address ID (and an address subject alternate name with > signature based authentication) matches. This is the defense against > some attacks because IKE doesn't protect the peer addresses at all > (a known security flaw which should be fixed in IKEv2). Of course > it doesn't work with NAT traversal (which can be considered intrinsicly > insecure) or with an initiator using a dynamic address (a road warrior) > but fortunately other ID types can (should in these cases) be used." > > This was the source of my thinking that the use of ID_IPV6_ADDR was > prohibited in all cases including dynamic key agreement. However, the > question in the email thread does seem to be related to preshared > secrets, > and perhaps the reply is in that context. > >=> preshared secrets have some additional issues with address based phase 1 >ID payloads. > > Still looking for a definitive response: Can ID_IPV6_ADDR be used > (and set > to the home address) in phase I if dynamic key agreement is used (no > preshared secret)? > >=> only when the responder is not a home agent or with other words only >when the apparent peer address of the mobile is its home address. > >Regards > >Francis.Dupont@enst-bretagne.fr Frank Quick office +1-858-658-3608 fax +1-858-651-1940 portable +1-619-890-5749 paging fquick@pager.qualcomm.com RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 7 21:10:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00411 for ; Tue, 7 Oct 2003 21:10:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A72q6-0002cC-Uo for mip6-archive@odin.ietf.org; Tue, 07 Oct 2003 21:10:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h981A6n7010046 for mip6-archive@odin.ietf.org; Tue, 7 Oct 2003 21:10:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A72q6-0002bx-Ny for mip6-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 21:10:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00406 for ; Tue, 7 Oct 2003 21:09:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A72q4-0006BM-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 21:10:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A72q3-0006BJ-00 for mip6-web-archive@ietf.org; Tue, 07 Oct 2003 21:10:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A72q2-0002Y0-PE; Tue, 07 Oct 2003 21:10:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A72pB-0002X6-4g for mip6@optimus.ietf.org; Tue, 07 Oct 2003 21:09:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00388 for ; Tue, 7 Oct 2003 21:08:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A72p8-0006Ay-00 for mip6@ietf.org; Tue, 07 Oct 2003 21:09:06 -0400 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1A72p7-0006Ak-00 for mip6@ietf.org; Tue, 07 Oct 2003 21:09:06 -0400 Received: from jurassic.eng.sun.com ([129.146.81.144]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9818SX0012582; Tue, 7 Oct 2003 18:08:28 -0700 (PDT) Received: from shubho (shubho.Eng.Sun.COM [129.146.85.207]) by jurassic.eng.sun.com (8.12.10+Sun/8.12.10) with SMTP id h9818RKT722445; Tue, 7 Oct 2003 18:08:28 -0700 (PDT) Message-Id: <200310080108.h9818RKT722445@jurassic.eng.sun.com> Date: Tue, 7 Oct 2003 18:09:41 -0700 (PDT) From: Samita Chakrabarti Reply-To: Samita Chakrabarti To: mip6@ietf.org Cc: Brian.Haley@hp.com, Vladislav.Yasevich@hp.com, jinmei@isl.rdc.toshiba.co.jp, keiichi@iij.ad.jp, erik.nordmark@sun.com, samita.chakrabarti@sun.com, basavaraj.patil@nokia.com MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: CI5V+teewLIPIuf0bURk6A== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_31 SunOS 5.10 sun4u sparc Subject: [Mip6] MIPV6API draft Issues/proposals Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , We have discussed the following issues in mobile-ip and mip6api@sun.com alias. The co-authors of MIP6API draft have addressed them as below and would like to close them on this alias. Thanks for your comments. PS: At Vienna IETF, MIP6 chairs wanted to discuss with IPv6 wg chairs to decide on the route of progress of this draft. Would like to know if there is any status on that. Basic Reference: draft-chakrabarti-mobileip-mipext-advapi-01.txt [Other minor issues have been resolved in the V02] ----------------------------------------------------------------- Issues addressed: (Brian, Keiichi) 1. For consistency: Changed all the data structure defined in ip6mh.h as following: ip6_mh -- MH hdr ip6_mh_ ip6_mh_opt_ ----- 2. (Brian, Keiichi) Some minor modification of field names based on implementor's recommendations. For example, resvd -> reserved etc. ip6hoa_->ip6oha_* --- 3. (Brian, Keiichi and others?) The data structure defined in icmp6.h for dynamic HA discovery etc. still has prefix MIP/mip. Proposal: Do people want to see it as MIP6/mip6 or does not matter? We need at least 3 votes to change it. --- 4. (Vladislav, Jinmei) Checksum issue: This API should manadate that the kernel does do the checksumming by default. This does not go along with RFC3542 where it recommends only ICMPv6 protocols are used for default checksumming, but for all other RAW IPv6 sockets app. must set IPV6_CHECKSUM socket option. Proposal: For compatibility with RFC3542, an application that opens a RAW socket with protocol IPPROTO_MH should set IPV6_CHECKSUM socket option. However, a Mobile IPv6 implementation must support mobility header API checksumming in the kernel for inbound and outbound path irrespective of IPV6_CHECKSUM socket option setting. Thus if the third argument of the socket() is IPPROTO_MH, the checksum is calculated by the kernel by default. A Mobile IPv6 implementation must not return error on IPV6_CHECKSUM socket option, even if the socket option is a NO-OP function for that implementation. ----- 5. (Vladislav) What is the value of IPPROTO_MH ? Is 55 an IANA assigned number for MIP6 ? --- 6. (Vladislav) Placement of HOA Destination option: RFC3542 adopts RFC2460 extension header ordering, but Mobile IPv6 (section 6.3 of draft 24) has need for different home address destination option ordering. Should we use single ancillary data item for HOA destination option ? Proposal: RFC3542 restricts that: - Each IPV6_xxx ancillary data object for a particular type of extension header can be specified at most once in a single control buffer. - IPV6_xxx ancillary data objects can appear in any order in a control buffer, because there is no ambiguity of the ordering. Since no other destination option(IPV6_DSTOPTS) is defined (so far) other than HOA destination option type, there will be only one HOA ancillary data object in a particular control buffer. Thus, if HOA IPV6_DSTOPTS is sent down to the kernel by the application, the kernel is responsible for extracting the data object and placing the HOA destination option extension header according to section 6.3 of base Mobile IPv6 specification. ----------------------------------- -Samita _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 8 04:17:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06057 for ; Wed, 8 Oct 2003 04:17:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79VI-0006fg-Q6 for mip6-archive@odin.ietf.org; Wed, 08 Oct 2003 04:17:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h988H4pr025645 for mip6-archive@odin.ietf.org; Wed, 8 Oct 2003 04:17:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79VI-0006fY-EC for mip6-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 04:17:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06040 for ; Wed, 8 Oct 2003 04:16:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A79VF-00025C-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 04:17:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A79VF-000259-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 04:17:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79VF-0006f4-LT; Wed, 08 Oct 2003 04:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A79UT-0006cj-9j for mip6@optimus.ietf.org; Wed, 08 Oct 2003 04:16:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06010 for ; Wed, 8 Oct 2003 04:16:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A79UQ-00024a-00 for mip6@ietf.org; Wed, 08 Oct 2003 04:16:10 -0400 Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx with esmtp (Exim 4.12) id 1A79UP-00024Q-00 for mip6@ietf.org; Wed, 08 Oct 2003 04:16:09 -0400 Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id h988FYN02272; Wed, 8 Oct 2003 10:15:34 +0200 Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id h988FXHN096917; Wed, 8 Oct 2003 10:15:34 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr) Message-Id: <200310080815.h988FXHN096917@givry.rennes.enst-bretagne.fr> From: Francis Dupont To: Frank Quick cc: Vijay Devarapalli , mip6@ietf.org Subject: Re: [Mip6] more confusion In-reply-to: Your message of Tue, 07 Oct 2003 10:58:41 PDT. <5.2.0.9.2.20031007102814.0276b020@unixmail.qualcomm.com> Date: Wed, 08 Oct 2003 10:15:33 +0200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , In your previous mail you wrote: Agreed that the context is very important. The particular context that I would like to address is phase 1, MN performing a Binding Update with its home agent. There seem to be two sub-contexts within that: 1. Where a preshared secret exists => this sub-case only adds some complexity but the recommended solution works for all kinds of authentication. 2. Where public-key methods are used (typically via exchange of certificates) The water is muddied a bit by the use of terms like "IKE phase 1" at some places in the I-D, while in other places IKE appears alone and the context seems to be phase 2 only. => phase 2 is easy: only address based ID payloads make sense and a care-of address is never used in phase 2. The only possible bad choices are in phase 1. 1. Where a preshared secret exists, the argument is that in phase 1: - aggressive mode must be used. => this is for an IKE reason: this stands as soon as the peer address is dynamic, i.e., the context is far larger than mobility. In messages from the MN: => you can remove the preshared secret context from here. - the Source Address must be the CoA because the phase 1 SA is with the CoA. => because only a CoA is usable before the home registration. - the Identification payload must uniquely identify the home address; but it can't be of type ID_IPV6_ADDR set to the home address because IPsec implementations will reject it (not equal to Source Address). => exactly In principle it would be possible to specify behavior for a home agent that would allow the ID payload to be the home address. My guess is that we do not do this because we want MIPv6 to run on IPsec from existing OS kernels without modification, and some/most/all of those perform the deadly consistency check. => yes, we don't want to change IKE. 2. For public-key-based phase 1 (presumably main mode?) => this doesn't matter: aggressive mode is more efficient but less flexible and less secure. Both work so there is no reason to specify one. the question is whether this same restriction on the ID payload exists. => the same reasoning applies so there are the same two restrictions. If it is truly an implementation issue, it would seem equally applicable to this case. => yes Your response below suggests that this is a general problem, not specific to preshared keys. Yet both I-Ds seem to limit the requirement against use of ID-IPV6_ADDR to the preshared case. => do you ask for a new wording or this thread in the mailing list is enough? Regards Francis.Dupont@enst-bretagne.fr _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 8 09:36:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14331 for ; Wed, 8 Oct 2003 09:36:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7EU0-00065G-4c for mip6-archive@odin.ietf.org; Wed, 08 Oct 2003 09:36:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Da4X1023380 for mip6-archive@odin.ietf.org; Wed, 8 Oct 2003 09:36:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7ETz-000651-Vy for mip6-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 09:36:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14306 for ; Wed, 8 Oct 2003 09:35:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7ETy-00050l-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 09:36:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7ETx-00050i-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 09:36:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7ETx-00064a-I7; Wed, 08 Oct 2003 09:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7ESy-00063Y-Nx for mip6@optimus.ietf.org; Wed, 08 Oct 2003 09:35:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14246 for ; Wed, 8 Oct 2003 09:34:51 -0400 (EDT) From: eremmell@elmic.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7ESw-000507-00 for mip6@ietf.org; Wed, 08 Oct 2003 09:34:58 -0400 Received: from [208.17.240.130] (helo=gobeam.net) by ietf-mx with smtp (Exim 4.12) id 1A7ESw-0004zw-00 for mip6@ietf.org; Wed, 08 Oct 2003 09:34:58 -0400 Received: from abs20 (127.0.0.1) by ABS20 (MailMax 4. 8. 3. 0) with ESMTP id 98202392 for mip6@ietf.org; Wed, 08 Oct 2003 06:30:21 -0700 PDT To: mip6@ietf.org Date: Wed, 08 Oct 2003 06:30:21 -0700 X-Mailer: Mailmax Webmail Message-Id: Subject: [Mip6] minor typo in MIPv6 base spec draft 24 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , A minor typo in section "9.3.2 Sending Packets to a Mobile Node", last sentence of first paragraph: "Before sending any packet, the sending node SHOULD examine its Binding Cache for an entry for the destination address to which the packet is being sent. ... However, the mobile node MUST not do this in the following cases:" "mobile node" => "correspondent node" or "sending node" Thanks. - Ed Remmell Elmic Systems, USA ______________________________________ This E-Mail was sent with MailMax/WEB. http://www.smartmax.com _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 8 09:44:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14728 for ; Wed, 8 Oct 2003 09:44:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Ebi-0006im-E7 for mip6-archive@odin.ietf.org; Wed, 08 Oct 2003 09:44:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Di2Vk025821 for mip6-archive@odin.ietf.org; Wed, 8 Oct 2003 09:44:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Ebi-0006hd-6W for mip6-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 09:44:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14721 for ; Wed, 8 Oct 2003 09:43:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7Ebg-00058w-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 09:44:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7Ebg-00058t-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 09:44:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Ebh-0006hC-1l; Wed, 08 Oct 2003 09:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Eb6-0006gt-GD for mip6@optimus.ietf.org; Wed, 08 Oct 2003 09:43:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14710 for ; Wed, 8 Oct 2003 09:43:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7Eb4-00058h-00 for mip6@ietf.org; Wed, 08 Oct 2003 09:43:22 -0400 Received: from p2.piuha.net ([131.160.192.2]) by ietf-mx with esmtp (Exim 4.12) id 1A7Eb4-00058e-00 for mip6@ietf.org; Wed, 08 Oct 2003 09:43:22 -0400 Received: from kolumbus.fi (p4.piuha.net [131.160.192.4]) by p2.piuha.net (Postfix) with ESMTP id 03FE86A908; Wed, 8 Oct 2003 16:43:15 +0300 (EEST) Message-ID: <3F841389.8010709@kolumbus.fi> Date: Wed, 08 Oct 2003 16:39:21 +0300 From: Jari Arkko User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: eremmell@elmic.com Cc: mip6@ietf.org Subject: Re: [Mip6] minor typo in MIPv6 base spec draft 24 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit eremmell@elmic.com wrote: > A minor typo in section "9.3.2 Sending Packets to a Mobile Node", last > sentence of first paragraph: > > "Before sending any packet, the sending node SHOULD examine its Binding Cache > for an entry for the destination address to which the packet is being sent. > ... > However, the mobile node MUST not do this in the following cases:" > > "mobile node" => "correspondent node" or "sending node" Right, thanks... --Jari _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 8 15:19:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04903 for ; Wed, 8 Oct 2003 15:19:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Jq1-0004B1-7X for mip6-archive@odin.ietf.org; Wed, 08 Oct 2003 15:19:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h98JJ9SB016055 for mip6-archive@odin.ietf.org; Wed, 8 Oct 2003 15:19:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Jq1-0004As-3P for mip6-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 15:19:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04847 for ; Wed, 8 Oct 2003 15:19:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7Jpz-00038K-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 15:19:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7Jpz-00038G-00 for mip6-web-archive@ietf.org; Wed, 08 Oct 2003 15:19:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Jpu-00048h-4p; Wed, 08 Oct 2003 15:19:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7Jpe-00047Z-6h for mip6@optimus.ietf.org; Wed, 08 Oct 2003 15:18:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04794 for ; Wed, 8 Oct 2003 15:18:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7Jpc-00037a-00 for mip6@ietf.org; Wed, 08 Oct 2003 15:18:44 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1A7Jpc-00037W-00 for mip6@ietf.org; Wed, 08 Oct 2003 15:18:44 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h98JIb77011633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Oct 2003 12:18:37 -0700 (PDT) Received: from FQUICK.qualcomm.com (fquick.qualcomm.com [129.46.73.22]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h98JIY7a012421; Wed, 8 Oct 2003 12:18:35 -0700 (PDT) Message-Id: <5.2.0.9.2.20031008114806.021e62f0@unixmail.qualcomm.com> X-Sender: fquick@unixmail.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 08 Oct 2003 12:18:31 -0700 To: Francis Dupont From: Frank Quick Subject: Re: [Mip6] more confusion Cc: Vijay Devarapalli , mip6@ietf.org In-Reply-To: <200310080815.h988FXHN096917@givry.rennes.enst-bretagne.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , At 10:15 AM 10/8/2003 +0200, Francis Dupont wrote: > Your response below suggests that this is a general problem, not > specific to preshared keys. Yet both I-Ds seem to limit the > requirement against use of ID-IPV6_ADDR to the preshared case. > >=> do you ask for a new wording or this thread in the mailing list >is enough? If new wording is possible at this late hour it would be preferable as a means of avoiding future confusion. The sections I have identified that should be considered for change are: In MIPv6 -24: 1. Section 5.1, page 21: When IKE version 1 is used with preshared secret authentication between the mobile node and the home agent, aggressive mode MUST be used. Similarly, the ID_IPV6_ADDR Identity Payload MUST NOT be used in IKEv1 phase 1. might be revised to separate the sentences, as follows: When IKE version 1 is used with preshared secret authentication between the mobile node and the home agent, aggressive mode MUST be used. The ID_IPV6_ADDR Identity Payload MUST NOT be used in IKEv1 phase 1. [a reference to the ipsec i-d would be useful here if appropriate] 2. Section 11.3.2, page 113: o In addition, for all security associations bound to the mobile node's home address established by IKE, the mobile node MUST include an ISAKMP Identification Payload [8] in the IKE exchange, giving the mobile node's home address as the initiator of the Security Association [7]. It is not critical, but I would suggest that "the IKE exchange" read "the IKE phase 2 exchange". In the ipsec-06 draft, section 4.4: There is no mention of any problem related to the use of ID_IPV6_ADDR except in the context of preshared keys, where it points out that the different addresses make the key lookup ambiguous. I think another paragraph about the implementation issue, applicable to all phase 1 exchanges, should be added. If this is done, a section reference might be added in the MIPv6 document as noted above. I am probably not the best qualified to write this new section, but here is a cut at it, hoping that it will be of some use: o During IKEv1 phase 1, the ISAKMP Identification payload cannot be of type ID_IPV6_ADDR. Since IKEv1 does not protect the Source Address, IKE implementations typically compare an ID_IPV6_ADDR Identification payload to the Source Address, and abort if the contents do not match. In IKEv1 phase 1, the Source Address must be the care-of address and the Identification payload must indicate the home address, therefore another Identification payload type must be used. This should follow the current paragraph related to the preshared key issue. >Regards > >Francis.Dupont@enst-bretagne.fr Frank Quick office +1-858-658-3608 fax +1-858-651-1940 portable +1-619-890-5749 paging fquick@pager.qualcomm.com RSA: 29EA D619 31F2 B4D3 8815 3D59 4340 FA43 D-H: 2A24 131C D38F 12E6 4D6A 46EE 8BBF B50A 754E F63D _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 9 12:56:00 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29190 for ; Thu, 9 Oct 2003 12:56:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7e4e-0008MJ-4U for mip6-archive@odin.ietf.org; Thu, 09 Oct 2003 12:55:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h99GtakB032126 for mip6-archive@odin.ietf.org; Thu, 9 Oct 2003 12:55:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7e4d-0008M5-Uf for mip6-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 12:55:36 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29161 for ; Thu, 9 Oct 2003 12:55:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7e46-0008IM-Tp; Thu, 09 Oct 2003 12:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7e3a-0008Ga-Oq for mip6@optimus.ietf.org; Thu, 09 Oct 2003 12:54:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29046; Thu, 9 Oct 2003 12:54:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7e3Y-0001Ha-00; Thu, 09 Oct 2003 12:54:28 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 1A7e3X-0001HT-00; Thu, 09 Oct 2003 12:54:27 -0400 Received: from clarinet.u-strasbg.fr (pichnet.u-strasbg.fr [130.79.90.171]) by dpt-info.u-strasbg.fr (8.12.3/8.12.3/Debian-6.6) with ESMTP id h99H49nu031505; Thu, 9 Oct 2003 19:04:10 +0200 Message-ID: <3F8592BA.1010608@clarinet.u-strasbg.fr> Date: Thu, 09 Oct 2003 18:54:18 +0200 From: montavont User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030727 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mip6@ietf.org, mobile-ip@sunroof.eng.sun.com, nemo@ietf.org, multi6@ops.ietf.org Content-Type: multipart/mixed; boundary="------------030708080606030603080409" Subject: [Mip6] New I-D on multi-homing Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------030708080606030603080409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi all, Just to inform you that we have submitted a new I-D on multihoming. Lot of people have already work on multihoming in individual submissions. We tried to write a problem statement for multihomed MN in this I-D and hope that this I-D will initiate some discussions on this topic. Here is the abstact of the I-D: Individual solutions have been proposed to extend Mobile IPv6 in order to allow mobile nodes to be multihomed, but all issues have not been addressed by a single document. In this document, we thus propose a taxonomy to classify the situations where a mobile node may be multihomed. This taxonomy is then used to describe all multihomed scenarios. Issues preventing mobile nodes to be multihomed while operating Mobile IPv6 are highlighted. This document doesn't aim at proposing solutions, however, it is expected to raise discussion in order to make sure forthcoming solutions will address all the issues. Nicolas --------------030708080606030603080409 Content-Type: text/plain; name="draft-montavont-mobileip-multihoming-pb-statement-00.txt" Content-Disposition: inline; filename="draft-montavont-mobileip-multihoming-pb-statement-00.txt" X-MIME-Autoconverted: from 8bit to quoted-printable by dpt-info.u-strasbg.fr id h99H49nu031505 Content-Transfer-Encoding: quoted-printable IETF Mobile IP Working Group N. Montavont Internet-Draft LSIIT Expires: April 9, 2004 R. Wakikawa T. Ernst WIDE at Keio University T. Noel LSIIT October 10, 2003 Problem Statement for multihomed Mobile Nodes draft-montavont-mobileip-multihoming-pb-statement-00.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on April 9, 2004. Copyright Notice Copyright (C) The Internet Society (2003). All Rights Reserved. Abstract Individual solutions have been proposed to extend Mobile IPv6 in order to allow mobile nodes to be multihomed, but all issues have not been addressed by a single document. In this document, we thus propose a taxonomy to classify the situations where a mobile node may be multihomed. This taxonomy is then used to describe all multihomed scenarios. Issues preventing mobile nodes to be multihomed while operating Mobile IPv6 are highlighted. This document doesn't aim at Montavont, et al. Expires April 9, 2004 [Page 1] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 proposing solutions, however, it is expected to raise discussion in order to make sure forthcoming solutions will address all the issues. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Multihoming Scenarios . . . . . . . . . . . . . . . . . . . . 6 4.1 Taxonomy . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2 scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.3 MN connected to home link . . . . . . . . . . . . . . . . . . 8 5. Open issues . . . . . . . . . . . . . . . . . . . . . . . . . 10 References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . 14 Montavont, et al. Expires April 9, 2004 [Page 2] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 1. Introduction New mobile nodes often integrate several wireless technologies. The main purpose of this integration is to federate all means of communications in order to have an ubiquitous mobile node which can be used to access to the Internet everywhere and at any time. Permanent Internet connectivity is required by some applications while a mobile node moves across several access networks (i.e. ISPs, hotspots, etc). For example, it is desirable to maintain the Internet connectivity while an automobile running on a freeway receives voice or video streaming data from different access networks. Unfortunately, there is no network interfaces assuring global scale connectivity. Therefore, a mobile node should use various type of network interfaces to obtain wide area network connectivity [11]. In addition, each network interface has different cost, performance, bandwidth, access range, and reliability. Users should thus be able to select the most appropriate set of network interface(s) depending on a visiting network environment, since wireless networks are mutable and less reliable than wired networks. Users should also be able to select the most appropriate interface per communication type. For example, TCP communication is best transmitted over wireless interface, while UDP communication is sent over a wired interface to avoid disturbing TCP connections. Mobile IPv6 [1] is being designed to allow a mobile node to maintain its IPv6 communications while moving between IPv6 subnets. However, the current specification does not give any hints nor requirements to deal with mobile nodes with several points of attachement, i.e. a multihomed mobile node. We propose to evaluate the behavior of standard Mobile IPv6 on a multihomed mobile node, and we will try to identify if modifications or enhancements are required in the specification. This document has two goals. The first goal is to define a taxonomy which helps to represent the different cases of multihoming. Then we describe scenarios where mobile nodes are multihomed. These scenarios show the configuration a mobile node may have (number of interfaces, number of home addresses or number of careof addresses). We also give a concrete illustration for each scenario. The second goal of this document is to define the requirements needed to manage multihomed mobile nodes. Different issues will be raised in order to provide full support of multihomed mobile nodes in MIPv6. The potentially needed solutions to support new features will be described in a separate document. Montavont, et al. Expires April 9, 2004 [Page 3] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 2. Terminology In this section we define the terms needed to analyse mobile node with mulitple points of attachment. Some definition are taken from [1], while other are completed or only defined in this document. Interface (from [7]) A node's attachment to a link Multihomed mobile node A mobile node is said multihomed when it has several IPv6 addresses to choose between. A mobile node has several IPv6 addresses to choose between in the following cases: multi-prefixed: multiple prefixes are advertised on the link(s) the mobile node is connected to. multi-interfaced: multiple interfaces to choose between, on the same link or not. multi-linked: multiple links to choose between (just like multi-interfaced but all interfaces are NOT connected to the same link) multi-sited: when using IPv6 site-local address and attached to different sites Montavont, et al. Expires April 9, 2004 [Page 4] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 3. Benefits Several benefits of multihoming can be envisioned: o Ubiquitous Computing: to provide an extended coverage area. Multiple interfaces bound to distinct technologies can then be used to ensure a permanent connectivity is offered. o Redundancy: to act upon failure of one point of attachment. o Load Balancing: to balance load between multiple point of attachments (simultaneously active or not). o Preference settings: to provide the user or the application the ability to choose the prefered transmission technology or access network for reasons of cost, politics, bandwidth requirement, delay, etc. Montavont, et al. Expires April 9, 2004 [Page 5] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 4. Multihoming Scenarios Different scenarios may lead to the fact that a mobile node may be multihomed. In this section are listed all the configurations where a mobile node may have multiple points of attachment. 4.1 Taxonomy To help to refer to a specific scenario, we define the following scheme: Scenario (x,y,z) where o x =3D number of home addresses (HoAs) o y =3D number of careof addresses (CoAs) o z =3D number of active interfaces The value of each identifier can be 1 if there is only one parameter, or n if there are several. The value n does not specify any number, but indicate that there are more than one parameters. An illustration of this taxonomy is given in Figure 1. Mobile Node HoA1 HoA2 ... HoAn --> Mobile IP layer (x) | | | +-----+--------+ | | | | | | | CoA1 +--CoA2 +---CoA3 ... CoAn --> IP layer (y) | | | | Link1 Link2 Link3 ... Linkn --> IPv6 Link (n/a *) | | | | +-----+----+ | | | | | IF1 IF2 ... IFn --> Physical layer (z) (z =3D the number of active i= nterface) HoA1 ::=3D {CoA1, 2, 3} [IF1 and IF2] HoA2 ::=3D {CoA3} [IF2] Mobile Node(x =3D 2, y =3D 3, z =3D 2) Figure 1. Illustration of the chosen taxonomy Montavont, et al. Expires April 9, 2004 [Page 6] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 * because number of IPv6 link is equal to the number of CoAs, equal to y The variable x indicates the number of HoAs allocated to a MN. A MN may have multiple HoAs (x=3Dn) when either: o The MN has only one home link, and all its HoAs are based on the same IPv6 prefix (e.g. the MN may have multiple interfaces). o The MN has only one home link, and several home addresses with distinct prefixes because there are several IPv6 prefixes advertised on the home link. o The MN has several home links, and thus has at least two HoAs with different IPv6 prefixes. 4.2 scenario 1. One HoA, one CoA, one interface (1,1,1) The MN is not multihomed. The MN has only one interface, with one HoA and is currently away from its home link. 2. Several HoAs, one CoA, one interface (n,1,1) The MN is multihomed, since it has several home addresses. Once the MN is connected to a visited IPv6 subnet, it gets one CoA and remains simulteneously reachable through all its HoAs. 3. Several HoAs, several CoAs, one interface (n,n,1) The MN is multihomed, since it has multiple addresses to choose between. In this case, the MN can be either connected to different IPv6 links at the same time, with the same interface, or it can be attached to a single link where several IPv6 prefixes are advertised. In the latter case, it configures a CoA for each prefix. Then, it may register several of them with distant nodes to benefit from its multihoming properties. 4. Several HoAs, several CoAs, several interfaces (n,n,n) The MN is multihomed. Many scenarios may lead to this case. For example, consider a MN with three interfaces, two of them connected to their home link(two different home addresses) and the last one connected to a visited link where two IPv6 prefixes are advertised. Montavont, et al. Expires April 9, 2004 [Page 7] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 5. One HoA, several CoAs, one interface (1,n,1) The MN is multihomed (several CoAs). The case (1,n,1) occurs when a MN is connected to different IPv6 links with the same interface: either there are several IPv6 prefixes advertised on the link, or the interface allows the MN to be connected to different access point in different IPv6 subnets. 6. One HoA, several CoAs, several interfaces (1,n,n) The MN is multihomed: the MN has several addresses to choose between. For example, assume a MN with several interfaces, each connected to an IPv6 network (the same or not). Then at least one IPv6 address is configured on each interface. The MN has only one home link, and only one home agent. 7. One HoA, one CoA, several interfaces (1,1,n) The MN may be multihomed: if the MN has two interfaces, one connected to its home link (using its home address) and the other connected to a visted link (using a careof address), the MN is multihomed. If the MN is connected to a visited link with one interface and has no IPv6 connectivity with the other interfaces (not in the range of an access point or no IPv6 prefix forwarded on a Layer 2 link), the MN is not multihomed. 4.3 MN connected to home link When a MN is multihomed, some of its interfaces may be connected to its home link(s), at any point of time. In all multihoming scenarii listed in the previous subsection, the MN may be directly connected to a home link. Sometimes, when a MN is connected to a home link, it may have an impact on the multihoming management. For example, in the case (n,n,n), a MN may be connected to its home link(s) with some interface(s). If we consider the case where a MN has three interfaces, three HoAs and two CoAs (connected to two visited IPv6 subnets), the CoAs can not be registered with the home agent serving to MN on the home link it is connected to. This case has to be considered when defining the management of multihoming. Otherwise, the case (n,n,n) can translate into either case (n,1,n) or (n,0,n) according to the way the MN is connected to the Internet. Case (n,1,n) only happens when the MN is connected to a visited link with only one interface and obtain only one CoA. Other interfaces are connected to the home link(s). Montavont, et al. Expires April 9, 2004 [Page 8] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 In the case (n,0,n), i.e. several HoAs, no CoA, and several interfaces, all interfaces of the MN is connected to a home link. If home links have different prefixes, a HoA can be a CoA regarding another HoA. Such considerations must be taken into account in a document which presents a solution for multihomed MN since some MIPv6 features can not be used when the MN is connected to the same link as its home agent (e.g. home registration). So the fact that a multihomed MN is connected to a home link must be considered. Montavont, et al. Expires April 9, 2004 [Page 9] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 5. Open issues In this section we highlight different points which have to be taken into account to handle a multihomed MN using Mobile IPv6. These items constitute the requirements for a Mobile IPv6 node to benefit from its multihomed configuration in an optimized fashion. Some of them do not require more processing than those defined in [1] but management operation, while other requires changes in [1]. Only the needed requirements are given in this document, the solutions to meet these requirements will be defined in a separate document. Issues related to the Mobile IPv6 protocol are the following: 1. How to define a relation between HoAs and CoAs. When a MN has several HoAs and obtain a new CoA, to which HoA the new CoA will be bound to ? Moreover, a HoA may be considered as CoA regarding another home link of the MN. 2. How to identify an entry in the Binding Cache: several CoAs can be simultaneously used by a mobile node when it has multiple points of attachments. These CoAs can be bound to the same HoA on any distant node, such as the home agent whih manages this mobile node for this particular HoA. Therefore both distant node and the mobile node need a way to identify an entry in the Binding Cache. 3. How to manage multiple CoAs bound to a single HoA: a multihomed MN may have multiple Care-of addresses. The MN must be able to register all CoAs with a single HoA on a distant node (Correspondant node or HA). Issues non-related to the Mobile IPv6 protocol are the following: 1. How to allow a mobile node to simultaneously use several interfaces: this will be the global purpose of such a solution to support multiple interfaces on a mobile node. The solution should bring support to allow a MN, or even a fixed multihomed MN to simultaneously use several interfaces, whatever the number of HoAs, of CoAs the mobile node may have and whatever the network configuration the mobile node is connected to. 2. How to manage multiple HoAs: a mobile node may have several HoAs. As the taxonomy suggests, the fact that the mobile node has several HoAs is independant from the fact that the mobile has multiple interfaces. By the way, the fact that the mobile node has multiple interfaces does not imply that it has multiple HoAs and vice-versa. A mechanism should thus be defined to detail how to bind HoAs to a MN. Montavont, et al. Expires April 9, 2004 [Page 10] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 3. How a mobile node may redirect flows from one interface to another, in the different scenarios presented in section 3: this functionality would allow a mobile node to pursue any communication began on an interface while this interface becomes down and another one is available. 4. When a MN has several interfaces, it may want to use each interface differently. According to some policies and preferences, a multihomed MN may want to independantly manage each flow, in order to define which flow would be mapped to which interface and/or which flow can not use a determined interface. In order to optimize the global connectivity of a multihomed MN, a solution may be defined to allow multihomed MN to set filters on flow on distant nodes, such as mechanisms proposed by [10], [5] and [4]. Montavont, et al. Expires April 9, 2004 [Page 11] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 References [1] Perkins, C. and J. Arko, "Mobility Support in IPv6", I-D draft-ietf-mobileip-ipv6-24.txt, June 2003. [2] Arkko, J., Devarapalli, V. and F. Dupont, "Using IPsec to protect Mobile IPv6 signaling between Mobile Nodes and Home Agents", I-D draft-ietf-mobileip-mipv6-ha-ipsec-06.txt, June 2003. [3] Montavont, N., Noel, T. and M. Kassi, "MIPv6 for Multiple Interfaces", I-D draft-montavont-mobileip-mmi-01.txt, October 2003. [4] Koojana, K., Fikouras, N., Koensgen, A. and C. Goerg, "Filters for Mobile IPv6 Bindings (NOMADv6)", I-D draft-nomadv6-mobileip-filters-00.txt, July 2003. [5] Montavont, N. and T. Noel, "Home Agent Filtering For Mobile IPv6", I-D draft-montavont-mobileip-ha-filtering-v6-00.txt, July 2003. [6] Wakikawa, R., Uehara, K., Ernst, T. and K. Nagami, "Multiple careof Address Registration on Mobile IPv6", I-D draft-wakikawa-mobileip-multiplecoa-02.txt, September 2003. [7] Manner, J. and M. Kojo, "Mobility Related Terminology", I-D draft-ietf-seamoby-mobility-terminology-04.txt, April 2003. [8] Fikouras, N., Udugama, A., Koensgen, A., Goerg, C., Zirwas, W. and J. Eichinger, "Filters for Mobile IPv6 Bindings (NOMADv6)", I-D draft-nomad-mobileip-v6-filters-00.txt, July 2003. [9] Ernst, T., "Network Mobility Support Terminology", I-D draft-ietf-nemo-terminology-00.txt, May 2003. [10] Soliman, H., Elmalki, K. and C. Castelluccia, "Flow Movement in Mobile IPv6", I-D draft-soliman-mobileip-flow-move-03.txt, June 2003. [11] Stemm, M. and R. Katz, "Vertical Handoffs in Wireless Overlay Networks", Journal Mobile Networks and Applications, vol. 3, number 4, pages 335-350, 1998. Montavont, et al. Expires April 9, 2004 [Page 12] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 Authors' Addresses Nicolas Montavont LSIIT - Univerity Louis Pasteur Ple API, bureau C444 Boulevard Sebastien Brant Illkirch 67400 FRANCE Phone: (33) 3 90 24 45 87 EMail: montavont@dpt-info.u-strasbg.fr URI: http://www-r2.u-strasbg.fr/~montavont/ Ryuji Wakikawa Jun Murai Lab., Keio University 5322 Endo Fujiwasa Kanagawa 252-8520 Japan Phone: +81-466-49-1394 EMail: ryuji@sfc.wide.ad.jp URI: http://www.mobileip.jp/ Thierry Ernst Jun Murai Lab. Keio University K2 Town Campus 1488-8 Ogura, Saiwai-ku, Kawasaki Kanagawa 212-0054 Japan Phone: +81-44-580-1600 EMail: ernst@sfc.wide.ad.jp URI: htpp://www.sfc.wide.ad.jp/~ernst Thomas Noel LSIIT - Univerity Louis Pasteur Ple API, bureau C444 Boulevard S=E9bastien Brant Illkirch 67400 FRANCE Phone: (33) 3 90 24 45 92 EMail: noel@dpt-info.u-strasbg.fr URI: http://www-r2.u-strasbg.fr/~noel/ Montavont, et al. Expires April 9, 2004 [Page 13] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2003). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Montavont, et al. Expires April 9, 2004 [Page 14] =0C Internet-Draft Problem statement for multihomed Mobile Nodes Octo= ber 2003 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Montavont, et al. Expires April 9, 2004 [Page 15] =0C --------------030708080606030603080409-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 9 15:39:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06695 for ; Thu, 9 Oct 2003 15:39:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7gcr-0002kd-5L for mip6-archive@odin.ietf.org; Thu, 09 Oct 2003 15:39:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h99Jd58Y010571 for mip6-archive@odin.ietf.org; Thu, 9 Oct 2003 15:39:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7gcr-0002kQ-0k for mip6-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 15:39:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06670 for ; Thu, 9 Oct 2003 15:38:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7gcp-0003J9-00 for mip6-web-archive@ietf.org; Thu, 09 Oct 2003 15:39:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7gcp-0003J4-00 for mip6-web-archive@ietf.org; Thu, 09 Oct 2003 15:39:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7gcm-0002jJ-Oz; Thu, 09 Oct 2003 15:39:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7gcT-0002is-Ej for mip6@optimus.ietf.org; Thu, 09 Oct 2003 15:38:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06648; Thu, 9 Oct 2003 15:38:29 -0400 (EDT) Message-Id: <200310091938.PAA06648@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; From: Internet-Drafts@ietf.org Cc: ipsec@lists.tislabs.com, multi6@ops.ietf.org, mip6@ietf.org, mip4@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 09 Oct 2003 15:38:28 -0400 Subject: [Mip6] I-D ACTION:draft-nikander-esp-beet-mode-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A Bound End-to-End Tunnel (BEET) mode for ESP Author(s) : P. Nikander Filename : draft-nikander-esp-beet-mode-00.txt Pages : 28 Date : 2003-10-9 This document specifies a new mode, called Bound End-to-End Tunnel (BEET) mode, for IPsec ESP. The new mode augments the existing ESP tunnel and transport modes. For end-to-end tunnels, the new mode provides limited tunnel mode semantics without the regular tunnel mode overhead. The mode is intended to support new uses of ESP, including mobility and multi-address multi-homing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-nikander-esp-beet-mode-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-nikander-esp-beet-mode-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-nikander-esp-beet-mode-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: <2003-10-9142307.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-nikander-esp-beet-mode-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-nikander-esp-beet-mode-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-9142307.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 10 04:29:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13874 for ; Fri, 10 Oct 2003 04:29:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7se6-0007Rc-4O for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 04:29:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9A8TAtn028614 for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 04:29:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7se5-0007RR-Ly for mip6-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 04:29:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13871 for ; Fri, 10 Oct 2003 04:29:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7se2-0003pC-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 04:29:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7se1-0003p9-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 04:29:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7sdz-0007Qk-7B; Fri, 10 Oct 2003 04:29:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7sdZ-0007Pv-QM for mip6@optimus.ietf.org; Fri, 10 Oct 2003 04:28:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13868; Fri, 10 Oct 2003 04:28:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7sdV-0003p1-00; Fri, 10 Oct 2003 04:28:33 -0400 Received: from teldanex.hiit.fi ([212.68.5.99] helo=n97.nomadiclab.com) by ietf-mx with esmtp (Exim 4.12) id 1A7sdV-0003oG-00; Fri, 10 Oct 2003 04:28:33 -0400 Received: from nomadiclab.com (teldanex.local.nikander.com [192.168.0.194]) by n97.nomadiclab.com (Postfix) with ESMTP id 63B1B1C; Fri, 10 Oct 2003 11:41:20 +0300 (EEST) Message-ID: <3F866D9C.6050807@nomadiclab.com> Date: Fri, 10 Oct 2003 11:28:12 +0300 From: Pekka Nikander User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hipsec@honor.trusecure.com Cc: Multi6 WG , IPV6 WG , MIP6 WG , IPsec WG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] An official HIP BOF request has been sent Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit [Apologies for cross-posting. Please trim the CC: on replies.] Folks, I sent an official BOF request for a Host Identity Protocol BOF a few moments ago. Based on the discussions with the INT area ADs, it looks fairly probable that a BOF will be scheduled. The latest version of the proposed BOF agenda is available at http://www.tml.hut.fi/~pnr/HIP/hipbof.txt The latest version of the proposed WG charter is available at http://www.tml.hut.fi/~pnr/HIP/hip_charter_proposal.txt Note to the IPsec WG: The charter proposal suggest that the new WG would specify a small addition to ESP, basing on draft-nikander-esp-beet-mode-00.txt. Folks at the IPsec WG may have strong opinions on this. The most appropiate place to discuss the BOF and charter proposals is the hipsec mailing list. See the bof agenda and/or charter proposal for details on how to join to the mailing list. The list policy requires non-member postings to be explicitly approved by the list admins. --Pekka Nikander _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 10 06:24:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17485 for ; Fri, 10 Oct 2003 06:24:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7uRI-0006Yl-A5 for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 06:24:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AAO4Xb025209 for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 06:24:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7uRI-0006YW-1w for mip6-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 06:24:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17449 for ; Fri, 10 Oct 2003 06:23:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7uRD-0005hN-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 06:23:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7uRD-0005hK-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 06:23:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7uRF-0006Wh-Ej; Fri, 10 Oct 2003 06:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7uR1-0006W6-Sd for mip6@optimus.ietf.org; Fri, 10 Oct 2003 06:23:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17416 for ; Fri, 10 Oct 2003 06:23:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7uQx-0005fz-00 for mip6@ietf.org; Fri, 10 Oct 2003 06:23:43 -0400 Received: from ool-43504898.dyn.optonline.net ([67.80.72.152] helo=67.80.72.152) by ietf-mx with smtp (Exim 4.12) id 1A7uQx-0005fq-00 for mip6@ietf.org; Fri, 10 Oct 2003 06:23:43 -0400 Date: Fri, 10 Oct 2003 18:48:57 -0500 From: 239835@bigfoot.com X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Reply-To: 239835@yahoo.com Organization: 2029526700 X-Priority: 3 (Normal) To: mip6@ietf.org MIME-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: Content-Transfer-Encoding: 8bit Subject: [Mip6] Upon Approval, Our US Licensed Doctors will 239835 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Wholesale Prescription Medications!

Wholesale Prescription Medications!
OUR DOCTORS WILL WRITE YOU
A PRESCRIPTION FOR FREE!
Get Your Prescription Meds Online
239835 536A5A3-B06CB5D-170A11E8-64CFDB9E-3C13DFCB 473229391
Meds like: Phentermine, Adipex, Soma, Fioricet, Ultram,
Celebrex, Viagra, Valtrex, Zyban, and many, many others.
239835 68E7FA2E-2DE1A0B9-772BC4D3-60C50253-42E5DD7F 368906171
Meds for: Weight Loss, Pain Relief, Muscle Pain Relief, Women's Health, Men's
Health, Impotence, Allergy Relief, Heartburn Relief, Migraine Relief and MORE!
239835  66D7ECB-671603B7-165EEF5E-7E3DCB01-654216BC 1475843424
No Prior Prescription Required - Lowest Prices Possible
Upon Approval, Our US Licensed Doctors will
Prescribe Your Medication For Free
And Have the Medication Shipped Overnight To Your Door.
239835 657208C4-3A11900B-6B5A35EE-41DACA93-21D18E0D 1488324112
You'll get the absolute best value and service on the Internet.

239835 36EBF552-3139166F-2C8CB3ED-6FC017F8-2C0270CC 944125062
Find Out How Here!
239835 3DB08346-725E5927-126E98BE-27B3738A-2F71F95A 1470132196
_______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 10 10:49:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01620 for ; Fri, 10 Oct 2003 10:49:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7yZn-0008IL-HV for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 10:49:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AEn7PG031879 for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 10:49:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7yZn-0008I6-CW for mip6-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 10:49:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01601 for ; Fri, 10 Oct 2003 10:48:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7yZk-0004UN-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 10:49:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A7yZk-0004UJ-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 10:49:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7yZi-0008Gx-OU; Fri, 10 Oct 2003 10:49:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A7yZB-0008F6-DC for mip6@optimus.ietf.org; Fri, 10 Oct 2003 10:48:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01535 for ; Fri, 10 Oct 2003 10:48:19 -0400 (EDT) From: felix_citrajaya@hotmail.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A7yZ8-0004SZ-00 for mip6@ietf.org; Fri, 10 Oct 2003 10:48:26 -0400 Received: from cm124.gamma53.maxonline.com.sg ([202.156.53.124] helo=PONDAL) by ietf-mx with esmtp (Exim 4.12) id 1A7yZ7-0004SK-00 for mip6@ietf.org; Fri, 10 Oct 2003 10:48:26 -0400 To: mip6@ietf.org Date: Fri, 10 Oct 2003 22:40:40 +0800 MIME-Version: 1.0 (produced by Synapse) x-mailer: Synapse - Delphi & Kylix TCP/IP library by Lukas Gebauer Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: Quoted-printable Content-Disposition: inline Content-Description: Message text Message-Id: Content-Transfer-Encoding: Quoted-printable Subject: [Mip6] Info Membangun ASSET Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: Quoted-printable Content-Transfer-Encoding: Quoted-printable Yth Bapak=2FIbu=2FSdr=2Fi Salam Sejahtera=2C Perkenalkan nama saya Felix=2C ingin mengajak anda untuk bekerja sama dalam bisnis yang sedang saya tekuni saat ini=2E Saya mengetahui email address anda dari salah satu web di internet dan= saya berpikir bahwa anda menyenangi komunikasi lewat internet=2E Oleh= karenannya=2C saya ingin membagi kesempatan ini kepada sesama rekan=2C kesempatan untuk melakukan kerjasama usaha melalui internet=2E Info bonus =3A http=3A=2F=2Fvisibaru=2Ewnetwork=2Ebiz=2Fshow=2Ecgi=2Ffcitrajaya=2Frespons= =2Fbonus=2Ehtml Mungkin tawaran ini tidak sesuai bidangnya dengan apa yang anda harapkan= =2C namun tidak ada salahnya bila anda mengetahui informasi mengenai bidang pekerjaan lain yang bisa memberikan penghasilan bagi anda dan keluarga= anda=2E Bisnis yang saya tawarkan ini bahkan bisa anda lakukan walaupun saat ini= anda sedang bekerja=2E Anda tidak perlu meninggalkan pekerjaan anda saat ini=2E Untuk INFO dan PENDAFTARAN free member anda bisa buka website berikut =3A http=3A=2F=2Fvisibaru=2Ewnetwork=2Ebiz=2Fshow=2Ecgi=2Ffcitrajaya Terimakasih atas perhatiannya=2C mohon maaf jika saya mengganggu waktu= anda=2E Salam Sukses=2C Felix Citrajaya Associate Distributor _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 10 22:38:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05139 for ; Fri, 10 Oct 2003 22:38:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A89du-0006DQ-2F for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 22:38:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9B2c6ac023886 for mip6-archive@odin.ietf.org; Fri, 10 Oct 2003 22:38:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A89dt-0006DB-Tc for mip6-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 22:38:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05127 for ; Fri, 10 Oct 2003 22:37:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A89dq-0006hQ-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 22:38:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A89dq-0006hL-00 for mip6-web-archive@ietf.org; Fri, 10 Oct 2003 22:38:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A89dp-0006Bx-Rf; Fri, 10 Oct 2003 22:38:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A89dm-0006B9-GT for mip6@optimus.ietf.org; Fri, 10 Oct 2003 22:37:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05119; Fri, 10 Oct 2003 22:37:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A89di-0006hD-00; Fri, 10 Oct 2003 22:37:54 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1A89di-0006gu-00; Fri, 10 Oct 2003 22:37:54 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9B2bOS29229; Fri, 10 Oct 2003 19:37:24 -0700 X-mProtect: <200310110237> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdhYS7Ff; Fri, 10 Oct 2003 19:37:23 PDT Message-ID: <3F876CE3.9BDDF3AD@iprg.nokia.com> Date: Fri, 10 Oct 2003 19:37:23 -0700 From: Rajeev Koodli 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: mipshop@ietf.org, mip6@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] fast handover revisions Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, I have made some changes. - consolidated the network-initiated handover to a Section (3.3) . Thanks to Jim Kempf for the suggestion and the text. - revised the security considerations section as a follow up on my previous message. This is mostly re-organizing the original text to more clearly outline the considerations and the suggested recommendations. I hope the draft is now ready for the last call! Chairs :-) I won't be able to participate in the discussions until IETF itself. I will be away for few weeks. Best Regards, -Rajeev ps: you can download the draft from http://people.nokia.net/~rajeev/draft-ietf-mobileip-fast-mip6-08.txt _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 11 23:24:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22439 for ; Sat, 11 Oct 2003 23:24:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Wpw-0002F1-KN for mip6-archive@odin.ietf.org; Sat, 11 Oct 2003 23:24:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9C3O4e9008609 for mip6-archive@odin.ietf.org; Sat, 11 Oct 2003 23:24:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Wpw-0002Em-Co for mip6-web-archive@optimus.ietf.org; Sat, 11 Oct 2003 23:24:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22433 for ; Sat, 11 Oct 2003 23:23:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8Wpu-0002qQ-00 for mip6-web-archive@ietf.org; Sat, 11 Oct 2003 23:24:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A8Wpu-0002qM-00 for mip6-web-archive@ietf.org; Sat, 11 Oct 2003 23:24:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8Wps-0002Dz-Iq; Sat, 11 Oct 2003 23:24:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8WpQ-0002DV-0T for mip6@optimus.ietf.org; Sat, 11 Oct 2003 23:23:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22408 for ; Sat, 11 Oct 2003 23:23:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8WpN-0002pl-00 for mip6@ietf.org; Sat, 11 Oct 2003 23:23:29 -0400 Received: from [61.250.95.55] (helo=MailUser) by ietf-mx with smtp (Exim 4.12) id 1A8WpM-0002pb-00 for mip6@ietf.org; Sat, 11 Oct 2003 23:23:29 -0400 Reply-To: "interco" From: "interco" To: "" Organization: Inter Co inc Programming X-Priority: 1 X-MSMail-Priority: High Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 12 Oct 2003 12:25:27 +0900 Message-Id: Subject: [Mip6] Security warning! Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Warning! The scamers, have invented a new way of larceny money from yours e-gold account. It is already, has suffered, hundreds users e-gold and other electronic systems. Our experts, have developed reliable protection, against breakings. To receive a paid advice on protection to you it is necessary to pay 0.30$ (e-gold) and enter your e-mail after payment. The instruction on safety will be sent to you mail. Protect yourself from hackers! http://61.250.95.55 For reception of more detailed information visit this dynamically allocated ip address specially for you. Best regards, General programmer of Inter co Inc, Mike. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sun Oct 12 23:38:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09062 for ; Sun, 12 Oct 2003 23:38:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8tX6-0001qR-DO for mip6-archive@odin.ietf.org; Sun, 12 Oct 2003 23:38:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9D3c8Pe007088 for mip6-archive@odin.ietf.org; Sun, 12 Oct 2003 23:38:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8tX6-0001qF-77 for mip6-web-archive@optimus.ietf.org; Sun, 12 Oct 2003 23:38:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09053 for ; Sun, 12 Oct 2003 23:37:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A8tX4-0006EJ-00 for mip6-web-archive@ietf.org; Sun, 12 Oct 2003 23:38:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A8tX3-0006EF-00 for mip6-web-archive@ietf.org; Sun, 12 Oct 2003 23:38:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8tWz-0001pQ-9s; Sun, 12 Oct 2003 23:38:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A8tWM-0001f1-Lc for mip6@optimus.ietf.org; Sun, 12 Oct 2003 23:37:22 -0400 Received: from CY ([218.109.140.98]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA09004 for ; Sun, 12 Oct 2003 23:37:11 -0400 (EDT) Message-Id: <200310130337.XAA09004@ietf.org> From: "bnad1@juno.com" To: "mip6@ietf.org" Date: Mon, 13 Oct 2003 11:40:27 +0800 X-Priority: 3 (normal) Importance: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 Subject: [Mip6] Genuine College Diplomas - no essays, books or exams! fdskop Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlvbmFs Ly9FTiI+DQoNCjxodG1sPg0KPGhlYWQ+DQo8dGl0bGU+bmE8L3RpdGxlPg0KPC9oZWFkPg0KPGJv ZHkgdG9wbWFyZ2luPSIwIiBiZ2NvbG9yPSIjMDAzMzk5Ij4NCjxkaXYgYWxpZ249ImNlbnRlciI+ PGJyPg0KPHRhYmxlIHdpZHRoPSI2NTAiIGJvcmRlcj0iMSIgY2VsbHNwYWNpbmc9IjAiIGNlbGxw YWRkaW5nPSIyIiBib3JkZXJjb2xvcj0iIzAwMDAwMCI+PHRyPjx0ZD48dGFibGUgd2lkdGg9IjY1 MCIgYm9yZGVyPSIwIiBjZWxsc3BhY2luZz0iMCIgY2VsbHBhZGRpbmc9IjQiIGFsaWduPSJjZW50 ZXIiPjx0cj4NCjx0ZCBiZ2NvbG9yPSIjMDAzMzY2Ij48Zm9udCBzaXplPSIyIiBjb2xvcj0iI0ZG RkZGRiIgZmFjZT0iQXJpYWwsIEhlbHZldGljYSwgc2Fucy1zZXJpZiI+LiBVIE4gPCEtLSBnYXNk MXVhc2QgLS0+SSBWIEUgUiBTIEkgVCBZIC4gRCBJIFAgTCA8IS0tIGdhc2QxdWFzZCAtLT5PIE0g QSBTIC48L2ZvbnQ+PC90ZD48L3RyPg0KPHRyPjx0ZCBiZ2NvbG9yPSJibGFjayIgaGVpZ2h0PSI0 MCIgdmFsaWduPSJtaWRkbGUiPg0KPGRpdiBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJWZXJk YW5hLCBBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXplPSIyIiBjb2xvcj0iI0ZGRkZG RiI+PGk+RG8geW91IHdhbnQgZm9yIGEgcHJvc3Blcm91cyBmdXR1cmUsIGluY3JlYXNlZCBtb25l eSBlYXJuaW5nIHBvd2VyLCBhbmQgdGhlIHJlc3BlY3Qgb2YgYWxsPzwvaT48YnI+PC9mb250Pjwv ZGl2Pg0KPC90ZD48L3RyPjx0cj4gPHRkIGJnY29sb3I9IkNDMDAzMyI+DQo8ZGl2IGFsaWduPSJj ZW50ZXIiPjxwPjxiPjxpPjxmb250IGZhY2U9IlZlcmRhbmEsIEFyaWFsLCBIZWx2ZXRpY2EsIHNh bnMtc2VyaWYiIHNpemU9IjIiPldlIGNhbiBhc3Npc3Qgd2l0aCBEaXA8IS0tIDIzMTQyMzFoIC0t PmxvbWFzIGZyb20gcHJlc3RpZ2lvdXMgbm9uLWFjY3JlZGl0ZWQgdW5pdmVyc2l0PCEtLSAyMzE0 MjMxaCAtLT5pZXMgYmFzZWQgb24geW91ciBwcmVzZW50IGtub3dsZWRnZSBhbmQgbGlmZSBleHBl cmllbmNlLjwvZm9udD48Lw0KPC90ZD48L3RyPjx0cj48dGQgYmdjb2xvcj0id2hpdGUiPg0KPGRp diBhbGlnbj0iY2VudGVyIj48Zm9udCBmYWNlPSJWZXJkYW5hLCBBcmlhbCwgSGVsdmV0aWNhLCBz YW5zLXNlcmlmIiBzaXplPSIzIj48YnI+PGI+PGZvbnQgY29sb3I9IiNGRjAwMDAiPk5vIGJvb2tz LCB0ZXN0cyBvciBpbnRlcnZpZXdzLi4gbm8gY2xhc3NlcyBlaXRoZXIhPC9mb250PjwvYj48L2Rp dj4NCjxwIGFsaWduPSJsZWZ0Ij48aT5CYWNoZWxvcnMsIG1hc3RlcnMsIE1CQSwgYW5kIGRvY3Rv cmF0ZSAoUGhEKSBkaXBsb21hcyBhdmFpbGFibGUgaW4gdGhlIGZpZWxkIG9mIHlvdXIgY2hvaWNl IC0gdGhhdCdzIHJpZ2h0LCB5b3UgY2FuIGJlY29tZSBhIERvY3RvciBhbmQgcmVjZWl2ZSBhbGwg dGhlIGJlbmVmaXRzIGFuZCBhZG1pcmF0aW9uIHRoYXQgY29tZXMgd2l0aCBpdCE8L2k+PC9mb250 PjwvcD4NCjxwIGFsaWduPSJjZW50ZXIiPjxiPjxmb250IHNpemU9IjUiIGNvbG9yPSIjMDAwMEZG Ij5ObyBvbmUgaXMgdHVybmVkIGRvd24uPC9mb250PjwvYj48L3A+DQo8cCBhbGlnbj0iY2VudGVy Ij48aT5Db25maWRlbnRpYWxpdHkgYXNzdXJlZDwvaT48L2ZvbnQ+PGJyPjxicj48L3A+DQo8L3Rk PjwvdHI+PHRyPjx0ZCBiZ2NvbG9yPSIjMDAwMDAwIj4NCjxkaXYgYWxpZ249ImNlbnRlciI+PHA+ PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwsIEhlbHZldGljYSwgc2Fucy1zZXJpZiIgY29sb3I9 IiNGRkZGRkYiPjxicj4NCkNBTEwgVVMmbmJzcDsgMjQgSE9VUlMgQSBEQVksIDcgREFZUyZuYnNw OyBBIFdFRUs8L2ZvbnQ+PC9wPg0KPHA+PGZvbnQgc2l6ZT0iMiIgZmFjZT0iQXJpYWwsIEhlbHZl dGljYSwgc2Fucy1zZXJpZiIgY29sb3I9IiNGRkZGRkYiPiZuYnNwOyA8Zm9udCBzaXplPSIxIj4o aW5jbHVkaW5nIFN1bmRheXMgYW5kIGhvbGlkYXlzKTo8L2ZvbnQ+PC9mb250PjwvcD4NCjxwPjxm b250IHNpemU9IjIiIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYiIGNvbG9yPSIj RkZGRkZGIj48Yj48Zm9udCBzaXplPSI1Ij5DQUxMIDEtMjwhLS0gZ2FzZDF1YXNkIC0tPjEyLTIw Mi00Nzg1PC9mb250PjwvYj4gPC9mb250PiA8Zm9udCBzaXplPSI1IiBmYWNlPSJBcmlhbCwgSGVs dmV0aWNhLCBzYW5zLXNlcmlmIiBjb2xvcj0iI0ZGRkZGRiI+PGJyPjwvYj48L2ZvbnQ+PC9wPjwv ZGl2Pg0KPC90ZD48L3RyPjx0cj4gPHRkIGJnY29sb3I9IiMwMDMzNjYiPg0KPGRpdiBhbGlnbj0i Y2VudGVyIj48Zm9udCBzaXplPSIyIiBjb2xvcj0iI0ZGRkZGRiIgZmFjZT0iQXJpYWwsIEhlbHZl dGljYSwgc2Fucy1zZXJpZiI+PGI+Q2FsbCB1cyBOT1cgdG8gcmVjZWl2ZSB5b3VyIGRpcGxvPCEt LSAyMzE0MjMxaCAtLT5tYSB3aXRoaW4gZGF5cywgYW5kIHN0YXJ0IGltcHJvdmluZyB5b3VyIGxp ZmUhPC9iPjwvZm9udD48L2Rpdj4NCjwvdGQ+PC90cj48L3RhYmxlPjwvdGQ+PC90cj48L3RhYmxl PjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 13 15:39:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22939 for ; Mon, 13 Oct 2003 15:39:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98X6-0003mZ-IO for mip6-archive@odin.ietf.org; Mon, 13 Oct 2003 15:39:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DJd8SL014533 for mip6-archive@odin.ietf.org; Mon, 13 Oct 2003 15:39:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98X6-0003mK-DW for mip6-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 15:39:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22928 for ; Mon, 13 Oct 2003 15:38:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A98X5-0007Gm-00 for mip6-web-archive@ietf.org; Mon, 13 Oct 2003 15:39:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A98X4-0007Gj-00 for mip6-web-archive@ietf.org; Mon, 13 Oct 2003 15:39:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98X0-0003lZ-0U; Mon, 13 Oct 2003 15:39:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A98WG-0003gm-GH for mip6@optimus.ietf.org; Mon, 13 Oct 2003 15:38:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22860 for ; Mon, 13 Oct 2003 15:38:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A98WF-0007FT-00 for mip6@ietf.org; Mon, 13 Oct 2003 15:38:15 -0400 Received: from [61.250.95.55] (helo=MailUser) by ietf-mx with smtp (Exim 4.12) id 1A98WD-0007FJ-00 for mip6@ietf.org; Mon, 13 Oct 2003 15:38:14 -0400 Reply-To: "interco" From: "interco" To: "" Organization: Inter Co inc Programming X-Priority: 1 X-MSMail-Priority: High Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 14 Oct 2003 04:40:12 +0900 Message-Id: Subject: [Mip6] Security Warning! Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Warning! The swindlers have invented a new way of stealing your money from your e-gold account. Hundreds of e-gold and other electronic systems users have already suffered from it. The swindlers have invented a new way of stealing your money from your e-gold account. Hundreds of e-gold and other electronic systems users have already suffered from it. http://61.250.95.55 CLICK RIGHT NOW! Protect yourself from hackers! http://61.250.95.55 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 14 04:30:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29903 for ; Tue, 14 Oct 2003 04:30:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9KZG-0006zb-M6 for mip6-archive@odin.ietf.org; Tue, 14 Oct 2003 04:30:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9E8UAKF026874 for mip6-archive@odin.ietf.org; Tue, 14 Oct 2003 04:30:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9KZF-0006zM-Ta for mip6-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 04:30:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29881 for ; Tue, 14 Oct 2003 04:30:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9KZC-0007FN-00 for mip6-web-archive@ietf.org; Tue, 14 Oct 2003 04:30:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9KZC-0007FJ-00 for mip6-web-archive@ietf.org; Tue, 14 Oct 2003 04:30:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9KZ8-0006ye-W4; Tue, 14 Oct 2003 04:30:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9KYB-0006xM-7L for mip6@optimus.ietf.org; Tue, 14 Oct 2003 04:29:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29865 for ; Tue, 14 Oct 2003 04:28:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9KY8-0007Et-00 for mip6@ietf.org; Tue, 14 Oct 2003 04:29:00 -0400 Received: from hermes.rz.fhtw-berlin.de ([141.45.5.100]) by ietf-mx with esmtp (Exim 4.12) id 1A9KY7-0007Ep-00 for mip6@ietf.org; Tue, 14 Oct 2003 04:28:59 -0400 Received: from rz-thinkapd02 (ip07243.in.fhtw-berlin.de [141.45.247.243]) by hermes.rz.fhtw-berlin.de (8.12.9/8.12.2) with ESMTP id h9E8SjEr016569 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Oct 2003 10:28:52 +0200 (MEST) Date: Tue, 14 Oct 2003 10:29:11 +0200 (=?X-UNKNOWN?Q?Westeurop=E4ische_Sommerzeit?=) From: Matthias Waehlisch To: zhang.liansheng@zte.com.cn cc: mobile-ip@sunroof.eng.sun.com, mip6@ietf.org In-Reply-To: Message-ID: References: X-X-Sender: mw@hermes.rz.fhtw-berlin.de MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Mip6] Re: [mobile-ip] how to measure the handoff latency in MIPv6 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , hello Zhang Liansheng, On Wed, 8 Oct 2003 zhang.liansheng@zte.com.cn wrote: > I want to know the handoff latency when a mobile IPv6 node moves from one > subnet to another, but I am not sure of the method to measure it. > > And my test bed is based on KAME-MIPv6,freebsd. Can anyone kindly tell me > how to measure it? > we have used only a simple 'ping' tool, which generated UDP packets (and a logfile with the appropriate values like roundtrip time), i.e. the MN send and receive numbered and time-stamped UDP packets following a predefined trigger of 10 to 20 ms. these packets are reflected by the CN. you can find our results at the Terena paper under: o http://www.rz.fhtw-berlin.de/projekte/ipv6/mipv6.html please, don't hesitate to contact me, if you have more questions about the topic. best regards matthias :::::::::::::::::: Matthias Waehlisch HRZ - FHTW Berlin mailto:mw at fhtw-berlin.de http://www.rz.fhtw-berlin.de _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 14 20:34:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11592 for ; Tue, 14 Oct 2003 20:34:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Zc3-0007Fn-9G for mip6-archive@odin.ietf.org; Tue, 14 Oct 2003 20:34:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F0Y338027882 for mip6-archive@odin.ietf.org; Tue, 14 Oct 2003 20:34:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Zc3-0007Fd-45 for mip6-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 20:34:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11559 for ; Tue, 14 Oct 2003 20:33:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9Zc0-0004Fe-00 for mip6-web-archive@ietf.org; Tue, 14 Oct 2003 20:34:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9Zc0-0004Fb-00 for mip6-web-archive@ietf.org; Tue, 14 Oct 2003 20:34:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Zc1-0007Ev-28; Tue, 14 Oct 2003 20:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9Zbp-0007EE-SG for mip6@optimus.ietf.org; Tue, 14 Oct 2003 20:33:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11546 for ; Tue, 14 Oct 2003 20:33:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9Zbn-0004FH-00 for mip6@ietf.org; Tue, 14 Oct 2003 20:33:47 -0400 Received: from h66-201-203-18.gtcust.grouptelecom.net ([66.201.203.18] helo=bvimailbox.com) by ietf-mx with smtp (Exim 4.12) id 1A9Zbg-0004Dz-00 for mip6@ietf.org; Tue, 14 Oct 2003 20:33:44 -0400 From: "Annuaire des subventions 2004" To: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Tue, 14 Oct 2003 20:33:41 -0400 Reply-To: "Annuaire des subventions 2004" Message-Id: Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA11547 Subject: [Mip6] Available / Disponible; subventions, prets, financement Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable MESSAGE FRANCAIS INCLUS****FRENCH MESSAGE INCLUDED CANADIAN SUBSIDY DIRECTORY 4865 HWY 138,R.R 1 ST-ANDREWS WEST ONTARIO, KOC 2A0 Publications Canadiennes 1556 Grand Marnier Val David Qc JoT 2N0 PRESS RELEASE CANADIAN SUBSIDY DIRECTORY YEAR 2003 EDITION Legal Deposit-National Library of Canada ISBN 2-922870-05-7 The new revised edition of the Canadian Subsidy Directory 2003 is now available.=20 The new edition is the most complete and affordable reference for anyone looking for financial support. It is deemed to be the perfect tool for new or existing businesses, individual ventures, foundations and associations. This Publication contains more than 2000 direct and indirect financial subsidies, grants and loans offered by government departments and agencies, foundations, associations and organisations. In this new 2003 edition all programs are well described. The Canadian Subsidy Directory is the most comprehensive tool to start up a business, improve existent activities, set up a business plan, or obtai= n assistance from experts in fields such as: Industry, transport, agriculture, communications, municipal infrastructure, education, import-export, labor, construction and renovation, the service sector, hi-tech industries, research and development, joint ventures, arts, cinema, theatre, music and recording industry, the self employed, contests, and new talents. Assistance from and for foundations and associations, guidance to prepare a business plan, market surveys, computers, and much more! The Canadian Subsidy Directory is sold $ 49.95, to obtain a copy please call: Canadian Publications: (866) 322-3376 MESSAGE FRANCAIS*******FRENCH MESSAGE ANNUAIRE DES SUBVENTIONS AU QU=C9BEC 2004 D=E9pot l=E9gal-Biblioth=E8que Nationale du Qu=E9bec ISBN 2-922870-06-5 COMMUNIQU=C9 DE PRESSE Les Publications Canadiennes offrent au public une =E9dition r=E9vis=E9e = de l'ANNUAIRE DES SUBVENTIONS AU QU=C9BEC contenant plus de 1900 programmes d'aides et de subventions provenant des divers paliers gouvernementaux et organismes. Dans la nouvelle =E9dition 2004 on trouve la description des programmes ainsi que les montants allou=E9s. L'ANNUAIRE DES SUBVENTIONS AU QU=C9BEC est l'outil id=E9al soit pour d=E9= marrer son entreprise, am=E9liorer une entreprise existante, mettre sur pied son pla= n d'affaires ou obtenir l'aide de conseillers experts dans le domaine des affaires: D=E9marrage d'entreprises, =E9tudes, recherches, arts, agriculture, impor= t export, main d'oeuvre, cin=E9ma, pr=EAts, promotion, bourses, th=E9atre, transpor= ts, communications, mise sur pied et d=E9veloppement d'entreprises, construct= ion et r=E9novation, a=E9rospatial, concours, nouveaux talents, aide aux associa= tions, organismes et fondations, informatique, musique, industrie du disque, pla= ns d'affaires, =E9tudes de march=E9s, infrastructures, aide aux travailleurs autonomes et plus encore ! L'annuaire des subventions est vendu $ 49,95. Informations.....................866-322-3376 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 15 03:30:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18845 for ; Wed, 15 Oct 2003 03:30:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9g6h-00008Z-Rk for mip6-archive@odin.ietf.org; Wed, 15 Oct 2003 03:30:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F7U7lT000524 for mip6-archive@odin.ietf.org; Wed, 15 Oct 2003 03:30:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9g6h-00008N-AF for mip6-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 03:30:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18822 for ; Wed, 15 Oct 2003 03:29:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9g6e-0000b2-00 for mip6-web-archive@ietf.org; Wed, 15 Oct 2003 03:30:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1A9g6e-0000az-00 for mip6-web-archive@ietf.org; Wed, 15 Oct 2003 03:30:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9g6d-00007X-Nu; Wed, 15 Oct 2003 03:30:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A9g6X-00006j-GY for mip6@optimus.ietf.org; Wed, 15 Oct 2003 03:29:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18795 for ; Wed, 15 Oct 2003 03:29:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A9g6V-0000ae-00 for mip6@ietf.org; Wed, 15 Oct 2003 03:29:55 -0400 Received: from bgp969832bgs.detrtc01.mi.comcast.net ([68.42.177.149] helo=68.42.177.149) by ietf-mx with smtp (Exim 4.12) id 1A9g6T-0000aV-00 for mip6@ietf.org; Wed, 15 Oct 2003 03:29:54 -0400 Date: Wed, 15 Oct 2003 15:51:30 -0500 From: 239930@mail.com X-Mailer: MailCity Service Reply-To: 239930@msn.com Organization: 689944334 X-Priority: 3 (Normal) To: mip6@ietf.org MIME-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-Id: Content-Transfer-Encoding: 8bit Subject: [Mip6] Effectively Spam Detecting 239930 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit
Spam Remedy   (3.17Mb)
Description:

The powerful, effective and intelligent anti-spam tool.
It automatically cleans spam messages out of your mailbox before you receive or read them.

Features:
  • Automatically Blocking Spam
    Spam Remedy automatically checks your mail boxes and filters unwanted, dangerous, or offensive mail messages to save your time from manually detecting and organizing mail messages. For more information click here 239930 7B8316D0-6AD21B73-7D1EE8A7-410D5E04-457C8C15 782612161
  • Effectively Spam Detecting
    A complex Aritificial Intelligence algorithm has been used in Spam Remedy product to detecting legitimate mail messages and spam messages,the technique has more precision than other filter-based and keyword-based anti-spam technologies . For more information click here 239930  44511620-7E9B923A-63FCEE92-185668AE-31535214 701451762
  • Be Sure You Get Your Right Mail Messages
    Spam Remedy doesn't confirm a spam message by a single keyword in mail content. It examines the entire message - source, headers and mail content to confirm whether it is a spam message . For more information click here 239930 773AD8DB-73525454-663BA11C-24EDDF42-3D14FD09 674812698
  • Supports Multiple Email Types and Almost All Email Clients
    Spam Remedy supports POP3, Hotmail/MSN, IMAP4 and MAPI email accounts,Directly works with almost all email clients(Outlook Express, Becky Mail,Foxmail,Outlook, The bat!, Eudora etc.), espacially includes support for web-based Hotmail/MSN email clients. Nothing you need to change to your email clients . For more information click here 239930 1BE36668-2A5C7201-27D00575-310E9F2B-13CBAF3 1161940408
  • Easy to use
    You don't need to set any complex filter rules, just add your email accounts to Spam Remedy and then it works . For more information click here 239930 3D557424-1C9FB23-4C320DF0-4260B65F-646E453 13499759
  • Friends List and Rejecting List
    With Friends List and Rejecting List, you have the chance to decide who are never blocked or directly treat their mail messages as spam . For more information click here 239930 4B2965E0-577F4380-6D445872-64CAEC01-132E2D60 703812992

  • Keep your inbox clean
    Spam Remedy places all intercepted spam messages to its interval mail database so that your inbox remains uncluttered and free of spam.If for some reason a legitimate email is flagged as spam, you can easily recover in multiple ways
    • . For more information click here 239930 24A239AD-333C5E82-7B90B73E-102EF69C-3C0185A7 1828131855
239930 5A009FD4-70BB8FEC-503B66A2-14C71985-54D82984 1377534570 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 16 03:55:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23798 for ; Thu, 16 Oct 2003 03:55:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA2yS-0006NY-Pz for mip6-archive@odin.ietf.org; Thu, 16 Oct 2003 03:55:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9G7t8X1024454 for mip6-archive@odin.ietf.org; Thu, 16 Oct 2003 03:55:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA2yQ-0006ML-NS for mip6-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 03:55:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23795 for ; Thu, 16 Oct 2003 03:54:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA2yO-0001qF-00 for mip6-web-archive@ietf.org; Thu, 16 Oct 2003 03:55:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AA2yN-0001qC-00 for mip6-web-archive@ietf.org; Thu, 16 Oct 2003 03:55:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA2yM-0006Lu-RJ; Thu, 16 Oct 2003 03:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA2y3-0006L9-9d for mip6@optimus.ietf.org; Thu, 16 Oct 2003 03:54:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23789; Thu, 16 Oct 2003 03:54:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA2y0-0001q1-00; Thu, 16 Oct 2003 03:54:40 -0400 Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1AA2xz-0001py-00; Thu, 16 Oct 2003 03:54:40 -0400 Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 1738615210; Thu, 16 Oct 2003 16:54:37 +0900 (JST) Date: Thu, 16 Oct 2003 16:54:35 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: ipv6@ietf.org Cc: mip6@ietf.org, ietf-send@standards.ericsson.net User-Agent: Wanderlust/2.10.0 (Venus) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Subject: [Mip6] RFC2462 update Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hello, (Sorry for the cross-posting. This is because many people who are not in the ipv6 list may want to join the discussion. I'll restrict my further posting to the ipv6 list in order to avoid unnecessary noise.) As asked by the IPv6 wg co-chairs, I'm going to update the "IPv6 Stateless Address Autoconfiguration" document (which is currently RFC2462) as a new I-D. Since we'll soon miss the cut-off date for an initial I-D, my current plan is to make a list of issues raised so far (that include the very recent discussion in the ipv6 list) and submit a 00 draft containing the list. I'll send an initial proposal of the issue list to the ipv6 list in a day or so, get quick comments on the issue list, and then edit and submit the draft. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 16 08:48:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00998 for ; Thu, 16 Oct 2003 08:48:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA7Xw-0004QD-0u for mip6-archive@odin.ietf.org; Thu, 16 Oct 2003 08:48:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GCm3fH016993 for mip6-archive@odin.ietf.org; Thu, 16 Oct 2003 08:48:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA7Xv-0004Q0-Qr for mip6-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 08:48:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00949 for ; Thu, 16 Oct 2003 08:47:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA7Xu-0004Mn-00 for mip6-web-archive@ietf.org; Thu, 16 Oct 2003 08:48:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AA7Xu-0004Mk-00 for mip6-web-archive@ietf.org; Thu, 16 Oct 2003 08:48:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA7Xt-0004O5-9F; Thu, 16 Oct 2003 08:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AA7XD-0004Mo-Na for mip6@optimus.ietf.org; Thu, 16 Oct 2003 08:47:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00936; Thu, 16 Oct 2003 08:47:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AA7XC-0004M9-00; Thu, 16 Oct 2003 08:47:18 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1AA7XB-0004Le-00; Thu, 16 Oct 2003 08:47:17 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RCK9R>; Thu, 16 Oct 2003 08:46:38 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922DD9@ftmail.lab.flarion.com> From: Soliman Hesham To: ipv6@ietf.org Cc: mip6@ietf.org, ietf-send@standards.ericsson.net Date: Thu, 16 Oct 2003 08:46:35 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="ISO-2022-JP" Subject: [Mip6] RFC2461 update Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Folks, Sorry for the cross posting. This is a heads up to let you know that I'm updating the Neighbour Discovery specification, RFC 2461 as requested by the IPv6 WG chairs. The updates are likely to include issues raised in the WGs copied on this email. If you're interested in following this discussion please monitor the IPv6 mailing list. Like Jinmeii, I'll be sending a list of issues that were raised and would appreciate your feedback. The list of issues will come towards the beginning of next week. I'm currently going through the archives. Hesham _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 17 15:35:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18435 for ; Fri, 17 Oct 2003 15:35:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaNU-0006EU-1w for mip6-archive@odin.ietf.org; Fri, 17 Oct 2003 15:35:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HJZBXF023952 for mip6-archive@odin.ietf.org; Fri, 17 Oct 2003 15:35:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaNT-0006EF-It for mip6-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 15:35:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18305 for ; Fri, 17 Oct 2003 15:35:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAaNS-0007RI-00 for mip6-web-archive@ietf.org; Fri, 17 Oct 2003 15:35:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAaNR-0007RE-00 for mip6-web-archive@ietf.org; Fri, 17 Oct 2003 15:35:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaNM-0006DI-6G; Fri, 17 Oct 2003 15:35:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAaN6-0006Bg-UR for mip6@optimus.ietf.org; Fri, 17 Oct 2003 15:34:48 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18246; Fri, 17 Oct 2003 15:34:39 -0400 (EDT) Message-Id: <200310171934.PAA18246@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip6@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 17 Oct 2003 15:34:39 -0400 Subject: [Mip6] I-D ACTION:draft-mkhalil-mipv6-nai-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Mobile IP Network Access Identifier Extension for IPv6 Author(s) : M. Khalil, et. al. Filename : draft-mkhalil-mipv6-nai-00.txt Pages : 0 Date : 2003-10-17 This document defines a way for the mobile node to identify itself, by including the NAI with the MIPv6 Binding Update messages. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-mkhalil-mipv6-nai-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-mkhalil-mipv6-nai-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-mkhalil-mipv6-nai-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: <2003-10-17123938.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-mkhalil-mipv6-nai-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-mkhalil-mipv6-nai-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-17123938.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 17 21:23:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02624 for ; Fri, 17 Oct 2003 21:23:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfo9-0005dS-Re for mip6-archive@odin.ietf.org; Fri, 17 Oct 2003 21:23:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9I1N5R9021656 for mip6-archive@odin.ietf.org; Fri, 17 Oct 2003 21:23:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfo9-0005dD-NG for mip6-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 21:23:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02618 for ; Fri, 17 Oct 2003 21:22:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAfo7-0003yB-00 for mip6-web-archive@ietf.org; Fri, 17 Oct 2003 21:23:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAfo6-0003y8-00 for mip6-web-archive@ietf.org; Fri, 17 Oct 2003 21:23:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfo5-0005cl-7l; Fri, 17 Oct 2003 21:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAfnn-0005cU-Tj for mip6@optimus.ietf.org; Fri, 17 Oct 2003 21:22:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02615 for ; Fri, 17 Oct 2003 21:22:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAfnl-0003y5-00 for mip6@ietf.org; Fri, 17 Oct 2003 21:22:41 -0400 Received: from smtp803.mail.ukl.yahoo.com ([217.12.12.140]) by ietf-mx with smtp (Exim 4.12) id 1AAfnk-0003xw-00 for mip6@ietf.org; Fri, 17 Oct 2003 21:22:40 -0400 Received: from unknown (HELO eremmell) (elmic@sbcglobal.net@206.169.187.21 with login) by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 18 Oct 2003 01:22:04 -0000 From: "Ed Remmell" To: Date: Fri, 17 Oct 2003 18:22:03 -0700 Message-ID: <000801c39516$3dc2edb0$6901a8c0@eremmell> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [Mip6] new v1.7 of Elmic Win32 demo: Mobille IPV6 MN+CN +IPsec/IKE Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, When we recently participated in MoonV6, it was using a Win32 port of our dual stack product for embedded systems. This can be downloaded here; http://www.elmic.com/TreckDemo.zip This has Mobile IPv6 MN and CN compliant with the latest drafts. This version adds support for some new products (SMTP client, web server), and also adds IPsec/IKE with the ability to configure the SPD and SADB using a flat file (the example ipsec.config file is setup with the HA address being 3ffe:aaaa::aaaa, and the MN home address being 3ffe:aaaa::bbbb). This version available on our web site does not have IPsec encryption of user data (you can still use IKE and AH with it, however). If you want the full version with the IPsec encryption algorithms (note: we can only provide it to U.S. companies or their subsidiaries for internal use, due to U.S. export restrictions on encryption), then send a request to support@elmic.com. MN movement detection is Eager Cell Switching, however since the MoonV6 test network didn't have frequent RA beacons, we also added L2 triggers (specifically, the winpcap Ethernet "link-up" indication causes a L3 handover). So, you can force a L3 move by disconnecting the Ethernet cable (on the MN), and reconnecting it (into a different hub on a different network, for example). Thanks. - Ed Remmell Elmic Systems USA, Inc. Best of Show Winner, ESC 2003 Click on the link and take a look! http://cmp.iconvention.com/escshowdaily/v33/index.cvn?ID=10183 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.522 / Virus Database: 320 - Release Date: 9/29/2003 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 18 02:51:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21681 for ; Sat, 18 Oct 2003 02:51:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAkvb-0004wN-EK for mip6-archive@odin.ietf.org; Sat, 18 Oct 2003 02:51:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9I6p7bw018990 for mip6-archive@odin.ietf.org; Sat, 18 Oct 2003 02:51:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAkva-0004wD-Vg for mip6-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 02:51:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21646 for ; Sat, 18 Oct 2003 02:50:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAkvW-0006ZW-00 for mip6-web-archive@ietf.org; Sat, 18 Oct 2003 02:51:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAkvW-0006ZT-00 for mip6-web-archive@ietf.org; Sat, 18 Oct 2003 02:51:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAkvW-0004vE-KZ; Sat, 18 Oct 2003 02:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAkvR-0004v0-9Y for mip6@optimus.ietf.org; Sat, 18 Oct 2003 02:50:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21637 for ; Sat, 18 Oct 2003 02:50:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAkvM-0006ZM-00 for mip6@ietf.org; Sat, 18 Oct 2003 02:50:52 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AAkvM-0006ZC-00 for mip6@ietf.org; Sat, 18 Oct 2003 02:50:52 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9I6oMH04328 for ; Fri, 17 Oct 2003 23:50:22 -0700 X-mProtect: <200310180650> Nokia Silicon Valley Messaging Protection Received: from tkniveto.iprg.nokia.com (205.226.2.111, claiming to be "kniveton.com") by darkstar.iprg.nokia.com smtpdBy1CtU; Fri, 17 Oct 2003 15:08:55 PDT Message-ID: <3F90686D.1EE5553@kniveton.com> Date: Fri, 17 Oct 2003 15:08:45 -0700 From: "T.J. Kniveton" X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mip6@ietf.org Subject: Re: [Mip6] I-D ACTION:draft-mkhalil-mipv6-nai-00.txt References: <200310171934.PAA18246@ietf.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > Title : Mobile IP Network Access Identifier Extension for IPv6 > Author(s) : M. Khalil, et. al. > Filename : draft-mkhalil-mipv6-nai-00.txt > Pages : 0 > Date : 2003-10-17 > > This document defines a way for the mobile node to identify itself, > by including the NAI with the MIPv6 Binding Update messages. I have some comments and questions on the draft, if you're ready for them. Is there supposed to be any way to authenticate a user as owning a particular NAI? Are you planning on integrating the use of AAAv6, PANA, or some other method? Upon receiving the Binding Update, the HA will first verify the authenticity of the Binding Update. It will then attempt to allocate a unique IP address to the MN. This is a catch-22, right? How can the HA verify the authenticity of the BU without having a pre-established security association with the MN at a certain address? There is no way listed to establish some sort of authenticity of the NAI, unless I am totally missing something.. Upon receiving a Binding Update, the HA MUST verify the authenticity of the Binding Update message. The authentication process is out side the scope of this draft. I disagree. If and when the HA receives a valid Binding Update with the Home IP address field set to zero and the NAI option included, it will attemnpt to allocate a unique IP address and proceed with registration procedure as stated in [MIPV6]. So this means you are turning off all security? I think I am not understanding the gist of the draft. Please explain how security works in this scheme.. thanks, TJ -- T.J. Kniveton Communication Systems Lab Nokia Research Center _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 18 13:10:42 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02907 for ; Sat, 18 Oct 2003 13:10:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAuas-0007Yr-RA for mip6-archive@odin.ietf.org; Sat, 18 Oct 2003 13:10:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9IHAMgG029066 for mip6-archive@odin.ietf.org; Sat, 18 Oct 2003 13:10:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAuas-0007Yj-Ii for mip6-web-archive@optimus.ietf.org; Sat, 18 Oct 2003 13:10:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02873 for ; Sat, 18 Oct 2003 13:10:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAuaq-0003Em-00 for mip6-web-archive@ietf.org; Sat, 18 Oct 2003 13:10:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAuaq-0003Ej-00 for mip6-web-archive@ietf.org; Sat, 18 Oct 2003 13:10:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAuaX-0007QZ-U6; Sat, 18 Oct 2003 13:10:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAua7-0007OO-HE for mip6@optimus.ietf.org; Sat, 18 Oct 2003 13:09:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02853 for ; Sat, 18 Oct 2003 13:09:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAua5-0003EE-00 for mip6@ietf.org; Sat, 18 Oct 2003 13:09:33 -0400 Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx with esmtp (Exim 4.12) id 1AAua5-0003E8-00 for mip6@ietf.org; Sat, 18 Oct 2003 13:09:33 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9IH9Q4t003336; Sat, 18 Oct 2003 10:09:26 -0700 (PDT) Received: from NAEXFE01.na.qualcomm.com (naexfe01.qualcomm.com [172.30.32.17]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9IH9O0N014469; Sat, 18 Oct 2003 10:09:24 -0700 (PDT) Received: from NAEX01.qualcomm.com ([129.46.51.60]) by NAEXFE01.na.qualcomm.com with Microsoft SMTPSVC(5.0.2195.6713); Sat, 18 Oct 2003 10:09:24 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] I-D ACTION:draft-mkhalil-mipv6-nai-00.txt X-MimeOLE: Produced By Microsoft Exchange V6.0.6470.0 Date: Sat, 18 Oct 2003 10:09:24 -0700 Message-ID: <17D8F6DF3ED94D40BD607380866D9B7F33D1A7@NAEX01.na.qualcomm.com> Thread-Topic: [Mip6] I-D ACTION:draft-mkhalil-mipv6-nai-00.txt Thread-Index: AcOVRDzWElwA+4w2Twax8cHCl02ovwAVSbGw From: "Barany, Pete" To: "T.J. Kniveton" , X-OriginalArrivalTime: 18 Oct 2003 17:09:24.0054 (UTC) FILETIME=[94357760:01C3959A] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable I too have questions about this (or perhaps I misunderstand). The I-D mentions the use of IKE/IPsec (where IKE is a "MAY" in Mobile IPv6) ... but the whole point of using IKE ISAKMP SA and the IKE IPsec SA in the first place is to start by authenticating the BU. In IKE Phase 1, if you cannot use the IP_V6_ADDR Identification Type in the ISAKMP Identification payload, then you can simply use ID_USER_FQDN Identification Type (i.e., mobile@foobar.com ... which is an NAI). Also, how is the HA supposed to assign an IPv6 address to the MN if the requested IPv6 address is set to zero? IPv6 (nor MIPv6) do not work that way. Pete -----Original Message----- From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On Behalf Of T.J. Kniveton Sent: Friday, October 17, 2003 3:09 PM To: mip6@ietf.org Subject: Re: [Mip6] I-D ACTION:draft-mkhalil-mipv6-nai-00.txt Internet-Drafts@ietf.org wrote: >=20 > A New Internet-Draft is available from the on-line Internet-Drafts directories. >=20 > Title : Mobile IP Network Access Identifier Extension for IPv6 > Author(s) : M. Khalil, et. al. > Filename : draft-mkhalil-mipv6-nai-00.txt > Pages : 0 > Date : 2003-10-17 >=20 > This document defines a way for the mobile node to identify itself, > by including the NAI with the MIPv6 Binding Update messages. I have some comments and questions on the draft, if you're ready for them. Is there supposed to be any way to authenticate a user as owning a particular NAI? Are you planning on integrating the use of AAAv6, PANA, or some other method? Upon receiving the Binding Update, the HA will first verify=20 the authenticity of the Binding Update. It will then attempt to allocate a unique IP address to the MN. This is a catch-22, right? How can the HA verify the authenticity of the BU without having a pre-established security association with the MN at a certain address? There is no way listed to establish some sort of authenticity of the NAI, unless I am totally missing something.. Upon receiving a Binding Update, the HA MUST verify the=20 authenticity of the Binding Update message. The authentication process is out side the scope of this draft. I disagree. If and when the HA receives a valid Binding Update with the Home IP address field set to zero and the NAI option included, it will attemnpt to allocate a unique IP address and=20 proceed with registration procedure as stated in [MIPV6]. So this means you are turning off all security? I think I am not understanding the gist of the draft. Please explain how security works in this scheme.. thanks, TJ --=20 T.J. Kniveton=20 Communication Systems Lab Nokia Research Center _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sun Oct 19 15:08:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15558 for ; Sun, 19 Oct 2003 15:08:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABIuN-0003Zi-Po for mip6-archive@odin.ietf.org; Sun, 19 Oct 2003 15:08:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9JJ87Ga013738 for mip6-archive@odin.ietf.org; Sun, 19 Oct 2003 15:08:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABIuN-0003ZV-M4 for mip6-web-archive@optimus.ietf.org; Sun, 19 Oct 2003 15:08:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15504 for ; Sun, 19 Oct 2003 15:07:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABIuK-0007Ry-00 for mip6-web-archive@ietf.org; Sun, 19 Oct 2003 15:08:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABIuK-0007Ru-00 for mip6-web-archive@ietf.org; Sun, 19 Oct 2003 15:08:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABIuH-0003Vs-7F; Sun, 19 Oct 2003 15:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABItO-0002xg-Uf for mip6@optimus.ietf.org; Sun, 19 Oct 2003 15:07:06 -0400 Received: from mail1.artmarket.com (mail1.artmarket.com [194.242.43.186]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15393 for ; Sun, 19 Oct 2003 15:06:52 -0400 (EDT) Date: Sun, 19 Oct 2003 15:06:52 -0400 (EDT) Message-Id: <200310191906.PAA15393@ietf.org> From: Fine Art Directory To: MIME-Version: 1.0 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA15400 Subject: [Mip6] [ADV] For Artists, Galleries, museums, Art centers Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable ART-ONLINE tm "> =20
=20 =20
=20
=20 =20
T=   H  E    F  I &nb= sp;N  E    A  R  T = ;   D  I  R  E  C&= nbsp; T  O  R  Y

Where people will find your web= site?

Artists/Medium/Painting/Oil or
Galleries/Periods/Modern & Contemporary Art?


=20
We daily add and update new sites to = our index,=20 and we invite you to submit your URL. =20

Most visited categories :

View=20 all our categories

Art-Online=20 is an information service provided by Artprice,=20 the world leader in Art market information.
To take advantage of the 900,000 Artprice customers (galleries, museum cu= rators,=20 collectors, appraisers,
auctioneers, art experts, art critics and lovers) and to give a worldwide= visibility=20 to your website:

Everything you always wanted to= know about=20 Fine Art
http://www.Art-Online.com

Edited and updated b= y a Human team

 

=20
=20   by =20  art-online ©1995   1987-2= 003
 ©Thierry Ehrmann









=20 =20
=20 To remove your email: mip6@ietf.org
please click below:
http://list.artists-server.com/?m=3Dmip6@ietf.org
In case the above link does not work you can go to
http://list.artists-server.com/
or reply to this message as it is.
Please allow us 72 H for your e-mail to be removed.
Thank you for your= co-operation. 		=20 Pour d=E9sinscrire votre email : mip6@ietf.org
cliquez ci-dessous :
http://list.= artists-server.com/?m=3Dmip6@ietf.org
Si le lien ci-dessus ne fonctionne pas, vous pouvez aller sur :
http://list.artists-server.com/
ou r=E9pondez svp =E0 ce message sans en modifier le contenu.
Votre d=E9sinscription sera effective dans les 72 H.
Merci de votre co= op=E9ration.
En conformité a= vec la loi=20 78-17 du 6/1/78 (CNIL), vous pouvez demander à ne plus figurer sur= notre=20 fichier de routage.
A-O.hmn.4243
Artprice.co= m - Domaine=20 de la Source BP 69 - F-69270 St Romain au Mont D'or - RCS : 411 309 198
_______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 20 02:02:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03882 for ; Mon, 20 Oct 2003 02:02:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABT7G-0006OQ-A1 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 02:02:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9K626Jl024575 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 02:02:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABT7G-0006OI-2p for mip6-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 02:02:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03348 for ; Mon, 20 Oct 2003 02:01:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABT7C-0004L3-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 02:02:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABT7C-0004L0-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 02:02:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABT7A-0006N1-V2; Mon, 20 Oct 2003 02:02:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABT6z-0006M3-Ng for mip6@optimus.ietf.org; Mon, 20 Oct 2003 02:01:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03052 for ; Mon, 20 Oct 2003 02:01:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABT6w-0004Kp-00 for mip6@ietf.org; Mon, 20 Oct 2003 02:01:46 -0400 Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx with esmtp (Exim 4.12) id 1ABT6v-0004Kl-00 for mip6@ietf.org; Mon, 20 Oct 2003 02:01:45 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h9K61bUC011693 for ; Mon, 20 Oct 2003 15:01:37 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h9K61apo002325 for ; Mon, 20 Oct 2003 15:01:36 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id h9K61a8H010254 for ; Mon, 20 Oct 2003 15:01:36 +0900 (JST) Received: from imd.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id PAA03789 for ; Mon, 20 Oct 2003 15:01:35 +0900 (JST) Received: from [127.0.0.1] by imd.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id PAA21045 for ; Mon, 20 Oct 2003 15:01:35 +0900 (JST) Date: Mon, 20 Oct 2003 15:06:04 +0900 From: Hiroyuki OHNISHI To: mip6@ietf.org Message-Id: <20031020142759.A20C.OHNISHI.HIROYUKI@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.11 Content-Transfer-Encoding: 7bit Subject: [Mip6] mipv6 deleting a binding cache Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I want to cofirm the operation in section 9.5.3. It says, If the Binding Cache entry was created by use of return routability nonces, the correspondent node MUST ensure that the same nonces are not used again with the particular home and care-of address. In which situation does the correspondent node MUST ensure that the same nonces are not used again? case1: CN has already deleted the Binding Cache entry case2: CN has the Binding Cache entry and is going to delete I think the nonce check in 9.5.3 is applied to case 1. Is it right? Thanks in advance, -- Hiroyuki OHNISHI NTT Network Service Systems Laboratories Phone: +81-422-59-4132, Fax: +81-422-60-7460 mailto: ohnishi.hiroyuki@lab.ntt.co.jp _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 20 02:32:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14616 for ; Mon, 20 Oct 2003 02:32:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTaJ-0006XV-08 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 02:32:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9K6W6Ap025135 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 02:32:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTaI-0006XK-EY for mip6-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 02:32:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14613 for ; Mon, 20 Oct 2003 02:31:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABTaE-0004iN-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 02:32:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABTaE-0004iK-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 02:32:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTaD-0006UE-N3; Mon, 20 Oct 2003 02:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABTZm-0006PF-0t for mip6@optimus.ietf.org; Mon, 20 Oct 2003 02:31:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14610 for ; Mon, 20 Oct 2003 02:31:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABTZi-0004iG-00 for mip6@ietf.org; Mon, 20 Oct 2003 02:31:30 -0400 Received: from india-ironport-1.cisco.com ([64.104.129.195]) by ietf-mx with esmtp (Exim 4.12) id 1ABTZh-0004i0-00 for mip6@ietf.org; Mon, 20 Oct 2003 02:31:29 -0400 Received: from cisco.com (64.104.129.221) by india-ironport-1.cisco.com with ESMTP; 20 Oct 2003 12:08:00 +0530 Received: from samrat.cisco.com (samrat.cisco.com [192.135.241.21]) by india-msg-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9KBwcGX004620 for ; Mon, 20 Oct 2003 11:58:39 GMT Received: from pramaswaw2k01 ([10.77.6.222]) by samrat.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA20815 for ; Mon, 20 Oct 2003 12:00:54 +0530 (IST) Reply-To: From: "Prashant Ramaswamy" To: Date: Mon, 20 Oct 2003 12:00:52 +0530 Organization: Wipro Message-ID: <000001c396d3$b5e53870$de064d0a@apac.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [Mip6] Addition of SA after 1st return routability Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am doing a study of performance with secure signaling in Mobile IPv6. I had a query: Considering the scenario where the Mobile node moves from one link to another, how does the MN send updates to the CNs to whom it was earlier talking. Does it start the return routability test again (as per current draft). Further, suppose after getting the Binding Update, I also instruct the CN to add a security association to its database (in some way), then it will be quite easy to send further updates. The MN will also update its SPD with SA=Home Address, DA=CN, use this SA. What are the risks involved in this? I feel this will help in efficiency because the major delay currently is when the MN moves from one foreign network to another. Hope I am not missing anything trivial. Thanks Prashant _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 20 13:54:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05658 for ; Mon, 20 Oct 2003 13:54:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeER-0000ar-Lg for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 13:54:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KHsFTh002275 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 13:54:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeER-0000ac-GM for mip6-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 13:54:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05607 for ; Mon, 20 Oct 2003 13:54:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABeEP-0002pY-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 13:54:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABeEO-0002pV-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 13:54:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeEC-0000QS-Ix; Mon, 20 Oct 2003 13:54:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABeDG-0000Ey-5K for mip6@optimus.ietf.org; Mon, 20 Oct 2003 13:53:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05553; Mon, 20 Oct 2003 13:52:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABeDD-0002oW-00; Mon, 20 Oct 2003 13:52:59 -0400 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1ABeDD-0002oL-00; Mon, 20 Oct 2003 13:52:59 -0400 Received: from jurassic.eng.sun.com ([129.146.17.55]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9KHqSxA002284; Mon, 20 Oct 2003 10:52:28 -0700 (PDT) Received: from shubho (shubho.Eng.Sun.COM [129.146.85.207]) by jurassic.eng.sun.com (8.12.10+Sun/8.12.10) with SMTP id h9KHqRuT723936; Mon, 20 Oct 2003 10:52:27 -0700 (PDT) Message-Id: <200310201752.h9KHqRuT723936@jurassic.eng.sun.com> Date: Mon, 20 Oct 2003 10:53:43 -0700 (PDT) From: Samita Chakrabarti Reply-To: Samita Chakrabarti To: mip6@ietf.org, mipshop@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: xt57uLf75oll/gEIEZrVLA== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_31 SunOS 5.10 sun4u sparc Subject: [Mip6] Mobile IPv6 Interop Testing Draft Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , As per Basavaraj Patil's recommendation, a mip6-interop design team has been formed and the team has worked on producing the first draft on the Mobile IPv6 remote interop testing requirements, scenarios and procedures. The draft has been submitted as an individual draft for now, but it is targeting to be a working group draft in the next revision. It is available through T.J Kniveton's webpage until the draft becomes available at the IETF directory. http://www.mipv6.org/specs/draft-kniveton-mipv6-remote-testing-00.txt Thanks. The mip6-interop design team. T.J Kniveton, Basavaraj Patil, Hesham Soliman, Henrik Petander, Samita Chakrabarti _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 20 17:10:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05390 for ; Mon, 20 Oct 2003 17:10:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABhI0-0005hO-4Z for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 17:10:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KLA8UX021900 for mip6-archive@odin.ietf.org; Mon, 20 Oct 2003 17:10:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABhI0-0005h9-0d for mip6-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 17:10:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05384 for ; Mon, 20 Oct 2003 17:09:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABhHx-0000ev-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 17:10:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABhHx-0000er-00 for mip6-web-archive@ietf.org; Mon, 20 Oct 2003 17:10:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABhHu-0005dw-1Z; Mon, 20 Oct 2003 17:10:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABhHN-0005U2-NW for mip6@optimus.ietf.org; Mon, 20 Oct 2003 17:09:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05343 for ; Mon, 20 Oct 2003 17:09:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABhHK-0000e4-00 for mip6@ietf.org; Mon, 20 Oct 2003 17:09:26 -0400 Received: from [61.34.161.105] (helo=MailUser) by ietf-mx with smtp (Exim 4.12) id 1ABhHJ-0000e1-00 for mip6@ietf.org; Mon, 20 Oct 2003 17:09:25 -0400 Reply-To: ""<> From: ""<> To: "" X-Priority: 1 X-MSMail-Priority: High Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 21 Oct 2003 06:10:06 +0900 Message-Id: Subject: [Mip6] Mad Cruz (earn-easy) Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hi! Visit top list of sites which will help you to earn! http://earn-easy.x-web-x.com/ I already have earned on it 500 $ and I am going to continue! Excuse for the letter. Yours (Mad Cruz). _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 21 08:29:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15408 for ; Tue, 21 Oct 2003 08:29:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABvdS-0003UG-1D for mip6-archive@odin.ietf.org; Tue, 21 Oct 2003 08:29:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LCTD87013402 for mip6-archive@odin.ietf.org; Tue, 21 Oct 2003 08:29:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABvdN-0003Sq-9k for mip6-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 08:29:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15398 for ; Tue, 21 Oct 2003 08:28:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABvdL-0002ye-00 for mip6-web-archive@ietf.org; Tue, 21 Oct 2003 08:29:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ABvdL-0002yb-00 for mip6-web-archive@ietf.org; Tue, 21 Oct 2003 08:29:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABvdI-0003R8-9W; Tue, 21 Oct 2003 08:29:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ABvcN-0003Dj-QC for mip6@optimus.ietf.org; Tue, 21 Oct 2003 08:28:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15328 for ; Tue, 21 Oct 2003 08:27:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ABvcM-0002xO-00 for mip6@ietf.org; Tue, 21 Oct 2003 08:28:06 -0400 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1ABvcL-0002x9-00 for mip6@ietf.org; Tue, 21 Oct 2003 08:28:05 -0400 Received: from bebop.France.Sun.COM ([129.157.174.15]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9LCRGxA013258; Tue, 21 Oct 2003 05:27:17 -0700 (PDT) Received: from lillen (lillen [129.157.212.23]) by bebop.France.Sun.COM (8.11.7+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id h9LCRGS09329; Tue, 21 Oct 2003 14:27:16 +0200 (MEST) Date: Tue, 21 Oct 2003 14:21:10 +0200 (CEST) From: Erik Nordmark Reply-To: Erik Nordmark Subject: Re: [Mip6] Addition of SA after 1st return routability To: pramaswa@cisco.com Cc: mip6@ietf.org In-Reply-To: "Your message with ID" <000001c396d3$b5e53870$de064d0a@apac.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > Further, suppose after getting the Binding Update, I also instruct the > CN to add a security association to its database (in some way), then it > will be quite easy to send further updates. The MN will also update its > SPD with SA=Home Address, DA=CN, use this SA. What are the risks > involved in this? I feel this will help in efficiency because the major > delay currently is when the MN moves from one foreign network to > another. One security concern that was taken into account for the base MIPv6 security of BUs to the CN was 3rd party flooding attacks. If the MN lives on a bandwidth limited path (e.g., 56kbps) and the CN does not (1 Gbps), then the ability for the MN to say "please send my packets to this CoA" without the CN verifying that the MN is in fact present at that CoA would introduce DoS flooding capabilities of 1 Gbps for the MN which only has 56 kbps bandwidth. This is part of the reason for the CoTI/CoT exchange. Having a SA between the MN and CN doesn't remove this concern. It might make sense to consider the security implications of an "optimistic" mode where CoTI/CoT can happen in parallel with the BU taking place and if, after a few seconds, the CoT doesn't arrive the binding would be undone. Erik _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 21 23:46:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26125 for ; Tue, 21 Oct 2003 23:46:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC9wi-0003mH-HC for mip6-archive@odin.ietf.org; Tue, 21 Oct 2003 23:46:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M3k4Rb014515 for mip6-archive@odin.ietf.org; Tue, 21 Oct 2003 23:46:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC9wi-0003m2-D9 for mip6-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 23:46:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26122 for ; Tue, 21 Oct 2003 23:45:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AC9wg-0007Mz-00 for mip6-web-archive@ietf.org; Tue, 21 Oct 2003 23:46:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AC9wf-0007Mv-00 for mip6-web-archive@ietf.org; Tue, 21 Oct 2003 23:46:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC9wf-0003ka-Qw; Tue, 21 Oct 2003 23:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AC9wE-0003bd-Bf for mip6@optimus.ietf.org; Tue, 21 Oct 2003 23:45:34 -0400 Received: from MailUser ([61.48.28.112]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA26108 for ; Tue, 21 Oct 2003 23:45:21 -0400 (EDT) Message-Id: <200310220345.XAA26108@ietf.org> Reply-To: "Mike" From: "Mike" To: "" X-Priority: 1 X-MSMail-Priority: High Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 22 Oct 2003 11:44:41 +0800 Subject: [Mip6] earn Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hi! Visit top list of sites which will help you to earn! http://earn-easy.x-web-x.com/ I already have earned on it 500 $ and I am going to continue! Excuse for the letter. Yours (Mad Cruz). _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 04:59:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29652 for ; Wed, 22 Oct 2003 04:59:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEpf-0000sb-5U for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 04:59:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M8x7lj003375 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 04:59:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEpe-0000sM-UA for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 04:59:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29619 for ; Wed, 22 Oct 2003 04:58:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACEpb-0002K8-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 04:59:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACEpb-0002K4-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 04:59:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEpa-0000pp-BL; Wed, 22 Oct 2003 04:59:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACEop-0000hw-BV for mip6@optimus.ietf.org; Wed, 22 Oct 2003 04:58:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29590; Wed, 22 Oct 2003 04:58:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACEol-0002JX-00; Wed, 22 Oct 2003 04:58:11 -0400 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 1ACEok-0002JT-00; Wed, 22 Oct 2003 04:58:11 -0400 Received: from comnets.uni-bremen.de (sheepdog.comnets.uni-bremen.de [134.102.155.160]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id h9M8w8d11419; Wed, 22 Oct 2003 10:58:08 +0200 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host sheepdog.comnets.uni-bremen.de [134.102.155.160] claimed to be comnets.uni-bremen.de Message-ID: <3F96469D.2080109@comnets.uni-bremen.de> Date: Wed, 22 Oct 2003 10:58:05 +0200 From: "Niko A. Fikouras" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org, mobile-ip@sunroof.eng.sun.com Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Official launch of the MobileIP.org web site Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear all, we are happy to announce the official launch of the www.mobileip.org web site. It is a web site dedicated to the discussion and publication of open source software, papers, proposed standards and other news in the area of Internet mobility support. We are currently adding content to the web site, so any contributions are very welcome. Please take the time to have a look. Best Regards MobileIP.org team _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 18:13:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01054 for ; Wed, 22 Oct 2003 18:13:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRE1-0004qw-P0 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 18:13:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9MMD5bv018650 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 18:13:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRE1-0004qj-K9 for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 18:13:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00983 for ; Wed, 22 Oct 2003 18:12:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACRDy-0003J7-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 18:13:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACRDy-0003J4-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 18:13:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRDx-0004qE-H8; Wed, 22 Oct 2003 18:13:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACRDr-0004oy-8W for mip6@optimus.ietf.org; Wed, 22 Oct 2003 18:12:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00967 for ; Wed, 22 Oct 2003 18:12:42 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACRDo-0003J1-00 for mip6@ietf.org; Wed, 22 Oct 2003 18:12:52 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ACRDn-0003Ix-00 for mip6@ietf.org; Wed, 22 Oct 2003 18:12:51 -0400 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9MMCnI24832 for ; Thu, 23 Oct 2003 01:12:49 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Thu, 23 Oct 2003 01:11:24 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 22 Oct 2003 15:10:59 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Oct 2003 17:10:58 -0500 Message-ID: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for WG meeting at IETF58 Thread-Index: AcOY6V7LQzDAEeJMSL2S0lABNrr1Jg== To: X-OriginalArrivalTime: 22 Oct 2003 22:10:59.0894 (UTC) FILETIME=[5FD28560:01C398E9] Content-Transfer-Encoding: quoted-printable Subject: [Mip6] Draft Agenda for WG meeting at IETF58 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Comments solicited on: MIP6 (Mobility for IPv6 WG) Draft Agenda ---------------------------------------- MONDAY, November 10, 2003=20 1530-1730 Afternoon Sessions II CHAIRS: Basavaraj Patil Gopal Dommety Agenda: 1. Preliminaries 10 Mins Chairs - Minutes - Document status - Agenda bashing =09 2. MIPv6 MIB 15 Mins Glenn Keeni I-D: draft-ietf-mip6-mipv6-mib-00.txt 3. MIPv6 Remote interop testing 15 Mins T.J Kniveton/Samita C. I-D: draft-kniveton-mipv6-remote-testing-00.txt 4. Inter Home Agents Protocol (HAHA) 10 Mins Ryuji Wakikawa I-D: draft-wakikawa-mip6-nemo-haha-00.txt 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K. Kuladinithi=20 I-D: draft-nomadv6-mobileip-filters-00.txt 6. Roadmap for the WG 15 Mins Chairs and ADs _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 22:01:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13650 for ; Wed, 22 Oct 2003 22:01:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACUmf-0000ch-Po for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 22:01:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N215Wg002389 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 22:01:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACUmf-0000cS-KP for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 22:01:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13637 for ; Wed, 22 Oct 2003 22:00:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACUmc-0006tp-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 22:01:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACUmc-0006tm-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 22:01:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACUmc-0000bR-8x; Wed, 22 Oct 2003 22:01:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACUmN-0000a5-9I for mip6@optimus.ietf.org; Wed, 22 Oct 2003 22:00:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13632 for ; Wed, 22 Oct 2003 22:00:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACUmK-0006tj-00 for mip6@ietf.org; Wed, 22 Oct 2003 22:00:44 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1ACUmJ-0006tW-00 for mip6@ietf.org; Wed, 22 Oct 2003 22:00:43 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RDA5P>; Wed, 22 Oct 2003 22:04:31 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922E00@ftmail.lab.flarion.com> From: Soliman Hesham To: "'Basavaraj.Patil@nokia.com'" , mip6@ietf.org Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Wed, 22 Oct 2003 22:04:15 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hi Raj, One comment below. > 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K. > Kuladinithi > I-D: draft-nomadv6-mobileip-filters-00.txt > => What is the intention of discussing the above draft? I'm not against this, in fact I think that the WG should start working in the area of flow movement (called filters in this draft). But the impression I got was that this is not going to be part of the charter for now, right? So I'm wondering if this is an informational presentation or if there is a change about the direction of the WG. Hesham _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 22:54:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15433 for ; Wed, 22 Oct 2003 22:54:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACVbv-0002sP-Q8 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 22:54:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N2s3ri011056 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 22:54:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACVbv-0002sF-LS for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 22:54:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15427 for ; Wed, 22 Oct 2003 22:53:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACVbs-0007ZG-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 22:54:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACVbr-0007ZD-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 22:53:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACVbt-0002rT-Lj; Wed, 22 Oct 2003 22:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACVbr-0002pb-Fp for mip6@optimus.ietf.org; Wed, 22 Oct 2003 22:53:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15422 for ; Wed, 22 Oct 2003 22:53:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACVbn-0007Z9-00 for mip6@ietf.org; Wed, 22 Oct 2003 22:53:55 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1ACVbn-0007Yw-00 for mip6@ietf.org; Wed, 22 Oct 2003 22:53:55 -0400 Received: from galibier.nautilus6.org (unknown [203.178.138.3]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 554585D0A0 for ; Thu, 23 Oct 2003 11:53:23 +0900 (JST) Date: Thu, 23 Oct 2003 11:47:57 +0900 From: Thierry Ernst To: mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Message-Id: <20031023114757.37c7485f.ernst@sfc.wide.ad.jp> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> Organization: Keio University X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I do have a concern about the agenda. First thing first: I may have missed something during the MIP6 charter discussion: I don't see anything related to multihomed mobile node. (multihoming covers MNs with several interfaces, MNs with several HAs, and MNs with several HoAs/CoAs). Is this something to be excluded or included in this WG ? About the agenda, draft draft-montavont-mobileip-multihoming-pb-statement-00.txt (http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html) has been submitted in an effort to investigate issues in supporting multihomed mobile nodes under Mobile IPv6. Thus, I'm wondering if it won't be better to discuss the issues and the potential items that will have to be taken under consideration by the new MIP6 WG, rather than discussing specific solutions (I guess that 4 and 5 somewhat fall into the same discussions [Ryuji, please correct me about 4]). In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt attemps to state what the problem is so that we are all on the wave in order to be able to design a single WG solution that would address all the issues. Probably it would be useful to include this draft in the agenda. Comments ? Thierry > MIP6 (Mobility for IPv6 WG) Draft Agenda > ---------------------------------------- > > MONDAY, November 10, 2003 > 1530-1730 Afternoon Sessions II > > CHAIRS: Basavaraj Patil > Gopal Dommety > > Agenda: > > 1. Preliminaries 10 Mins Chairs > - Minutes > - Document status > - Agenda bashing > > > 2. MIPv6 MIB 15 Mins Glenn Keeni > I-D: draft-ietf-mip6-mipv6-mib-00.txt > > 3. MIPv6 Remote interop testing 15 Mins T.J Kniveton/Samita C. > I-D: draft-kniveton-mipv6-remote-testing-00.txt > > 4. Inter Home Agents Protocol (HAHA) 10 Mins Ryuji Wakikawa > I-D: draft-wakikawa-mip6-nemo-haha-00.txt > > 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K. Kuladinithi > I-D: draft-nomadv6-mobileip-filters-00.txt > > 6. Roadmap for the WG 15 Mins Chairs and ADs > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > -- Thierry Ernst, PhD WIDE at Keio University, Japan E-mail: ernst@sfc.wide.ad.jp Web: http://www.sfc.wide.ad.jp/~ernst/ -- Jun Murai Lab Keio University K-square Town Campus 1488-8 Ogura, Saiwai-ku, Kawasaki Kanagawa, 212-0054 Japan Phone : +81-44-580-1600 Fax : +81-44-580-1437 Mobile: 090-9815-8023 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 23:19:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16114 for ; Wed, 22 Oct 2003 23:19:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW08-0007bP-Fa for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 23:19:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N3J4lc029222 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 23:19:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW08-0007bF-11 for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 23:19:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16110 for ; Wed, 22 Oct 2003 23:18:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACW05-0007ma-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 23:19:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACW05-0007mX-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 23:19:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW05-0007ag-CA; Wed, 22 Oct 2003 23:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACVzV-0007T8-3U for mip6@optimus.ietf.org; Wed, 22 Oct 2003 23:18:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16101 for ; Wed, 22 Oct 2003 23:18:14 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACVzS-0007mU-00 for mip6@ietf.org; Wed, 22 Oct 2003 23:18:22 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ACVzS-0007mR-00 for mip6@ietf.org; Wed, 22 Oct 2003 23:18:22 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9N3ILI23345 for ; Thu, 23 Oct 2003 06:18:21 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Thu, 23 Oct 2003 06:17:59 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 22 Oct 2003 22:18:00 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Wed, 22 Oct 2003 22:17:59 -0500 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB93C@daebe007.americas.nokia.com> Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOZCW/hTAUl2ookSLye3a55pwiMFAACmhAw To: , X-OriginalArrivalTime: 23 Oct 2003 03:18:00.0059 (UTC) FILETIME=[4318A4B0:01C39914] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable >=20 > Hi Raj,=20 >=20 > One comment below. >=20 > > 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K.=20 > > Kuladinithi=20 > > I-D: draft-nomadv6-mobileip-filters-00.txt > >=20 >=20 > =3D> What is the intention of discussing the above draft? > I'm not against this, in fact I think that the WG should=20 > start working in the area of flow movement (called filters > in this draft). But the impression I got was that this=20 > is not going to be part of the charter for now, right? > So I'm wondering if this is an informational presentation > or if there is a change about the direction of the WG.=20 Good question. Note that the current agenda is only draft. This agenda item will be dropped as you currently note that the charter scope does not cover this.=20 I added this to the agenda as a result of a request from the authors. However I have indicated to the authors that the criteria for allocating time at a WG meeting is: 1. The work is within the scope of the charter=20 2. There is a significant interest (as seen on ML) and hence worth discussing >=20 >=20 > Hesham >=20 -Basavaraj _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 22 23:24:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16361 for ; Wed, 22 Oct 2003 23:24:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW4v-0000Sc-FK for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 23:24:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N3O11o001763 for mip6-archive@odin.ietf.org; Wed, 22 Oct 2003 23:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW4v-0000SM-AT for mip6-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 23:24:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16349 for ; Wed, 22 Oct 2003 23:23:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACW4t-00002l-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 23:23:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACW4s-00002i-00 for mip6-web-archive@ietf.org; Wed, 22 Oct 2003 23:23:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW4u-0000QN-Ao; Wed, 22 Oct 2003 23:24:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACW49-0000Hq-3A for mip6@optimus.ietf.org; Wed, 22 Oct 2003 23:23:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16337 for ; Wed, 22 Oct 2003 23:23:02 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACW47-00002R-00 for mip6@ietf.org; Wed, 22 Oct 2003 23:23:11 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ACW46-00002N-00 for mip6@ietf.org; Wed, 22 Oct 2003 23:23:10 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9N3NAI26920 for ; Thu, 23 Oct 2003 06:23:10 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Thu, 23 Oct 2003 06:23:08 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Wed, 22 Oct 2003 20:23:08 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Wed, 22 Oct 2003 22:23:08 -0500 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB93D@daebe007.americas.nokia.com> Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOZEPgXZEWl7YdyTgS2zQR0nmQ37AAA1/QQ To: , X-OriginalArrivalTime: 23 Oct 2003 03:23:08.0905 (UTC) FILETIME=[FB2ECD90:01C39914] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable >=20 > Hi, >=20 > I do have a concern about the agenda.=20 Glad to see that we are having the agenda bashing on the ML now rather than at the WG meeting ;) >=20 > First thing first: I may have missed something during the MIP6 charter > discussion: I don't see anything related to multihomed mobile node. > (multihoming covers MNs with several interfaces, MNs with several HAs, > and MNs with several HoAs/CoAs). Is this something to be excluded or > included in this WG ? This is not within the scope of the current charter. I (chair hat off) do not believe there is any urgency to deal with this problem. Hence can be considered in a future revision of the charter if deemed = necessary. >=20 > About the agenda, draft > draft-montavont-mobileip-multihoming-pb-statement-00.txt > (http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html) > has been submitted in an effort to investigate issues in supporting > multihomed mobile nodes under Mobile IPv6. >=20 > Thus, I'm wondering if it won't be better to discuss the=20 > issues and the > potential items that will have to be taken under consideration by the > new MIP6 WG, rather than discussing specific solutions (I guess that 4 > and 5 somewhat fall into the same discussions [Ryuji, please=20 > correct me about 4]).=20 >=20 > In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt > attemps to state what the problem is so that we are all on the wave in > order to be able to design a single WG solution that would address all > the issues. Probably it would be useful to include this draft in the > agenda. I agree that it is a good idea to discuss the problem statement. But = given the current scope of the charter and the priorities of the WG, I would = rather have that this discussion be carried out on the Mailing list first. I = would like to see the opinions of the WG members w.r.t this problem. >=20 >=20 > Comments ? > Thierry -Basavaraj >=20 >=20 >=20 >=20 > > MIP6 (Mobility for IPv6 WG) Draft Agenda > > ---------------------------------------- > >=20 > > MONDAY, November 10, 2003=20 > > 1530-1730 Afternoon Sessions II > >=20 > > CHAIRS: Basavaraj Patil > > Gopal Dommety > >=20 > > Agenda: > >=20 > > 1. Preliminaries 10 Mins Chairs > > - Minutes > > - Document status > > - Agenda bashing > > =09 > >=20 > > 2. MIPv6 MIB 15 Mins Glenn Keeni > > I-D: draft-ietf-mip6-mipv6-mib-00.txt > >=20 > > 3. MIPv6 Remote interop testing 15 Mins T.J=20 > Kniveton/Samita C. > > I-D: draft-kniveton-mipv6-remote-testing-00.txt > >=20 > > 4. Inter Home Agents Protocol (HAHA) 10 Mins Ryuji Wakikawa > > I-D: draft-wakikawa-mip6-nemo-haha-00.txt > >=20 > > 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K.=20 > Kuladinithi=20 > > I-D: draft-nomadv6-mobileip-filters-00.txt > >=20 > > 6. Roadmap for the WG 15 Mins Chairs and ADs > >=20 > >=20 > > _______________________________________________ > > Mip6 mailing list > > Mip6@ietf.org > > https://www.ietf.org/mailman/listinfo/mip6 > >=20 >=20 >=20 > --=20 >=20 > Thierry Ernst, PhD > WIDE at Keio University, Japan > E-mail: ernst@sfc.wide.ad.jp > Web: http://www.sfc.wide.ad.jp/~ernst/ > -- > Jun Murai Lab > Keio University K-square Town Campus > 1488-8 Ogura, Saiwai-ku, Kawasaki > Kanagawa, 212-0054 Japan > Phone : +81-44-580-1600 > Fax : +81-44-580-1437 > Mobile: 090-9815-8023 >=20 > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 >=20 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 03:15:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05944 for ; Thu, 23 Oct 2003 03:15:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACZga-00081F-BR for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:15:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N7F8K7030824 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:15:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACZga-000815-7Z for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 03:15:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05892 for ; Thu, 23 Oct 2003 03:14:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACZgX-0002fX-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:15:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACZgX-0002fT-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:15:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACZgX-0007zN-IF; Thu, 23 Oct 2003 03:15:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACZgM-0007xm-0X for mip6@optimus.ietf.org; Thu, 23 Oct 2003 03:14:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05887 for ; Thu, 23 Oct 2003 03:14:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACZgJ-0002fN-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:14:51 -0400 Received: from omgo.iij.ad.jp ([202.232.30.157]) by ietf-mx with esmtp (Exim 4.12) id 1ACZgI-0002fA-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:14:50 -0400 Received: from jc-smtp.iij.ad.jp ([192.168.176.35]) by omgo.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9N7ElvG011798 for ; Thu, 23 Oct 2003 16:14:47 +0900 (JST) Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.65.65]) by jc-smtp.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9N7EK7R026542 for ; Thu, 23 Oct 2003 16:14:20 +0900 (JST) Date: Thu, 23 Oct 2003 16:13:41 +0900 (JST) Message-Id: <20031023.161341.38807935.keiichi@iij.ad.jp> To: mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 From: Keiichi SHIMA / =?iso-2022-jp?B?GyRCRWc3RDBsGyhC?= In-Reply-To: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> X-Mailer: Mew version 4.0.59 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I wonder if we can have a time to discuss mechanisms for RO procedure initiation judgement. The basic draft mentions that a mobile/correpondent node should be administratively enabled/disabled to allow RO. However, I think we need more flexible mechanism for managed networks. Please take a look into http://www.ietf.org/internet-drafts/draft-shima-mip6-rohints-00.txt, which describes one such proposal. Regards, --- Keiichi SHIMA IIJ Research Laboratory KAME Project From: Basavaraj.Patil@nokia.com Subject: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Wed, 22 Oct 2003 17:10:58 -0500 > > Comments solicited on: > > MIP6 (Mobility for IPv6 WG) Draft Agenda > ---------------------------------------- > > MONDAY, November 10, 2003 > 1530-1730 Afternoon Sessions II > > CHAIRS: Basavaraj Patil > Gopal Dommety > > Agenda: > > 1. Preliminaries 10 Mins Chairs > - Minutes > - Document status > - Agenda bashing > > > 2. MIPv6 MIB 15 Mins Glenn Keeni > I-D: draft-ietf-mip6-mipv6-mib-00.txt > > 3. MIPv6 Remote interop testing 15 Mins T.J Kniveton/Samita C. > I-D: draft-kniveton-mipv6-remote-testing-00.txt > > 4. Inter Home Agents Protocol (HAHA) 10 Mins Ryuji Wakikawa > I-D: draft-wakikawa-mip6-nemo-haha-00.txt > > 5. Filters for Mobile IPv6 Bindings (NOMADv6) 10 Mins K. Kuladinithi > I-D: draft-nomadv6-mobileip-filters-00.txt > > 6. Roadmap for the WG 15 Mins Chairs and ADs > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 03:38:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06813 for ; Thu, 23 Oct 2003 03:38:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACa2m-00078T-Pe for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:38:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N7c3kE027403 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:38:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACa2l-000779-5B for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 03:38:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06792 for ; Thu, 23 Oct 2003 03:37:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACa2i-0002zp-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:38:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACa2i-0002zm-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:38:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACa2j-00075y-Q3; Thu, 23 Oct 2003 03:38:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACa1q-0006kK-OH for mip6@optimus.ietf.org; Thu, 23 Oct 2003 03:37:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06753 for ; Thu, 23 Oct 2003 03:36:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACa1n-0002zC-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:37:03 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1ACa1n-0002yx-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:37:03 -0400 Received: from galibier.nautilus6.org (unknown [203.178.138.3]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id BB4625D01E; Thu, 23 Oct 2003 16:36:33 +0900 (JST) Date: Thu, 23 Oct 2003 16:31:07 +0900 From: Thierry Ernst To: mip6@ietf.org Cc: Basavaraj.Patil@nokia.com Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Message-Id: <20031023163107.58cbc631.ernst@sfc.wide.ad.jp> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB93D@daebe007.americas.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44024DB93D@daebe007.americas.nokia.com> Organization: Keio University X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj, Thanks to your answer. Comments to your answer, and request below: > > First thing first: I may have missed something during the MIP6 charter > > discussion: I don't see anything related to multihomed mobile node. > > (multihoming covers MNs with several interfaces, MNs with several HAs, > > and MNs with several HoAs/CoAs). Is this something to be excluded or > > included in this WG ? > > This is not within the scope of the current charter. I (chair hat off) > do not believe there is any urgency to deal with this problem. Hence > can be considered in a future revision of the charter if deemed necessary. Well, I cannot really agree. In the first place, why did you list the Nomad draft if it's not within the scope ? In the second place, there are a few drafts turning around this issues, and drafts have been submitted regularly for a few years. So, given the number of drafts and period of effect, I find it rather important. On a personal side, I would like to see something coming up from this activity so that we can implement a common solution, no doing our own cooking in our lab. Anyway, let's see why the other people are thinking. If it happens that there is no room in this WG to deal with issue, I will most likely propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, because the benefit of having several interfaces [either actual, or virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not exclusively thinking about NEMO, although the idea comes from there]). The reason I have not yet pushed toward a new WG is because there are already many WGs. In conclusion, may I request a short slot to deal the issue (not the solutions) during the meeting, please, so that we come to a WG consensus and act upon it ? Thierry. > > > > About the agenda, draft > > draft-montavont-mobileip-multihoming-pb-statement-00.txt > > (http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html) > > has been submitted in an effort to investigate issues in supporting > > multihomed mobile nodes under Mobile IPv6. > > > > Thus, I'm wondering if it won't be better to discuss the > > issues and the > > potential items that will have to be taken under consideration by the > > new MIP6 WG, rather than discussing specific solutions (I guess that 4 > > and 5 somewhat fall into the same discussions [Ryuji, please > > correct me about 4]). > > > > In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt > > attemps to state what the problem is so that we are all on the wave in > > order to be able to design a single WG solution that would address all > > the issues. Probably it would be useful to include this draft in the > > agenda. > > I agree that it is a good idea to discuss the problem statement. But given > the current scope of the charter and the priorities of the WG, I would rather > have that this discussion be carried out on the Mailing list first. I would > like to see the opinions of the WG members w.r.t this problem. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 03:58:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07537 for ; Thu, 23 Oct 2003 03:58:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACaM6-0004Bq-Sv for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:58:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N7w239016102 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 03:58:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACaM6-0004Bd-OA for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 03:58:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07504 for ; Thu, 23 Oct 2003 03:57:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACaM4-0003GB-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:58:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACaM3-0003G8-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 03:57:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACaM5-0004B3-Pr; Thu, 23 Oct 2003 03:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACaLo-000482-BI for mip6@optimus.ietf.org; Thu, 23 Oct 2003 03:57:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07499 for ; Thu, 23 Oct 2003 03:57:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACaLl-0003G5-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:57:41 -0400 Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 1ACaLk-0003Fs-00 for mip6@ietf.org; Thu, 23 Oct 2003 03:57:41 -0400 Received: (qmail 16269 invoked for bounce); 23 Oct 2003 07:57:48 -0000 Received: from unknown (HELO clarinet.u-strasbg.fr) (montavont@unknown) by unknown with RC4-MD5 encrypted SMTP; 23 Oct 2003 07:57:48 -0000 Message-ID: <3F9789E4.2070904@clarinet.u-strasbg.fr> Date: Thu, 23 Oct 2003 09:57:24 +0200 From: montavont User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030727 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thierry Ernst CC: mip6@ietf.org, Basavaraj.Patil@nokia.com Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB93D@daebe007.americas.nokia.com> <20031023163107.58cbc631.ernst@sfc.wide.ad.jp> In-Reply-To: <20031023163107.58cbc631.ernst@sfc.wide.ad.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj, Thierry, I don't understand neither why you give a slot to nomadv6, while other solutions which are very close where also submitted as I-D. Anyway, I think that before considering any solutions, it is important to first see what are the issues of a multihomed host / MN. The draft "draft-montavont-mobileip-multihoming-pb-statement-00.txt" could initiate discussion around multihoming and make people work together on a unique solution if needed. Nicolas Thierry Ernst wrote: >Hi Basavaraj, > >Thanks to your answer. Comments to your answer, and request below: > > > > >>>First thing first: I may have missed something during the MIP6 charter >>>discussion: I don't see anything related to multihomed mobile node. >>>(multihoming covers MNs with several interfaces, MNs with several HAs, >>>and MNs with several HoAs/CoAs). Is this something to be excluded or >>>included in this WG ? >>> >>> >>This is not within the scope of the current charter. I (chair hat off) >>do not believe there is any urgency to deal with this problem. Hence >>can be considered in a future revision of the charter if deemed necessary. >> >> > >Well, I cannot really agree. > >In the first place, why did you list the Nomad draft if it's not within >the scope ? > >In the second place, there are a few drafts turning around this issues, >and drafts have been submitted regularly for a few years. So, given the >number of drafts and period of effect, I find it rather important. On a >personal side, I would like to see something coming up from this >activity so that we can implement a common solution, no doing our own >cooking in our lab. > >Anyway, let's see why the other people are thinking. If it happens that >there is no room in this WG to deal with issue, I will most likely >propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >because the benefit of having several interfaces [either actual, or >virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >exclusively thinking about NEMO, although the idea comes from there]). >The reason I have not yet pushed toward a new WG is because there are >already many WGs. > >In conclusion, may I request a short slot to deal the issue (not the >solutions) during the meeting, please, so that we come to a WG consensus >and act upon it ? > >Thierry. > > > > >>>About the agenda, draft >>>draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>(http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html) >>>has been submitted in an effort to investigate issues in supporting >>>multihomed mobile nodes under Mobile IPv6. >>> >>>Thus, I'm wondering if it won't be better to discuss the >>>issues and the >>>potential items that will have to be taken under consideration by the >>>new MIP6 WG, rather than discussing specific solutions (I guess that 4 >>>and 5 somewhat fall into the same discussions [Ryuji, please >>>correct me about 4]). >>> >>>In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>attemps to state what the problem is so that we are all on the wave in >>>order to be able to design a single WG solution that would address all >>>the issues. Probably it would be useful to include this draft in the >>>agenda. >>> >>> >>I agree that it is a good idea to discuss the problem statement. But given >>the current scope of the charter and the priorities of the WG, I would rather >>have that this discussion be carried out on the Mailing list first. I would >>like to see the opinions of the WG members w.r.t this problem. >> >> > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 04:53:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08927 for ; Thu, 23 Oct 2003 04:53:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACbDM-0000fk-0I for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 04:53:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9N8r3l8002556 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 04:53:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACbDL-0000f4-3r for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 04:53:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08917 for ; Thu, 23 Oct 2003 04:52:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACbDH-0003p2-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 04:52:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACbDH-0003oz-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 04:52:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACbDJ-0000e6-L9; Thu, 23 Oct 2003 04:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACbCa-0000QA-5q for mip6@optimus.ietf.org; Thu, 23 Oct 2003 04:52:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08911 for ; Thu, 23 Oct 2003 04:52:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACbCX-0003ow-00 for mip6@ietf.org; Thu, 23 Oct 2003 04:52:13 -0400 Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47]) by ietf-mx with esmtp (Exim 4.12) id 1ACbCW-0003ot-00 for mip6@ietf.org; Thu, 23 Oct 2003 04:52:12 -0400 Received: from esealnt611.al.sw.ericsson.se ([153.88.254.121]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9N8qCSs005946; Thu, 23 Oct 2003 10:52:12 +0200 (MEST) Received: from ericsson.com (research-86xokp.ki.sw.ericsson.se [147.214.181.220]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id 43DWNZAM; Thu, 23 Oct 2003 10:52:58 +0200 Message-ID: <3F9796B6.3020101@ericsson.com> Date: Thu, 23 Oct 2003 10:52:06 +0200 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Conny Larsson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Thierry Ernst CC: mip6@ietf.org, Basavaraj.Patil@nokia.com Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB93D@daebe007.americas.nokia.com> <20031023163107.58cbc631.ernst@sfc.wide.ad.jp> In-Reply-To: <20031023163107.58cbc631.ernst@sfc.wide.ad.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thierry, I agree with you. I believe the multihoming scenarios, as discussed in draft-montavont-mobileip-multihoming-pb-statement-00.txt, are of interest. I also believe that we have to look into how a mobile node may redirect flows from one interface to another, as mentioned in Chapter 5. It seems to me that the multihoming problem could be covered by the mip6 wg (i.e. if the charter is changed). I would like it to cover flow mobility as well since this will be interesting when you are multihomed. However, one could also argue that flows are something above the IP layer and should be handled somewhere else and I believe this is the current position of the wg. Regards Conny Larsson Thierry Ernst wrote: >Hi Basavaraj, > >Thanks to your answer. Comments to your answer, and request below: > > > > >>>First thing first: I may have missed something during the MIP6 charter >>>discussion: I don't see anything related to multihomed mobile node. >>>(multihoming covers MNs with several interfaces, MNs with several HAs, >>>and MNs with several HoAs/CoAs). Is this something to be excluded or >>>included in this WG ? >>> >>> >>This is not within the scope of the current charter. I (chair hat off) >>do not believe there is any urgency to deal with this problem. Hence >>can be considered in a future revision of the charter if deemed necessary. >> >> > >Well, I cannot really agree. > >In the first place, why did you list the Nomad draft if it's not within >the scope ? > >In the second place, there are a few drafts turning around this issues, >and drafts have been submitted regularly for a few years. So, given the >number of drafts and period of effect, I find it rather important. On a >personal side, I would like to see something coming up from this >activity so that we can implement a common solution, no doing our own >cooking in our lab. > >Anyway, let's see why the other people are thinking. If it happens that >there is no room in this WG to deal with issue, I will most likely >propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >because the benefit of having several interfaces [either actual, or >virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >exclusively thinking about NEMO, although the idea comes from there]). >The reason I have not yet pushed toward a new WG is because there are >already many WGs. > >In conclusion, may I request a short slot to deal the issue (not the >solutions) during the meeting, please, so that we come to a WG consensus >and act upon it ? > >Thierry. > > > > >>>About the agenda, draft >>>draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>(http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html) >>>has been submitted in an effort to investigate issues in supporting >>>multihomed mobile nodes under Mobile IPv6. >>> >>>Thus, I'm wondering if it won't be better to discuss the >>>issues and the >>>potential items that will have to be taken under consideration by the >>>new MIP6 WG, rather than discussing specific solutions (I guess that 4 >>>and 5 somewhat fall into the same discussions [Ryuji, please >>>correct me about 4]). >>> >>>In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>attemps to state what the problem is so that we are all on the wave in >>>order to be able to design a single WG solution that would address all >>>the issues. Probably it would be useful to include this draft in the >>>agenda. >>> >>> >>I agree that it is a good idea to discuss the problem statement. But given >>the current scope of the charter and the priorities of the WG, I would rather >>have that this discussion be carried out on the Mailing list first. I would >>like to see the opinions of the WG members w.r.t this problem. >> >> > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 06:07:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11240 for ; Thu, 23 Oct 2003 06:07:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACcMy-0002HW-6J for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 06:07:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NA73qY008762 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 06:07:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACcMx-0002Gr-8D for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 06:07:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11198 for ; Thu, 23 Oct 2003 06:06:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACcMt-0004hB-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 06:06:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACcMs-0004h7-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 06:06:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACcMv-0002FY-FE; Thu, 23 Oct 2003 06:07:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACcMS-0002Ba-64 for mip6@optimus.ietf.org; Thu, 23 Oct 2003 06:06:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11170; Thu, 23 Oct 2003 06:06:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACcMN-0004gW-00; Thu, 23 Oct 2003 06:06:27 -0400 Received: from teldanex.hiit.fi ([212.68.5.99] helo=n97.nomadiclab.com) by ietf-mx with esmtp (Exim 4.12) id 1ACcMN-0004fv-00; Thu, 23 Oct 2003 06:06:27 -0400 Received: from nomadiclab.com (teldanex.local.nikander.com [192.168.0.194]) by n97.nomadiclab.com (Postfix) with ESMTP id 14E6C1C; Thu, 23 Oct 2003 13:19:11 +0300 (EEST) Message-ID: <3F97A807.9060706@nomadiclab.com> Date: Thu, 23 Oct 2003 13:05:59 +0300 From: Pekka Nikander Reply-To: hipsec@honor.trusecure.com User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mobile IPv6 WG , Mobile IPv4 WG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Host Identity Protocol Architecture and BOF Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Folks, The Host Identity Protocol, first discussed after the the MALLOC meeting at 43th IETF in Orlando and again at BOFs during the 50th IETF in Minneapolis and 51st in London, is surfacing again. The HIP work has proceeded at the side of the IETF, without any formal organization, to a level where the HIP Architecture document is ready to be published as an Informational RFC. The actual protocol specification is also quite mature, and there there are at least six implementations, four of which have been tested for interoperability. To complete the remaining work on infrastructure so that it would be possible to experiment with HIP on a wide scale, we have requested a BOF for the next IETF in Minneapolis. While the BOF is still pending formal approval from the ADs, it does appear at the preliminary agenda. The architecture specification, draft-moskowitz-hip-arch-05.txt, is on its way to the archives. The plan is to submit it directly to the RFC Editor on Monday, October 27th, following the procedure of RFC2026 Section 4.2.3. It would be very valuable if people would read the draft either before Oct27th or soon afterwards, allowing possible comments to be considered before publishing the document. The comments should be sent either directly to the authors or to the hipsec mailing list. Since it may take some time before the draft appears in the repository, it is currently also available at the following URLs: http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.txt http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.html http://www.tml.hut.fi/~pnr/HIP/draft-moskowitz-hip-arch-05.xml The corresponding protocol specification, draft-moskowitz-hip-08.txt, will be heading to the repository later today. It will also be available at URLs similar to the ones above. An announcement will be sent to the hipsec mailing list. The BOF is currently scheduled for Thursday, Nov 13, at 1300-1500, but as the agenda is still much in flux, it may be moved. The BOF description is available at http://www.ietf.org/ietf/03nov/hipbof.txt At this stage I want to thank the large number of people that have contributed to HIP during these years, allowing it to proceed this far. You know who you are. Without your work it would not have been possible to get even here. HIP has been a community effort, and will continue as such. This announcement was sent to the Multi6, Mobile IPv4, Mobile IPv6, and IPsec WGs, in addition to the IETF Discuss mailing lists. The reason for this is that HIP, if adopted, may have effects on IPsec based security, IP layer mobility, and multi-address multi-homing. The HIP architecture and protocol should be discussed at the hipsec mailing list; see the BOF description for details on how to subscribe. --Pekka Nikander _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 10:01:48 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21976 for ; Thu, 23 Oct 2003 10:01:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACg1o-0007BF-KH for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 10:01:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NE1SxY027600 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 10:01:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACg1o-0007B5-HE for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 10:01:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21923 for ; Thu, 23 Oct 2003 10:01:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACg1m-0000R8-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 10:01:26 -0400 Received: from sausage.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1ACg1m-0000R2-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 10:01:26 -0400 Received: from [132.151.6.22] (helo=optimus.ietf.org) by manatick with esmtp (Exim 4.24) id 1ACfdG-0008DG-Ly for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 09:36:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACfdA-0002hY-JJ; Thu, 23 Oct 2003 09:36:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACfd2-0002gB-UD for mip6@optimus.ietf.org; Thu, 23 Oct 2003 09:35:52 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19236; Thu, 23 Oct 2003 09:35:41 -0400 (EDT) Message-Id: <200310231335.JAA19236@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip6@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 23 Oct 2003 09:35:41 -0400 Subject: [Mip6] I-D ACTION:draft-ietf-mip6-mipv6-mib-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IPv6 Working Group of the IETF. Title : The Mobile IPv6 MIB Author(s) : G. Keeni, K. Nagami, K. Koide, S. Gundavelli Filename : draft-ietf-mip6-mipv6-mib-00.txt Pages : 53 Date : 2003-10-23 This memo defines a portion of the Management Information Base (MIB), the the Mobile-IPv6 MIB, for use with network management protocols in the Internet community. In particular, Mobile-IPv6 MIB will be used to monitor and control Mobile Node, Home Agent and Correspondent Node functions of an MIPv6 entity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-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-mip6-mipv6-mib-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-mip6-mipv6-mib-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: <2003-10-23095734.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip6-mipv6-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip6-mipv6-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-23095734.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 10:45:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26762 for ; Thu, 23 Oct 2003 10:45:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACgi2-0006Dd-EZ for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 10:45:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NEj6sE023901 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 10:45:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACgi2-0006DQ-99 for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 10:45:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26729 for ; Thu, 23 Oct 2003 10:44:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACghw-0001Z1-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 10:45:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACghw-0001Yy-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 10:45:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACghy-0006C4-28; Thu, 23 Oct 2003 10:45:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACghc-00068l-VK for mip6@optimus.ietf.org; Thu, 23 Oct 2003 10:44:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26696 for ; Thu, 23 Oct 2003 10:44:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACgha-0001YI-00 for mip6@ietf.org; Thu, 23 Oct 2003 10:44:38 -0400 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx with esmtp (Exim 4.12) id 1ACghZ-0001Vk-00 for mip6@ietf.org; Thu, 23 Oct 2003 10:44:37 -0400 Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 23 Oct 2003 16:43:46 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE : [Mip6] Draft Agenda for WG meeting at IETF58 Date: Thu, 23 Oct 2003 16:43:45 +0200 Message-ID: Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOZQxeOyPaHgTnaTr+zY+v+p7tn+AAK8C2g From: "KASSI-LAHLOU Mohammed FTRD/DMI/CAE" To: "Conny Larsson" , "Thierry Ernst" Cc: , X-OriginalArrivalTime: 23 Oct 2003 14:43:46.0285 (UTC) FILETIME=[102879D0:01C39974] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, I agree too. The multihoming (multi-interfaces, multi-HAs...) are = important topics. Situations with access networks and hosts of various = technologies or with different suppliers will increase. Therefore, the = behavior of mobileIP in these cases has to be specified. Kassi -----Message d'origine----- De : Conny Larsson [mailto:conny.larsson@ericsson.com]=20 Envoy=E9 : jeudi 23 octobre 2003 10:52 =C0 : Thierry Ernst Cc : mip6@ietf.org; Basavaraj.Patil@nokia.com Objet : Re: [Mip6] Draft Agenda for WG meeting at IETF58 Thierry, I agree with you. I believe the multihoming scenarios, as discussed in=20 draft-montavont-mobileip-multihoming-pb-statement-00.txt, are of=20 interest. I also believe that we have to look into how a mobile node may = redirect flows from one interface to another, as mentioned in Chapter 5. It seems to me that the multihoming problem could be covered by the mip6 = wg (i.e. if the charter is changed). I would like it to cover flow=20 mobility as well since this will be interesting when you are multihomed. = However, one could also argue that flows are something above the IP=20 layer and should be handled somewhere else and I believe this is the=20 current position of the wg. Regards Conny Larsson Thierry Ernst wrote: >Hi Basavaraj, > >Thanks to your answer. Comments to your answer, and request below: > > > =20 > >>>First thing first: I may have missed something during the MIP6=20 >>>charter >>>discussion: I don't see anything related to multihomed mobile node. >>>(multihoming covers MNs with several interfaces, MNs with several = HAs, >>>and MNs with several HoAs/CoAs). Is this something to be excluded or >>>included in this WG ? >>> =20 >>> >>This is not within the scope of the current charter. I (chair hat off) = >>do not believe there is any urgency to deal with this problem. Hence=20 >>can be considered in a future revision of the charter if deemed=20 >>necessary. >> =20 >> > >Well, I cannot really agree. > >In the first place, why did you list the Nomad draft if it's not within = >the scope ? > >In the second place, there are a few drafts turning around this issues, = >and drafts have been submitted regularly for a few years. So, given the = >number of drafts and period of effect, I find it rather important. On a = >personal side, I would like to see something coming up from this=20 >activity so that we can implement a common solution, no doing our own=20 >cooking in our lab. > >Anyway, let's see why the other people are thinking. If it happens that = >there is no room in this WG to deal with issue, I will most likely=20 >propose a BOF at Seoul Meeting (and, well, this might not be a bad=20 >idea, because the benefit of having several interfaces [either actual,=20 >or virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm=20 >not exclusively thinking about NEMO, although the idea comes from=20 >there]). The reason I have not yet pushed toward a new WG is because=20 >there are already many WGs. > >In conclusion, may I request a short slot to deal the issue (not the >solutions) during the meeting, please, so that we come to a WG=20 >consensus and act upon it ? > >Thierry. > > > =20 > >>>About the agenda, draft=20 >>>draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>(http://www.ietf.org/mail-archive/ietf-announce/Current/msg26474.html >>>) >>>has been submitted in an effort to investigate issues in supporting >>>multihomed mobile nodes under Mobile IPv6. >>> >>>Thus, I'm wondering if it won't be better to discuss the >>>issues and the >>>potential items that will have to be taken under consideration by the >>>new MIP6 WG, rather than discussing specific solutions (I guess that = 4 >>>and 5 somewhat fall into the same discussions [Ryuji, please=20 >>>correct me about 4]).=20 >>> >>>In any case, draft-montavont-mobileip-multihoming-pb-statement-00.txt >>>attemps to state what the problem is so that we are all on the wave=20 >>>in order to be able to design a single WG solution that would address = >>>all the issues. Probably it would be useful to include this draft in=20 >>>the agenda. >>> =20 >>> >>I agree that it is a good idea to discuss the problem statement. But=20 >>given the current scope of the charter and the priorities of the WG, I = >>would rather have that this discussion be carried out on the Mailing=20 >>list first. I would like to see the opinions of the WG members w.r.t=20 >>this problem. >> =20 >> > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > =20 > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 11:36:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29821 for ; Thu, 23 Oct 2003 11:36:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChVL-0000MZ-QI for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 11:36:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NFa3NL001394 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 11:36:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChVL-0000MP-Ms for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 11:36:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29790 for ; Thu, 23 Oct 2003 11:35:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AChVK-0002Z2-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 11:36:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AChVK-0002Yz-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 11:36:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChVK-0000Kp-C8; Thu, 23 Oct 2003 11:36:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AChUO-00006y-PN for mip6@optimus.ietf.org; Thu, 23 Oct 2003 11:35:04 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29702; Thu, 23 Oct 2003 11:34:50 -0400 (EDT) Message-Id: <200310231534.LAA29702@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip6@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 23 Oct 2003 11:34:50 -0400 Subject: [Mip6] I-D ACTION:draft-wakikawa-mip6-nemo-haha-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Inter Home Agents Protocol (HAHA) Author(s) : R. Wakikawa, V. Devarapalli, P. Thubert Filename : draft-wakikawa-mip6-nemo-haha-00.txt Pages : 34 Date : 2003-10-23 This document describes an inter Home Agents (HAHA) protocol to provide multiple Home Agents support for both Mobile IPv6 and the Nemo Basic Support protocol. The HAHA protocol provides Home Agent redundancy and load-balancing for both protocols. The HAHA protocol allows multiple Home Agents to be placed at different links. It also allows a Mobile Node/Router to utilize multiple Home Agents simultaneously. The protocol consists of 3 mechanisms, Home Agent List management, Binding Synchronization, and Home Agent Switching. A Mobile Node/Router picks one Home Agent as its primary Home Agent and registers with it. The primary Home Agent synchronizes the binding cache information with other Home Agents. Any of Home Agents can intercept a packet meant for the Mobile Node/Router and tunnel the packet directly to its current Care-of address. Alternatively, the Home Agent can tunnel the packet to the primary Home Agent. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-wakikawa-mip6-nemo-haha-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-wakikawa-mip6-nemo-haha-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-wakikawa-mip6-nemo-haha-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: <2003-10-23112130.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-wakikawa-mip6-nemo-haha-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-wakikawa-mip6-nemo-haha-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-23112130.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 13:09:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07388 for ; Thu, 23 Oct 2003 13:09:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACixK-0002IJ-5W for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 13:09:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NH92JE008813 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 13:09:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACixK-0002I4-1F for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 13:09:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07373 for ; Thu, 23 Oct 2003 13:08:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACixI-0004vJ-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 13:09:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACixI-0004vG-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 13:09:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACixI-0002Ha-JX; Thu, 23 Oct 2003 13:09:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACix3-0002De-Rn for mip6@optimus.ietf.org; Thu, 23 Oct 2003 13:08:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07364 for ; Thu, 23 Oct 2003 13:08:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACix1-0004v1-00 for mip6@ietf.org; Thu, 23 Oct 2003 13:08:44 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1ACix1-0004uy-00 for mip6@ietf.org; Thu, 23 Oct 2003 13:08:43 -0400 Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NH8eVY026215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Oct 2003 10:08:40 -0700 (PDT) Received: from naexfe02.na.qualcomm.com (naexfe02.qualcomm.com [129.46.51.214]) by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NH8YFE007459 for ; Thu, 23 Oct 2003 10:08:38 -0700 (PDT) Received: from NAEX01.qualcomm.com ([129.46.51.60]) by naexfe02.na.qualcomm.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Oct 2003 10:08:34 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6470.0 Date: Thu, 23 Oct 2003 10:08:34 -0700 Message-ID: <17D8F6DF3ED94D40BD607380866D9B7F33D1B8@NAEX01.na.qualcomm.com> Thread-Topic: Removal of name selector from RFC 2401 Thread-Index: AcOZiEp5kHHnuhZuRX6Png7WvBd1vg== From: "Barany, Pete" To: X-OriginalArrivalTime: 23 Oct 2003 17:08:34.0279 (UTC) FILETIME=[4A9B2770:01C39988] Content-Transfer-Encoding: quoted-printable Subject: [Mip6] Removal of name selector from RFC 2401 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, The IETF IPsec WG is discussing RFC 2401bis and is considering removing the "name" selector from Section 4.4.2 of RFC 2401. They are asking if anyone is using it? Since the Mobile IPv6 specification has mention of using the ID_USER_FQDN (e.g., mobile@foobar.com) or ID_FQDN (e.g., foobar.com) Identification Type value in the ISAKMP Identification payload for Phase I aggressive mode (pre-shared secret), I suggest that this is not a good idea and that perhaps the Chairs should communicate this to the Chairs of the IETF IPsec WG. Thanks. See the INSERTed e-mail below. Regards, Pete --> INSERT e-mail -------- Original Message -------- Subject: 2401bis Issue # 89 -- Remove the selector "name" Date: Wed, 22 Oct 2003 20:31:23 -0700 From: Karen Seo To: ipsec mailingList CC: , , "Angelos D. Keromytis"=20 , , Folks, Here's a description and proposed approach for: IPsec Issue #: 89 Title: Remove the selector "name" Description =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D In the interest of simplifying things, we propose to remove the selector "Name". Is anyone using this selector? Proposed approach =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Remove text such as the following: [From Section 4.4.2 "Selectors"] "- Name: There are 2 cases (Note that these name forms are supported in the IPsec DOI.) 1. User ID a. a fully qualified user name string (DNS), e.g., mozart@foo.bar.com b. X.500 distinguished name, e.g., C =3D US, SP =3D MA, O =3D GTE Internetworking, CN =3D Stephen T. Kent. 2. System name (host, security gateway, etc.) a. a fully qualified DNS name, e.g., foo.bar.com b. X.500 distinguished name c. X.500 general name NOTE: One of the possible values of this selector is "OPAQUE". [REQUIRED for the following cases. Note that support for name forms other than addresses is not required for manually keyed SAs. o User ID - native host implementations - BITW and BITS implementations acting as HOSTS with only one user - security gateway implementations for INBOUND processing. o System names -- all implementations]" Thank you, Karen _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 14:39:30 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11594 for ; Thu, 23 Oct 2003 14:39:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkMV-0002fz-SO for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:39:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NId7aS010284 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:39:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkMV-0002fj-Oc for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 14:39:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11575 for ; Thu, 23 Oct 2003 14:38:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkMT-0006Ha-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:39:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACkMS-0006HX-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:39:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkMP-0002eK-2g; Thu, 23 Oct 2003 14:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkLY-0002V9-IZ for mip6@optimus.ietf.org; Thu, 23 Oct 2003 14:38:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11563 for ; Thu, 23 Oct 2003 14:37:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkLW-0006HL-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:38:06 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1ACkLV-0006HH-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:38:05 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NIbwVY001865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Oct 2003 11:37:59 -0700 (PDT) Received: from NAEXFE03.na.qualcomm.com (naexfe03.qualcomm.com [172.30.32.23]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NIbuTx026703 for ; Thu, 23 Oct 2003 11:37:56 -0700 (PDT) Received: from NAEX01.qualcomm.com ([129.46.51.60]) by NAEXFE03.na.qualcomm.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Oct 2003 11:37:56 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6470.0 Subject: FW: [Mip6] Removal of name selector from RFC 2401 Date: Thu, 23 Oct 2003 11:37:56 -0700 Message-ID: <17D8F6DF3ED94D40BD607380866D9B7F327C30@NAEX01.na.qualcomm.com> Thread-Topic: [Mip6] Removal of name selector from RFC 2401 Thread-Index: AcOZiEp5kHHnuhZuRX6Png7WvBd1vgADBFnQ From: "Barany, Pete" To: X-OriginalArrivalTime: 23 Oct 2003 18:37:56.0406 (UTC) FILETIME=[C6AECD60:01C39994] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Actually, after obtaining a section of the as-of-yet unpublished RFC 2401bis Internet draft, the following section in it addresses my concerns (relating to IPsec policy enforcement and not IKE policy enforcement): Sec 4.4.2 in 2401bis (as of yet unpublished I-D) - IPv6 Mobility Header Message Type (MH type) [Mobip]: This is an 8-bit selector that identifies the particular mobility message in question. This MUST be used only if the Next Layer Protocol is defined to be an IPv6 Mobility Header. Note that the MH type may not be available in the case of receipt of a packet with an ESP header, thus a value of "OPAQUE" SHOULD be supported. My apologies if this had already been discussed on this reflector previously. Pete -----Original Message----- From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On Behalf Of Barany, Pete Sent: Thursday, October 23, 2003 10:09 AM To: mip6@ietf.org Subject: [Mip6] Removal of name selector from RFC 2401 Hi, The IETF IPsec WG is discussing RFC 2401bis and is considering removing the "name" selector from Section 4.4.2 of RFC 2401. They are asking if anyone is using it? Since the Mobile IPv6 specification has mention of using the ID_USER_FQDN (e.g., mobile@foobar.com) or ID_FQDN (e.g., foobar.com) Identification Type value in the ISAKMP Identification payload for Phase I aggressive mode (pre-shared secret), I suggest that this is not a good idea and that perhaps the Chairs should communicate this to the Chairs of the IETF IPsec WG. Thanks. See the INSERTed e-mail below. Regards, Pete --> INSERT e-mail -------- Original Message -------- Subject: 2401bis Issue # 89 -- Remove the selector "name" Date: Wed, 22 Oct 2003 20:31:23 -0700 From: Karen Seo To: ipsec mailingList CC: , , "Angelos D. Keromytis"=20 , , Folks, Here's a description and proposed approach for: IPsec Issue #: 89 Title: Remove the selector "name" Description =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D In the interest of simplifying things, we propose to remove the selector "Name". Is anyone using this selector? Proposed approach =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Remove text such as the following: [From Section 4.4.2 "Selectors"] "- Name: There are 2 cases (Note that these name forms are supported in the IPsec DOI.) 1. User ID a. a fully qualified user name string (DNS), e.g., mozart@foo.bar.com b. X.500 distinguished name, e.g., C =3D US, SP =3D MA, O =3D GTE Internetworking, CN =3D Stephen T. Kent. 2. System name (host, security gateway, etc.) a. a fully qualified DNS name, e.g., foo.bar.com b. X.500 distinguished name c. X.500 general name NOTE: One of the possible values of this selector is "OPAQUE". [REQUIRED for the following cases. Note that support for name forms other than addresses is not required for manually keyed SAs. o User ID - native host implementations - BITW and BITS implementations acting as HOSTS with only one user - security gateway implementations for INBOUND processing. o System names -- all implementations]" Thank you, Karen _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 14:43:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11763 for ; Thu, 23 Oct 2003 14:43:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkQJ-0003Om-BS for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:43:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NIh3mo013058 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:43:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkQJ-0003OX-6B for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 14:43:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11732 for ; Thu, 23 Oct 2003 14:42:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkQG-0006Jr-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:43:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACkQG-0006Jn-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:43:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkQH-0003Mo-Rq; Thu, 23 Oct 2003 14:43:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkPo-0003Hu-Ac for mip6@optimus.ietf.org; Thu, 23 Oct 2003 14:42:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11689 for ; Thu, 23 Oct 2003 14:42:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkPl-0006JH-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:42:29 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ACkPk-0006J8-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:42:29 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9NIfub18041; Thu, 23 Oct 2003 11:41:56 -0700 X-mProtect: <200310231841> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdXUdAL3; Thu, 23 Oct 2003 11:41:54 PDT Message-ID: <3F982175.70800@iprg.nokia.com> Date: Thu, 23 Oct 2003 11:44:05 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Barany, Pete" CC: mip6@ietf.org Subject: Re: [Mip6] Removal of name selector from RFC 2401 References: <17D8F6DF3ED94D40BD607380866D9B7F33D1B8@NAEX01.na.qualcomm.com> In-Reply-To: <17D8F6DF3ED94D40BD607380866D9B7F33D1B8@NAEX01.na.qualcomm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit isnt the proposal in the IPsec WG just to remove 'Name' from IPsec selectors? not the ability to use "name" in IKE phase1. Vijay Barany, Pete wrote: > Hi, > > The IETF IPsec WG is discussing RFC 2401bis and is considering removing > the "name" selector from Section 4.4.2 of RFC 2401. They are asking if > anyone is using it? Since the Mobile IPv6 specification has mention of > using the ID_USER_FQDN (e.g., mobile@foobar.com) or ID_FQDN (e.g., > foobar.com) Identification Type value in the ISAKMP Identification > payload for Phase I aggressive mode (pre-shared secret), I suggest that > this is not a good idea and that perhaps the Chairs should communicate > this to the Chairs of the IETF IPsec WG. Thanks. > > See the INSERTed e-mail below. > > Regards, > > Pete > > --> INSERT e-mail > -------- Original Message -------- > Subject: 2401bis Issue # 89 -- Remove the selector "name" > Date: Wed, 22 Oct 2003 20:31:23 -0700 > From: Karen Seo > To: ipsec mailingList > CC: , , "Angelos D. Keromytis" > , , > > > > Folks, > > Here's a description and proposed approach for: > > IPsec Issue #: 89 > > Title: Remove the selector "name" > > Description > =========== > In the interest of simplifying things, we propose to remove the selector > "Name". Is anyone using this selector? > > Proposed approach > ================= > Remove text such as the following: > > [From Section 4.4.2 "Selectors"] > > "- Name: There are 2 cases (Note that these name forms are > supported in the IPsec DOI.) > 1. User ID > a. a fully qualified user name string (DNS), > e.g., mozart@foo.bar.com > b. X.500 distinguished name, e.g., C = US, > SP = MA, O = GTE Internetworking, CN = > Stephen T. Kent. > 2. System name (host, security gateway, etc.) > a. a fully qualified DNS name, e.g., > foo.bar.com > b. X.500 distinguished name > c. X.500 general name > > NOTE: One of the possible values of this selector is > "OPAQUE". > > [REQUIRED for the following cases. Note that support > for name forms other than addresses is not required for > manually keyed SAs. > o User ID > - native host implementations > - BITW and BITS implementations acting as HOSTS > with only one user > - security gateway implementations for INBOUND > processing. > o System names -- all implementations]" > > Thank you, > Karen > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 14:52:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12411 for ; Thu, 23 Oct 2003 14:52:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkZ2-000513-FO for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:52:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NIq4gD019275 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 14:52:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkZ2-0004zn-Ao for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 14:52:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12383 for ; Thu, 23 Oct 2003 14:51:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkYy-0006VE-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:52:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACkYx-0006VB-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 14:51:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkYz-0004zC-NI; Thu, 23 Oct 2003 14:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACkYJ-0004td-RZ for mip6@optimus.ietf.org; Thu, 23 Oct 2003 14:51:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12326 for ; Thu, 23 Oct 2003 14:51:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACkYH-0006US-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:51:17 -0400 Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx with esmtp (Exim 4.12) id 1ACkYG-0006UL-00 for mip6@ietf.org; Thu, 23 Oct 2003 14:51:16 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NIpDVY002631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Oct 2003 11:51:13 -0700 (PDT) Received: from naexfe02.na.qualcomm.com (naexfe02.qualcomm.com [129.46.51.214]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id h9NIpA0N001016; Thu, 23 Oct 2003 11:51:11 -0700 (PDT) Received: from NAEX01.qualcomm.com ([129.46.51.60]) by naexfe02.na.qualcomm.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Oct 2003 11:51:10 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6470.0 Subject: RE: [Mip6] Removal of name selector from RFC 2401 Date: Thu, 23 Oct 2003 11:51:10 -0700 Message-ID: <17D8F6DF3ED94D40BD607380866D9B7F327C31@NAEX01.na.qualcomm.com> Thread-Topic: [Mip6] Removal of name selector from RFC 2401 Thread-Index: AcOZlYe5EQd4cSixTqmXkQnTAAWlBwAAQyXg From: "Barany, Pete" To: "Vijay Devarapalli" Cc: X-OriginalArrivalTime: 23 Oct 2003 18:51:10.0725 (UTC) FILETIME=[A0224350:01C39996] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable You are correct ... see my follow-up e-mail. Thanks. Pete -----Original Message----- From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On Behalf Of Vijay Devarapalli Sent: Thursday, October 23, 2003 11:44 AM To: Barany, Pete Cc: mip6@ietf.org Subject: Re: [Mip6] Removal of name selector from RFC 2401 isnt the proposal in the IPsec WG just to remove 'Name' from IPsec selectors? not the ability to use "name" in IKE phase1. Vijay Barany, Pete wrote: > Hi, >=20 > The IETF IPsec WG is discussing RFC 2401bis and is considering removing > the "name" selector from Section 4.4.2 of RFC 2401. They are asking if > anyone is using it? Since the Mobile IPv6 specification has mention of > using the ID_USER_FQDN (e.g., mobile@foobar.com) or ID_FQDN (e.g., > foobar.com) Identification Type value in the ISAKMP Identification > payload for Phase I aggressive mode (pre-shared secret), I suggest that > this is not a good idea and that perhaps the Chairs should communicate > this to the Chairs of the IETF IPsec WG. Thanks. >=20 > See the INSERTed e-mail below. >=20 > Regards, >=20 > Pete >=20 > --> INSERT e-mail > -------- Original Message -------- > Subject: 2401bis Issue # 89 -- Remove the selector "name" > Date: Wed, 22 Oct 2003 20:31:23 -0700 > From: Karen Seo > To: ipsec mailingList > CC: , , "Angelos D. Keromytis"=20 > , , >=20 >=20 >=20 > Folks, >=20 > Here's a description and proposed approach for: >=20 > IPsec Issue #: 89 >=20 > Title: Remove the selector "name" >=20 > Description > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > In the interest of simplifying things, we propose to remove the selector > "Name". Is anyone using this selector? >=20 > Proposed approach > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Remove text such as the following: >=20 > [From Section 4.4.2 "Selectors"] >=20 > "- Name: There are 2 cases (Note that these name forms are > supported in the IPsec DOI.) > 1. User ID > a. a fully qualified user name string (DNS), > e.g., mozart@foo.bar.com > b. X.500 distinguished name, e.g., C =3D US, > SP =3D MA, O =3D GTE Internetworking, CN =3D > Stephen T. Kent. > 2. System name (host, security gateway, etc.) > a. a fully qualified DNS name, e.g., > foo.bar.com > b. X.500 distinguished name > c. X.500 general name >=20 > NOTE: One of the possible values of this selector is > "OPAQUE". >=20 > [REQUIRED for the following cases. Note that support > for name forms other than addresses is not required for > manually keyed SAs. > o User ID > - native host implementations > - BITW and BITS implementations acting as HOSTS > with only one user > - security gateway implementations for INBOUND > processing. > o System names -- all implementations]" >=20 > Thank you, > Karen >=20 > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 16:45:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18092 for ; Thu, 23 Oct 2003 16:45:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmKN-0004Yt-J7 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 16:45:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NKj3vO017531 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 16:45:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmKN-0004Yg-FF for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 16:45:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18076 for ; Thu, 23 Oct 2003 16:44:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACmKL-0000IE-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 16:45:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACmKL-0000IB-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 16:45:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmKL-0004Xp-7S; Thu, 23 Oct 2003 16:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmJd-0004Hc-Qp for mip6@optimus.ietf.org; Thu, 23 Oct 2003 16:44:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18042 for ; Thu, 23 Oct 2003 16:44:07 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACmJb-0000H8-00 for mip6@ietf.org; Thu, 23 Oct 2003 16:44:15 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ACmJa-0000H5-00 for mip6@ietf.org; Thu, 23 Oct 2003 16:44:15 -0400 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9NKiDI11317 for ; Thu, 23 Oct 2003 23:44:13 +0300 (EET DST) Received: from daebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id for ; Thu, 23 Oct 2003 23:44:13 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 23 Oct 2003 15:44:10 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [Mip6] Draft Agenda for WG meeting at IETF58 - Rev2 Date: Thu, 23 Oct 2003 15:44:10 -0500 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB949@daebe007.americas.nokia.com> Thread-Topic: Draft Agenda for WG meeting at IETF58 Thread-Index: AcOY6V7LQzDAEeJMSL2S0lABNrr1JgAvPLdQ To: , X-OriginalArrivalTime: 23 Oct 2003 20:44:10.0510 (UTC) FILETIME=[69335AE0:01C399A6] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable MIP6 (Mobility for IPv6 WG) Draft Agenda (Rev 2) ------------------------------------------------ MONDAY, November 10, 2003=20 1530-1730 Afternoon Sessions II CHAIRS: Basavaraj Patil Gopal Dommety Agenda: 1. Preliminaries 10 Mins Chairs - Minutes - Document status - Agenda bashing 2. MIPv6 MIB 15 Mins Glenn Keeni I-D: draft-ietf-mip6-mipv6-mib-00.txt 3. MIPv6 Remote interop testing 15 Mins T.J Kniveton/Samita C. I-D: draft-kniveton-mipv6-remote-testing-00.txt 4. Inter Home Agents Protocol (HAHA) 10 Mins Ryuji Wakikawa I-D: draft-wakikawa-mip6-nemo-haha-00.txt 5. Extension to Sockets API for Mobile IPv6 15 Mins S. Chakrabarti I-D: draft-chakrabarti-mobileip-mipext-advapi-01.txt 6. Roadmap for WG 15 Mins Chairs and ADs _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 17:18:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19483 for ; Thu, 23 Oct 2003 17:18:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmqI-0004r1-HO for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 17:18:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NLI2MU018653 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 17:18:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmqI-0004qT-CW for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 17:18:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19454 for ; Thu, 23 Oct 2003 17:17:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACmqG-0000nP-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 17:18:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACmqF-0000nM-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 17:17:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmqH-0004pm-9r; Thu, 23 Oct 2003 17:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACmpL-0004fF-1S for mip6@optimus.ietf.org; Thu, 23 Oct 2003 17:17:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19435 for ; Thu, 23 Oct 2003 17:16:51 -0400 (EDT) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACmpI-0000mv-00 for mip6@ietf.org; Thu, 23 Oct 2003 17:17:00 -0400 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1ACmpI-0000ms-00 for mip6@ietf.org; Thu, 23 Oct 2003 17:17:00 -0400 Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9NLGxI10157 for ; Fri, 24 Oct 2003 00:16:59 +0300 (EET DST) Received: from daebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 24 Oct 2003 00:16:57 +0300 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Thu, 23 Oct 2003 14:16:55 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Thu, 23 Oct 2003 16:16:54 -0500 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOZOIeq8wQfIqgMSIW3UG8plZkNSQAclWJA To: , X-OriginalArrivalTime: 23 Oct 2003 21:16:55.0222 (UTC) FILETIME=[FC429D60:01C399AA] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Thierry, >Hi Basavaraj, > >Thanks to your answer. Comments to your answer, and request below: > > >> > First thing first: I may have missed something during the MIP6 = charter >> > discussion: I don't see anything related to multihomed mobile node. >> > (multihoming covers MNs with several interfaces, MNs with several = HAs, >> > and MNs with several HoAs/CoAs). Is this something to be excluded = or >> > included in this WG ? >>=20 >> This is not within the scope of the current charter. I (chair hat = off) >> do not believe there is any urgency to deal with this problem. Hence >> can be considered in a future revision of the charter if deemed = necessary. > >Well, I cannot really agree.=20 Not a problem. We can disagree about its need for now. >In the first place, why did you list the Nomad draft if it's not within >the scope ? Well... My mistake. I did ask the author(s) to justify how this I-D fits in the charter, and if it did not, to show that there is WG = interest in this by having a discussion on the ML. But that has not happened.=20 >In the second place, there are a few drafts turning around this issues, >and drafts have been submitted regularly for a few years. So, given the >number of drafts and period of effect, I find it rather important. On a >personal side, I would like to see something coming up from this >activity so that we can implement a common solution, no doing our own >cooking in our lab. I am aware of the various drafts addressing this. But I do not see why this is a critical need for the WG to take on at this time. I do not for example see a large number of people in the WG demanding that this be a work item because it is absolutely a MUST for mobile IPv6 to be deployed. What you are cooking in your lab may be interesting but is not necessarily needed by the industry at this time. So if you believe that there is interest in this work, the I-D can always be standardized as Experimental (without WG intervention) which would let the people with common interests implement it and interop. > >Anyway, let's see why the other people are thinking. If it happens that >there is no room in this WG to deal with issue, I will most likely >propose a BOF at Seoul Meeting (and, well, this might not be a bad = idea, >because the benefit of having several interfaces [either actual, or >virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >exclusively thinking about NEMO, although the idea comes from there]). >The reason I have not yet pushed toward a new WG is because there are >already many WGs.=20 Well, please do intiate a discussion on this topic to determine=20 - the interest - how vital is this for IPv6 mobility > >In conclusion, may I request a short slot to deal the issue (not the >solutions) during the meeting, please, so that we come to a WG = consensus >and act upon it ? Sure, but first you have to demonstrate via the ML that there is some interest in this topic. If you can do that in the next week or so, we can include it on the agenda. > >Thierry. > -Basavaraj _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 21:11:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27517 for ; Thu, 23 Oct 2003 21:11:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACqTp-00047E-Ay for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 21:11:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O1B5hP015816 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 21:11:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACqTn-00045p-M6 for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 21:11:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27502 for ; Thu, 23 Oct 2003 21:10:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACqTk-0003Df-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 21:11:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACqTk-0003Dc-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 21:11:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACqTl-000455-05; Thu, 23 Oct 2003 21:11:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACqT6-00041t-5Y for mip6@optimus.ietf.org; Thu, 23 Oct 2003 21:10:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27488; Thu, 23 Oct 2003 21:10:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACqT3-0003DN-00; Thu, 23 Oct 2003 21:10:17 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ACqT2-0003D9-00; Thu, 23 Oct 2003 21:10:17 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9O19iL13607; Thu, 23 Oct 2003 18:09:44 -0700 X-mProtect: <200310240109> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdxzsP5s; Thu, 23 Oct 2003 18:09:43 PDT Message-ID: <3F987C5B.9070905@iprg.nokia.com> Date: Thu, 23 Oct 2003 18:11:55 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jinmei@isl.rdc.toshiba.co.jp, Soliman Hesham CC: ipv6@ietf.org, mip6@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [Mip6] Re: A list of issues for RFC2462 update Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, here is another issue. it involves both 2461 and 2462. RFC 2461 says Before a host sends an initial solicitation, it SHOULD delay the transmission for a random amount of time between 0 and MAX_RTR_SOLICITATION_DELAY. RFC 2462 says If the Neighbor Solicitation is the first message to be sent from an interface after interface (re)initialization, the node should delay sending the message by a random delay between 0 and MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY]. lets assume a Mobile Node moves and attaches to a new link. it does router discovery and configures a Care-of address. the mobile node cannot send a Binding Update until it completes DAD for the Care-of address. these two random delays (before router discovery and before DAD) contribute a lot to the movement detection delay. I think this needs to be fixed. MAX_RTR_SOLICITATION_DELAY is 1 second. taking the worst case scenario, it could be 1 second before a sending router solicitation, one second before sending neighbor solicitation for DAD and then 1 second before DAD completes. the Binding Update cannot be sent until then. we had a long discussion on the Mobile IP mailing list. some argued that this needs to be done only when the interface is initialized and not when the mobile node attaches to a new link. others argued that this random delay is essential to avoid a DAD storm if a bunch of mobile nodes move at the same time. there is some discussion on this at http://www.piuha.net/~jarkko/publications/mipv6/issues/issue230.txt Vijay JINMEI Tatuya / ???? wrote: > Hello, > > The attached below is a issue list to make necessary updates on > RFC2462 (Stateless Address Autoconfiguration). > > To make this list, I've grepped the ipngwg/ipv6 ML archives from > Jan. 1998 with the keywords "2462" and "stateless," and picked up > issues that seem to be related to this update. Of course, I'm not > claiming the keywords are enough, and even if they are, I may have > missed something important. > > Thus, any corrections/additions are welcome. I'd apologize in advance > the list is not necessarily very readable, but I believe it provides > some hints to start discussion. I'll collect comments on the list, > and edit a new internet draft which will basically be a copy of > RFC2462 with the issue list. > > Due to a lack of time to the cut-off date of an initial draft, I > don't think I can propose any resolutions to the issues. So, please > concentrate, at the moment, on completing or correcting the list, > rather than to discuss how to solve particular ones. > > Thanks, > > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp > > > Easy ones (which will only need some editorial works): > > - A minor typo > by Ignatios Souvatzis, Dec. 1998 > http://www.wcug.wwu.edu/lists/ipng/199812/msg00043.html > > - Dead Code in Addrconf DOS Algortim Prevention > by Jim Bound, Nov 1998 > http://www.wcug.wwu.edu/lists/ipng/199811/msg00024.html > > - A corner case about inbound NA processing > by Richard Draves (via TAHI test), Jun 2000 > > There was a consensus on the behavior, but the text is not clear. > Need to update. > > - Unclear text about StoredLifetime > by jinmei, Aug 2001 > http://www.wcug.wwu.edu/lists/ipng/200108/msg00541.html > > need to clarify the text. > > === > > Issues that may require some discussion, but will not be very hard to > get consensus: > > - Source address selection issues wrt deprecated addresses > mainly by Richard Draves, several times. > e.g. which should be preferred between a deprecated address and > smaller-scope address? > > - Deprecated address handling (the semantics of "new communication" is > not very clear) > by itojun, Nov 2000 and Aug 2002 > > There seemed to be a consensus on a text proposed by Thomas Narten: > http://www.atm.tut.fi/list-archive/ipng/msg05182.html > > Erik Nordmark made a related point (what if an application specifies > a deprecated address as a source address): > http://www.atm.tut.fi/list-archive/ipng/msg05311.html > > There seemed to be no discussion on this, but we may need to > consider this as well. > > - Semantics about the L=0 and A=1 case > by Fred Templin, Feb 2003 > > Thomas Narten said he did not see the need for further > clarification (which I agree on): > http://www.atm.tut.fi/list-archive/ipng/msg07820.html > > - Conflict with the MLD spec about random delay for the first packet > by Greg Daley, May 2005 > http://www.atm.tut.fi/list-archive/ipng/msg09614.html > > - Using stable storage for autoconfigured addresses > by Erik Nordmark, Jun 2002 > http://www.atm.tut.fi/list-archive/ipng/msg04383.html > > There seemed to be no discussion on this. > > === > > Issues that may be controversial: > > - DAD related issues > inconsistency in the text (mixture of SHOULD and MAY) > by itojun, Jun 2001 > > What about the link partitioning case > by Pekka Savola, Jun 2001(?) > > omitting DAD, DAD vs DIID, etc. > many people, many times > > - Possible Denial of Service Attack > by Ken Powell, Feb 2002 > What if a malicious node intentionally sends prefixes for other LANs? > There seemed to be no clear consensus. > > - The semantics of the M/O flags > by several people, several times. Points from Ralph Droms in Mar > 2003 seems to be a good starting point: > http://www.atm.tut.fi/list-archive/ipng/msg03047.html > > a. the text needs to be updated to use RFC 2119 keywords > b. which keywords? > c. what is "the stateful configuration protocol"? > d. if the answer to "c" is DHCPv6, should RFC 2462 more > explicitly reference the configuration-only version > of DHCPv6 in the description of the 'O'flag? > > Adam Machalek also pointed out some inconsistency about mandatory > level of the stateful configuration protocol: > > http://www.atm.tut.fi/list-archive/ipng/msg04363.html > > - Whether a (not a host) router can autoconfigure itself using RFC2462 > (or bis) including > if a router can configure a global address by stateless autoconf > if a router can configure a link-local address in a way described > in RFC 2462 > if a router can configure itself about "other" configuration > information > > by several people, several times > > - If we need a 'not-yet-ready' status of an autoconfigured address to > help renumbering operation > by Fred Baker, Apr 2003 > http://www.atm.tut.fi/list-archive/ipng/msg09394.html > > - Avoiding interface failure upon DAD failure > (mainly) by Jari Arkko, May 2003 > related to mip6. (the latest draft leaves this as "ND extensions") > > - If RFC2462 requires 64bit IFID > by several people, several times. > > - Issues raised in the send requirement draft. > (Sorry, I've not gone through the send requirement draft. So there > may or may not be issues from the draft that need to be added here) > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 22:10:24 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29332 for ; Thu, 23 Oct 2003 22:10:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrOu-0008Q3-Vm for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 22:10:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O2A4d8032357 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 22:10:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrOu-0008Po-OD for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 22:10:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29312 for ; Thu, 23 Oct 2003 22:09:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrOr-0003xM-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 22:10:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACrOr-0003xJ-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 22:10:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrOt-0008O6-Lw; Thu, 23 Oct 2003 22:10:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrNx-0008Et-9G for mip6@optimus.ietf.org; Thu, 23 Oct 2003 22:09:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29304; Thu, 23 Oct 2003 22:08:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrNt-0003x8-00; Thu, 23 Oct 2003 22:09:01 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1ACrNt-0003wy-00; Thu, 23 Oct 2003 22:09:01 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RDFGF>; Thu, 23 Oct 2003 22:12:50 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922E0F@ftmail.lab.flarion.com> From: Soliman Hesham To: "'Vijay Devarapalli'" , jinmei@isl.rdc.toshiba.co.jp Cc: ipv6@ietf.org, mip6@ietf.org Date: Thu, 23 Oct 2003 22:12:46 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Mip6] RE: A list of issues for RFC2462 update Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Vijay, Yes, this issue is the same as issue 11 for the RS. I'll add that to the list. Thanks, Hesham > -----Original Message----- > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] > Sent: Thursday, October 23, 2003 9:12 PM > To: jinmei@isl.rdc.toshiba.co.jp; Soliman Hesham > Cc: ipv6@ietf.org; mip6@ietf.org > Subject: Re: A list of issues for RFC2462 update > > > hi, > > here is another issue. it involves both 2461 and 2462. > > RFC 2461 says > > Before a host sends an initial solicitation, it SHOULD delay the > transmission for a random amount of time between 0 and > MAX_RTR_SOLICITATION_DELAY. > > RFC 2462 says > > If the Neighbor Solicitation is the first message to be > sent from an > interface after interface (re)initialization, the node > should delay > sending the message by a random delay between 0 and > MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY]. > > lets assume a Mobile Node moves and attaches to a new > link. it does router discovery and configures a Care-of > address. the mobile node cannot send a Binding Update > until it completes DAD for the Care-of address. these > two random delays (before router discovery and before > DAD) contribute a lot to the movement detection delay. > I think this needs to be fixed. > MAX_RTR_SOLICITATION_DELAY is 1 second. taking the worst > case scenario, it could be 1 second before a sending > router solicitation, one second before sending neighbor > solicitation for DAD and then 1 second before DAD > completes. the Binding Update cannot be sent until then. > > we had a long discussion on the Mobile IP mailing list. > some argued that this needs to be done only when the > interface is initialized and not when the mobile node > attaches to a new link. others argued that this random > delay is essential to avoid a DAD storm if a bunch of > mobile nodes move at the same time. > > there is some discussion on this at > http://www.piuha.net/~jarkko/publications/mipv6/issues/issue230.txt > > Vijay > > > JINMEI Tatuya / ???? wrote: > > Hello, > > > > The attached below is a issue list to make necessary updates on > > RFC2462 (Stateless Address Autoconfiguration). > > > > To make this list, I've grepped the ipngwg/ipv6 ML archives from > > Jan. 1998 with the keywords "2462" and "stateless," and picked up > > issues that seem to be related to this update. Of course, I'm not > > claiming the keywords are enough, and even if they are, I may have > > missed something important. > > > > Thus, any corrections/additions are welcome. I'd > apologize in advance > > the list is not necessarily very readable, but I believe > it provides > > some hints to start discussion. I'll collect comments on the list, > > and edit a new internet draft which will basically be a copy of > > RFC2462 with the issue list. > > > > Due to a lack of time to the cut-off date of an initial draft, I > > don't think I can propose any resolutions to the issues. > So, please > > concentrate, at the moment, on completing or correcting the list, > > rather than to discuss how to solve particular ones. > > > > Thanks, > > > > JINMEI, Tatuya > > Communication Platform Lab. > > Corporate R&D Center, > Toshiba Corp. > > jinmei@isl.rdc.toshiba.co.jp > > > > > > Easy ones (which will only need some editorial works): > > > > - A minor typo > > by Ignatios Souvatzis, Dec. 1998 > > http://www.wcug.wwu.edu/lists/ipng/199812/msg00043.html > > > > - Dead Code in Addrconf DOS Algortim Prevention > > by Jim Bound, Nov 1998 > > http://www.wcug.wwu.edu/lists/ipng/199811/msg00024.html > > > > - A corner case about inbound NA processing > > by Richard Draves (via TAHI test), Jun 2000 > > > > There was a consensus on the behavior, but the text is not clear. > > Need to update. > > > > - Unclear text about StoredLifetime > > by jinmei, Aug 2001 > > http://www.wcug.wwu.edu/lists/ipng/200108/msg00541.html > > > > need to clarify the text. > > > > === > > > > Issues that may require some discussion, but will not be > very hard to > > get consensus: > > > > - Source address selection issues wrt deprecated addresses > > mainly by Richard Draves, several times. > > e.g. which should be preferred between a deprecated address and > > smaller-scope address? > > > > - Deprecated address handling (the semantics of "new > communication" is > > not very clear) > > by itojun, Nov 2000 and Aug 2002 > > > > There seemed to be a consensus on a text proposed by > Thomas Narten: > > http://www.atm.tut.fi/list-archive/ipng/msg05182.html > > > > Erik Nordmark made a related point (what if an > application specifies > > a deprecated address as a source address): > > http://www.atm.tut.fi/list-archive/ipng/msg05311.html > > > > There seemed to be no discussion on this, but we may need to > > consider this as well. > > > > - Semantics about the L=0 and A=1 case > > by Fred Templin, Feb 2003 > > > > Thomas Narten said he did not see the need for further > > clarification (which I agree on): > > http://www.atm.tut.fi/list-archive/ipng/msg07820.html > > > > - Conflict with the MLD spec about random delay for the > first packet > > by Greg Daley, May 2005 > > http://www.atm.tut.fi/list-archive/ipng/msg09614.html > > > > - Using stable storage for autoconfigured addresses > > by Erik Nordmark, Jun 2002 > > http://www.atm.tut.fi/list-archive/ipng/msg04383.html > > > > There seemed to be no discussion on this. > > > > === > > > > Issues that may be controversial: > > > > - DAD related issues > > inconsistency in the text (mixture of SHOULD and MAY) > > by itojun, Jun 2001 > > > > What about the link partitioning case > > by Pekka Savola, Jun 2001(?) > > > > omitting DAD, DAD vs DIID, etc. > > many people, many times > > > > - Possible Denial of Service Attack > > by Ken Powell, Feb 2002 > > What if a malicious node intentionally sends prefixes > for other LANs? > > There seemed to be no clear consensus. > > > > - The semantics of the M/O flags > > by several people, several times. Points from Ralph Droms in Mar > > 2003 seems to be a good starting point: > > http://www.atm.tut.fi/list-archive/ipng/msg03047.html > > > > a. the text needs to be updated to use RFC 2119 keywords > > b. which keywords? > > c. what is "the stateful configuration protocol"? > > d. if the answer to "c" is DHCPv6, should RFC 2462 more > > explicitly reference the configuration-only version > > of DHCPv6 in the description of the 'O'flag? > > > > Adam Machalek also pointed out some inconsistency about mandatory > > level of the stateful configuration protocol: > > > > http://www.atm.tut.fi/list-archive/ipng/msg04363.html > > > > - Whether a (not a host) router can autoconfigure itself > using RFC2462 > > (or bis) including > > if a router can configure a global address by > stateless autoconf > > if a router can configure a link-local address in a > way described > > in RFC 2462 > > if a router can configure itself about "other" configuration > > information > > > > by several people, several times > > > > - If we need a 'not-yet-ready' status of an autoconfigured > address to > > help renumbering operation > > by Fred Baker, Apr 2003 > > http://www.atm.tut.fi/list-archive/ipng/msg09394.html > > > > - Avoiding interface failure upon DAD failure > > (mainly) by Jari Arkko, May 2003 > > related to mip6. (the latest draft leaves this as "ND > extensions") > > > > - If RFC2462 requires 64bit IFID > > by several people, several times. > > > > - Issues raised in the send requirement draft. > > (Sorry, I've not gone through the send requirement > draft. So there > > may or may not be issues from the draft that need to be > added here) > > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > ipv6@ietf.org > > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 23 22:25:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29825 for ; Thu, 23 Oct 2003 22:25:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrdQ-0004U3-Rm for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 22:25:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O2P4EZ017229 for mip6-archive@odin.ietf.org; Thu, 23 Oct 2003 22:25:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrdQ-0004Tk-M0 for mip6-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 22:25:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29817 for ; Thu, 23 Oct 2003 22:24:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrdN-00048l-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 22:25:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACrdN-00048i-00 for mip6-web-archive@ietf.org; Thu, 23 Oct 2003 22:25:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrdP-0004TG-Nj; Thu, 23 Oct 2003 22:25:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACrcn-0004Og-NZ for mip6@optimus.ietf.org; Thu, 23 Oct 2003 22:24:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29811; Thu, 23 Oct 2003 22:24:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACrck-00048T-00; Thu, 23 Oct 2003 22:24:22 -0400 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1ACrcj-00048A-00; Thu, 23 Oct 2003 22:24:21 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HN800C01PBRYM@mailout2.samsung.com>; Fri, 24 Oct 2003 11:23:51 +0900 (KST) Received: from ep_mmp1 (localhost [127.0.0.1]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HN8008AJPBQQ6@mailout2.samsung.com>; Fri, 24 Oct 2003 11:23:50 +0900 (KST) Received: from daniel ([168.219.203.183]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HN800DJHPBQ46@mmp1.samsung.com>; Fri, 24 Oct 2003 11:23:50 +0900 (KST) Date: Fri, 24 Oct 2003 11:24:08 +0900 From: Soohong Daniel Park Subject: RE: [Mip6] Re: A list of issues for RFC2462 update In-reply-to: <3F987C5B.9070905@iprg.nokia.com> To: "'Vijay Devarapalli'" , jinmei@isl.rdc.toshiba.co.jp, "'Soliman Hesham'" Cc: ipv6@ietf.org, mip6@ietf.org, dna@eng.monash.edu.au Message-id: <01ae01c399d5$e748d660$b7cbdba8@daniel> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Content-Transfer-Encoding: 7BIT Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Hello Vijay I agreed with your mention and this issue is work in progress at the DNA BOF. A second BOF will be scheduled during this meeting. For more reference, please look into this draft. http://www.ietf.org/internet-drafts/draft-park-dna-ipv6dadopt-requiremen t-01.txt Regards Daniel (Soohong Daniel Park) Mobile Platform Laboratory, SAMSUNG Electronics > -----Original Message----- > From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On > Behalf Of Vijay Devarapalli > Sent: Friday, October 24, 2003 10:12 AM > To: jinmei@isl.rdc.toshiba.co.jp; Soliman Hesham > Cc: ipv6@ietf.org; mip6@ietf.org > Subject: [Mip6] Re: A list of issues for RFC2462 update > > > hi, > > here is another issue. it involves both 2461 and 2462. > > RFC 2461 says > > Before a host sends an initial solicitation, it SHOULD delay the > transmission for a random amount of time between 0 and > MAX_RTR_SOLICITATION_DELAY. > > RFC 2462 says > > If the Neighbor Solicitation is the first message to be > sent from an > interface after interface (re)initialization, the node > should delay > sending the message by a random delay between 0 and > MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY]. > > lets assume a Mobile Node moves and attaches to a new > link. it does router discovery and configures a Care-of > address. the mobile node cannot send a Binding Update until > it completes DAD for the Care-of address. these two random > delays (before router discovery and before > DAD) contribute a lot to the movement detection delay. > I think this needs to be fixed. > MAX_RTR_SOLICITATION_DELAY is 1 second. taking the worst > case scenario, it could be 1 second before a sending > router solicitation, one second before sending neighbor > solicitation for DAD and then 1 second before DAD completes. > the Binding Update cannot be sent until then. > > we had a long discussion on the Mobile IP mailing list. > some argued that this needs to be done only when the > interface is initialized and not when the mobile node > attaches to a new link. others argued that this random > delay is essential to avoid a DAD storm if a bunch of > mobile nodes move at the same time. > > there is some discussion on this at > http://www.piuha.net/~jarkko/publications/mipv6/issues/issue230.txt > > Vijay > > > JINMEI Tatuya / ???? wrote: > > Hello, > > > > The attached below is a issue list to make necessary updates on > > RFC2462 (Stateless Address Autoconfiguration). > > > > To make this list, I've grepped the ipngwg/ipv6 ML archives > from Jan. > > 1998 with the keywords "2462" and "stateless," and picked up issues > > that seem to be related to this update. Of course, I'm not > claiming > > the keywords are enough, and even if they are, I may have missed > > something important. > > > > Thus, any corrections/additions are welcome. I'd apologize > in advance > > the list is not necessarily very readable, but I believe it > provides > > some hints to start discussion. I'll collect comments on the list, > > and edit a new internet draft which will basically be a copy of > > RFC2462 with the issue list. > > > > Due to a lack of time to the cut-off date of an initial > draft, I don't > > think I can propose any resolutions to the issues. So, please > > concentrate, at the moment, on completing or correcting the list, > > rather than to discuss how to solve particular ones. > > > > Thanks, > > > > JINMEI, Tatuya > > Communication Platform Lab. > > Corporate R&D Center, > Toshiba Corp. > > jinmei@isl.rdc.toshiba.co.jp > > > > > > Easy ones (which will only need some editorial works): > > > > - A minor typo > > by Ignatios Souvatzis, Dec. 1998 > > http://www.wcug.wwu.edu/lists/ipng/199812/msg00043.html > > > > - Dead Code in Addrconf DOS Algortim Prevention > > by Jim Bound, Nov 1998 > > http://www.wcug.wwu.edu/lists/ipng/199811/msg00024.html > > > > - A corner case about inbound NA processing > > by Richard Draves (via TAHI test), Jun 2000 > > > > There was a consensus on the behavior, but the text is not clear. > > Need to update. > > > > - Unclear text about StoredLifetime > > by jinmei, Aug 2001 > > http://www.wcug.wwu.edu/lists/ipng/200108/msg00541.html > > > > need to clarify the text. > > > > === > > > > Issues that may require some discussion, but will not be > very hard to > > get consensus: > > > > - Source address selection issues wrt deprecated addresses > > mainly by Richard Draves, several times. > > e.g. which should be preferred between a deprecated address and > > smaller-scope address? > > > > - Deprecated address handling (the semantics of "new > communication" is > > not very clear) > > by itojun, Nov 2000 and Aug 2002 > > > > There seemed to be a consensus on a text proposed by > Thomas Narten: > > http://www.atm.tut.fi/list-archive/ipng/msg05182.html > > > > Erik Nordmark made a related point (what if an > application specifies > > a deprecated address as a source address): > > http://www.atm.tut.fi/list-archive/ipng/msg05311.html > > > > There seemed to be no discussion on this, but we may need to > > consider this as well. > > > > - Semantics about the L=0 and A=1 case > > by Fred Templin, Feb 2003 > > > > Thomas Narten said he did not see the need for further > > clarification (which I agree on): > > http://www.atm.tut.fi/list-archive/ipng/msg07820.html > > > > - Conflict with the MLD spec about random delay for the first packet > > by Greg Daley, May 2005 > > http://www.atm.tut.fi/list-archive/ipng/msg09614.html > > > > - Using stable storage for autoconfigured addresses > > by Erik Nordmark, Jun 2002 > > http://www.atm.tut.fi/list-archive/ipng/msg04383.html > > > > There seemed to be no discussion on this. > > > > === > > > > Issues that may be controversial: > > > > - DAD related issues > > inconsistency in the text (mixture of SHOULD and MAY) > > by itojun, Jun 2001 > > > > What about the link partitioning case > > by Pekka Savola, Jun 2001(?) > > > > omitting DAD, DAD vs DIID, etc. > > many people, many times > > > > - Possible Denial of Service Attack > > by Ken Powell, Feb 2002 > > What if a malicious node intentionally sends prefixes > for other LANs? > > There seemed to be no clear consensus. > > > > - The semantics of the M/O flags > > by several people, several times. Points from Ralph Droms in Mar > > 2003 seems to be a good starting point: > > http://www.atm.tut.fi/list-archive/ipng/msg03047.html > > > > a. the text needs to be updated to use RFC 2119 keywords > > b. which keywords? > > c. what is "the stateful configuration protocol"? > > d. if the answer to "c" is DHCPv6, should RFC 2462 more > > explicitly reference the configuration-only version > > of DHCPv6 in the description of the 'O'flag? > > > > Adam Machalek also pointed out some inconsistency about mandatory > > level of the stateful configuration protocol: > > > > http://www.atm.tut.fi/list-archive/ipng/msg04363.html > > > > - Whether a (not a host) router can autoconfigure itself > using RFC2462 > > (or bis) including > > if a router can configure a global address by stateless autoconf > > if a router can configure a link-local address in a way > described > > in RFC 2462 > > if a router can configure itself about "other" configuration > > information > > > > by several people, several times > > > > - If we need a 'not-yet-ready' status of an autoconfigured > address to > > help renumbering operation > > by Fred Baker, Apr 2003 > > http://www.atm.tut.fi/list-archive/ipng/msg09394.html > > > > - Avoiding interface failure upon DAD failure > > (mainly) by Jari Arkko, May 2003 > > related to mip6. (the latest draft leaves this as "ND > extensions") > > > > - If RFC2462 requires 64bit IFID > > by several people, several times. > > > > - Issues raised in the send requirement draft. > > (Sorry, I've not gone through the send requirement draft. > So there > > may or may not be issues from the draft that need to be > added here) > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > ipv6@ietf.org > > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > > -------------------------------------------------------------------- > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 00:49:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03136 for ; Fri, 24 Oct 2003 00:49:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtsl-0001M5-KP for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 00:49:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O4n3XY005203 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 00:49:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtsl-0001Lq-E7 for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 00:49:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03133 for ; Fri, 24 Oct 2003 00:48:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACtsi-0005JR-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 00:49:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACtsi-0005JO-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 00:49:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtsj-0001Kb-Ea; Fri, 24 Oct 2003 00:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACtrl-0001Ct-Qr for mip6@optimus.ietf.org; Fri, 24 Oct 2003 00:48:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03117 for ; Fri, 24 Oct 2003 00:47:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACtri-0005J7-00 for mip6@ietf.org; Fri, 24 Oct 2003 00:47:58 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1ACtri-0005Iy-00 for mip6@ietf.org; Fri, 24 Oct 2003 00:47:58 -0400 Received: from galibier.nautilus6.org (unknown [203.178.138.3]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id F0DA05D09D; Fri, 24 Oct 2003 13:47:26 +0900 (JST) Date: Fri, 24 Oct 2003 13:41:58 +0900 From: Thierry Ernst To: Cc: mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Message-Id: <20031024134158.109fc429.ernst@sfc.wide.ad.jp> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> Organization: Keio University X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj, I find your answer amazing... Given the fact the MIP6 WG is a new group, I find it very appropriate to discuss the missions of the WG right now. Also, I would find very appropriate to raise the issue at the meeting to see how many people have interest in this. If only a minority has, so, very fine, it means it's not considered important. Demonstration done. > >In the second place, there are a few drafts turning around this issues, > >and drafts have been submitted regularly for a few years. So, given the > >number of drafts and period of effect, I find it rather important. On a > >personal side, I would like to see something coming up from this > >activity so that we can implement a common solution, no doing our own > >cooking in our lab. > > I am aware of the various drafts addressing this. But I do not see why > this is a critical need for the WG to take on at this time. I do not > for example see a large number of people in the WG demanding that this Please specify: how many people is considered "large" ? > be a work item because it is absolutely a MUST for mobile IPv6 to be > deployed. What you are cooking in your lab may be interesting but is > not necessarily needed by the industry at this time. Huh ? The industry your are refering too is not the same as the one I'm involved in. The fact that I work for a University doesn't necessarily make me unaware of business realities. > So if you believe > that there is interest in this work, the I-D can always be > standardized as Experimental (without WG intervention) which would let > the people with common interests implement it and interop. Don't take me wrong: I don't have any solution, so I cannot expect anything to be experimental ... But THERE ARE solutions, and all of them address distinct and complementary issues. The purpose of this discussion and draft-montavont is to come to an agreement on what is needed so that all the parties involved can work on a single solution. The need WG directive to achieve this. Designing a single specification is clearly a WG task. > >Anyway, let's see why the other people are thinking. If it happens that > >there is no room in this WG to deal with issue, I will most likely > >propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, > >because the benefit of having several interfaces [either actual, or > >virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not > >exclusively thinking about NEMO, although the idea comes from there]). > >The reason I have not yet pushed toward a new WG is because there are > >already many WGs. > > Well, please do intiate a discussion on this topic to determine > - the interest > - how vital is this for IPv6 mobility > >In conclusion, may I request a short slot to deal the issue (not the > >solutions) during the meeting, please, so that we come to a WG consensus > >and act upon it ? > > Sure, but first you have to demonstrate via the ML that there is some > interest in this topic. If you can do that in the next week or so, we > can include it on the agenda. This discussion is already initiated, and several people have already answered. I don't think it's necessary to demonstrate how vital it is for IPv6 mobility (could you by the way demonstrate how vital Mobile IPv6 is ? What about RO ? Just kidding); simply demonstrating the interest of people to work on this is enough. So, I will let the other intereted ML members with some space to pop up on the ML. Thierry. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 04:50:34 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21565 for ; Fri, 24 Oct 2003 04:50:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACxe8-00038E-E3 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 04:50:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O8oC6g012031 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 04:50:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACxe7-00037i-N5 for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 04:50:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21537 for ; Fri, 24 Oct 2003 04:50:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACxe4-0007n8-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 04:50:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACxe4-0007n4-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 04:50:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACxe0-00033N-Df; Fri, 24 Oct 2003 04:50:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACxdQ-0002wd-7T for mip6@optimus.ietf.org; Fri, 24 Oct 2003 04:49:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21516 for ; Fri, 24 Oct 2003 04:49:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACxdN-0007mZ-00 for mip6@ietf.org; Fri, 24 Oct 2003 04:49:25 -0400 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 1ACxdM-0007mV-00 for mip6@ietf.org; Fri, 24 Oct 2003 04:49:24 -0400 Received: from comnets.uni-bremen.de (sheepdog.comnets.uni-bremen.de [134.102.155.160]) by bugs.comnets.uni-bremen.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) with ESMTP id h9O8nAQ10992; Fri, 24 Oct 2003 10:49:11 +0200 X-Authentication-Warning: bugs.comnets.uni-bremen.de: Host sheepdog.comnets.uni-bremen.de [134.102.155.160] claimed to be comnets.uni-bremen.de Message-ID: <3F98E781.5010809@comnets.uni-bremen.de> Date: Fri, 24 Oct 2003 10:49:05 +0200 From: "Niko A. Fikouras" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Basavaraj.Patil@nokia.com CC: mip6@ietf.org, =?ISO-8859-1?Q?=22C=2E_G=F6rg=22?= , Eichinger Josef , Zirwas Wolfgang Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> Content-Type: multipart/alternative; boundary="------------070606000407070809060906" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------070606000407070809060906 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear all, since the name of the Nomad draft has been involved in this discussion, we think that we should contribute our 2 cents. First of all, independently of whether it is the nomad draft that gets presented in the next IETF meeting, we think that there has to be some presentation in the area of multiple CoA, flow distribution, etc. and maybe it should be accompanied by some thoughts on amending the WG charter. After all, it should reflect the topics of interest of the community and if this discussion is not a signal in that direction then we do not know what is. IMHO, Basavaraj's selection of the nomad draft for the draft agenda was based on the fact that nomad is the only of the proposed solutions, to my knowledge, that maintains an implementation for quite some time now and could bring some results into the discussion. We have been working on the protocol (initially for the v4 version) for a long time and we could bring in some "hands-on" experience. Even if nomad does not eventually get the chance to be presented in the next meeting let us at least start with a useful discussion on this topic in the ML apart from just hosting tense discussions. All comments are welcome. Best Regards nomad authors Basavaraj.Patil@nokia.com wrote: >Hi Thierry, > > > >>Hi Basavaraj, >> >>Thanks to your answer. Comments to your answer, and request below: >> >> >> >> >>>>First thing first: I may have missed something during the MIP6 charter >>>>discussion: I don't see anything related to multihomed mobile node. >>>>(multihoming covers MNs with several interfaces, MNs with several HAs, >>>>and MNs with several HoAs/CoAs). Is this something to be excluded or >>>>included in this WG ? >>>> >>>> >>>This is not within the scope of the current charter. I (chair hat off) >>>do not believe there is any urgency to deal with this problem. Hence >>>can be considered in a future revision of the charter if deemed necessary. >>> >>> >>Well, I cannot really agree. >> >> > >Not a problem. We can disagree about its need for now. > > > >>In the first place, why did you list the Nomad draft if it's not within >>the scope ? >> >> > >Well... My mistake. I did ask the author(s) to justify how this I-D >fits in the charter, and if it did not, to show that there is WG interest >in this by having a discussion on the ML. But that has not >happened. > > > >>In the second place, there are a few drafts turning around this issues, >>and drafts have been submitted regularly for a few years. So, given the >>number of drafts and period of effect, I find it rather important. On a >>personal side, I would like to see something coming up from this >>activity so that we can implement a common solution, no doing our own >>cooking in our lab. >> >> > >I am aware of the various drafts addressing this. But I do not see why >this is a critical need for the WG to take on at this time. I do not >for example see a large number of people in the WG demanding that this >be a work item because it is absolutely a MUST for mobile IPv6 to be >deployed. What you are cooking in your lab may be interesting but is >not necessarily needed by the industry at this time. So if you believe >that there is interest in this work, the I-D can always be >standardized as Experimental (without WG intervention) which would let >the people with common interests implement it and interop. > > > >>Anyway, let's see why the other people are thinking. If it happens that >>there is no room in this WG to deal with issue, I will most likely >>propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >>because the benefit of having several interfaces [either actual, or >>virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >>exclusively thinking about NEMO, although the idea comes from there]). >>The reason I have not yet pushed toward a new WG is because there are >>already many WGs. >> >> > >Well, please do intiate a discussion on this topic to determine > - the interest > - how vital is this for IPv6 mobility > > > >>In conclusion, may I request a short slot to deal the issue (not the >>solutions) during the meeting, please, so that we come to a WG consensus >>and act upon it ? >> >> > >Sure, but first you have to demonstrate via the ML that there is some >interest in this topic. If you can do that in the next week or so, we >can include it on the agenda. > > > >>Thierry. >> >> >> > >-Basavaraj > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > > > > --------------070606000407070809060906 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Dear all,

since the name of the Nomad draft has been involved in this discussion, we think that we should contribute our 2 cents.

First of all, independently of whether it is the nomad draft that gets presented in the next IETF meeting, we think that there has to be some presentation in the area of multiple CoA, flow distribution, etc. and maybe it should be accompanied by some thoughts on amending the WG charter. After all, it should reflect the topics of interest of the community and if this discussion is not a signal in that direction then we do not know what is.

IMHO, Basavaraj's selection of the nomad draft for the draft agenda was based on the fact that nomad is the only of the proposed solutions, to my knowledge, that maintains an implementation for quite some time now and could bring some results into the discussion. We have been working on the protocol (initially for the v4 version) for a long time and we could bring in some "hands-on" experience. Even if nomad does not eventually get the chance to be presented in the next meeting let us at least start with a useful discussion on this topic in the ML apart from just hosting tense discussions.

All comments are welcome.

Best Regards
nomad authors

Basavaraj.Patil@nokia.com wrote:
Hi Thierry,

  
Hi Basavaraj,

Thanks to your answer. Comments to your answer, and request below:


    
First thing first: I may have missed something during the MIP6 charter
discussion: I don't see anything related to multihomed mobile node.
(multihoming covers MNs with several interfaces, MNs with several HAs,
and MNs with several HoAs/CoAs). Is this something to be excluded or
included in this WG ?
        
This is not within the scope of the current charter. I (chair hat off)
do not believe there is any urgency to deal with this problem. Hence
can be considered in a future revision of the charter if deemed necessary.
      
Well, I cannot really agree. 
    

Not a problem. We can disagree about its need for now.

  
In the first place, why did you list the Nomad draft if it's not within
the scope ?
    

Well... My mistake. I did ask the author(s) to justify how this I-D
fits in the charter, and if it did not, to show that there is WG interest
in this by having a discussion on the ML. But that has not
happened. 

  
In the second place, there are a few drafts turning around this issues,
and drafts have been submitted regularly for a few years. So, given the
number of drafts and period of effect, I find it rather important. On a
personal side, I would like to see something coming up from this
activity so that we can implement a common solution, no doing our own
cooking in our lab.
    

I am aware of the various drafts addressing this. But I do not see why
this is a critical need for the WG to take on at this time. I do not
for example see a large number of people in the WG demanding that this
be a work item because it is absolutely a MUST for mobile IPv6 to be
deployed. What you are cooking in your lab may be interesting but is
not necessarily needed by the industry at this time. So if you believe
that there is interest in this work, the I-D can always be
standardized as Experimental (without WG intervention) which would let
the people with common interests implement it and interop.

  
Anyway, let's see why the other people are thinking. If it happens that
there is no room in this WG to deal with issue, I will most likely
propose a BOF at Seoul Meeting (and, well, this might not be a bad idea,
because the benefit of having several interfaces [either actual, or
virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not
exclusively thinking about NEMO, although the idea comes from there]).
The reason I have not yet pushed toward a new WG is because there are
already many WGs. 
    

Well, please do intiate a discussion on this topic to determine 
 - the interest
 - how vital is this for IPv6 mobility

  
In conclusion, may I request a short slot to deal the issue (not the
solutions) during the meeting, please, so that we come to a WG consensus
and act upon it ?
    

Sure, but first you have to demonstrate via the ML that there is some
interest in this topic. If you can do that in the next week or so, we
can include it on the agenda.

  
Thierry.

    

-Basavaraj

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6
--------------070606000407070809060906-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 05:13:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22210 for ; Fri, 24 Oct 2003 05:13:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACy0F-0007fd-Og for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 05:13:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O9D3b7029482 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 05:13:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACy0F-0007fR-A2 for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 05:13:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22200 for ; Fri, 24 Oct 2003 05:12:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACy0B-0000Go-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 05:13:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACy0B-0000Gl-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 05:12:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACy0D-0007eQ-5f; Fri, 24 Oct 2003 05:13:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACxzh-0007WQ-GI for mip6@optimus.ietf.org; Fri, 24 Oct 2003 05:12:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22189 for ; Fri, 24 Oct 2003 05:12:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACxze-0000GQ-00 for mip6@ietf.org; Fri, 24 Oct 2003 05:12:26 -0400 Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 1ACxzd-0000GN-00 for mip6@ietf.org; Fri, 24 Oct 2003 05:12:25 -0400 Received: (qmail 23284 invoked for bounce); 24 Oct 2003 09:12:32 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (noel@unknown) by unknown with RC4-MD5 encrypted SMTP; 24 Oct 2003 09:12:32 -0000 Message-ID: <3F98ECF6.6090107@dpt-info.u-strasbg.fr> Date: Fri, 24 Oct 2003 11:12:22 +0200 From: Thomas Noel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030912 Thunderbird/0.3a X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Niko A. Fikouras" CC: Basavaraj.Patil@nokia.com, mip6@ietf.org, =?ISO-8859-1?Q?=22C=2E_?= =?ISO-8859-1?Q?G=F6rg=22?= , Eichinger Josef , Zirwas Wolfgang Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> <3F98E781.5010809@comnets.uni-bremen.de> In-Reply-To: <3F98E781.5010809@comnets.uni-bremen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Niko, all > > First of all, independently of whether it is the nomad draft that gets > presented in the next IETF meeting, we think that there has to be some > presentation in the area of multiple CoA, flow distribution, etc. and > maybe it should be accompanied by some thoughts on amending the WG > charter. After all, it should reflect the topics of interest of the > community and if this discussion is not a signal in that direction then > we do not know what is. Agreed, > > IMHO, Basavaraj's selection of the nomad draft for the draft agenda was > based on the fact that nomad is the only of the proposed solutions, to > my knowledge, that maintains an implementation for quite some time now > and could bring some results into the discussion. We have been working > on the protocol (initially for the v4 version) for a long time and we > could bring in some "hands-on" experience. Even if nomad does not > eventually get the chance to be presented in the next meeting let us at > least start with a useful discussion on this topic in the ML apart from > just hosting tense discussions. Yes, but I think it would be interesting to present and discuss the issues before describing solutions and results. Thomas _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 06:26:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23964 for ; Fri, 24 Oct 2003 06:26:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACz8u-0004Rm-Ih for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 06:26:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OAQ4E0017091 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 06:26:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACz8t-0004RX-Re for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 06:26:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23934 for ; Fri, 24 Oct 2003 06:25:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACz8p-0000yi-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 06:25:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ACz8p-0000yf-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 06:25:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACz8r-0004Py-Kd; Fri, 24 Oct 2003 06:26:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ACz8A-0004Jl-Ms for mip6@optimus.ietf.org; Fri, 24 Oct 2003 06:25:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23903 for ; Fri, 24 Oct 2003 06:25:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ACz86-0000y2-00 for mip6@ietf.org; Fri, 24 Oct 2003 06:25:14 -0400 Received: from 80.179.107.66.forward.012.net.il ([80.179.107.66] helo=ietf-mx.ietf.org) by ietf-mx with smtp (Exim 4.12) id 1ACz84-0000xW-00 for mip6@ietf.org; Fri, 24 Oct 2003 06:25:14 -0400 From: "Philemon Muhkele" Date: Fri, 24 Oct 2003 11:24:34 To: mip6@ietf.org MIME-Version: 1.0 Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: Content-Transfer-Encoding: 7bit Subject: [Mip6] Partnership Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit From: Philemon Muhkele(chief auditor) 155 president street, Johannesburg, South Africa. Tel: +874-762919-885. Fax:+874-762919-886. Dear , Though I know that a transaction of this magnitude will make any one apprehensive and worried, but I am assuring you that everything will be well at theend of the day. We have decided to contact you due to the urgency of this transaction. I got your email address while searching for trustworthy individual. Let me start by introducing myself properly to you. I am Philemon Muhkele an auditor with Ned Credit Bank, Johannesburg, South Africa . MY PROPOSITION: A French foreigner Late Engr.Peter Claude (Snr) a merchant with The Federal Government of South Africa, Formerly working in Witwatersrand Johannesburg Gold Mine, Johannesburg South Africa. Until his death few year ago in Kenya Air Bus (A310 - 304)Flight KQ431, He banked with us at Ned Credit Bank Johannesburg and had a closing balance as at the end of September, 2000 worth $30,800.000.00 (Thirty Million eight hundred thousand United State Dollars), (this is aside the accrued interest so far from that date) the bank now expects his next of kin as beneficiary. Valuable efforts are being made by the Bank to get in touch with any of the Claude's Family or Relatives but to no success. Since we got information about his death, we have been expecting his next of kin to come over and claim his money because we cannot release it unless somebody applies for it as next of kin or relation to the deceased as indicated in our banking guidelines but unfortunately we learnt that all his supposed next of kin or relation died alongside with him at the plane crash leaving nobody behind for the claim. It is because of the perceived possibility of not being able to locate any of Late Engr. Peter Claude(Snr.)'s next of kin . The Management under the influence of our Chairman and Members of the Board of Directors, Thus that arrangement has been made for the fund to be decleare"Unclaimed" and subsequentlly be donated to the trust fund for arms and ammunition to further enhance the course of War in Africa and the World in General. In order to avert this negative development, some of my trusted colleagues and I, now seek your permission to have you stand as next of kin to the late Engr.peter Claude (Snr.) so that the fund will be released and paid into your Account as the beneficiary/next of kin.The request of A foreigner as next of kin in this business is occasioned by the fact that the customer(Claude) was a foreigner and a Local person here in the country cannot stand as next of kin to a foreigner). All documents and proves to enable you get this fund will be carefully worked out. We have secured from the probate registry, an order of Mandamus to locate any of the deceased's beneficiary(ies), and more so we are assuring you that this business is 100% Risk Free. Your share will be 30% of the total sum while 10% will be set aside for any expences incured during the course of the transaction, The rest of 60% will be for myself and my colleagues for investment purposes, According to agreement between both parties. Therefore to enable the immediate transfer of this fund to you as arranged, you must apply first to the bank as relations or next of kin to the deceased indicating your bank name, your bank account number, your private telephone and fax number for easy and effective communication and location where-in the money will be remitted. I will also instruct you on how you can add in your application to our bank, so that you get paid through our corresponding bank overseas as this will be easier for us. Upon receipt of your reply, I will send to you by fax or email the text of the application. Please note that for the purposes of confidentiality, you may further correspond through my alternative email address: philemonm@hknetmail.com or have me called through my telephone +874-762919-885. Accept my warm regards as I await your response. Sincerely Philemon Muhkele _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 08:34:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28043 for ; Fri, 24 Oct 2003 08:34:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD18k-0003gp-89 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 08:34:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OCY2Ji014179 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 08:34:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD18k-0003gW-1N for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 08:34:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28034 for ; Fri, 24 Oct 2003 08:33:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD18i-0002fK-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 08:34:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD18i-0002fG-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 08:34:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD18i-0003el-OB; Fri, 24 Oct 2003 08:34:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD18f-0003cy-4J for mip6@optimus.ietf.org; Fri, 24 Oct 2003 08:33:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28031; Fri, 24 Oct 2003 08:33:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD18d-0002fD-00; Fri, 24 Oct 2003 08:33:55 -0400 Received: from omgo.iij.ad.jp ([202.232.30.157]) by ietf-mx with esmtp (Exim 4.12) id 1AD18c-0002fA-00; Fri, 24 Oct 2003 08:33:55 -0400 Received: from jc-smtp.iij.ad.jp ([192.168.176.35]) by omgo.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9OCXmEN007939; Fri, 24 Oct 2003 21:33:48 +0900 (JST) Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.65.65]) by jc-smtp.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9OCXKxX029899; Fri, 24 Oct 2003 21:33:21 +0900 (JST) Date: Fri, 24 Oct 2003 21:32:44 +0900 (JST) Message-Id: <20031024.213244.38493611.keiichi@iij.ad.jp> To: Samita.Chakrabarti@eng.sun.com Cc: mip6@ietf.org, mipshop@ietf.org Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft From: Keiichi SHIMA / =?iso-2022-jp?B?GyRCRWc3RDBsGyhC?= In-Reply-To: <200310201752.h9KHqRuT723936@jurassic.eng.sun.com> References: <200310201752.h9KHqRuT723936@jurassic.eng.sun.com> X-Mailer: Mew version 4.0.59 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Samita and T.J., It is very interesting and good idea to establish a remote test environment. (and we are interested in participating the test, of course :-) By the way, I have a question (or concern) about the virtual home link described in Section 8 in the draft. Section 8 proposes the method for mobile node implementers to test 'returning to home' with other home agent vendor's implementation, even when the mobile node cannot access the real home link of the home agent. My question is, how is a home agent (and a home link) configured? I imagined the following network, for example. ----+---------- home link P::/64 | |P::1 (home agent address) IF1|200.0.0.1 +--+-+ | HA | IF3(200.0.0.1 - 100.0.0.1) +--+-+ IF2| | ((Internet)) | | ---+---------+------------ visited link of MN tester Q::/64 | |Q::100 (care-of address) IF1|100.0.0.1 +--+-+ | MN | IF2(100.0.0.1-200.0.0.1) +----+ HA has physically two interfaces, IF1 and IF2. In this case, IF2 has nothing to do with this scenario, I ignore it. HA also has one tunnel interface IF3 between 200.0.0.1 and 100.0.0.1. MN has physically one interface IF1, and one tunnel interface IF2 between 100.0.0.1 and 200.0.0.1. The draft says, MN receives a router advertisement for home link from HA via the tunnel interface IF2. However I think it is difficult, since HA must have two different interfaces and those interfaces must be assigned the same prefix (in this case, P::/64). This means HA is required to support a kind of multi-link subnet technology. (Or did I misread?) If there is no physical home link, I think it is possible to configure. For example, +--+-+ IF1(200.0.0.1 - 100.0.0.1) | HA | P::1/64 (home address) +--+-+ IF2|200.0.0.1 | ((Internet)) | | ---+---------+------------ visited link of MN tester Q::/64 | |Q::100 (care-of address) IF1|100.0.0.1 +--+-+ | MN | IF2(100.0.0.1-200.0.0.1) +----+ In this case, I see no problem. However, this scenario requires as many home subnets as the number of mobile nodes, since HA must arrange different tunnel interface and home prefix for each mobile node. I don't think the former scenario is not appropriate. It is of course more efficient than the latter, if HA can do that. But I just think not so many home agent can do it. I may be wrong... Best Regards, --- Keiichi SHIMA IIJ Research Laboratory KAME Project _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 10:51:32 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05363 for ; Fri, 24 Oct 2003 10:51:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3HV-0002Yl-Qb for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 10:51:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OEpDer009835 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 10:51:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3HV-0002YY-LD for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 10:51:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05276 for ; Fri, 24 Oct 2003 10:51:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD3HT-0004LL-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 10:51:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD3HS-0004LI-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 10:51:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3HM-0002Wo-CI; Fri, 24 Oct 2003 10:51:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD3Gs-0002Tf-MN for mip6@optimus.ietf.org; Fri, 24 Oct 2003 10:50:34 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05198; Fri, 24 Oct 2003 10:50:22 -0400 (EDT) Message-Id: <200310241450.KAA05198@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: mip6@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 24 Oct 2003 10:50:21 -0400 Subject: [Mip6] I-D ACTION:draft-ietf-mip6-mipv6-mib-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobility for IPv6 Working Group of the IETF. Title : The Mobile IPv6 MIB Author(s) : G. Keeni, K. Nagami, K. Koide, S. Gundavelli Filename : draft-ietf-mip6-mipv6-mib-00.txt Pages : 53 Date : 2003-10-23 This memo defines a portion of the Management Information Base (MIB), the the Mobile-IPv6 MIB, for use with network management protocols in the Internet community. In particular, Mobile-IPv6 MIB will be used to monitor and control Mobile Node, Home Agent and Correspondent Node functions of an MIPv6 entity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mip6-mipv6-mib-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-mip6-mipv6-mib-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-mip6-mipv6-mib-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: <2003-10-24103610.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mip6-mipv6-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mip6-mipv6-mib-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-10-24103610.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 14:51:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22911 for ; Fri, 24 Oct 2003 14:51:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD71d-0000Bi-MH for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 14:51:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OIp5Jv000715 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 14:51:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD71d-0000BS-HP for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 14:51:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22868 for ; Fri, 24 Oct 2003 14:50:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD71a-0002cQ-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 14:51:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD71a-0002cN-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 14:51:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD71b-0000Aw-Ix; Fri, 24 Oct 2003 14:51:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD71O-00008N-Ia for mip6@optimus.ietf.org; Fri, 24 Oct 2003 14:50:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22861 for ; Fri, 24 Oct 2003 14:50:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD71L-0002c8-00 for mip6@ietf.org; Fri, 24 Oct 2003 14:50:47 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AD71L-0002bj-00 for mip6@ietf.org; Fri, 24 Oct 2003 14:50:47 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9OIoCO23656; Fri, 24 Oct 2003 11:50:12 -0700 X-mProtect: <200310241850> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdEv8EBY; Fri, 24 Oct 2003 11:50:10 PDT Message-ID: <3F9974EB.9050507@iprg.nokia.com> Date: Fri, 24 Oct 2003 11:52:27 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thierry Ernst CC: Basavaraj.Patil@nokia.com, mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> <20031024134158.109fc429.ernst@sfc.wide.ad.jp> In-Reply-To: <20031024134158.109fc429.ernst@sfc.wide.ad.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thierry, I wish you had bought this up a month ago when the MIP6 charter was being discussed. we could have added multi- homed (or more explicitly multi-interface) mobile nodes to the charter. now the charter is finalised, there are work items and the schedule to complete the work items on the charter is very aggresive. see http://www.ietf.org/html.charters/mip6-charter.html. there is nothing wrong when Raj said he didnt see any interest for multi-homed mobile nodes. nobody bought them up when the charter was being discussed. Vijay ps: I am not against including multi-homed mobile nodes in the charter. infact I think we should work on them. Thierry Ernst wrote: > Hi Basavaraj, > > I find your answer amazing... > > Given the fact the MIP6 WG is a new group, I find it very appropriate to > discuss the missions of the WG right now. Also, I would find very > appropriate to raise the issue at the meeting to see how many people > have interest in this. If only a minority has, so, very fine, it means > it's not considered important. Demonstration done. > > >>>In the second place, there are a few drafts turning around this issues, >>>and drafts have been submitted regularly for a few years. So, given the >>>number of drafts and period of effect, I find it rather important. On a >>>personal side, I would like to see something coming up from this >>>activity so that we can implement a common solution, no doing our own >>>cooking in our lab. >> >>I am aware of the various drafts addressing this. But I do not see why >>this is a critical need for the WG to take on at this time. I do not >>for example see a large number of people in the WG demanding that this > > > Please specify: how many people is considered "large" ? > > >>be a work item because it is absolutely a MUST for mobile IPv6 to be >>deployed. What you are cooking in your lab may be interesting but is >>not necessarily needed by the industry at this time. > > > Huh ? The industry your are refering too is not the same as the one I'm > involved in. The fact that I work for a University doesn't necessarily > make me unaware of business realities. > > >>So if you believe >>that there is interest in this work, the I-D can always be >>standardized as Experimental (without WG intervention) which would let >>the people with common interests implement it and interop. > > > Don't take me wrong: I don't have any solution, so I cannot expect > anything to be experimental ... But THERE ARE solutions, and all of them > address distinct and complementary issues. The purpose of this > discussion and draft-montavont is to come to an agreement on what is > needed so that all the parties involved can work on a single solution. > The need WG directive to achieve this. Designing a single specification > is clearly a WG task. > > >>>Anyway, let's see why the other people are thinking. If it happens that >>>there is no room in this WG to deal with issue, I will most likely >>>propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >>>because the benefit of having several interfaces [either actual, or >>>virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >>>exclusively thinking about NEMO, although the idea comes from there]). >>>The reason I have not yet pushed toward a new WG is because there are >>>already many WGs. >> >>Well, please do intiate a discussion on this topic to determine >> - the interest >> - how vital is this for IPv6 mobility > > >>>In conclusion, may I request a short slot to deal the issue (not the >>>solutions) during the meeting, please, so that we come to a WG consensus >>>and act upon it ? >> >>Sure, but first you have to demonstrate via the ML that there is some >>interest in this topic. If you can do that in the next week or so, we >>can include it on the agenda. > > > This discussion is already initiated, and several people have already > answered. I don't think it's necessary to demonstrate how vital it is > for IPv6 mobility (could you by the way demonstrate how vital Mobile > IPv6 is ? What about RO ? Just kidding); simply demonstrating the > interest of people to work on this is enough. So, I will let the other > intereted ML members with some space to pop up on the ML. > > Thierry. > > > > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 15:03:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23322 for ; Fri, 24 Oct 2003 15:03:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7DC-00026j-87 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:03:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJ32MX008095 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:03:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7DC-00026S-21 for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:03:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23287 for ; Fri, 24 Oct 2003 15:02:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7D9-0002kB-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:02:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7D8-0002k8-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:02:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7DB-00025z-0n; Fri, 24 Oct 2003 15:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Co-0001zX-5J for mip6@optimus.ietf.org; Fri, 24 Oct 2003 15:02:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23240 for ; Fri, 24 Oct 2003 15:02:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Ck-0002ja-00 for mip6@ietf.org; Fri, 24 Oct 2003 15:02:35 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Ck-0002j7-00 for mip6@ietf.org; Fri, 24 Oct 2003 15:02:34 -0400 Received: from huez (U190221.ppp.dion.ne.jp [218.222.190.221]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 3D4BA5D08F; Sat, 25 Oct 2003 04:01:59 +0900 (JST) Date: Sat, 25 Oct 2003 04:01:20 +0900 From: Thierry Ernst To: Vijay Devarapalli Cc: Basavaraj.Patil@nokia.com, mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Message-Id: <20031025040120.15f730ec.ernst@sfc.wide.ad.jp> In-Reply-To: <3F9974EB.9050507@iprg.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44024DB94A@daebe007.americas.nokia.com> <20031024134158.109fc429.ernst@sfc.wide.ad.jp> <3F9974EB.9050507@iprg.nokia.com> Organization: Keio University X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj, > I wish you had bought this up a month ago when the MIP6 > charter was being discussed. we could have added multi- > homed (or more explicitly multi-interface) mobile nodes > to the charter. Just one quick comment: I did brought this up a month ago. See in the archives. The first answer I got was from Hesham. Thierry. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 15:17:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25079 for ; Fri, 24 Oct 2003 15:17:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Ql-0004YN-RH for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:17:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJH3Kb017496 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:17:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Ql-0004Xj-Io for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:17:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25026 for ; Fri, 24 Oct 2003 15:16:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7Qk-0002we-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:17:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7Qj-0002wV-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:17:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Qj-0004Ur-Gp; Fri, 24 Oct 2003 15:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7QI-0004Om-Fh for mip6@optimus.ietf.org; Fri, 24 Oct 2003 15:16:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24968; Fri, 24 Oct 2003 15:16:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7QG-0002w0-00; Fri, 24 Oct 2003 15:16:32 -0400 Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx with esmtp (Exim 4.12) id 1AD7QG-0002vc-00; Fri, 24 Oct 2003 15:16:32 -0400 Received: from jurassic.eng.sun.com ([129.146.88.31]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9OJG1xA005153; Fri, 24 Oct 2003 12:16:01 -0700 (PDT) Received: from shubho (shubho.Eng.Sun.COM [129.146.85.207]) by jurassic.eng.sun.com (8.12.10+Sun/8.12.10) with SMTP id h9OJG1Gs118291; Fri, 24 Oct 2003 12:16:01 -0700 (PDT) Message-Id: <200310241916.h9OJG1Gs118291@jurassic.eng.sun.com> Date: Fri, 24 Oct 2003 12:17:18 -0700 (PDT) From: Samita Chakrabarti Reply-To: Samita Chakrabarti Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft To: keiichi@iij.ad.jp Cc: mip6@ietf.org, mipshop@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: pcMrtz0owoUAOdDtVtDEsg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_31 SunOS 5.10 sun4u sparc Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > Section 8 proposes the method for mobile node implementers to test > 'returning to home' with other home agent vendor's implementation, > even when the mobile node cannot access the real home link of the home > agent. > > My question is, how is a home agent (and a home link) configured? We need to discuss more and flush out the configuration of HA and virtual home tunnel without changing the HA implementation. Working group comments would be helpful for this. > > I imagined the following network, for example. > > > ----+---------- home link P::/64 > | > |P::1 (home agent address) > IF1|200.0.0.1 > +--+-+ > | HA | IF3(200.0.0.1 - 100.0.0.1) > +--+-+ > IF2| > | > ((Internet)) > | > | > ---+---------+------------ visited link of MN tester Q::/64 > | > |Q::100 (care-of address) > IF1|100.0.0.1 > +--+-+ > | MN | IF2(100.0.0.1-200.0.0.1) > +----+ > > HA has physically two interfaces, IF1 and IF2. In this case, IF2 has > nothing to do with this scenario, I ignore it. HA also has one tunnel > interface IF3 between 200.0.0.1 and 100.0.0.1. > > MN has physically one interface IF1, and one tunnel interface IF2 > between 100.0.0.1 and 200.0.0.1. > > The draft says, MN receives a router advertisement for home link from > HA via the tunnel interface IF2. However I think it is difficult, > since HA must have two different interfaces and those interfaces must > be assigned the same prefix (in this case, P::/64). This means HA is > required to support a kind of multi-link subnet technology. (Or did I > misread?) > I think the draft meant virtual tunnel interface. The idea is that the MN would setup the tunnel when it thinks it comes back home and when it is away, it should disable the tunnel and thus not receive any HA adv. It would require some special configuration on HA side. I don't know if that is not possible or complicated - TJ and others in the design team may have comments on that. > If there is no physical home link, I think it is possible to configure. > For example, > > +--+-+ IF1(200.0.0.1 - 100.0.0.1) > | HA | P::1/64 (home address) > +--+-+ > IF2|200.0.0.1 > | > ((Internet)) > | > | > ---+---------+------------ visited link of MN tester Q::/64 > | > |Q::100 (care-of address) > IF1|100.0.0.1 > +--+-+ > | MN | IF2(100.0.0.1-200.0.0.1) > +----+ > > In this case, I see no problem. However, this scenario requires as > many home subnets as the number of mobile nodes, since HA must arrange > different tunnel interface and home prefix for each mobile node. > This scenario looks ok to me for adv. But not sure how HA would receive packets from CN to relay to MN on a different tunnel. Thanks, -Samita _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 15:23:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25413 for ; Fri, 24 Oct 2003 15:23:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7Wa-0005mu-O3 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:23:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OJN4Aa022244 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 15:23:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7WZ-0005m9-5B for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 15:23:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25356 for ; Fri, 24 Oct 2003 15:22:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7WX-000303-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:23:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD7WW-0002zx-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 15:23:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7WX-0005lF-Fi; Fri, 24 Oct 2003 15:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD7WD-0005hL-Rs for mip6@optimus.ietf.org; Fri, 24 Oct 2003 15:22:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25327 for ; Fri, 24 Oct 2003 15:22:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD7WC-0002zL-00 for mip6@ietf.org; Fri, 24 Oct 2003 15:22:40 -0400 Received: from smtp808.mail.sc5.yahoo.com ([66.163.168.187]) by ietf-mx with smtp (Exim 4.12) id 1AD7WB-0002zI-00 for mip6@ietf.org; Fri, 24 Oct 2003 15:22:39 -0400 Received: from adsl-64-170-248-130.dsl.lsan03.pacbell.net (HELO eremmell) (elmic@sbcglobal.net@64.170.248.130 with login) by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 24 Oct 2003 19:22:38 -0000 From: "Ed Remmell" To: "'Samita Chakrabarti'" , Cc: , Subject: RE: [Mip6] Mobile IPv6 Interop Testing Draft Date: Fri, 24 Oct 2003 12:22:39 -0700 Message-ID: <000301c39a64$30afcaa0$0900a8c0@eremmell> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <200310241916.h9OJG1Gs118291@jurassic.eng.sun.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Gee, it seems like it will be difficult to test the "MN return-to-home" and/or "MN move-from-home" scenarios this way, but no biggie, I'd prefer if MIPv6 was deployed using virtual home networks implemented internal to the HA anyways since that's a big simplification to MIPv6 protocol operation. So, we probably won't test MN operation on the home link via this remote testing, instead our MN will always be attached to a foreign link. Still, you can get some good test coverage this way. Thanks. - Ed > -----Original Message----- > From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On > Behalf Of Samita Chakrabarti > Sent: Friday, October 24, 2003 12:17 PM > To: keiichi@iij.ad.jp > Cc: mip6@ietf.org; mipshop@ietf.org > Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft > > > > > > Section 8 proposes the method for mobile node implementers to test > > 'returning to home' with other home agent vendor's implementation, > > even when the mobile node cannot access the real home link > of the home > > agent. > > > > My question is, how is a home agent (and a home link) configured? > > > We need to discuss more and flush out the configuration of HA > and virtual home tunnel without changing the HA > implementation. Working group comments would be helpful for this. > > > > > I imagined the following network, for example. > > > > > > ----+---------- home link P::/64 > > | > > |P::1 (home agent address) > > IF1|200.0.0.1 > > +--+-+ > > | HA | IF3(200.0.0.1 - 100.0.0.1) > > +--+-+ > > IF2| > > | > > ((Internet)) > > | > > | > > ---+---------+------------ visited link of MN tester Q::/64 > > | > > |Q::100 (care-of address) > > IF1|100.0.0.1 > > +--+-+ > > | MN | IF2(100.0.0.1-200.0.0.1) > > +----+ > > > > HA has physically two interfaces, IF1 and IF2. In this > case, IF2 has > > nothing to do with this scenario, I ignore it. HA also has > one tunnel > > interface IF3 between 200.0.0.1 and 100.0.0.1. > > > > MN has physically one interface IF1, and one tunnel interface IF2 > > between 100.0.0.1 and 200.0.0.1. > > > > The draft says, MN receives a router advertisement for home > link from > > HA via the tunnel interface IF2. However I think it is difficult, > > since HA must have two different interfaces and those > interfaces must > > be assigned the same prefix (in this case, P::/64). This > means HA is > > required to support a kind of multi-link subnet technology. > (Or did I > > misread?) > > > > I think the draft meant virtual tunnel interface. The idea is > that the MN would setup the tunnel when it thinks it comes > back home and when it is away, it should disable the tunnel > and thus not receive any HA adv. It would require some > special configuration on HA side. I don't know if that is not > possible or complicated - TJ and others in the design team > may have comments on that. > > > If there is no physical home link, I think it is possible to > > configure. For example, > > > > +--+-+ IF1(200.0.0.1 - 100.0.0.1) > > | HA | P::1/64 (home address) > > +--+-+ > > IF2|200.0.0.1 > > | > > ((Internet)) > > | > > | > > ---+---------+------------ visited link of MN tester Q::/64 > > | > > |Q::100 (care-of address) > > IF1|100.0.0.1 > > +--+-+ > > | MN | IF2(100.0.0.1-200.0.0.1) > > +----+ > > > > In this case, I see no problem. However, this scenario requires as > > many home subnets as the number of mobile nodes, since HA > must arrange > > different tunnel interface and home prefix for each mobile node. > > > > This scenario looks ok to me for adv. But not sure how HA > would receive packets from CN to relay to MN on a different tunnel. > > Thanks, > -Samita > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.522 / Virus Database: 320 - Release Date: 9/29/2003 > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.522 / Virus Database: 320 - Release Date: 9/29/2003 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 24 16:36:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28699 for ; Fri, 24 Oct 2003 16:36:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8fD-0003ao-QB for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 16:36:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9OKa3Tr013798 for mip6-archive@odin.ietf.org; Fri, 24 Oct 2003 16:36:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8fD-0003aT-L9 for mip6-web-archive@optimus.ietf.org; Fri, 24 Oct 2003 16:36:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28679 for ; Fri, 24 Oct 2003 16:35:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8fB-000421-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 16:36:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AD8fB-00041w-00 for mip6-web-archive@ietf.org; Fri, 24 Oct 2003 16:36:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8fB-0003ZG-F4; Fri, 24 Oct 2003 16:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AD8ee-0003Vo-5H for mip6@optimus.ietf.org; Fri, 24 Oct 2003 16:35:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28634 for ; Fri, 24 Oct 2003 16:35:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AD8ec-00041A-00 for mip6@ietf.org; Fri, 24 Oct 2003 16:35:26 -0400 Received: from sausage.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AD8eb-000412-00 for mip6@ietf.org; Fri, 24 Oct 2003 16:35:25 -0400 Received: from [61.41.140.174] (helo=MailUser) by manatick with smtp (Exim 4.24) id 1AD8ea-0000KO-Km for mip6@ietf.org; Fri, 24 Oct 2003 16:35:25 -0400 Reply-To: "Mike" From: "Mike" To: "" Organization: best-invest X-Priority: 1 X-MSMail-Priority: High Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 25 Oct 2003 05:35:21 +0900 Message-Id: Subject: [Mip6] Mike's (best-Invest in real money) Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Hi call me Mike. I earn money in the Internet. Visit a site on which I has collected all links on which it is possible well to earn. http://best-invest.x-internet-x.com The best investment sites on which here are included it is possible to increase the capital, and also to earn participating in the partner programs. Really money is not necessary for you? _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 00:58:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13138 for ; Sat, 25 Oct 2003 00:58:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADGV1-0003WK-FG for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 00:58:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9P4w33o013528 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 00:58:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADGV1-0003W7-95 for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 00:58:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13130 for ; Sat, 25 Oct 2003 00:57:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADGUy-00012s-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 00:58:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADGUy-00012p-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 00:58:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADGUz-0003VY-4C; Sat, 25 Oct 2003 00:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADGUk-0003Uv-NB for mip6@optimus.ietf.org; Sat, 25 Oct 2003 00:57:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13124 for ; Sat, 25 Oct 2003 00:57:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADGUh-00012f-00 for mip6@ietf.org; Sat, 25 Oct 2003 00:57:43 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1ADGUh-00012Z-00 for mip6@ietf.org; Sat, 25 Oct 2003 00:57:43 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RDJJM>; Sat, 25 Oct 2003 00:57:12 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922E18@ftmail.lab.flarion.com> From: Soliman Hesham To: "'Vijay Devarapalli'" , Thierry Ernst Cc: mip6@ietf.org Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Sat, 25 Oct 2003 00:57:08 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > Thierry, > > I wish you had bought this up a month ago when the MIP6 > charter was being discussed. we could have added multi- > homed (or more explicitly multi-interface) mobile nodes > to the charter. => FWIW, he did bring it up and so did I (In Minneapolis meeting 2001 and it got delayed because of the MIPv6 debacle) and a few other people. Hesham > > now the charter is finalised, there are work items and > the schedule to complete the work items on the charter > is very aggresive. see > http://www.ietf.org/html.charters/mip6-charter.html. > > there is nothing wrong when Raj said he didnt see any > interest for multi-homed mobile nodes. nobody bought > them up when the charter was being discussed. > > Vijay > > ps: I am not against including multi-homed mobile nodes > in the charter. infact I think we should work on them. > > Thierry Ernst wrote: > > Hi Basavaraj, > > > > I find your answer amazing... > > > > Given the fact the MIP6 WG is a new group, I find it very > appropriate to > > discuss the missions of the WG right now. Also, I would find very > > appropriate to raise the issue at the meeting to see how > many people > > have interest in this. If only a minority has, so, very > fine, it means > > it's not considered important. Demonstration done. > > > > > >>>In the second place, there are a few drafts turning > around this issues, > >>>and drafts have been submitted regularly for a few years. > So, given the > >>>number of drafts and period of effect, I find it rather > important. On a > >>>personal side, I would like to see something coming up from this > >>>activity so that we can implement a common solution, no > doing our own > >>>cooking in our lab. > >> > >>I am aware of the various drafts addressing this. But I do > not see why > >>this is a critical need for the WG to take on at this > time. I do not > >>for example see a large number of people in the WG > demanding that this > > > > > > Please specify: how many people is considered "large" ? > > > > > >>be a work item because it is absolutely a MUST for mobile > IPv6 to be > >>deployed. What you are cooking in your lab may be > interesting but is > >>not necessarily needed by the industry at this time. > > > > > > Huh ? The industry your are refering too is not the same > as the one I'm > > involved in. The fact that I work for a University doesn't > necessarily > > make me unaware of business realities. > > > > > >>So if you believe > >>that there is interest in this work, the I-D can always be > >>standardized as Experimental (without WG intervention) > which would let > >>the people with common interests implement it and interop. > > > > > > Don't take me wrong: I don't have any solution, so I cannot expect > > anything to be experimental ... But THERE ARE solutions, > and all of them > > address distinct and complementary issues. The purpose of this > > discussion and draft-montavont is to come to an agreement > on what is > > needed so that all the parties involved can work on a > single solution. > > The need WG directive to achieve this. Designing a single > specification > > is clearly a WG task. > > > > > >>>Anyway, let's see why the other people are thinking. If > it happens that > >>>there is no room in this WG to deal with issue, I will most likely > >>>propose a BOF at Seoul Meeting (and, well, this might not > be a bad idea, > >>>because the benefit of having several interfaces [either > actual, or > >>>virtual] could be shared by both Fixed Nodes and Mobile > Nodes (I'm not > >>>exclusively thinking about NEMO, although the idea comes > from there]). > >>>The reason I have not yet pushed toward a new WG is > because there are > >>>already many WGs. > >> > >>Well, please do intiate a discussion on this topic to determine > >> - the interest > >> - how vital is this for IPv6 mobility > > > > > >>>In conclusion, may I request a short slot to deal the > issue (not the > >>>solutions) during the meeting, please, so that we come to > a WG consensus > >>>and act upon it ? > >> > >>Sure, but first you have to demonstrate via the ML that > there is some > >>interest in this topic. If you can do that in the next > week or so, we > >>can include it on the agenda. > > > > > > This discussion is already initiated, and several people > have already > > answered. I don't think it's necessary to demonstrate how > vital it is > > for IPv6 mobility (could you by the way demonstrate how > vital Mobile > > IPv6 is ? What about RO ? Just kidding); simply demonstrating the > > interest of people to work on this is enough. So, I will > let the other > > intereted ML members with some space to pop up on the ML. > > > > Thierry. > > > > > > > > > > > > > > _______________________________________________ > > Mip6 mailing list > > Mip6@ietf.org > > https://www.ietf.org/mailman/listinfo/mip6 > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 06:06:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01211 for ; Sat, 25 Oct 2003 06:06:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLJ9-0005SJ-R9 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 06:06:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PA67Ni020965 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 06:06:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLJ9-0005RF-KE for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 06:06:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01186 for ; Sat, 25 Oct 2003 06:05:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADLJ2-0003QN-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 06:06:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADLJ2-0003QH-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 06:06:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLJ4-0005NF-Fs; Sat, 25 Oct 2003 06:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLIh-0005Iy-8p for mip6@optimus.ietf.org; Sat, 25 Oct 2003 06:05:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01170; Sat, 25 Oct 2003 06:05:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADLId-0003Q3-00; Sat, 25 Oct 2003 06:05:35 -0400 Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1ADLIc-0003Q0-00; Sat, 25 Oct 2003 06:05:35 -0400 Message-ID: <04b601c39adf$93c2af60$896015ac@dclkempt40> From: "James Kempf" To: , Cc: "Kempf" Date: Sat, 25 Oct 2003 03:05:48 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Bar BOF on Multilink Flows Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Folks, There's been some discussion over the last couple days about multiple interfaces and Mobile IP, however, I think this may be just one piece of a larger problem: how to utilize multiple wireless links to achieve more robustness for logical flows. The best example application I've seen on this so far is an MPEG compressed video session, in which a base layer is sent over a cellular link with wide geographical availability, while hotspot links are utilized as they become available for additional layers to increase fidelity. The advantage of this over handing over the entire flow is that the handover signaling might get cut off by movement out of the hotspot, causing the stream to drop momentarily; whereas, if multiple links are utilized, there is just a reduction in quality when the hotspot stream drops. Here's the drafts I've found that deal with some part of this issue: draft-nomadv6-mobileip-filters-00.txt draft-soliman-mobileip-flow-move-04.txt (expired) draft-elmalki-mobileip-bicasting-v6-04.txt (expired) draft-matsuoka-multilink-transport-00.txt I believe SCTP declined to allow multilink flows, and I'd like to understand why. Multilink Mobile IP may be one part of the solution, but also some kind of striping transport protocol (on which there has been some research) might be part. Or, it might also be the case that the problem domain is so restricted that it should just be left up to the application. In any event, I'd like to organize a bar BOF on Monday night after the evening session, 10 PM, meet at the IETF registration desk. Anybody up for it? jak _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 06:24:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01570 for ; Sat, 25 Oct 2003 06:24:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLaU-0007Iw-5P for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 06:24:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PAO2N3028072 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 06:24:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLaU-0007Ih-15 for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 06:24:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01558 for ; Sat, 25 Oct 2003 06:23:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADLaQ-0003aR-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 06:23:58 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADLaP-0003aN-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 06:23:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLaT-0007I1-3K; Sat, 25 Oct 2003 06:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADLaJ-0007Gm-7Y for mip6@optimus.ietf.org; Sat, 25 Oct 2003 06:23:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01545 for ; Sat, 25 Oct 2003 06:23:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADLaE-0003aC-00 for mip6@ietf.org; Sat, 25 Oct 2003 06:23:46 -0400 Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 1ADLa3-0003Zx-00 for mip6@ietf.org; Sat, 25 Oct 2003 06:23:35 -0400 Received: (qmail 29660 invoked for bounce); 25 Oct 2003 10:23:42 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (noel@unknown) by unknown with RC4-MD5 encrypted SMTP; 25 Oct 2003 10:23:42 -0000 Message-ID: <3F9A4F22.3050508@dpt-info.u-strasbg.fr> Date: Sat, 25 Oct 2003 12:23:30 +0200 From: Thomas Noel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030829 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: James Kempf CC: mip4@ietf.org, mip6@ietf.org Subject: Re: [Mip6] Bar BOF on Multilink Flows References: <04b601c39adf$93c2af60$896015ac@dclkempt40> In-Reply-To: <04b601c39adf$93c2af60$896015ac@dclkempt40> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi James, Good idea , > Here's the drafts I've found that deal with some part of this issue: > > draft-nomadv6-mobileip-filters-00.txt > draft-soliman-mobileip-flow-move-04.txt (expired) > draft-elmalki-mobileip-bicasting-v6-04.txt (expired) > draft-matsuoka-multilink-transport-00.txt There are several other drafts on this topics : - draft-wakikawa-mobileip-multiplecoa-02.txt - draft-montavont-mip6-mmi-01.txt - draft-montavont-mobileip-multihoming-pb-statement-00.txt - draft-montavont-mobileip-ha-filtering-v6-00.txt Thomas > Here's the drafts I've found that deal with some part of this issue: > > draft-nomadv6-mobileip-filters-00.txt > draft-soliman-mobileip-flow-move-04.txt (expired) > draft-elmalki-mobileip-bicasting-v6-04.txt (expired) > draft-matsuoka-multilink-transport-00.txt > > I believe SCTP declined to allow multilink flows, and I'd like to understand > why. Multilink Mobile IP may be one part of the solution, but also some kind > of striping transport protocol (on which there has been some research) might > be part. Or, it might also be the case that the problem domain is so > restricted that it should just be left up to the application. > > In any event, I'd like to organize a bar BOF on Monday night after the > evening session, 10 PM, meet at the IETF registration desk. Anybody up for > it? > > jak > > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 07:11:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02599 for ; Sat, 25 Oct 2003 07:11:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADMK2-0003cJ-Pk for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 07:11:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PBB68f013889 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 07:11:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADMK2-0003bo-Eq for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 07:11:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02584 for ; Sat, 25 Oct 2003 07:10:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADMJy-00041t-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 07:11:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADMJx-00041p-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 07:11:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADMJx-0003b2-Pm; Sat, 25 Oct 2003 07:11:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADMJd-0003Zy-55 for mip6@optimus.ietf.org; Sat, 25 Oct 2003 07:10:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02581; Sat, 25 Oct 2003 07:10:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADMJY-00041m-00; Sat, 25 Oct 2003 07:10:36 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1ADMJY-00041i-00; Sat, 25 Oct 2003 07:10:36 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RDJTY>; Sat, 25 Oct 2003 07:09:58 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922E1A@ftmail.lab.flarion.com> From: Soliman Hesham To: "'James Kempf'" , mip4@ietf.org, mip6@ietf.org Subject: RE: [Mip6] Bar BOF on Multilink Flows Date: Sat, 25 Oct 2003 07:09:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > I believe SCTP declined to allow multilink flows, and I'd > like to understand > why. => I don't know why they did it, but in general it's a good idea to keep traffic that belongs to the same connection, one a single path. Things are a bit more robust and predictable this way. Multilink Mobile IP may be one part of the solution, > but also some kind > of striping transport protocol (on which there has been some > research) might > be part. Or, it might also be the case that the problem domain is so > restricted that it should just be left up to the application. > > In any event, I'd like to organize a bar BOF on Monday night > after the > evening session, 10 PM, meet at the IETF registration desk. > Anybody up for > it? => Good idea, I hope you plan to send minutes. I won't be able to attend this IETF. Hesham _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 14:29:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11612 for ; Sat, 25 Oct 2003 14:29:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADT9r-0005yl-6T for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 14:29:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PIT3Yf022977 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 14:29:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADT9q-0005yQ-Vr for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 14:29:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11605 for ; Sat, 25 Oct 2003 14:28:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADT9o-0000sN-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 14:29:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADT9o-0000sJ-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 14:29:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADT9o-0005xH-Rf; Sat, 25 Oct 2003 14:29:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADT9h-0005ub-3W for mip6@optimus.ietf.org; Sat, 25 Oct 2003 14:28:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11593 for ; Sat, 25 Oct 2003 14:28:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADT9e-0000rx-00 for mip6@ietf.org; Sat, 25 Oct 2003 14:28:50 -0400 Received: from h195n1fls311o871.telia.com ([213.64.174.195] helo=riesling.local.levkowetz.com) by ietf-mx with smtp (Exim 4.12) id 1ADT9d-0000rr-00 for mip6@ietf.org; Sat, 25 Oct 2003 14:28:49 -0400 Received: (qmail 8986 invoked from network); 25 Oct 2003 18:28:44 -0000 Received: from unknown (HELO riesling) (127.0.0.1) by localhost with SMTP; 25 Oct 2003 18:28:44 -0000 Date: Sat, 25 Oct 2003 20:28:42 +0200 From: Henrik Levkowetz To: "James Kempf" Cc: , , "Kempf" Message-Id: <20031025202842.651051b9.henrik@levkowetz.com> In-Reply-To: <04b601c39adf$93c2af60$896015ac@dclkempt40> References: <04b601c39adf$93c2af60$896015ac@dclkempt40> X-Mailer: Sylpheed version 0.9.5claws (GTK+ 1.2.10; i386-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Multipart_Sat__25_Oct_2003_20_28_42_+0200_=.30yA2mBZEN88yJ" Subject: [Mip6] Re: [Mip4] Bar BOF on Multilink Flows Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --Multipart_Sat__25_Oct_2003_20_28_42_+0200_=.30yA2mBZEN88yJ Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Sounds interesting. I'll be there. Henrik Saturday 25 October 2003, James wrote: > Folks, > > There's been some discussion over the last couple days about multiple > interfaces and Mobile IP, however, I think this may be just one piece of a > larger problem: how to utilize multiple wireless links to achieve more > robustness for logical flows. The best example application I've seen on this > so far is an MPEG compressed video session, in which a base layer is sent > over a cellular link with wide geographical availability, while hotspot > links are utilized as they become available for additional layers to > increase fidelity. The advantage of this over handing over the entire flow > is that the handover signaling might get cut off by movement out of the > hotspot, causing the stream to drop momentarily; whereas, if multiple links > are utilized, there is just a reduction in quality when the hotspot stream > drops. > > Here's the drafts I've found that deal with some part of this issue: > > draft-nomadv6-mobileip-filters-00.txt > draft-soliman-mobileip-flow-move-04.txt (expired) > draft-elmalki-mobileip-bicasting-v6-04.txt (expired) > draft-matsuoka-multilink-transport-00.txt > > I believe SCTP declined to allow multilink flows, and I'd like to understand > why. Multilink Mobile IP may be one part of the solution, but also some kind > of striping transport protocol (on which there has been some research) might > be part. Or, it might also be the case that the problem domain is so > restricted that it should just be left up to the application. > > In any event, I'd like to organize a bar BOF on Monday night after the > evening session, 10 PM, meet at the IETF registration desk. Anybody up for > it? > > jak > > > > > -- > Mip4 mailing list > Mip4@ietf.org > https://www.ietf.org/mailman/listinfo/mip4 > --Multipart_Sat__25_Oct_2003_20_28_42_+0200_=.30yA2mBZEN88yJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/msDbeVhrtTJkXCMRAjzWAJoCZE15+HFYpivRV8o5ROpNqKN6DgCffieD 9vo5wtBcXtP36Wfo0OosPEs= =M4aB -----END PGP SIGNATURE----- --Multipart_Sat__25_Oct_2003_20_28_42_+0200_=.30yA2mBZEN88yJ-- _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sat Oct 25 18:32:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18797 for ; Sat, 25 Oct 2003 18:32:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADWx0-0007vo-AU for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 18:32:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9PMW2kL030482 for mip6-archive@odin.ietf.org; Sat, 25 Oct 2003 18:32:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADWx0-0007vZ-4T for mip6-web-archive@optimus.ietf.org; Sat, 25 Oct 2003 18:32:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18789 for ; Sat, 25 Oct 2003 18:31:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADWwx-0003eo-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 18:31:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADWww-0003el-00 for mip6-web-archive@ietf.org; Sat, 25 Oct 2003 18:31:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADWwy-0007vA-RA; Sat, 25 Oct 2003 18:32:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADWwc-0007uX-Tw for mip6@optimus.ietf.org; Sat, 25 Oct 2003 18:31:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18786 for ; Sat, 25 Oct 2003 18:31:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADWwZ-0003eN-00 for mip6@ietf.org; Sat, 25 Oct 2003 18:31:35 -0400 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1ADWwZ-0003dn-00 for mip6@ietf.org; Sat, 25 Oct 2003 18:31:35 -0400 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9PMUxg29829; Sat, 25 Oct 2003 15:30:59 -0700 X-mProtect: <200310252230> Nokia Silicon Valley Messaging Protection Received: from danira-pool050172.americas.nokia.com (10.241.50.172, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdShn8pu; Sat, 25 Oct 2003 15:30:58 PDT Message-ID: <3F9AF997.2020203@iprg.nokia.com> Date: Sat, 25 Oct 2003 15:30:47 -0700 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Soliman Hesham CC: Thierry Ernst , mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <748C6D0A58C0F94CA63C198B6674697A01922E18@ftmail.lab.flarion.com> In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922E18@ftmail.lab.flarion.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Soliman Hesham wrote: > > Thierry, > > > > I wish you had bought this up a month ago when the MIP6 > > charter was being discussed. we could have added multi- > > homed (or more explicitly multi-interface) mobile nodes > > to the charter. > > => FWIW, he did bring it up you missed the point. there is a big difference between bringing it up and generating interest in the WG. > and so did I (In Minneapolis > meeting 2001 and it got delayed because of the MIPv6 debacle) > and a few other people. so? without MIPv6 being standardized first, there was no point talking about multiple interfaces and multiple flows. Vijay ps: FWIW, I support adding multi-homed mobile nodes to the charter. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sun Oct 26 00:24:35 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24963 for ; Sun, 26 Oct 2003 00:24:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADcRq-0001mM-K1 for mip6-archive@odin.ietf.org; Sun, 26 Oct 2003 00:24:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9Q4OEhw006832 for mip6-archive@odin.ietf.org; Sun, 26 Oct 2003 00:24:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADcRp-0001m2-Tx for mip6-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 00:24:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24901 for ; Sun, 26 Oct 2003 00:24:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADcRn-0006o1-00 for mip6-web-archive@ietf.org; Sun, 26 Oct 2003 00:24:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADcRm-0006nZ-00 for mip6-web-archive@ietf.org; Sun, 26 Oct 2003 00:24:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADcRi-0001i4-Oi; Sun, 26 Oct 2003 00:24:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADbwF-0006Pl-QV for mip6@optimus.ietf.org; Sat, 25 Oct 2003 23:51:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24333 for ; Sat, 25 Oct 2003 23:51:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADbwD-0006Pm-00 for mip6@ietf.org; Sat, 25 Oct 2003 23:51:33 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 1ADbwD-0006Oa-00 for mip6@ietf.org; Sat, 25 Oct 2003 23:51:33 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <497RDKRC>; Sat, 25 Oct 2003 23:50:57 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922E1C@ftmail.lab.flarion.com> From: Soliman Hesham To: "'Vijay Devarapalli'" Cc: Thierry Ernst , mip6@ietf.org Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Sat, 25 Oct 2003 23:50:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > > => FWIW, he did bring it up > > you missed the point. there is a big difference between > bringing it up and generating interest in the WG. => I think you missed a few emails! There is clear interest in the WG. In fact, I haven't seen one email objecting to this topic being added (except Raj's last email). > > > and so did I (In Minneapolis > > meeting 2001 and it got delayed because of the MIPv6 debacle) > > and a few other people. > > so? without MIPv6 being standardized first, there was no > point talking about multiple interfaces and multiple flows. => Now it's done. So let's talk. > ps: FWIW, I support adding multi-homed mobile nodes to the > charter. => Great. Hesham _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Sun Oct 26 22:10:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09661 for ; Sun, 26 Oct 2003 22:10: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 1ADxlg-0007VO-E9 for mip6-archive@odin.ietf.org; Sun, 26 Oct 2003 22:10:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R3A8eM028844 for mip6-archive@odin.ietf.org; Sun, 26 Oct 2003 22:10:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADxlg-0007V9-96 for mip6-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 22:10: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 WAA09654 for ; Sun, 26 Oct 2003 22:09:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADxld-00059m-00 for mip6-web-archive@ietf.org; Sun, 26 Oct 2003 22:10:05 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1ADxlc-00059i-00 for mip6-web-archive@ietf.org; Sun, 26 Oct 2003 22:10:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADxlb-0007Tm-0W; Sun, 26 Oct 2003 22:10:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1ADxl5-0007Rt-Q2 for mip6@optimus.ietf.org; Sun, 26 Oct 2003 22:09:31 -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 WAA09642; Sun, 26 Oct 2003 22:09:18 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ADxl2-00059L-00; Sun, 26 Oct 2003 22:09:28 -0500 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1ADxl1-000599-00; Sun, 26 Oct 2003 22:09:28 -0500 Received: from huez (net56-dhcp-760.sfc.keio.ac.jp [133.27.59.248]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 5C32D5D084; Mon, 27 Oct 2003 12:08:56 +0900 (JST) Date: Sun, 26 Oct 2003 23:46:48 +0900 From: Thierry Ernst To: "James Kempf" Cc: mip4@ietf.org, mip6@ietf.org, kempf@docomolabs-usa.com Subject: Re: [Mip6] Bar BOF on Multilink Flows Message-Id: <20031026234648.1b761564.ernst@sfc.wide.ad.jp> In-Reply-To: <04b601c39adf$93c2af60$896015ac@dclkempt40> References: <04b601c39adf$93c2af60$896015ac@dclkempt40> Organization: Keio University X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi James, > In any event, I'd like to organize a bar BOF on Monday night after the > evening session, 10 PM, meet at the IETF registration desk. Anybody up for > it? Of course I would be up for it (since I raised the idea in a previous mail :-), but: - I would prefer to raise the issue in the MIP6 WG first, and call for a bar BOF after, depending on the discussion, - I guess there were valuable reasons behing splitting mobile IP in two (I mean IPv4 and IPv6), and the same would apply here, - If BOF there is, it should not only cover MNs, but also fixed nodes because those too may have to deal with dual interfaces. Thierry. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 02:57:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29954 for ; Mon, 27 Oct 2003 02: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 1AE2FM-00030Z-JO for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 02:57:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R7v4JP011556 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 02:57:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE2FM-00030J-Dy for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 02:57: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 CAA29947 for ; Mon, 27 Oct 2003 02:56:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE2FI-0000YV-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 02:57:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AE2FI-0000YS-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 02:57:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE2FK-0002y0-B7; Mon, 27 Oct 2003 02:57:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE2Ed-0002vD-K7 for mip6@optimus.ietf.org; Mon, 27 Oct 2003 02:56: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 CAA29930; Mon, 27 Oct 2003 02:56:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE2EZ-0000Xt-00; Mon, 27 Oct 2003 02:56:15 -0500 Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1AE2EU-0000X7-00; Mon, 27 Oct 2003 02:56:10 -0500 Message-ID: <00da01c39c5f$bdf593c0$3d6015ac@dclkempt40> From: "James Kempf" To: "Thierry Ernst" Cc: , References: <04b601c39adf$93c2af60$896015ac@dclkempt40> <20031026234648.1b761564.ernst@sfc.wide.ad.jp> Subject: Re: [Mip6] Bar BOF on Multilink Flows Date: Sun, 26 Oct 2003 23:55:49 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thierry, If the WG chairs agree, then by all means raise the issue in the MIP6 WG. The bar BOF is intended to examine more archiectural questions: why did multilink flows get pulled out of SCTP, has anything changed in the application space (especially with wireless) to make them more attractive or is there new research that characterizes them better, how should the functionality be partitioned between layers if it looks like a good idea, etc. I would guess Mobile IP support for multiple interfaces will come up, but its not the only topic I'd like to see discussed, and I don't see the architectural question restricted just to IPv6 at this point. It seems you've got a more narrowly focussed agenda, just Mobile IPv6 or maybe just IPv6 at the network layer. You're welcome to come to the bar BOF too, and I've heard enough interest expressed in the more general discussion that I'm convinced its a good idea to discuss it, so I'd like to hold the bar BOF regardless of what the MIP chairs agree to. Whether the discussion goes beyond that is an open question at this point. jak ----- Original Message ----- From: "Thierry Ernst" To: "James Kempf" Cc: ; ; Sent: Sunday, October 26, 2003 6:46 AM Subject: Re: [Mip6] Bar BOF on Multilink Flows > > Hi James, > > > In any event, I'd like to organize a bar BOF on Monday night after the > > evening session, 10 PM, meet at the IETF registration desk. Anybody up for > > it? > > Of course I would be up for it (since I raised the idea in a previous > mail :-), but: > > - I would prefer to raise the issue in the MIP6 WG first, and call for a > bar BOF after, depending on the discussion, > > - I guess there were valuable reasons behing splitting mobile IP in two > (I mean IPv4 and IPv6), and the same would apply here, > > - If BOF there is, it should not only cover MNs, but also fixed nodes > because those too may have to deal with dual interfaces. > > Thierry. > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 03:58:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01921 for ; Mon, 27 Oct 2003 03:58: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 1AE3CN-0000Io-Mf for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 03:58:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R8w3DJ001118 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 03:58:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE3CN-0000Hh-21 for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 03:58: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 DAA01902 for ; Mon, 27 Oct 2003 03:57:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE3CK-0001JP-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 03:58:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AE3CK-0001JM-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 03:58:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE3CK-0000Gk-PR; Mon, 27 Oct 2003 03:58:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE3Bx-0000Ef-Sj for mip6@optimus.ietf.org; Mon, 27 Oct 2003 03:57:37 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01876; Mon, 27 Oct 2003 03:57:26 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE3Bv-0001J3-00; Mon, 27 Oct 2003 03:57:35 -0500 Received: from email10.etsi.org ([212.234.161.112] helo=email10.etsihq.org) by ietf-mx with esmtp (Exim 4.12) id 1AE3Bu-0001IM-00; Mon, 27 Oct 2003 03:57:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] Mobile IPv6 Interop Testing Draft Date: Mon, 27 Oct 2003 09:57:03 +0100 Message-ID: <4091553999CBE4409CC2B562152B5A3302CFFBB5@email10.etsihq.org> Thread-Topic: [Mip6] Mobile IPv6 Interop Testing Draft Thread-Index: AcOXMzLqNZag6DCzSdCH20Q5Y7v6RgFNM1Mg From: "Maeva Petitjean" To: "Samita Chakrabarti" , , Cc: =?us-ascii?Q?Patrick_Rene_Guillemin?= Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Dear Samita, dear all, I am currently working on the Remote tests MIP6 web site, and I need to understand a few details in order to build the site : In the draft-kniveton-mipv6-remote-testing-00.txt, we have the following : 5.3.1. Home Agent - Company and contact information - Home agent IPv6 address and the corresponding IPv4 addresses (if dual stack) --> Is there more than one corresponding IPv4 address for one IPv6 address ? - List of home-addresses it assigns. This list must also indicate which home-addresses are presently used and which are available. Example: HOA1 (used by KEIO Univ.- contact name) HOA2 (available) HOA3 (available) --> Is there more than one home-address for one home agent ? Best regards, Maeva Petitjean,=20 ETSI Plugtests -----Original Message----- From: Samita Chakrabarti [mailto:Samita.Chakrabarti@eng.sun.com] Sent: 20 October 2003 19:54 To: mip6@ietf.org; mipshop@ietf.org Subject: [Mip6] Mobile IPv6 Interop Testing Draft As per Basavaraj Patil's recommendation, a mip6-interop design team has been formed and the team has worked on producing the first draft on the Mobile IPv6 remote interop testing requirements, scenarios and procedures. The draft has been submitted as an individual draft for now, but it is targeting to be a working group draft in the next revision. It is available through T.J Kniveton's webpage until the draft becomes available at the IETF directory. http://www.mipv6.org/specs/draft-kniveton-mipv6-remote-testing-00.txt Thanks. The mip6-interop design team. T.J Kniveton, Basavaraj Patil, Hesham Soliman, Henrik Petander, Samita Chakrabarti _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 05:02:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04510 for ; Mon, 27 Oct 2003 05:02:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE4CL-0005zc-MJ for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 05:02:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RA25Ki023036 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 05:02:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE4CK-0005zT-Ie for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 05:02: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 FAA04483 for ; Mon, 27 Oct 2003 05:01:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE4CH-0002BE-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 05:02:01 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AE4CG-0002BB-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 05:02:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE4CG-0005z0-Rc; Mon, 27 Oct 2003 05:02:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE4BW-0005y7-EJ for mip6@optimus.ietf.org; Mon, 27 Oct 2003 05:01: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 FAA04468 for ; Mon, 27 Oct 2003 05:01:02 -0500 (EST) From: xiaobao.chen@orange.co.uk Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE4BT-0002As-00 for mip6@ietf.org; Mon, 27 Oct 2003 05:01:11 -0500 Received: from mail32.messagelabs.com ([62.173.108.211]) by ietf-mx with smtp (Exim 4.12) id 1AE4BS-0002Ag-00 for mip6@ietf.org; Mon, 27 Oct 2003 05:01:10 -0500 X-VirusChecked: Checked X-Env-Sender: xiaobao.chen@orange.co.uk X-Msg-Ref: server-12.tower-32.messagelabs.com!1067248833!2790642 X-StarScan-Version: 5.1.9.3; banners=-,-,- Received: (qmail 16129 invoked from network); 27 Oct 2003 10:00:33 -0000 Received: from smtpout11.orange.co.uk (HELO dumbledore.orange.co.uk) (193.35.135.134) by server-12.tower-32.messagelabs.com with SMTP; 27 Oct 2003 10:00:33 -0000 Received: from bit.orange.co.uk (bit.orange.co.uk) by dumbledore.orange.co.uk (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Mon, 27 Oct 2003 10:00:33 +0000 Received: from ruddick (notes-gw.orange.co.uk [172.16.133.18]) by bit.orange.co.uk with SMTP id h9RA0Vw08755; Mon, 27 Oct 2003 10:00:31 GMT X-Lotus-FromDomain: HTLUK To: Vijay Devarapalli cc: Thierry Ernst , Basavaraj.Patil@nokia.com, mip6@ietf.org, martin.harris@orange.co.uk, nick.sampson@orange.co.uk, sulina.connal@orange.co.uk Message-ID: <80256DCC.00370607.00@ruddick> Date: Mon, 27 Oct 2003 10:03:44 +0000 Subject: [Mip6] Draft Agenda for WG meeting at IETF58 in relation to 3G Mime-Version: 1.0 Content-type: text/plain; charset="us-ascii" Content-Disposition: inline Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Vijay and all, It is stated in the charter that "The primary goal of the MIP6 working group will be to enhance base IPv6 mobility by continuing work on developments that are required for wide-scale deployments." I assume that the "the developments that are required for wide-scale deployments" include the issues of deploying Mobile IPv6 in 3G. Regards, Xiaobao Chen Orange PCS Ltd. Email:xiaobao.chen@orange.co.uk From: Vijay Devarapalli on 24/10/2003 19:52 To: Thierry Ernst @SMTP@Exchange cc: Basavaraj.Patil@nokia.com@SMTP@Exchange mip6@ietf.org@SMTP@Exchange Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 now the charter is finalised, there are work items and the schedule to complete the work items on the charter is very aggresive. see http://www.ietf.org/html.charters/mip6-charter.html. there is nothing wrong when Raj said he didnt see any interest for multi-homed mobile nodes. nobody bought them up when the charter was being discussed. Vijay ps: I am not against including multi-homed mobile nodes in the charter. infact I think we should work on them. Thierry Ernst wrote: > Hi Basavaraj, > > I find your answer amazing... > > Given the fact the MIP6 WG is a new group, I find it very appropriate to > discuss the missions of the WG right now. Also, I would find very > appropriate to raise the issue at the meeting to see how many people > have interest in this. If only a minority has, so, very fine, it means > it's not considered important. Demonstration done. > > >>>In the second place, there are a few drafts turning around this issues, >>>and drafts have been submitted regularly for a few years. So, given the >>>number of drafts and period of effect, I find it rather important. On a >>>personal side, I would like to see something coming up from this >>>activity so that we can implement a common solution, no doing our own >>>cooking in our lab. >> >>I am aware of the various drafts addressing this. But I do not see why >>this is a critical need for the WG to take on at this time. I do not >>for example see a large number of people in the WG demanding that this > > > Please specify: how many people is considered "large" ? > > >>be a work item because it is absolutely a MUST for mobile IPv6 to be >>deployed. What you are cooking in your lab may be interesting but is >>not necessarily needed by the industry at this time. > > > Huh ? The industry your are refering too is not the same as the one I'm > involved in. The fact that I work for a University doesn't necessarily > make me unaware of business realities. > > >>So if you believe >>that there is interest in this work, the I-D can always be >>standardized as Experimental (without WG intervention) which would let >>the people with common interests implement it and interop. > > > Don't take me wrong: I don't have any solution, so I cannot expect > anything to be experimental ... But THERE ARE solutions, and all of them > address distinct and complementary issues. The purpose of this > discussion and draft-montavont is to come to an agreement on what is > needed so that all the parties involved can work on a single solution. > The need WG directive to achieve this. Designing a single specification > is clearly a WG task. > > >>>Anyway, let's see why the other people are thinking. If it happens that >>>there is no room in this WG to deal with issue, I will most likely >>>propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >>>because the benefit of having several interfaces [either actual, or >>>virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >>>exclusively thinking about NEMO, although the idea comes from there]). >>>The reason I have not yet pushed toward a new WG is because there are >>>already many WGs. >> >>Well, please do intiate a discussion on this topic to determine >> - the interest >> - how vital is this for IPv6 mobility > > >>>In conclusion, may I request a short slot to deal the issue (not the >>>solutions) during the meeting, please, so that we come to a WG consensus >>>and act upon it ? >> >>Sure, but first you have to demonstrate via the ML that there is some >>interest in this topic. If you can do that in the next week or so, we >>can include it on the agenda. > > > This discussion is already initiated, and several people have already > answered. I don't think it's necessary to demonstrate how vital it is > for IPv6 mobility (could you by the way demonstrate how vital Mobile > IPv6 is ? What about RO ? Just kidding); simply demonstrating the > interest of people to work on this is enough. So, I will let the other > intereted ML members with some space to pop up on the ML. > > Thierry. > > > > > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 ******************************************************************************* Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. ******************************************************************************* _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 07:37:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09931 for ; Mon, 27 Oct 2003 07:37: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 1AE6cJ-0005Vh-5g for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 07:37:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RCb2vo021165 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 07:37:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE6cI-0005V5-LQ for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 07:37: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 HAA09889 for ; Mon, 27 Oct 2003 07:36:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE6cI-0004Fh-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 07:37:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AE6cH-0004Fe-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 07:37:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AE6cH-0005To-1S; Mon, 27 Oct 2003 07: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 1AE6bI-0005Ou-Lu for mip6@optimus.ietf.org; Mon, 27 Oct 2003 07:36: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 HAA09846; Mon, 27 Oct 2003 07:35:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AE6bH-0004Eo-00; Mon, 27 Oct 2003 07:35:59 -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 1AE6bH-0004Ej-00; Mon, 27 Oct 2003 07:35:59 -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 h9RCZFQ32451; Mon, 27 Oct 2003 13:35:15 +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: "'James Kempf'" , "'Thierry Ernst'" Cc: , , =?iso-8859-1?Q?Carmelita_G=F6rg?= Subject: AW: [Mip6] Bar BOF on Multilink Flows Date: Mon, 27 Oct 2003 13:35:16 +0100 Message-ID: <001001c39c86$c6b24b30$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 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <00da01c39c5f$bdf593c0$3d6015ac@dclkempt40> Importance: Normal Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hello James, It is a good idea, arranging a Bar BOF to discuss Multiple Links. We = will=20 gladly participate. Most of the authors of drafts that you and Thomas have listed = contributed to the ML discussion on following subjects in July. new I-D on HA filtering multiple CoAs registration Hope to discuss them in a useful way, as you suggested. Regards, Koojana > -----Urspr=FCngliche Nachricht----- > Von: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] Im Auftrag von = James > Kempf > Gesendet: Montag, 27. Oktober 2003 08:56 > An: Thierry Ernst > Cc: mip4@ietf.org; mip6@ietf.org > Betreff: Re: [Mip6] Bar BOF on Multilink Flows >=20 > Thierry, >=20 > If the WG chairs agree, then by all means raise the issue in the MIP6 = WG. > The bar BOF is intended to examine more archiectural questions: why = did > multilink flows get pulled out of SCTP, has anything changed in the > application space (especially with wireless) to make them more = attractive > or > is there new research that characterizes them better, how should the > functionality be partitioned between layers if it looks like a good = idea, > etc. I would guess Mobile IP support for multiple interfaces will come = up, > but its not the only topic I'd like to see discussed, and I don't see = the > architectural question restricted just to IPv6 at this point. >=20 > It seems you've got a more narrowly focussed agenda, just Mobile IPv6 = or > maybe just IPv6 at the network layer. You're welcome to come to the = bar > BOF > too, and I've heard enough interest expressed in the more general > discussion > that I'm convinced its a good idea to discuss it, so I'd like to hold = the > bar BOF regardless of what the MIP chairs agree to. Whether the = discussion > goes beyond that is an open question at this point. >=20 > jak >=20 > ----- Original Message ----- > From: "Thierry Ernst" > To: "James Kempf" > Cc: ; ; > Sent: Sunday, October 26, 2003 6:46 AM > Subject: Re: [Mip6] Bar BOF on Multilink Flows >=20 >=20 > > > > Hi James, > > > > > In any event, I'd like to organize a bar BOF on Monday night after = the > > > evening session, 10 PM, meet at the IETF registration desk. = Anybody up > for > > > it? > > > > Of course I would be up for it (since I raised the idea in a = previous > > mail :-), but: > > > > - I would prefer to raise the issue in the MIP6 WG first, and call = for a > > bar BOF after, depending on the discussion, > > > > - I guess there were valuable reasons behing splitting mobile IP in = two > > (I mean IPv4 and IPv6), and the same would apply here, > > > > - If BOF there is, it should not only cover MNs, but also fixed = nodes > > because those too may have to deal with dual interfaces. > > > > Thierry. > > >=20 >=20 > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 11:28:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23525 for ; Mon, 27 Oct 2003 11:28:24 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEADt-0004RD-NW for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 11:28:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RGS5K2017053 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 11:28:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEADt-0004Qy-Hd for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 11:28:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23512 for ; Mon, 27 Oct 2003 11:27:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEADs-0007f9-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 11:28:04 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEADs-0007f6-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 11:28:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEADp-0004QH-DC; Mon, 27 Oct 2003 11: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 1AEADe-0004Ph-VF for mip6@optimus.ietf.org; Mon, 27 Oct 2003 11:27: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 LAA23507 for ; Mon, 27 Oct 2003 11:27:39 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEADd-0007ez-00 for mip6@ietf.org; Mon, 27 Oct 2003 11:27:50 -0500 Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AEADd-0007eo-00 for mip6@ietf.org; Mon, 27 Oct 2003 11:27:49 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h9RGRAE16441; Mon, 27 Oct 2003 08:27:10 -0800 X-mProtect: <200310271627> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdUElUUz; Mon, 27 Oct 2003 08:27:09 PST Message-ID: <3F9D47F3.6070100@iprg.nokia.com> Date: Mon, 27 Oct 2003 08:29:39 -0800 From: Vijay Devarapalli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: xiaobao.chen@orange.co.uk CC: Basavaraj.Patil@nokia.com, mip6@ietf.org, martin.harris@orange.co.uk, nick.sampson@orange.co.uk, sulina.connal@orange.co.uk Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 in relation to 3G References: <80256DCC.00370607.00@ruddick> In-Reply-To: <80256DCC.00370607.00@ruddick> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit xiaobao.chen@orange.co.uk wrote: > Vijay and all, > > It is stated in the charter that "The primary goal of the MIP6 working group > will be to enhance base > IPv6 mobility by continuing work on developments that are required for > wide-scale deployments." I assume that the "the developments that are required > for wide-scale deployments" include the issues of deploying Mobile IPv6 in > 3G. yes, ofcourse. but I didnt get what you are trying to say. do you see issues in deploying Mobile IPv6 in 3G (pp/pp2)? if so, please bring them up either on the mailing list or in the WG meeting. IMO, fixing those issues is high priority. Vijay _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 13:16:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28101 for ; Mon, 27 Oct 2003 13: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 1AEBuO-0006RP-Qe for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 13:16:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RIG4NI024755 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 13:16:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEBuO-0006RC-LI for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 13:16: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 NAA28077 for ; Mon, 27 Oct 2003 13:15:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEBuM-0001PB-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 13:16:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEBuM-0001P8-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 13:16:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEBuM-0006Qd-Pk; Mon, 27 Oct 2003 13:16:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEBuJ-0006Pm-Uo for mip6@optimus.ietf.org; Mon, 27 Oct 2003 13:16: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 NAA28065 for ; Mon, 27 Oct 2003 13:15:46 -0500 (EST) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEBuH-0001Os-00 for mip6@ietf.org; Mon, 27 Oct 2003 13:15:57 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AEBuH-0001Op-00 for mip6@ietf.org; Mon, 27 Oct 2003 13:15:57 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9RIFuI29692 for ; Mon, 27 Oct 2003 20:15:56 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 27 Oct 2003 20:15:56 +0200 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 27 Oct 2003 10:15:54 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Mon, 27 Oct 2003 12:15:53 -0600 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOZ6fZN0MNqeocKTQqpY1BkYU5PGwCzFzUQ To: Cc: X-OriginalArrivalTime: 27 Oct 2003 18:15:54.0009 (UTC) FILETIME=[5C200890:01C39CB6] Content-Transfer-Encoding: quoted-printable Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Thierry, >Hi Basavaraj, > >I find your answer amazing... > >Given the fact the MIP6 WG is a new group, I find it very appropriate = to >discuss the missions of the WG right now. Also, I would find very >appropriate to raise the issue at the meeting to see how many people >have interest in this. If only a minority has, so, very fine, it means >it's not considered important. Demonstration done. As you note above, MIP6 is a new WG. What the WG ought to do was discussed at 2 BOFs (NSIIM at IETF56 and MIP6 at IETF57). The charter has been discussed at length and what you see now is the conclusion of those discussions in addition to the feedback from the IESG/IAB. Of course it does not imply that it is set in stone and no changes can be made. We can obviously look at what are the importnat issues that need to be dealt with for Mobile IPv6 and if there are missing pieces we can always recharter. The scope of the charter has been intentionally kept limited in order to ensure that only the most immediate problems are dealt with. IETF58 will be the first WG meeting for MIP6. The milestones are until Nov 04. It is very likely that we will see a recharter of this WG at IETF60. Hence I am not ruling out this work altogether, all I am saying is that the WG has an agenda and a roadmap and we will stick to that. So far the discussion on the ML has been more about the agenda itself and very little about the actual problem. If I can see some interest in the problem (by some I mean more than 5 people :) ), then we can consider it on the MIP6 agenda. Of course I am glad to see that there is a BoF to discuss this work. So there is an avenue to determine the interest already. > >> >In the second place, there are a few drafts turning around this = issues, >> >and drafts have been submitted regularly for a few years. So, given = the >> >number of drafts and period of effect, I find it rather important. = On a >> >personal side, I would like to see something coming up from this >> >activity so that we can implement a common solution, no doing our = own >> >cooking in our lab. >>=20 >> I am aware of the various drafts addressing this. But I do not see = why >> this is a critical need for the WG to take on at this time. I do not >> for example see a large number of people in the WG demanding that = this > >Please specify: how many people is considered "large" ? Large > 5 people (since in a given WG, there are very few active people and hence even if WG meetings have attendance of about 150~200 people or the number of people on ML is > 1000, large is relative) > >> be a work item because it is absolutely a MUST for mobile IPv6 to be >> deployed. What you are cooking in your lab may be interesting but is >> not necessarily needed by the industry at this time.=20 > >Huh ? The industry your are refering too is not the same as the one I'm >involved in. The fact that I work for a University doesn't necessarily >make me unaware of business realities. Of course not. I am sure that there is plenty of industry-university interaction for you to be aware of the business realities. > >> So if you believe >> that there is interest in this work, the I-D can always be >> standardized as Experimental (without WG intervention) which would = let >> the people with common interests implement it and interop. > >Don't take me wrong: I don't have any solution, so I cannot expect >anything to be experimental ... But THERE ARE solutions, and all of = them >address distinct and complementary issues. The purpose of this >discussion and draft-montavont is to come to an agreement on what is >needed so that all the parties involved can work on a single solution. >The need WG directive to achieve this. Designing a single specification >is clearly a WG task. > >> >Anyway, let's see why the other people are thinking. If it happens = that >> >there is no room in this WG to deal with issue, I will most likely >> >propose a BOF at Seoul Meeting (and, well, this might not be a bad = idea, >> >because the benefit of having several interfaces [either actual, or >> >virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm = not >> >exclusively thinking about NEMO, although the idea comes from = there]). >> >The reason I have not yet pushed toward a new WG is because there = are >> >already many WGs.=20 >>=20 >> Well, please do intiate a discussion on this topic to determine=20 >> - the interest >> - how vital is this for IPv6 mobility > >> >In conclusion, may I request a short slot to deal the issue (not the >> >solutions) during the meeting, please, so that we come to a WG = consensus >> >and act upon it ? >>=20 >> Sure, but first you have to demonstrate via the ML that there is some >> interest in this topic. If you can do that in the next week or so, we >> can include it on the agenda. > >This discussion is already initiated, and several people have already >answered. I don't think it's necessary to demonstrate how vital it is >for IPv6 mobility (could you by the way demonstrate how vital Mobile >IPv6 is ? What about RO ? Just kidding); simply demonstrating the >interest of people to work on this is enough. So, I will let the other >intereted ML members with some space to pop up on the ML. I am counting and watching the ML :) So far it is not very encouraging.=20 > >Thierry. > -Basavaraj _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 14:27:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02180 for ; Mon, 27 Oct 2003 14:27: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 1AED16-00069J-3j for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 14:27:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RJR46C023636 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 14:27:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AED15-000699-Uu for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 14:27: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 OAA02082 for ; Mon, 27 Oct 2003 14:26:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AED13-0002ek-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 14:27:01 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AED13-0002eh-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 14:27:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AED13-00067q-9y; Mon, 27 Oct 2003 14:27:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AED0F-000645-8G for mip6@optimus.ietf.org; Mon, 27 Oct 2003 14:26: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 OAA01953; Mon, 27 Oct 2003 14:25:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AED0C-0002c6-00; Mon, 27 Oct 2003 14:26:08 -0500 Received: from brmea-mail-2.sun.com ([192.18.98.43]) by ietf-mx with esmtp (Exim 4.12) id 1AED0B-0002bp-00; Mon, 27 Oct 2003 14:26:08 -0500 Received: from jurassic.eng.sun.com ([129.146.86.31]) by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id h9RJQ0Ph017167; Mon, 27 Oct 2003 12:26:00 -0700 (MST) Received: from shubho (shubho.Eng.Sun.COM [129.146.85.207]) by jurassic.eng.sun.com (8.12.10+Sun/8.12.10) with SMTP id h9RJQ0Gs685542; Mon, 27 Oct 2003 11:26:00 -0800 (PST) Message-Id: <200310271926.h9RJQ0Gs685542@jurassic.eng.sun.com> Date: Mon, 27 Oct 2003 11:27:18 -0800 (PST) From: Samita Chakrabarti Reply-To: Samita Chakrabarti Subject: Re: [Mipshop] RE: [Mip6] Mobile IPv6 Interop Testing Draft To: Maeva.Petitjean@etsi.org Cc: mip6@ietf.org, mipshop@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: zNWMfvjz4ydP8NW5HZtFPw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_31 SunOS 5.10 sun4u sparc Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > > 5.3.1. Home Agent > > - Company and contact information > > - Home agent IPv6 address and the corresponding IPv4 addresses (if > dual stack) > > --> Is there more than one corresponding IPv4 address for one IPv6 > address ? > Actually listing IPv4 addresses are not necessary. But sometimes knowing the corresponding IPv4 address helps in finding out whether the node is dead or having trouble with IPv6 connection. Thus one IPv4 address on the node should be fine, I think. > - List of home-addresses it assigns. This list must also indicate > which home-addresses are presently used and which are available. > Example: > HOA1 (used by KEIO Univ.- contact name) > HOA2 (available) > HOA3 (available) > > --> Is there more than one home-address for one home agent ? > Yes. It depends on the administrator of the home-agent. I assume, usually they would allow multiple mobile-nodes for testing. -Samita > > -----Original Message----- > From: Samita Chakrabarti [mailto:Samita.Chakrabarti@eng.sun.com] > Sent: 20 October 2003 19:54 > To: mip6@ietf.org; mipshop@ietf.org > Subject: [Mip6] Mobile IPv6 Interop Testing Draft > > > > As per Basavaraj Patil's recommendation, a mip6-interop > design team has been formed and the team has worked on producing > the first draft on the Mobile IPv6 remote interop testing > requirements, scenarios and procedures. > > The draft has been submitted as an individual draft for > now, but it is targeting to be a working group draft in > the next revision. It is available through T.J Kniveton's > webpage until the draft becomes available at the IETF directory. > > http://www.mipv6.org/specs/draft-kniveton-mipv6-remote-testing-00.txt > > > Thanks. > > The mip6-interop design team. > T.J Kniveton, > Basavaraj Patil, > Hesham Soliman, > Henrik Petander, > Samita Chakrabarti > > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ > Mipshop mailing list > Mipshop@ietf.org > https://www1.ietf.org/mailman/listinfo/mipshop > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Mon Oct 27 18:04:22 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25915 for ; Mon, 27 Oct 2003 18:04: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 1AEGP7-0004sV-5D for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 18:04:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RN45qC018750 for mip6-archive@odin.ietf.org; Mon, 27 Oct 2003 18:04:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGP6-0004sL-Ur for mip6-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 18:04: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 SAA25850 for ; Mon, 27 Oct 2003 18:03:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEGP4-0001PE-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 18:04:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEGP3-0001PB-00 for mip6-web-archive@ietf.org; Mon, 27 Oct 2003 18:04:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGP3-0004rq-34; Mon, 27 Oct 2003 18:04:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGOW-0004pc-Cx for mip6@optimus.ietf.org; Mon, 27 Oct 2003 18:03: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 SAA25812 for ; Mon, 27 Oct 2003 18:03:15 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEGOT-0001Ov-00 for mip6@ietf.org; Mon, 27 Oct 2003 18:03:25 -0500 Received: from smtp.polymtl.ca ([132.207.4.11] ident=0) by ietf-mx with esmtp (Exim 4.12) id 1AEGOS-0001Oo-00 for mip6@ietf.org; Mon, 27 Oct 2003 18:03:24 -0500 Received: from localhost (c4.si.polymtl.ca [132.207.4.29]) by smtp.polymtl.ca (8.12.10/8.12.10) with ESMTP id h9RN3NXF029384 for ; Mon, 27 Oct 2003 18:03:23 -0500 Received: from 132.207.67.78 ( [132.207.67.78]) as user stell@132.207.4.132 by www.imp.polymtl.ca with HTTP; Mon, 27 Oct 2003 18:03:23 -0500 Message-ID: <1067295803.3f9da43b40c51@www.imp.polymtl.ca> Date: Mon, 27 Oct 2003 18:03:23 -0500 From: Stephane Elleingand To: mip6@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 132.207.67.78 X-Poly-FromMTA: (c4.si.polymtl.ca [132.207.4.29]) at Mon, 27 Oct 2003 23:03:23 +0000 X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.22.0.1; VDF 6.22.0.17 Content-Transfer-Encoding: 8bit Subject: [Mip6] needs help with HMIPv6 Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi all i m graduate students of Ecole polytechnique of montreal working on mobile IPv6 and QoS... precisely with Hierchical Mobile IPv6. I understand pretty well how it(HMIPv6)works but i got issues to visualizes the different parts 1) The architecture of HMIPv6 contains: - some acces networks: with access routers (ARs) and access points (APs) does the acces networks include the MAP? in others words should i place the MAP in the Acces networks or at the edge of the IPv6 backbone network? - an IPv6 backbone networks : with Mobile-IPv6 routers does the backbone network include the MAP? - the Home Network: with the Home Agent (HA)+ HMIPv6-aware routers - the Correspondent node CN and the mobile node MN. in an HMIPv6 networks 2) How many access routers can a MAP support? 3) How many access points can an AR support? thank you in advance for your help. stephane _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Tue Oct 28 05:57:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15649 for ; Tue, 28 Oct 2003 05:57: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 1AERX5-00035P-TW for mip6-archive@odin.ietf.org; Tue, 28 Oct 2003 05:57:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SAv3Nf011853 for mip6-archive@odin.ietf.org; Tue, 28 Oct 2003 05:57:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AERX5-000356-NH for mip6-web-archive@optimus.ietf.org; Tue, 28 Oct 2003 05:57: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 FAA15618 for ; Tue, 28 Oct 2003 05:56:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AERX1-0000LR-00 for mip6-web-archive@ietf.org; Tue, 28 Oct 2003 05:57:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AERX1-0000LN-00 for mip6-web-archive@ietf.org; Tue, 28 Oct 2003 05:56:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AERX2-00033Z-T4; Tue, 28 Oct 2003 05:57:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AERWV-000318-U6 for mip6@optimus.ietf.org; Tue, 28 Oct 2003 05:56: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 FAA15584; Tue, 28 Oct 2003 05:56:15 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AERWS-0000KJ-00; Tue, 28 Oct 2003 05:56:24 -0500 Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47]) by ietf-mx with esmtp (Exim 4.12) id 1AERWR-0000KD-00; Tue, 28 Oct 2003 05:56:23 -0500 Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118]) by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id h9SAu1Ss007128; Tue, 28 Oct 2003 11:56:12 +0100 (MET) Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2655.55) id ; Tue, 28 Oct 2003 11:56:00 +0100 Message-ID: <37FB7AA6F5F9814FB634A7BF4C35A6F563989D@ESEALNT442.al.sw.ericsson.se> From: "Karim El-Malki (HF/EAB)" To: "'James Kempf'" , mip4@ietf.org, mip6@ietf.org Subject: RE: [Mip6] Bar BOF on Multilink Flows Date: Tue, 28 Oct 2003 11:55:43 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , > Here's the drafts I've found that deal with some part of this issue: > > draft-nomadv6-mobileip-filters-00.txt > draft-soliman-mobileip-flow-move-04.txt (expired) > draft-elmalki-mobileip-bicasting-v6-04.txt (expired) > draft-matsuoka-multilink-transport-00.txt The two expired drafts were not supposed to expire until Dec. 2003 but for some reason they have been removed. Resubmitted the bicasting draft but it hasn't been published yet. Missed the deadline for flow move draft but we will resubmit soon. Here's the links to the drafts for those who are interested: http://standards.ericsson.net/karim/draft-elmalki-mobileip-bicasting-v6-05.txt http://standards.ericsson.net/karim/draft-soliman-mobileip-flow-move-03.txt > In any event, I'd like to organize a bar BOF on Monday night > after the > evening session, 10 PM, meet at the IETF registration desk. > Anybody up for > it? It's a good idea but can't join since I won't be coming to ietf this time. Please send out the minutes. /Karim _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 29 04:58:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01008 for ; Wed, 29 Oct 2003 04:58: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 1AEn5b-0002wI-29 for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 04:58:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T9w6Yx011287 for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 04:58:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEn5a-0002v2-2m for mip6-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 04:58: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 EAA00975 for ; Wed, 29 Oct 2003 04:57:54 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEn5W-0005Jh-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 04:58:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEn5W-0005Je-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 04:58:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEn5V-0002sx-Ac; Wed, 29 Oct 2003 04:58:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEn5E-0002ry-LO for mip6@optimus.ietf.org; Wed, 29 Oct 2003 04:57: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 EAA00967; Wed, 29 Oct 2003 04:57:33 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEn5A-0005J9-00; Wed, 29 Oct 2003 04:57:40 -0500 Received: from omgo.iij.ad.jp ([202.232.30.157]) by ietf-mx with esmtp (Exim 4.12) id 1AEn59-0005J4-00; Wed, 29 Oct 2003 04:57:40 -0500 Received: from jc-smtp.iij.ad.jp ([192.168.176.35]) by omgo.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9T9vZFF015581; Wed, 29 Oct 2003 18:57:36 +0900 (JST) Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.65.65]) by jc-smtp.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9T9v7HY010496; Wed, 29 Oct 2003 18:57:08 +0900 (JST) Date: Wed, 29 Oct 2003 18:56:20 +0900 (JST) Message-Id: <20031029.185620.62826787.keiichi@iij.ad.jp> To: Samita.Chakrabarti@eng.sun.com Cc: mip6@ietf.org, mipshop@ietf.org Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft From: Keiichi SHIMA / =?iso-2022-jp?B?GyRCRWc3RDBsGyhC?= In-Reply-To: <200310241916.h9OJG1Gs118291@jurassic.eng.sun.com> References: <200310241916.h9OJG1Gs118291@jurassic.eng.sun.com> X-Mailer: Mew version 4.0.59 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, From: Samita Chakrabarti Subject: Re: [Mip6] Mobile IPv6 Interop Testing Draft Date: Fri, 24 Oct 2003 12:17:18 -0700 (PDT) > We need to discuss more and flush out the configuration of HA and > virtual home tunnel without changing the HA implementation. Working > group comments would be helpful for this. Yes, I agree that we need more discussion of the technology for emulating home networks over the Internet. > > If there is no physical home link, I think it is possible to configure. > > For example, > > > > +--+-+ IF1(200.0.0.1 - 100.0.0.1) > > | HA | P::1/64 (home address) > > +--+-+ > > IF2|200.0.0.1 > > | > > ((Internet)) > > | > > | > > ---+---------+------------ visited link of MN tester Q::/64 > > | > > |Q::100 (care-of address) > > IF1|100.0.0.1 > > +--+-+ > > | MN | IF2(100.0.0.1-200.0.0.1) > > +----+ > > > > In this case, I see no problem. However, this scenario requires as > > many home subnets as the number of mobile nodes, since HA must arrange > > different tunnel interface and home prefix for each mobile node. > > > > This scenario looks ok to me for adv. But not sure how HA would receive > packets from CN to relay to MN on a different tunnel. Are you considering any confliction between the tunnel described above and a tunnel which is used for non-route optimized traffic? If so, I think there is no problem. Logically, MN and HA will have two tunnel interfaces, one is for non route optimized traffic which is IPv6 over IPv6 (which is not described in the figure above), the other is for emulating a home network which is IPv6 over IPv4 (in the above case.) Best Regards, --- Keiichi SHIMA IIJ Research Laboratory KAME Project _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 29 07:00:27 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04300 for ; Wed, 29 Oct 2003 07:00: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 1AEozh-0008EW-FI for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 07:00:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TC093t031642 for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 07:00:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEozg-0008EH-V3 for mip6-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 07:00: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 GAA04275 for ; Wed, 29 Oct 2003 06:59:56 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEozc-0007CU-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 07:00:04 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEozc-0007CP-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 07:00:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEoza-0008Cy-Lp; Wed, 29 Oct 2003 07:00:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEoyb-000833-EA for mip6@optimus.ietf.org; Wed, 29 Oct 2003 06:59:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04263 for ; Wed, 29 Oct 2003 06:58:48 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEoyW-00079u-00 for mip6@ietf.org; Wed, 29 Oct 2003 06:58:56 -0500 Received: from p2.piuha.net ([131.160.192.2]) by ietf-mx with esmtp (Exim 4.12) id 1AEoyW-00079q-00 for mip6@ietf.org; Wed, 29 Oct 2003 06:58:56 -0500 Received: from kolumbus.fi (p4.piuha.net [131.160.192.4]) by p2.piuha.net (Postfix) with ESMTP id E62DC6A90B; Wed, 29 Oct 2003 13:58:56 +0200 (EET) Message-ID: <3F9FAA86.8000201@kolumbus.fi> Date: Wed, 29 Oct 2003 13:54:46 +0200 From: Jari Arkko User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Al-Absi Ayman (AC/EED)" Cc: mip6@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Re: [mobile-ip] question Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit (responding to the mip6 list, mobile-ip should no longer be used) > hello, > I would to ask this question please, > 1) when a MN moves to a new subnet, so should it make a Duplicate Address Detection for its own link- local IP address ( which it was using it in the previous subnet) ? Yes. --Jari _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 29 13:05:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23869 for ; Wed, 29 Oct 2003 13:05: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 1AEugq-0000Iy-LN for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 13:05:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TI54hU001162 for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 13: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 1AEugp-0000Ie-LU for mip6-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 13:05: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 NAA23834 for ; Wed, 29 Oct 2003 13:04:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEugn-0006x9-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 13:05:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AEugn-0006x6-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 13:05:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEugn-0000Gr-6G; Wed, 29 Oct 2003 13:05:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEufp-00005m-U2 for mip6@optimus.ietf.org; Wed, 29 Oct 2003 13:04:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23633 for ; Wed, 29 Oct 2003 13:03:49 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEufo-0006sc-00 for mip6@ietf.org; Wed, 29 Oct 2003 13:04:00 -0500 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1AEufa-0006qO-00 for mip6@ietf.org; Wed, 29 Oct 2003 13:03:46 -0500 Received: from cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 29 Oct 2003 10:02:09 -0800 Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id h9TI3DjP004473 for ; Wed, 29 Oct 2003 10:03:14 -0800 (PST) Received: from cisco.com ([128.107.176.180]) by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AMZ77101; Wed, 29 Oct 2003 10:01:10 -0800 (PST) Message-ID: <3FA000E0.30306@cisco.com> Date: Wed, 29 Oct 2003 10:03:12 -0800 From: Alpesh User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mip6@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] draft-patel-vendor-options-00.txt Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi - A new draft is available for your reference: ftp://ftp-eng.cisco.com/ftp/mipdrafts/draft-patel-vendor-options-00.txt Title : Vendor/Organization Specific Mobility Options for MiPv6 Author(s) : A. Patel, K. Leung Filename : draft-patel-vendor-options-00.txt Pages : 6 Date : 2003-10-29 Abstract This document defines new vendor/organization specific mobility option for Mobile IPv6. Equipment vendors and organizations may use this option as they see fit for research or deployment purposes. Thanks Alpesh _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Wed Oct 29 19:32:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16944 for ; Wed, 29 Oct 2003 19:32: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 1AF0jK-0005vZ-Sg for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 19:32:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9U0W2YT022784 for mip6-archive@odin.ietf.org; Wed, 29 Oct 2003 19:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AF0jK-0005vP-PP for mip6-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 19:32: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 TAA16934 for ; Wed, 29 Oct 2003 19:31:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AF0jJ-0000rp-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 19:32:01 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AF0jI-0000rm-00 for mip6-web-archive@ietf.org; Wed, 29 Oct 2003 19:32:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AF0jI-0005uv-J3; Wed, 29 Oct 2003 19:32:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AF0jD-0005ug-40 for mip6@optimus.ietf.org; Wed, 29 Oct 2003 19:31: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 TAA16931 for ; Wed, 29 Oct 2003 19:31:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AF0jB-0000rc-00 for mip6@ietf.org; Wed, 29 Oct 2003 19:31:53 -0500 Received: from mail.riscinfo.com ([209.213.195.152] helo=Fred.development.riscinfo.com) by ietf-mx with esmtp (Exim 4.12) id 1AF0jA-0000qs-00 for mip6@ietf.org; Wed, 29 Oct 2003 19:31:52 -0500 Received: from smtp0100.mail.yahoo.com ([200.67.215.64]) by Fred.development.riscinfo.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 29 Oct 2003 18:30:57 -0600 Date: Fri, 31 Oct 2003 09:31:00 GMT From: "PETERSON" X-Priority: 3 To: mip6@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-OriginalArrivalTime: 30 Oct 2003 00:31:16.0789 (UTC) FILETIME=[21930650:01C39E7D] Content-Transfer-Encoding: 7bit Subject: [Mip6] mip6,SOLICITING FOR YOUR PARTNERSHIP IN A BUSINESS TRANSACTION Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit PETERSON BULINGA Contracts Award Monitoring Committee. Zambian Ministry of Mining and Resources. 0031 627 105 921 ATTN:, I humbly wish to solicit for your assistance in a business transaction. This business proposal I wish to intimate you of will be of mutual benefit to the both of us and its success is entirely based on mutual trust, cooperation and a high level of confidentiality. I am representing the board of the contract award and monitoring committee of the Zambian Ministry of Mining and Resources. I am seeking your assistance to enable me transfer the sum of US$30,500,000.00 (Thirty Million, Five Hundred Thousand United States Dollars) into your private/company account. The fund came up as a result of a contract awarded and executed for and on behalf of my Ministry. The contract was supposed to be awarded to two foreign contractors to the tune of US$180,000,000.00 (One hundred and Eighty Million United States Dollars). But in the course of negotiation, the contract was awarded to a Bulgarian contractor at the cost of US$149,500,000.00 (One hundred and Forty-nine Million, Five Hundred Thousand United States Dollars) to our advantage unknown to the contractor. This contract has been satisfactorily executed and inspected as the Bulgarian firm is presently securing payment from my Ministry, where our Board is in-charge of all foreign contract payment approval. As a civil servant still in active government service, I am forbidden by law to operate an account outside the shores of Zambia. Hence this message to you seeking your assistance so as to enable me present your private/company account details as a beneficiary of contractual claims alongside that of the Bulgarian contractor, to enable me transfer the difference of US$30,500,000.00 (Thirty Million, Five Hundred Thousand United States Dollars) into your provided account. On actualization, the fund will be disbursed as stated below. 1. 20% of the fund will be for you as beneficiary 2. 80% of the fund will be for us. All logistics are in place and all modalities worked out for a smooth actualization of the transaction within the next few working days of commencement. For further details as to the workability of this transaction, please reach me as soon as possible for further clarification. Thank you and God bless as I await your urgent response. Yours Sincerely, PETERSON BULINGA _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Thu Oct 30 01:28:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27884 for ; Thu, 30 Oct 2003 01:28: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 1AF6Hq-0001WO-MJ for mip6-archive@odin.ietf.org; Thu, 30 Oct 2003 01:28:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9U6S2Qn005848 for mip6-archive@odin.ietf.org; Thu, 30 Oct 2003 01:28:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AF6Hq-0001WF-IT for mip6-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 01:28: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 BAA27874 for ; Thu, 30 Oct 2003 01:27:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AF6Hn-0005ru-00 for mip6-web-archive@ietf.org; Thu, 30 Oct 2003 01:27:59 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AF6Hn-0005rr-00 for mip6-web-archive@ietf.org; Thu, 30 Oct 2003 01:27:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AF6Hp-0001Vi-1f; Thu, 30 Oct 2003 01: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 1AF6H9-0001To-Mv for mip6@optimus.ietf.org; Thu, 30 Oct 2003 01:27: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 BAA27861 for ; Thu, 30 Oct 2003 01:27:09 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AF6H6-0005rS-00 for mip6@ietf.org; Thu, 30 Oct 2003 01:27:16 -0500 Received: from sausage.foretec.com ([4.17.168.5] helo=manatick) by ietf-mx with esmtp (Exim 4.12) id 1AF6H5-0005rL-00 for mip6@ietf.org; Thu, 30 Oct 2003 01:27:15 -0500 Received: from [216.13.40.192] (helo=bvimailbox.com) by manatick with smtp (Exim 4.24) id 1AF6H7-0005MV-UL for mip6@ietf.org; Thu, 30 Oct 2003 01:27:18 -0500 From: "C / P CSD" To: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 30 Oct 2003 01:27:18 -0500 Reply-To: "C / P CSD" Content-Transfer-Encoding: 8bit Message-Id: Content-Transfer-Encoding: 8bit Subject: [Mip6] PRESS RELEASE Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit CANADIAN SUBSIDY DIRECTORY 4865 HWY 138, R.R. 1 ST-ANDREWS WEST ONTARIO, K0C 2A0 1-866-322-3376 PRESS RELEASE CANADIAN SUBSIDY DIRECTORY YEAR 2003 EDITION Legal Deposit-National Library of Canada ISBN 2-922870-05-7 The new revised edition of the Canadian Subsidy Directory 2003 is now available. The new edition is the most complete and affordable reference for anyone looking for financial support. It is deemed to be the perfect tool for new or existing businesses, individual ventures, foundations and associations. This Publication contains more than 2000 direct and indirect financial subsidies, grants and loans offered by government departments and agencies, foundations, associations and organisations. In this new 2003 edition all programs are well described. The Canadian Subsidy Directory is the most comprehensive tool to start up a business, improve existent activities, set up a business plan, or obtain assistance from experts in fields such as: Industry, transport, agriculture, communications, municipal infrastructure, education, import-export, labor, construction and renovation, the service sector, hi-tech industries, research and development, joint ventures, arts, cinema, theatre, music and recording industry, the self employed, contests, and new talents. Assistance from and for foundations and associations, guidance to prepare a business plan, market surveys, computers, and much more! The Canadian Subsidy Directory is sold $ 69.95, to obtain a copy please call: Canadian Publications............... 1-866-322-3376 _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 02:24:08 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15873 for ; Fri, 31 Oct 2003 02:24: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 1AFTdN-0006Sg-Ra for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02:23:50 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V7NnVA024832 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02:23:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFTdL-0006SQ-32 for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 02:23:47 -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 CAA15867 for ; Fri, 31 Oct 2003 02:23:34 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFTdH-0002ub-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02:23:43 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFTdH-0002uX-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02:23:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFTcd-0006Hf-Ji; Fri, 31 Oct 2003 02:23:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFTcZ-0006HO-Ap for mip6@optimus.ietf.org; Fri, 31 Oct 2003 02:22: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 CAA15850; Fri, 31 Oct 2003 02:22:46 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFTcV-0002u6-00; Fri, 31 Oct 2003 02:22:55 -0500 Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx with esmtp (Exim 4.12) id 1AFTcU-0002tm-00; Fri, 31 Oct 2003 02:22:54 -0500 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HNM00AZW1S535@mailout2.samsung.com>; Fri, 31 Oct 2003 16:21:41 +0900 (KST) Received: from ep_mmp2 (localhost [127.0.0.1]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HNM004HQ1Q43U@mailout2.samsung.com>; Fri, 31 Oct 2003 16:20:28 +0900 (KST) Received: from LocalHost ([75.2.47.54]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HNM00E281Q31Q@mmp2.samsung.com>; Fri, 31 Oct 2003 16:20:28 +0900 (KST) Date: Fri, 31 Oct 2003 16:20:16 +0900 From: ??? Subject: [Mip6] draft-jang-mip6-smreg-00 To: mip6@ietf.org Cc: Basavaraj.Patil@nokia.com, ietf-secretariat@ietf.org, gdommety@cisco.com Message-id: <00c201c39f7f$70fba9b0$362f024b@LocalHost> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook Express 6.00.2800.1158 Content-type: text/plain; charset=Windows-1252 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal Content-Transfer-Encoding: 7BIT Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT I submitted new draft last week but it's not yet announced. The new draft is available now on my homepage and you can reference it :) http://home.postech.ac.kr/~arche/draft-jang-mip6-smreg-00 ps> It was submitted on 19th.(10/19) but not yet announced. I tried 2 more times but just got auto-reply without announcement. (Also I sent it to ietf-secritariat, Basavaraj Patil & Goral Dommety) Does anyone know to whom i can discuss this problem? --------------------------------------------------------------------- Document title : Simultaneous Registration of multiple Care-of Addresses Working group : mip6 Authors : H. Jang, J. Cheon and S. Singh Abstract : This draft proposes a scheme that allows a mobile node to register a primary care-of address(CoA) as well as one or more non-primary CoAs by sending a single binding update message to the home agent and/or correspondent node. This is achieved by using two new mobility options defined in this draft. Mobile nodes that perform duplicate address detection procedure, such as Advance DAD and Optimistic DAD can benefit from this scheme. Proposed scheme does not require to exchange CoTI and CoT messages, usually required for the registration of each of the non-primary CoA(s). It also does not require to maintain binding management key for each of the non-primary CoA(s). Thus the proposed scheme reduces the signaling and processing overhead in Mobile IPv6 networks. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 02:31:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16123 for ; Fri, 31 Oct 2003 02:31: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 1AFTkS-0007iX-0s for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02:31:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V7V7AF029592 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02:31:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFTkP-0007hD-SV for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 02:31:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16109 for ; Fri, 31 Oct 2003 02:30:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFTkM-00038T-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02:31:02 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFTkL-00038Q-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02: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 1AFTkO-0007gk-53; Fri, 31 Oct 2003 02:31:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFTjo-0007eA-80 for mip6@optimus.ietf.org; Fri, 31 Oct 2003 02: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 CAA16063 for ; Fri, 31 Oct 2003 02:30:15 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFTjk-00037h-00 for mip6@ietf.org; Fri, 31 Oct 2003 02:30:24 -0500 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1AFTjj-0002zQ-00 for mip6@ietf.org; Fri, 31 Oct 2003 02:30:23 -0500 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HNM00H5Y25THA@mailout1.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:29:53 +0900 (KST) Received: from ep_mmp1 (localhost [127.0.0.1]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HNM00KWR24HI3@mailout1.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:29:05 +0900 (KST) Received: from LocalHost ([75.2.47.54]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HNM00MA724HRR@mmp1.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:29:05 +0900 (KST) Date: Fri, 31 Oct 2003 16:28:57 +0900 From: Heejin jang Subject: [Mip6] draft-jang-mip6-smreg-00 To: mip6@ietf.org Message-id: <00f301c39f80$a54504e0$362f024b@LocalHost> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook Express 6.00.2800.1158 Content-type: text/plain; charset=Windows-1252 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal Content-Transfer-Encoding: 7BIT Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT I submitted new draft last week but it's not yet announced. The new draft is available now on my homepage and you can reference it :) http://home.postech.ac.kr/~arche/draft-jang-mip6-smreg-00 --------------------------------------------------------------------- Document title : Simultaneous Registration of multiple Care-of Addresses Working group : mip6 Authors : H. Jang, J. Cheon and S. Singh Abstract : This draft proposes a scheme that allows a mobile node to register a primary care-of address(CoA) as well as one or more non-primary CoAs by sending a single binding update message to the home agent and/or correspondent node. This is achieved by using two new mobility options defined in this draft. Mobile nodes that perform duplicate address detection procedure, such as Advance DAD and Optimistic DAD can benefit from this scheme. Proposed scheme does not require to exchange CoTI and CoT messages, usually required for the registration of each of the non-primary CoA(s). It also does not require to maintain binding management key for each of the non-primary CoA(s). Thus the proposed scheme reduces the signaling and processing overhead in Mobile IPv6 networks. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 02:50:25 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16670 for ; Fri, 31 Oct 2003 02:50:25 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFU2p-00016t-41 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02:50:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V7o6la004189 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 02: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 1AFU2l-00015O-Bf for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 02:50: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 CAA16652 for ; Fri, 31 Oct 2003 02:49:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFU2h-0003NB-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02:49:59 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFU2h-0003N8-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 02:49:59 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFU2j-00014p-Iu; Fri, 31 Oct 2003 02:50:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFU1s-00010A-Qz for mip6@optimus.ietf.org; Fri, 31 Oct 2003 02:49: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 CAA16640 for ; Fri, 31 Oct 2003 02:48:55 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFU1o-0003Mi-00 for mip6@ietf.org; Fri, 31 Oct 2003 02:49:05 -0500 Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx with esmtp (Exim 4.12) id 1AFU1o-0003MN-00 for mip6@ietf.org; Fri, 31 Oct 2003 02:49:04 -0500 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HNM00I0830YAG@mailout1.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:48:34 +0900 (KST) Received: from ep_mmp2 (localhost [127.0.0.1]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HNM00JUT30PIW@mailout1.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:48:25 +0900 (KST) Received: from daniel ([168.219.203.183]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0HNM007MZ30P9I@mmp2.samsung.com> for mip6@ietf.org; Fri, 31 Oct 2003 16:48:25 +0900 (KST) Date: Fri, 31 Oct 2003 16:48:45 +0900 From: Soohong Daniel Park Subject: RE: [Mip6] draft-jang-mip6-smreg-00 In-reply-to: <00f301c39f80$a54504e0$362f024b@LocalHost> To: "'Heejin jang'" , mip6@ietf.org Message-id: <007501c39f83$696b55c0$b7cbdba8@daniel> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Content-Transfer-Encoding: 7BIT Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Hello Heejin After roughly reading, two questions occured in my mind. 1) Which applicability is possible ? network mobility (NEMO) ? If yes, you should be moved to there. If not, please let me know it. 2) Comparison with previous job (Ryuji's draft) It seems like a similar approach to me where the multiple CoA are binded by new option. Sorry if I am missing something. Regards Daniel (Soohong Daniel Park) Mobile Platform Laboratory, SAMSUNG Electronics > -----Original Message----- > From: mip6-admin@ietf.org [mailto:mip6-admin@ietf.org] On > Behalf Of Heejin jang > Sent: Friday, October 31, 2003 4:29 PM > To: mip6@ietf.org > Subject: [Mip6] draft-jang-mip6-smreg-00 > > > I submitted new draft last week but it's not yet announced. > The new draft is available now on my homepage and you can > reference it :) > http://home.postech.ac.kr/~arche/draft-jang-mip6-smreg-00 > > --------------------------------------------------------------------- > Document title : Simultaneous Registration of multiple > Care-of Addresses > > Working group : mip6 > > Authors : H. Jang, J. Cheon and S. Singh > > Abstract : This draft proposes a scheme that allows a mobile > node to register a > primary care-of address(CoA) as well as one or more > non-primary CoAs > by sending a single binding update message to the home agent and/or > correspondent node. This is achieved by using two new mobility > options defined in this draft. Mobile nodes that perform duplicate > address detection procedure, such as Advance DAD and Optimistic DAD > can benefit from this scheme. Proposed scheme does not require to > exchange CoTI and CoT messages, usually required for the > registration > of each of the non-primary CoA(s). It also does not require to > maintain binding management key for each of the non-primary CoA(s). > Thus the proposed scheme reduces the signaling and > processing overhead > in Mobile IPv6 networks. > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 03:08:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17122 for ; Fri, 31 Oct 2003 03:08: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 1AFUKG-00039e-4C for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 03:08:09 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V886mg012061 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 03:08:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUKD-00038F-3N for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 03:08:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17072 for ; Fri, 31 Oct 2003 03:07:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFUK8-0003a9-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 03:08:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFUK8-0003a5-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 03:08:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUKA-00034z-NG; Fri, 31 Oct 2003 03:08:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUJS-0002tj-HZ for mip6@optimus.ietf.org; Fri, 31 Oct 2003 03:07:18 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17044 for ; Fri, 31 Oct 2003 03:07:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFUJO-0003ZM-00 for mip6@ietf.org; Fri, 31 Oct 2003 03:07:14 -0500 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1AFUJN-0003Z7-00 for mip6@ietf.org; Fri, 31 Oct 2003 03:07:13 -0500 Received: from galibier.nautilus6.org (unknown [203.178.138.3]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 143485D114; Fri, 31 Oct 2003 17:06:43 +0900 (JST) Date: Fri, 31 Oct 2003 17:01:09 +0900 From: Thierry Ernst To: Cc: mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Message-Id: <20031031170109.20030ca8.ernst@sfc.wide.ad.jp> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> References: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> Organization: Keio University X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj, On Mon, 27 Oct 2003 12:15:53 -0600 wrote: > >Given the fact the MIP6 WG is a new group, I find it very appropriate to > >discuss the missions of the WG right now. Also, I would find very > >appropriate to raise the issue at the meeting to see how many people > >have interest in this. If only a minority has, so, very fine, it means > >it's not considered important. Demonstration done. > > As you note above, MIP6 is a new WG. What the WG ought to do was > discussed at 2 BOFs (NSIIM at IETF56 and MIP6 at IETF57). The charter > has been discussed at length and what you see now is the conclusion of > those discussions in addition to the feedback from the IESG/IAB. Of > course it does not imply that it is set in stone and no changes can be > made. We can obviously look at what are the importnat issues that need > to be dealt with for Mobile IPv6 and if there are missing pieces we > can always recharter. The scope of the charter has been intentionally > kept limited in order to ensure that only the most immediate problems > are dealt with. IETF58 will be the first WG meeting for MIP6. The > milestones are until Nov 04. It is very likely that we will see a > recharter of this WG at IETF60. Hence I am not ruling out this work > altogether, all I am saying is that the WG has an agenda and a roadmap > and we will stick to that. So far the discussion on the ML has been > more about the agenda itself and very little about the actual > problem. If I can see some interest in the problem (by some I mean > more than 5 people :) ), then we can consider it on the MIP6 > agenda. Of course I am glad to see that there is a BoF to discuss > this work. So there is an avenue to determine the interest already. I must admit I was not very active on this list to make sure multihoming would be considered, and I missed the thread when the charter was approved. So, I'm partly to blame the discussion was not deepened. But other draft authors too, they should have voiced up more, but may be they don't know that at the IETF voicing up is the only way to get through. When was the draft charter last discussed on the ML the way ? The only time I got my eyes open, I did raised the issue, and this was followed up by people who agreed with me it is an important topic to consider. Noone disagree. I take this as explicit agreement and I guess other people concerned by this topic took this for granted. BTW, the point of view you express in this thread is not consistent with the initial draft agenda where you listed NOMAD (note to Nomad authors: sorry to cite you all the time, it's surely not a temptative to blame you although you are in the middle of the firework. Sorry about that :-) - if that is not important topic, why did you list Nomad at the first place, and why did you retract yourself ? (I'm not seeking any responsabilities in posting draft agenda, I'm trying to understand your thinking - you may have unconsciously considered multihoming and related issues as an important topic ;-) > >> I am aware of the various drafts addressing this. But I do not see why > >> this is a critical need for the WG to take on at this time. I do not > >> for example see a large number of people in the WG demanding that this > > > >Please specify: how many people is considered "large" ? > > Large > 5 people (since in a given WG, there are very few active > people and hence even if WG meetings have attendance of about 150~200 > people or the number of people on ML is > 1000, large is relative) Ah, we need 6 people then ? :-) Might not be that difficult. First, if we add up all the draft co-authors dealing with this subject we have 10 persons at least :-) Well, I would see the number of drafts dealing around the subject as a more important parameter to determine how much is large. I wish other draft authors were more eager to discuss the issue, but most likely they have already said all they have to said in their own drafts. They need comments from other. Particularly, I wish the MIP6 chairs could comment on draft-montavont-mobileip-multihoming-pb-statement-00.txt. I don't think you read it yet. So, I will follow this discussion in a new thread "Multihomed mobile nodes". > >> Sure, but first you have to demonstrate via the ML that there is some > >> interest in this topic. If you can do that in the next week or so, we > >> can include it on the agenda. > > > >This discussion is already initiated, and several people have already > >answered. I don't think it's necessary to demonstrate how vital it is > >for IPv6 mobility (could you by the way demonstrate how vital Mobile > >IPv6 is ? What about RO ? Just kidding); simply demonstrating the > >interest of people to work on this is enough. So, I will let the other > >intereted ML members with some space to pop up on the ML. > > I am counting and watching the ML :) So far it is not very > encouraging. Is it ? I might not have subscribed to the right mailing list then ... Thierry. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 03:08:26 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17125 for ; Fri, 31 Oct 2003 03:08: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 1AFUKG-00039p-CJ for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 03:08:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9V886Cq012067 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 03:08:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUKD-00038L-At for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 03:08:05 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17075 for ; Fri, 31 Oct 2003 03:07:51 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFUK9-0003aC-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 03:08:01 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFUK8-0003a6-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 03:08:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFUKB-00035F-DP; Fri, 31 Oct 2003 03: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 1AFUJZ-0002v1-Mw for mip6@optimus.ietf.org; Fri, 31 Oct 2003 03:07: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 DAA17048 for ; Fri, 31 Oct 2003 03:07:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFUJV-0003ZR-00 for mip6@ietf.org; Fri, 31 Oct 2003 03:07:21 -0500 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]) by ietf-mx with esmtp (Exim 4.12) id 1AFUJV-0003Z8-00 for mip6@ietf.org; Fri, 31 Oct 2003 03:07:21 -0500 Received: from galibier.nautilus6.org (unknown [203.178.138.3]) by shonan.sfc.wide.ad.jp (Postfix) with ESMTP id 307FA5D137 for ; Fri, 31 Oct 2003 17:06:52 +0900 (JST) Date: Fri, 31 Oct 2003 17:01:18 +0900 From: Thierry Ernst To: mip6@ietf.org Message-Id: <20031031170118.5f203cb5.ernst@sfc.wide.ad.jp> Organization: Keio University X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Mip6] Multihomed Mobile Nodes Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear all, As you know there have been a number of drafts dealing around the issues of multihomed mobile nodes, including draft-montavont-mobileip-multihoming-pb-statement-00.txt The intend of the draft is to list the cases where a MN is multihomed, and the issues that must be addressed at large to allow this configuration. So, the real intend is to investigate what are the issues peculiar to MIPv6, and other issues not peculiar to MIPv6. I guess that there is no other group in a better position than MIPv6 to understand the issues peculiar to MIP6. May be the solutions can be divised in other WGs, but a prior work for this is for the MIP6 group to give comments. In order to introduce the discussion, may I ask the following questions to the list (including authors of the other drafts): - if people agree with the definition of multihoming ? - is there any case (the one you the most concerned about) which is not covered by the definition ? - if people agree with the issues ? - what are the missing issues we need to consider ? - where should the issues be solved ? Get the draft here: http://clarinet.u-strasbg.fr/~montavont/ Abstract: ~~~~~~~~~ Individual solutions have been proposed to extend Mobile IPv6 in order to allow mobile nodes to be multihomed, but all issues have not been addressed by a single document. In this document, we thus propose a taxonomy to classify the situations where a mobile node may be multihomed. This taxonomy is then used to describe all multihomed scenarios. Issues preventing mobile nodes to be multihomed while operating Mobile IPv6 are highlighted. This document doesn't aim at proposing solutions, however, it is expected to raise discussion in order to make sure forthcoming solutions will address all the issues. Thierry. _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 08:01:01 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26677 for ; Fri, 31 Oct 2003 08:01:00 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFYtN-0000hq-LX for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:00:42 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9VD0f4P002707 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:00:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFYtN-0000ha-HD for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 08:00: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 IAA26667 for ; Fri, 31 Oct 2003 08:00:29 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFYtA-0007TI-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08:00:28 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFYtA-0007TF-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08:00:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFYsk-0000cY-3e; Fri, 31 Oct 2003 08:00:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFYsd-0000bV-CM for mip6@optimus.ietf.org; Fri, 31 Oct 2003 07:59: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 HAA26621 for ; Fri, 31 Oct 2003 07:59:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFYsb-0007Sw-00 for mip6@ietf.org; Fri, 31 Oct 2003 07:59:54 -0500 Received: from omgo.iij.ad.jp ([202.232.30.157]) by ietf-mx with esmtp (Exim 4.12) id 1AFYsb-0007St-00 for mip6@ietf.org; Fri, 31 Oct 2003 07:59:53 -0500 Received: from jc-smtp.iij.ad.jp ([192.168.176.35]) by omgo.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9VCxnhD020755 for ; Fri, 31 Oct 2003 21:59:50 +0900 (JST) Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.65.65]) by jc-smtp.iij.ad.jp (8.12.10/8.12.9) with ESMTP id h9VCxLi0016007 for ; Fri, 31 Oct 2003 21:59:22 +0900 (JST) Date: Fri, 31 Oct 2003 21:58:41 +0900 (JST) Message-Id: <20031031.215841.71166249.keiichi@iij.ad.jp> To: mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 From: Keiichi SHIMA / =?iso-2022-jp?B?GyRCRWc3RDBsGyhC?= In-Reply-To: <20031023.161341.38807935.keiichi@iij.ad.jp> References: <697DAA22C5004B4596E033803A7CEF44013EFBF4@daebe007.americas.nokia.com> <20031023.161341.38807935.keiichi@iij.ad.jp> X-Mailer: Mew version 4.0.59 on Emacs 21.3.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, Since it seems no one is intersted in this topic, I stop requesting a slot for this. I'll raise the same topic again before next next IETF probablly with implementation and some operational experience. # Comments or contacts about this topic are of course welcome at any time --- Keiichi SHIMA IIJ Research Laboratory KAME Project From: Keiichi SHIMA / 島慶一 Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Thu, 23 Oct 2003 16:13:41 +0900 (JST) > Hi, > > I wonder if we can have a time to discuss mechanisms for RO procedure > initiation judgement. The basic draft mentions that a > mobile/correpondent node should be administratively enabled/disabled > to allow RO. However, I think we need more flexible mechanism for > managed networks. > > Please take a look into > http://www.ietf.org/internet-drafts/draft-shima-mip6-rohints-00.txt, > which describes one such proposal. > > Regards, > --- > Keiichi SHIMA > IIJ Research Laboratory > KAME Project _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 08:17:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27135 for ; Fri, 31 Oct 2003 08:17: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 1AFZ9C-0003ED-1K for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:17:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9VDH2DB012403 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:17:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZ9B-0003Dy-Oz for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 08:17:01 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27105 for ; Fri, 31 Oct 2003 08:16:50 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFZ9A-0007df-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08:17:00 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFZ9A-0007dc-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08: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 1AFZ9A-0003B5-NU; Fri, 31 Oct 2003 08: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 1AFZ8o-00036c-Te for mip6@optimus.ietf.org; Fri, 31 Oct 2003 08:16:39 -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 IAA27088 for ; Fri, 31 Oct 2003 08:16:27 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFZ8n-0007d7-00 for mip6@ietf.org; Fri, 31 Oct 2003 08:16:37 -0500 Received: from motgate7.mot.com ([129.188.136.7]) by ietf-mx with esmtp (Exim 4.12) id 1AFZ8n-0007d4-00 for mip6@ietf.org; Fri, 31 Oct 2003 08:16:37 -0500 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate7.mot.com (Motorola/Motgate7) with ESMTP id h9VDFmBO028974; Fri, 31 Oct 2003 06:15:49 -0700 (MST) Received: from thorgal.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id h9VDF7T0022845; Fri, 31 Oct 2003 07:15:08 -0600 Received: from nal.motlabs.com (test9.crm.mot.com [10.161.201.219]) by thorgal.crm.mot.com (Postfix) with ESMTP id 5F22C2EC95; Fri, 31 Oct 2003 14:16:31 +0100 (CET) Message-ID: <3FA260AF.20200@nal.motlabs.com> Date: Fri, 31 Oct 2003 14:16:31 +0100 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thierry Ernst Cc: Basavaraj.Patil@nokia.com, mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> <20031031170109.20030ca8.ernst@sfc.wide.ad.jp> In-Reply-To: <20031031170109.20030ca8.ernst@sfc.wide.ad.jp> X-Enigmail-Version: 0.72.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thierry Ernst wrote: >> The charter has been discussed at length and what you see now is >> the conclusion of those discussions in addition to the feedback >> from the IESG/IAB. [...] > When was the draft charter last discussed on the ML the way? Before the mip6 list discussions there was much discussion on the mipcharter list somewhere at sun. Maybe these mipcharter threads have something about multi-homing. Alex GBU _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 08:20:23 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27225 for ; Fri, 31 Oct 2003 08:20: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 1AFZC8-0003cK-SU for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:20:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9VDK4tC013849 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 08:20:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZC8-0003aq-3H for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 08:20: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 IAA27211 for ; Fri, 31 Oct 2003 08:19:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFZC7-0007fm-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08:20:03 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFZC6-0007fj-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 08:20:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZC6-0003Z8-Ng; Fri, 31 Oct 2003 08:20:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFZBG-0003U4-FA for mip6@optimus.ietf.org; Fri, 31 Oct 2003 08:19:10 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27173 for ; Fri, 31 Oct 2003 08:18:58 -0500 (EST) From: Basavaraj.Patil@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFZBF-0007fA-00 for mip6@ietf.org; Fri, 31 Oct 2003 08:19:09 -0500 Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx with esmtp (Exim 4.12) id 1AFZBE-0007f7-00 for mip6@ietf.org; Fri, 31 Oct 2003 08:19:08 -0500 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9VDJ7F01167 for ; Fri, 31 Oct 2003 15:19:07 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Fri, 31 Oct 2003 15:19:07 +0200 Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Fri, 31 Oct 2003 05:19:05 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Subject: RE: [Mip6] Draft Agenda for WG meeting at IETF58 Date: Fri, 31 Oct 2003 07:19:05 -0600 Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB9BE@daebe007.americas.nokia.com> Thread-Topic: [Mip6] Draft Agenda for WG meeting at IETF58 Thread-Index: AcOfrvS2wPNDW0lWRJCFhZxzHLq1DQAAhV/g To: , X-OriginalArrivalTime: 31 Oct 2003 13:19:05.0715 (UTC) FILETIME=[8F350430:01C39FB1] Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Keiichi, > > Hi all, > > Since it seems no one is intersted in this topic, I stop requesting a > slot for this. I'll raise the same topic again before next next IETF > probablly with implementation and some operational experience. I think this proposal is actually quite relevant to the MIP6 WG. I am definitely interested in this work. I think it makes sense to include this on the agenda for the upcoming meeting. RO is a part of the base spec. However the base spec does not have any guidance on when RO should be used. And this I-D is the only one so far that is making any recommendations at all. So, I will add this to the agenda item. -Basavaraj > > # Comments or contacts about this topic are of course welcome > at any time > > --- > Keiichi SHIMA > IIJ Research Laboratory > KAME Project > > From: Keiichi SHIMA / 島慶一 > Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 > Date: Thu, 23 Oct 2003 16:13:41 +0900 (JST) > > > Hi, > > > > I wonder if we can have a time to discuss mechanisms for RO > procedure > > initiation judgement. The basic draft mentions that a > > mobile/correpondent node should be administratively enabled/disabled > > to allow RO. However, I think we need more flexible mechanism for > > managed networks. > > > > Please take a look into > > http://www.ietf.org/internet-drafts/draft-shima-mip6-rohints-00.txt, > > which describes one such proposal. > > > > Regards, > > --- > > Keiichi SHIMA > > IIJ Research Laboratory > > KAME Project > > _______________________________________________ > Mip6 mailing list > Mip6@ietf.org > https://www.ietf.org/mailman/listinfo/mip6 > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6 From exim@www1.ietf.org Fri Oct 31 10:35:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03907 for ; Fri, 31 Oct 2003 10:35:52 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFbJH-0004JY-Dr for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 10:35:35 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9VFZZfP016580 for mip6-archive@odin.ietf.org; Fri, 31 Oct 2003 10:35:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFbJH-0004JL-9P for mip6-web-archive@optimus.ietf.org; Fri, 31 Oct 2003 10:35: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 KAA03867 for ; Fri, 31 Oct 2003 10:35:21 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFbJE-0001sH-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 10:35:32 -0500 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFbJE-0001sE-00 for mip6-web-archive@ietf.org; Fri, 31 Oct 2003 10:35:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFbIl-0004DS-B8; Fri, 31 Oct 2003 10: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 1AFbII-0004Az-F2 for mip6@optimus.ietf.org; Fri, 31 Oct 2003 10:34: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 KAA03796 for ; Fri, 31 Oct 2003 10:34:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFbIG-0001r3-00 for mip6@ietf.org; Fri, 31 Oct 2003 10:34:32 -0500 Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx with smtp (Exim 4.12) id 1AFbIF-0001r0-00 for mip6@ietf.org; Fri, 31 Oct 2003 10:34:31 -0500 Received: (qmail 13705 invoked for bounce); 31 Oct 2003 15:34:40 -0000 Received: from unknown (HELO clarinet.u-strasbg.fr) (montavont@unknown) by unknown with RC4-MD5 encrypted SMTP; 31 Oct 2003 15:34:40 -0000 Message-ID: <3FA28104.9080506@clarinet.u-strasbg.fr> Date: Fri, 31 Oct 2003 16:34:28 +0100 From: Nicolas Montavont User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Basavaraj.Patil@nokia.com CC: ernst@sfc.wide.ad.jp, mip6@ietf.org Subject: Re: [Mip6] Draft Agenda for WG meeting at IETF58 References: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB960@daebe007.americas.nokia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: mip6-admin@ietf.org Errors-To: mip6-admin@ietf.org X-BeenThere: mip6@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Basavaraj and all, I have to add some comments too... see inline Basavaraj.Patil@nokia.com wrote: >Hi Thierry, > > > >>Hi Basavaraj, >> >>I find your answer amazing... >> >>Given the fact the MIP6 WG is a new group, I find it very appropriate to >>discuss the missions of the WG right now. Also, I would find very >>appropriate to raise the issue at the meeting to see how many people >>have interest in this. If only a minority has, so, very fine, it means >>it's not considered important. Demonstration done. >> >> > >As you note above, MIP6 is a new WG. What the WG ought to do was >discussed at 2 BOFs (NSIIM at IETF56 and MIP6 at IETF57). The charter >has been discussed at length and what you see now is the conclusion of >those discussions in addition to the feedback from the IESG/IAB. Of >course it does not imply that it is set in stone and no changes can be >made. We can obviously look at what are the importnat issues that need >to be dealt with for Mobile IPv6 and if there are missing pieces we >can always recharter. The scope of the charter has been intentionally >kept limited in order to ensure that only the most immediate problems >are dealt with. IETF58 will be the first WG meeting for MIP6. The >milestones are until Nov 04. It is very likely that we will see a >recharter of this WG at IETF60. Hence I am not ruling out this work >altogether, all I am saying is that the WG has an agenda and a roadmap >and we will stick to that. So far the discussion on the ML has been >more about the agenda itself and very little about the actual >problem. If I can see some interest in the problem (by some I mean >more than 5 people :) ), then we can consider it on the MIP6 >agenda. Of course I am glad to see that there is a BoF to discuss >this work. So there is an avenue to determine the interest already. > Let me refer authors of current available drafts on multihoming: - Thierry E. - Ryuji W. - Niko F. and all authors of Nomad - Hesham S. - Thomas N. - Mohammed K.-L. - Hosei M. - Karim E. - Julien and Chan-Wha (who work on multihoming in NEMO) And as Thierry said, lot of drafts deal with multihoming issues. Maybe there is only few discussion in the maling list because of a lack of a common objective/goal between all authors. I think it really is the good time to initiate discussion on multihoming at next IETF, even if it is only a short discussion. I think it is better than a bar BOF because we never know where discussion can go... Nicolas > > > > >>>>In the second place, there are a few drafts turning around this issues, >>>>and drafts have been submitted regularly for a few years. So, given the >>>>number of drafts and period of effect, I find it rather important. On a >>>>personal side, I would like to see something coming up from this >>>>activity so that we can implement a common solution, no doing our own >>>>cooking in our lab. >>>> >>>> >>>I am aware of the various drafts addressing this. But I do not see why >>>this is a critical need for the WG to take on at this time. I do not >>>for example see a large number of people in the WG demanding that this >>> >>> >>Please specify: how many people is considered "large" ? >> >> > >Large > 5 people (since in a given WG, there are very few active >people and hence even if WG meetings have attendance of about 150‾200 >people or the number of people on ML is > 1000, large is relative) > > > >>>be a work item because it is absolutely a MUST for mobile IPv6 to be >>>deployed. What you are cooking in your lab may be interesting but is >>>not necessarily needed by the industry at this time. >>> >>> >>Huh ? The industry your are refering too is not the same as the one I'm >>involved in. The fact that I work for a University doesn't necessarily >>make me unaware of business realities. >> >> > >Of course not. I am sure that there is plenty of industry-university >interaction for you to be aware of the business realities. > > > >>>So if you believe >>>that there is interest in this work, the I-D can always be >>>standardized as Experimental (without WG intervention) which would let >>>the people with common interests implement it and interop. >>> >>> >>Don't take me wrong: I don't have any solution, so I cannot expect >>anything to be experimental ... But THERE ARE solutions, and all of them >>address distinct and complementary issues. The purpose of this >>discussion and draft-montavont is to come to an agreement on what is >>needed so that all the parties involved can work on a single solution. >>The need WG directive to achieve this. Designing a single specification >>is clearly a WG task. >> >> >> >>>>Anyway, let's see why the other people are thinking. If it happens that >>>>there is no room in this WG to deal with issue, I will most likely >>>>propose a BOF at Seoul Meeting (and, well, this might not be a bad idea, >>>>because the benefit of having several interfaces [either actual, or >>>>virtual] could be shared by both Fixed Nodes and Mobile Nodes (I'm not >>>>exclusively thinking about NEMO, although the idea comes from there]). >>>>The reason I have not yet pushed toward a new WG is because there are >>>>already many WGs. >>>> >>>> >>>Well, please do intiate a discussion on this topic to determine >>> - the interest >>> - how vital is this for IPv6 mobility >>> >>> >>>>In conclusion, may I request a short slot to deal the issue (not the >>>>solutions) during the meeting, please, so that we come to a WG consensus >>>>and act upon it ? >>>> >>>> >>>Sure, but first you have to demonstrate via the ML that there is some >>>interest in this topic. If you can do that in the next week or so, we >>>can include it on the agenda. >>> >>> >>This discussion is already initiated, and several people have already >>answered. I don't think it's necessary to demonstrate how vital it is >>for IPv6 mobility (could you by the way demonstrate how vital Mobile >>IPv6 is ? What about RO ? Just kidding); simply demonstrating the >>interest of people to work on this is enough. So, I will let the other >>intereted ML members with some space to pop up on the ML. >> >> > >I am counting and watching the ML :) So far it is not very >encouraging. > > > >>Thierry. >> >> >> >-Basavaraj > >_______________________________________________ >Mip6 mailing list >Mip6@ietf.org >https://www.ietf.org/mailman/listinfo/mip6 > > _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www.ietf.org/mailman/listinfo/mip6