From exim@www1.ietf.org  Thu Sep  4 16:07: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 QAA19463
	for <mip6-archive@odin.ietf.org>; Thu, 4 Sep 2003 16:07: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 19v0Nk-0003w9-GB
	for mip6-archive@odin.ietf.org; Thu, 04 Sep 2003 16:07:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h84K74kt015129
	for mip6-archive@odin.ietf.org; Thu, 4 Sep 2003 16:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v0Nj-0003vj-TO
	for mip6-web-archive@optimus.ietf.org; Thu, 04 Sep 2003 16: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 QAA19443
	for <mip6-web-archive@ietf.org>; Thu, 4 Sep 2003 16:06:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v0Ni-0003mV-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 16:07:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19v0Nh-0003mR-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 16:07:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v0Nh-0003uk-NK; Thu, 04 Sep 2003 16: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 19v0Mk-0003td-8G
	for mip6@optimus.ietf.org; Thu, 04 Sep 2003 16:06: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 QAA19405
	for <mip6@ietf.org>; Thu, 4 Sep 2003 16:05:55 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v0Mi-0003ko-00
	for mip6@ietf.org; Thu, 04 Sep 2003 16:06:00 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v0Mg-0003kk-00
	for mip6@ietf.org; Thu, 04 Sep 2003 16:05:58 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h84K5p400419
	for <mip6@ietf.org>; Thu, 4 Sep 2003 23:05:56 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T647b43820dac158f23077@esvir03nok.nokia.com> for <mip6@ietf.org>;
 Thu, 4 Sep 2003 23:05:51 +0300
Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 4 Sep 2003 23:05:51 +0300
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 4 Sep 2003 15:05:22 -0500
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
Date: Thu, 4 Sep 2003 15:05:12 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com>
Thread-Topic: Seeking consensus on a MIP6 charter item
Thread-Index: AcNzH9kP1m2nuhqkRCKRYUggXD9qXw==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 04 Sep 2003 20:05:22.0014 (UTC) FILETIME=[DF114FE0:01C3731F]
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Seeking consensus on a MIP6 charter item
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Hello,

The following is a milestone identified in the current charter for
Mobile IPv6:

 o Mar 04 Submit alternate security mechanisms for HA-MN to IESG

However there is no corresponding text describing what this milestone
really means in the charter. My view of the above milestone is as
follows:
   Currently IPsec provides the means for authenticating a MN to the
   HA. This mandates the existence of an IPsec SA between the MN and
   HA. It is possible that an equivalent degree of security for the
   BU/BAck can be achieved by encapsulating an authenticator in a
   Binding data suboption. This basically falls back to the Mobile
   IPv4 model of authentication between MN-HA where the MN-HA auth
   extension is sufficient to create the binding in the HA. With this
   approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
   MN, which I think is an overkill for basically doing authentication
   between two entities that are aware of each other.=20

So the question is:
1. Should the Mobile IPv6 take on the work item mentioned in the
   milestone above?=20

A:=20
   Yes  [ ]
   No   [ ]

Reason:=20

Note that if there is consensus to work on this, the above text or
some equivalent would be added to the charter.

Please express your views on this by Sept 12th, 2003.

-Basavaraj




_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep  4 17:30: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 RAA23910
	for <mip6-archive@odin.ietf.org>; Thu, 4 Sep 2003 17: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 19v1g6-0007dN-6j
	for mip6-archive@odin.ietf.org; Thu, 04 Sep 2003 17:30:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h84LU6hG029345
	for mip6-archive@odin.ietf.org; Thu, 4 Sep 2003 17:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v1g4-0007d9-Kj
	for mip6-web-archive@optimus.ietf.org; Thu, 04 Sep 2003 17:30: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 RAA23884
	for <mip6-web-archive@ietf.org>; Thu, 4 Sep 2003 17:29:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v1g2-0005Hw-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 17:30:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19v1g1-0005Hr-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 17:30:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v1g2-0007ck-KU; Thu, 04 Sep 2003 17: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 19v1f6-0007bj-Su
	for mip6@optimus.ietf.org; Thu, 04 Sep 2003 17:29: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 RAA23851
	for <mip6@ietf.org>; Thu, 4 Sep 2003 17:28:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v1f4-0005Gq-00
	for mip6@ietf.org; Thu, 04 Sep 2003 17:29:02 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v1f3-0005GG-00
	for mip6@ietf.org; Thu, 04 Sep 2003 17:29:01 -0400
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h84LSRC07141;
	Thu, 4 Sep 2003 16:28:27 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <R7KB3XY0>; Thu, 4 Sep 2003 16:28:28 -0500
Message-ID: <F72ED4AED0592B469BF057F380DEECEA635A9F@zrc2c014.us.nortel.com>
From: "Mohamed Khalil" <mkhalil@nortelnetworks.com>
To: "'Basavaraj.Patil@nokia.com'" <Basavaraj.Patil@nokia.com>, mip6@ietf.org
Subject: RE: [Mip6] Seeking consensus on a MIP6 charter item
Date: Thu, 4 Sep 2003 16:28:23 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3732B.47E8A404"
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C3732B.47E8A404
Content-Type: text/plain



-----Original Message-----
From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com] 
Sent: Thursday, September 04, 2003 3:05 PM
To: mip6@ietf.org
Subject: [Mip6] Seeking consensus on a MIP6 charter item



Hello,

The following is a milestone identified in the current charter for Mobile
IPv6:

 o Mar 04 Submit alternate security mechanisms for HA-MN to IESG

However there is no corresponding text describing what this milestone really
means in the charter. My view of the above milestone is as
follows:
   Currently IPsec provides the means for authenticating a MN to the
   HA. This mandates the existence of an IPsec SA between the MN and
   HA. It is possible that an equivalent degree of security for the
   BU/BAck can be achieved by encapsulating an authenticator in a
   Binding data suboption. This basically falls back to the Mobile
   IPv4 model of authentication between MN-HA where the MN-HA auth
   extension is sufficient to create the binding in the HA. With this
   approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
   MN, which I think is an overkill for basically doing authentication
   between two entities that are aware of each other. 

So the question is:
1. Should the Mobile IPv6 take on the work item mentioned in the
   milestone above? 

A: 
   Yes  [x]
   No   [ ]

Reason: 

Note that if there is consensus to work on this, the above text or some
equivalent would be added to the charter.

Please express your views on this by Sept 12th, 2003.

-Basavaraj




_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6

------_=_NextPart_001_01C3732B.47E8A404
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>RE: [Mip6] Seeking consensus on a MIP6 charter item</TITLE>
</HEAD>
<BODY>
<BR>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Basavaraj.Patil@nokia.com [<A =
HREF=3D"mailto:Basavaraj.Patil@nokia.com">mailto:Basavaraj.Patil@nokia.c=
om</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, September 04, 2003 3:05 PM</FONT>
<BR><FONT SIZE=3D2>To: mip6@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Mip6] Seeking consensus on a MIP6 charter =
item</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Hello,</FONT>
</P>

<P><FONT SIZE=3D2>The following is a milestone identified in the =
current charter for Mobile IPv6:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;o Mar 04 Submit alternate security mechanisms =
for HA-MN to IESG</FONT>
</P>

<P><FONT SIZE=3D2>However there is no corresponding text describing =
what this milestone really means in the charter. My view of the above =
milestone is as</FONT></P>

<P><FONT SIZE=3D2>follows:</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Currently IPsec provides the means for =
authenticating a MN to the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; HA. This mandates the existence of an =
IPsec SA between the MN and</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; HA. It is possible that an equivalent =
degree of security for the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; BU/BAck can be achieved by =
encapsulating an authenticator in a</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Binding data suboption. This basically =
falls back to the Mobile</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; IPv4 model of authentication between =
MN-HA where the MN-HA auth</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; extension is sufficient to create the =
binding in the HA. With this</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; approach there is no reason to =
implement IPsec/IKE(v2) in a MIPv6</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; MN, which I think is an overkill for =
basically doing authentication</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; between two entities that are aware of =
each other. </FONT>
</P>

<P><FONT SIZE=3D2>So the question is:</FONT>
<BR><FONT SIZE=3D2>1. Should the Mobile IPv6 take on the work item =
mentioned in the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; milestone above? </FONT>
</P>

<P><FONT SIZE=3D2>A: </FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Yes&nbsp; [x]</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; No&nbsp;&nbsp; [ ]</FONT>
</P>

<P><FONT SIZE=3D2>Reason: </FONT>
</P>

<P><FONT SIZE=3D2>Note that if there is consensus to work on this, the =
above text or some equivalent would be added to the charter.</FONT>
</P>

<P><FONT SIZE=3D2>Please express your views on this by Sept 12th, =
2003.</FONT>
</P>

<P><FONT SIZE=3D2>-Basavaraj</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Mip6 mailing list</FONT>
<BR><FONT SIZE=3D2>Mip6@ietf.org</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mip6" =
TARGET=3D"_blank">https://www.ietf.org/mailman/listinfo/mip6</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3732B.47E8A404--

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep  4 17:58: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 RAA25290
	for <mip6-archive@odin.ietf.org>; Thu, 4 Sep 2003 17:58: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 19v27F-0000Pm-2s
	for mip6-archive@odin.ietf.org; Thu, 04 Sep 2003 17:58:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h84Lw9Ue001588
	for mip6-archive@odin.ietf.org; Thu, 4 Sep 2003 17:58:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v27E-0000PX-Up
	for mip6-web-archive@optimus.ietf.org; Thu, 04 Sep 2003 17:58: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 RAA25274
	for <mip6-web-archive@ietf.org>; Thu, 4 Sep 2003 17:58:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v27C-0005qu-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 17:58:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19v27A-0005qm-00
	for mip6-web-archive@ietf.org; Thu, 04 Sep 2003 17:58:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v278-0000Nv-OR; Thu, 04 Sep 2003 17: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 19v270-0000Mi-5x
	for mip6@optimus.ietf.org; Thu, 04 Sep 2003 17:57: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 RAA25234
	for <mip6@ietf.org>; Thu, 4 Sep 2003 17:57:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v26x-0005pT-00
	for mip6@ietf.org; Thu, 04 Sep 2003 17:57:51 -0400
Received: from smtp.gcis.net ([64.132.170.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v26w-0005pE-00
	for mip6@ietf.org; Thu, 04 Sep 2003 17:57:50 -0400
Received: from eremmell [12.99.240.208] by smtp.gcis.net with ESMTP
  (SMTPD32-7.07) id A5BD25C0128; Thu, 04 Sep 2003 17:59:25 -0400
From: "Ed Remmell" <eremmell@elmic.com>
To: <mip6@ietf.org>
Subject: RE: [Mip6] Seeking consensus on a MIP6 charter item
Date: Thu, 4 Sep 2003 14:57:33 -0700
Message-ID: <000201c3732f$8c08ccf0$d0f0630c@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
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com>
X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam.
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> However there is no corresponding text describing what this 
> milestone really means in the charter. My view of the above 
> milestone is as
> follows:
>    Currently IPsec provides the means for authenticating a MN to the
>    HA. This mandates the existence of an IPsec SA between the MN and
>    HA. It is possible that an equivalent degree of security for the
>    BU/BAck can be achieved by encapsulating an authenticator in a
>    Binding data suboption. This basically falls back to the Mobile
>    IPv4 model of authentication between MN-HA where the MN-HA auth
>    extension is sufficient to create the binding in the HA. With this
>    approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
>    MN, which I think is an overkill for basically doing authentication
>    between two entities that are aware of each other. 
> 
> So the question is:
> 1. Should the Mobile IPv6 take on the work item mentioned in the
>    milestone above? 
> 
>    Yes  [X]

> Reason:
I trust Charles Perkins' opinion on this. At the SF IETF-56 meeting, he
seemed to think it was worthwhile to pursue the AAA extensions to MIPv6
that have previously been specified for MIPv4.

Thanks.
- Ed Remmell
Elmic Systems, USA

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 00:01: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 AAA17447
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 00:01: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 19v7mX-0007nq-6i
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 00:01:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h85418CZ029985
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 00:01:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v7mV-0007nP-Hq
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 00:01: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 AAA17419
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 00:01:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v7mT-0000Gt-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 00:01:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19v7mS-0000Gq-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 00:01:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v7mQ-0007mG-P2; Fri, 05 Sep 2003 00: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 19v7ld-0007l4-H9
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 00:00: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 AAA17390
	for <mip6@ietf.org>; Fri, 5 Sep 2003 00:00:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v7lb-0000Fh-00
	for mip6@ietf.org; Fri, 05 Sep 2003 00:00:11 -0400
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 19v7la-0000FS-00
	for mip6@ietf.org; Fri, 05 Sep 2003 00:00:10 -0400
Received: from kolumbus.fi (p4.piuha.net [131.160.192.4])
	by p2.piuha.net (Postfix) with ESMTP
	id 6840F6A901; Fri,  5 Sep 2003 07:00:03 +0300 (EEST)
Message-ID: <3F58098E.1060102@kolumbus.fi>
Date: Fri, 05 Sep 2003 06:57:02 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
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: Basavaraj.Patil@nokia.com
Cc: mip6@ietf.org
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
References: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com>
In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Basavaraj.Patil@nokia.com wrote:
> Hello,
> 
> The following is a milestone identified in the current charter for
> Mobile IPv6:
> 
>  o Mar 04 Submit alternate security mechanisms for HA-MN to IESG
> 
> However there is no corresponding text describing what this milestone
> really means in the charter. My view of the above milestone is as
> follows:
>    Currently IPsec provides the means for authenticating a MN to the
>    HA. This mandates the existence of an IPsec SA between the MN and
>    HA. It is possible that an equivalent degree of security for the
>    BU/BAck can be achieved by encapsulating an authenticator in a
>    Binding data suboption. This basically falls back to the Mobile
>    IPv4 model of authentication between MN-HA where the MN-HA auth
>    extension is sufficient to create the binding in the HA. With this
>    approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
>    MN, which I think is an overkill for basically doing authentication
>    between two entities that are aware of each other. 
> 
> So the question is:
> 1. Should the Mobile IPv6 take on the work item mentioned in the
>    milestone above? 
> 
> A: 
>    Yes  [ ]
>    No   [ ]

I believe we need the work item, but I am unsure about the text
that was provided. Basically, at this time we lack two important
functions from the HA-MN interface security. Here's what the old
charter proposals said about them:

    - A bootstrap mechanism for setting up security
      associations between the MN and HA that would enable easier
      deployment of Mobile IPv6.

    - Support for the MN's changing addresses either because of
      renumbering in its home network or because it periodically
      changes addresses (perhaps via rfc3041)

Its unclear to me whether your intent was to replace the work
on these with the options work, or would both still be done?
If its the latter, is that work independent of the alternative
HA-MN security work or performed together?

Basically, I believe the bootstrap and dynamic addressing
features are more important than simply replacing current
protocol mechanism with another. Note that, as discussed in
IETF-57, taking in account these two features could well mean
replacing IPsec with something else; the choices really are
something IKEv2 based or something "application" layer based -
and I prefer the latter. But I think the charter should be
written so that we require a mechanism to be designed such
that these two features are provided, and leave more room
for the specific solution to be developed.

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 01:57:57 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 BAA22583
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 01:57:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v9bA-0003Tk-0L
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 01:57:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h855vVAS013366
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 01:57:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v9b9-0003TV-R8
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 01:57:31 -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 BAA22574
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 01:57: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 19v9ae-0003Rn-P3; Fri, 05 Sep 2003 01:57:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19v9a9-0003RB-8q
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 01:56:39 -0400
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22554
	for <mip6@ietf.org>; Fri, 5 Sep 2003 01:56:23 -0400 (EDT)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-1.sun.com (8.12.9/8.12.9) with ESMTP id h855tK6Q029320;
	Thu, 4 Sep 2003 22:55:21 -0700 (PDT)
Received: from lillen (punchin-nordmark.Eng.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.2) with SMTP id h855tGQ20667;
	Fri, 5 Sep 2003 07:55:17 +0200 (MEST)
Date: Fri, 5 Sep 2003 07:18:51 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
To: Jari Arkko <jari.arkko@kolumbus.fi>
Cc: Basavaraj.Patil@nokia.com, mip6@ietf.org
In-Reply-To: "Your message with ID" <3F58098E.1060102@kolumbus.fi>
Message-ID: <Roam.SIMC.2.0.6.1062739131.14957.nordmark@bebop.france>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

> Basically, I believe the bootstrap and dynamic addressing
> features are more important than simply replacing current
> protocol mechanism with another. Note that, as discussed in
> IETF-57, taking in account these two features could well mean
> replacing IPsec with something else; the choices really are
> something IKEv2 based or something "application" layer based -
> and I prefer the latter. But I think the charter should be
> written so that we require a mechanism to be designed such
> that these two features are provided, and leave more room
> for the specific solution to be developed.

Agreed.

  Erik


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 10:57: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 KAA28435
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 10:57: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 19vI1G-0001qM-3s
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 10:57:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h85Ev2Jg007078
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 10:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vI1F-0001q3-Tt
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 10:57: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 KAA28417
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 10:56:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vI1D-0002mm-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 10:56:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vI1C-0002mj-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 10:56:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vI1E-0001pT-9r; Fri, 05 Sep 2003 10:57:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vI0I-0001i0-V5
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 10:56: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 KAA28346
	for <mip6@ietf.org>; Fri, 5 Sep 2003 10:55:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vI0G-0002YN-00
	for mip6@ietf.org; Fri, 05 Sep 2003 10:56:00 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vI0F-0002R9-00
	for mip6@ietf.org; Fri, 05 Sep 2003 10:55:59 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <S1MLTYA8>; Fri, 5 Sep 2003 10:55:28 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922CE1@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>,
        Jari Arkko
	 <jari.arkko@kolumbus.fi>
Cc: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: RE: [Mip6] Seeking consensus on a MIP6 charter item
Date: Fri, 5 Sep 2003 10:55:18 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

 > 
 > > Basically, I believe the bootstrap and dynamic addressing
 > > features are more important than simply replacing current
 > > protocol mechanism with another. Note that, as discussed in
 > > IETF-57, taking in account these two features could well mean
 > > replacing IPsec with something else; the choices really are
 > > something IKEv2 based or something "application" layer based -
 > > and I prefer the latter. But I think the charter should be
 > > written so that we require a mechanism to be designed such
 > > that these two features are provided, and leave more room
 > > for the specific solution to be developed.
 > 
 > Agreed.

=> Agreed. Agreed. ;)

Hesham

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 12:15: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 MAA03345
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 12:15: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 19vJEm-0004aa-Ko
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 12:15:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h85GF4bL017633
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 12:15:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vJEm-0004aK-E9
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 12:15: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 MAA03310
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 12:14:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJEl-00043b-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 12:15:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJEk-00043Y-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 12:15:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vJEk-0004Zj-2k; Fri, 05 Sep 2003 12:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vJEF-0004W2-T0
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 12:14: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 MAA03280
	for <mip6@ietf.org>; Fri, 5 Sep 2003 12:14:25 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJEE-000407-00
	for mip6@ietf.org; Fri, 05 Sep 2003 12:14:30 -0400
Received: from [63.78.179.217] (helo=mgw-dax2.ext.nokia.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJED-0003zz-00
	for mip6@ietf.org; Fri, 05 Sep 2003 12:14:29 -0400
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h85GESG12041
	for <mip6@ietf.org>; Fri, 5 Sep 2003 11:14:28 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T647dde8ee2ac12f255079@davir02nok.americas.nokia.com>;
 Fri, 5 Sep 2003 11:14:27 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 5 Sep 2003 09:14:17 -0700
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] Seeking consensus on a MIP6 charter item
Date: Fri, 5 Sep 2003 11:14:17 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB67F@daebe007.americas.nokia.com>
Thread-Topic: [Mip6] Seeking consensus on a MIP6 charter item
Thread-Index: AcNzYje0pb/EkBGxQ9uMS1rvnfeMrQAZoGtg
To: <jari.arkko@kolumbus.fi>
Cc: <mip6@ietf.org>
X-OriginalArrivalTime: 05 Sep 2003 16:14:17.0458 (UTC) FILETIME=[C18FB520:01C373C8]
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Hi Jari,

>> So the question is:
>> 1. Should the Mobile IPv6 take on the work item mentioned in the
>>    milestone above?=20
>>=20
>> A:=20
>>    Yes  [ ]
>>    No   [ ]
>
>I believe we need the work item,=20

I guess I can take that as a Yes, with modifications required.

>but I am unsure about the text
>that was provided. Basically, at this time we lack two important
>functions from the HA-MN interface security. Here's what the old
>charter proposals said about them:
>
>    - A bootstrap mechanism for setting up security
>      associations between the MN and HA that would enable easier
>      deployment of Mobile IPv6.
>
>    - Support for the MN's changing addresses either because of
>      renumbering in its home network or because it periodically
>      changes addresses (perhaps via rfc3041)
>
>Its unclear to me whether your intent was to replace the work
>on these with the options work, or would both still be done?

Both of the above would be done. No intention of replacing this work.

>If its the latter, is that work independent of the alternative
>HA-MN security work or performed together?

This is a harder question :(=20
First of all we really need to come to grips about the scope of the
bootstrapping work that is realistic. To do so, we plan on having a
problem statement I-D that explains the various scenarios and options
and then decide on the mechanism for bootstrapping. It is possible
that the bootstrapping solution will bootstrap either an IPsec SA
between the MN-HA or maybe enable exchange of session keys between the
two that are used for setting up the simpler [non-IPsec] SA. Hence it
depends on what the MN is capable of. The bootstrapping solution may
also be used for addressing the problem of MNs that change their HoA
because of renumbering or use of RFC3041 for HoA's. Here I believe an
existing SA (IPsec or otherwise) can be used to setup the new SA and
this is simpler than bootstrapping from NULL state. But the point is
that the alternative to IPsec SA bewteen MN-HA is also an option.=20
So this work would be done independently of the above two work items.=20

>
>Basically, I believe the bootstrap and dynamic addressing
>features are more important than simply replacing current
>protocol mechanism with another.=20

Agreed. We know that the currently specified mechanism works. However
I also believe that if we really want to enable wide-scale
deployments, there is a need for a simpler solution. So while the
alternate solution is NOT critical for making Mobile IPv6 work, it
would be easier for implementing a nonIPsec based MIPv6 MN.

>Note that, as discussed in
>IETF-57, taking in account these two features could well mean
>replacing IPsec with something else; the choices really are
>something IKEv2 based or something "application" layer based -
>and I prefer the latter. But I think the charter should be
>written so that we require a mechanism to be designed such
>that these two features are provided, and leave more room
>for the specific solution to be developed.

Sure. We can work on the proper text that describes the work item more
accurately than what I scribbled earlier.

>
>--Jari

-Basavaraj

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 12:19: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 MAA03658
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 12:19: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 19vJId-00058l-A2
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 12:19:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h85GJ3Rb019749
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 12:19:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vJId-00058I-22
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 12:19: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 MAA03596
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 12:18:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJIb-0004Vo-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 12:19:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJIa-0004Vl-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 12:19:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vJIb-00055d-Pd; Fri, 05 Sep 2003 12: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 19vJHw-00051E-AD
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 12:18: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 MAA03556
	for <mip6@ietf.org>; Fri, 5 Sep 2003 12:18:13 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJHu-0004RR-00
	for mip6@ietf.org; Fri, 05 Sep 2003 12:18:18 -0400
Received: from [63.78.179.216] (helo=mgw-dax1.ext.nokia.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vJHt-0004RA-00
	for mip6@ietf.org; Fri, 05 Sep 2003 12:18:17 -0400
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h85GIH107047
	for <mip6@ietf.org>; Fri, 5 Sep 2003 11:18:17 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T647de20d0dac12f254079@davir01nok.americas.nokia.com> for <mip6@ietf.org>;
 Fri, 5 Sep 2003 11:18:16 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 5 Sep 2003 11:18:13 -0500
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
Date: Fri, 5 Sep 2003 11:18:12 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44013EFBB2@daebe007.americas.nokia.com>
Thread-Topic: Revised Charter
Thread-Index: AcNzyUzPwcbiF+nuRRqy/k8ifr0wuQ==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 05 Sep 2003 16:18:13.0024 (UTC) FILETIME=[4DF83A00:01C373C9]
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Revised Charter
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Hello,

Below is the most recent or updated charter that has also
had the benefit of AD review:

-Basavaraj


Charter:
--------

  Internet Area (int)
       Thomas Narten (narten@us.ibm.com)
       Margaret Wasserman (mrw@windriver.com)

  Chairs:

       Mailing list: mip6@ietf.org
       To subscribe: https://www.ietf.org/mailman/listinfo/mip6
       To post: mip6@ietf.org
       Archive:=20
http://www1.ietf.org/mail-archive/working-groups/mip6/current/

  Mobile IPv6 (MIPv6) specifies routing support to permit an IPv6 host =
to
  continue using its "permanent" home address as it moves around
  the Internet. Mobile IPv6 supports transparency above the IP
  layer, including maintenance of active TCP connections and UDP port
  bindings. The specifications for these mechanisms consist of:

        draft-ietf-mobileip-ipv6-24 and
        draft-ietf-mobileip-mipv6-ha-ipsec-06

  The protocol as specified in the above two documents can be considered
  as  the baseline or minimum protocol set for implementing IPv6
  mobility. During the development phase of the base protocol, a few
  additional features were identified as necessary to facilitate
  deployment (described below).

  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. Additionally the working group will ensure
  that any issues identified by the interop testing of the MIPv6
  specifications are addressed quickly. Specific work items with this
  goal in mind are listed below:

  1) Create and maintain an issue list that is generated on the basis of
     interop testing and address these issues as enhancements to the
     base protocol

  2) Features such as renumbering of the home link, home agent =
discovery,
     Route Optimization, which are currently a part of the base
     specification can be specified more explicitly as separate
     specifications. This will also enable modularizing the Mobile
     IPv6 specification further into the minimal subset and add-on
     features. Some of these specifications will be identified as
     base mechanisms of Mobile IPv6.

  3) A number of enhancements to basic IPv6 mobility were identified
     during the development of the base specification. These
     enhancements will be taken up in a phased manner depending on the
     priority identified with each. Below are listed the work items to
     be taken up by the WG:

      - A bootstrap mechanism for setting up security associations
        between the Mobile Node (MN) and Home Agent (HA) that would
        enable easier deployment of Mobile IPv6. This bootstrap
        mechanism is intended to be used when the device is turned on
        the very first time and activates MIPv6. The WG should
        investigate and define the scope before solving the problem.

     - Improving home agent reliability: in the event of a home agent
       crashing, this would allow another home agent to continue
       providing service to a given mobile node.

     - Support for a Mobile Node changing its home address, either
       because of renumbering in its home network or because it
       periodically changes addresses (perhaps via RFC3041)

     - Route optimization will require security mechanisms for
       trusting and updating the binding information. Return-routability
       is the basic mechanism for route-optimization. Mechanisms using
       a shared secret Key/Security Association will be considered.
       Methods for establishing a security association between the =
mobile
       node and the correspondent node are out of the scope of the WG.

     - The working group will also document problem statements
       associated with deploying Mobile IPv6 in the following areas:
         a. Mobile IPv6 issues in the presence of firewalls
         b. Mobile IPv6 deployment and transition issues in the presence
            of IPv4/IPv6 networks
         c. Multicast issues

  It should be noted that there are potential optimizations that might
  make mobile IP more attractive for use by certain applications (e.g.,
  making handovers "faster"). The latter category of optimizations is
  explicitly out-of-scope at this time; this WG will focus on issues
  for which there is strong consensus that the work is needed to get
  basic mobility deployable on a large scale.


  ------------------------------------------


  Sep 03 Charter approval

  Nov 03 Problem statement documents (to IESG)
           - Issues with firewall
           - Mobile IPv6 transition between v4/v6 networks

  Jan 03 Bootstrapping problem statement to IESG

  Feb 04 Submit MIPv6 MIB to IESG

  Mar 04 Submit alternate security mechanisms for securing the
	 signaling message between Mobile Node (MN) and Home Agent
	 (HA) to IESG=20

  Mar 04 Alternate Route Optimization scheme to IESG

  May 04 Home agent reliability to IESG

  Aug 04 Bootstrapping solution to IESG

  Nov 04 Separate specs for Home Agent (HA) Discovery, Route =
Optimization,
         Renumbering to IESG



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep  5 13:50: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 NAA08816
	for <mip6-archive@odin.ietf.org>; Fri, 5 Sep 2003 13:50: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 19vKij-0008Tj-MO
	for mip6-archive@odin.ietf.org; Fri, 05 Sep 2003 13:50:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h85Ho5AT032581
	for mip6-archive@odin.ietf.org; Fri, 5 Sep 2003 13:50:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vKij-0008TP-G4
	for mip6-web-archive@optimus.ietf.org; Fri, 05 Sep 2003 13:50: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 NAA08784
	for <mip6-web-archive@ietf.org>; Fri, 5 Sep 2003 13:49:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vKih-0005xN-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 13:50:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vKig-0005xK-00
	for mip6-web-archive@ietf.org; Fri, 05 Sep 2003 13:50:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vKih-0008RS-E2; Fri, 05 Sep 2003 13:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vKi9-0008Nn-NG
	for mip6@optimus.ietf.org; Fri, 05 Sep 2003 13:49: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 NAA08766
	for <mip6@ietf.org>; Fri, 5 Sep 2003 13:49:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vKi7-0005tx-00
	for mip6@ietf.org; Fri, 05 Sep 2003 13:49:27 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vKi6-0005qu-00
	for mip6@ietf.org; Fri, 05 Sep 2003 13:49:26 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h85Hmr522016;
	Fri, 5 Sep 2003 10:48:53 -0700
X-mProtect: <200309051748> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdxtC10a; Fri, 05 Sep 2003 10:48:51 PDT
Message-ID: <3F58CC84.F380DC74@iprg.nokia.com>
Date: Fri, 05 Sep 2003 10:48:52 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
CC: mip6@ietf.org
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
References: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yes.

Vijay

Basavaraj.Patil@nokia.com wrote:
> 
> Hello,
> 
> The following is a milestone identified in the current charter for
> Mobile IPv6:
> 
>  o Mar 04 Submit alternate security mechanisms for HA-MN to IESG
> 
> However there is no corresponding text describing what this milestone
> really means in the charter. My view of the above milestone is as
> follows:
>    Currently IPsec provides the means for authenticating a MN to the
>    HA. This mandates the existence of an IPsec SA between the MN and
>    HA. It is possible that an equivalent degree of security for the
>    BU/BAck can be achieved by encapsulating an authenticator in a
>    Binding data suboption. This basically falls back to the Mobile
>    IPv4 model of authentication between MN-HA where the MN-HA auth
>    extension is sufficient to create the binding in the HA. With this
>    approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
>    MN, which I think is an overkill for basically doing authentication
>    between two entities that are aware of each other.
> 
> So the question is:
> 1. Should the Mobile IPv6 take on the work item mentioned in the
>    milestone above?
> 
> A:
>    Yes  [ ]
>    No   [ ]
> 
> Reason:
> 
> Note that if there is consensus to work on this, the above text or
> some equivalent would be added to the charter.
> 
> Please express your views on this by Sept 12th, 2003.
> 
> -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



From exim@www1.ietf.org  Sat Sep  6 00:41: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 AAA08538
	for <mip6-archive@odin.ietf.org>; Sat, 6 Sep 2003 00:41: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 19vUsh-00069l-Fx
	for mip6-archive@odin.ietf.org; Sat, 06 Sep 2003 00:41:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h864f3P6023659
	for mip6-archive@odin.ietf.org; Sat, 6 Sep 2003 00:41:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vUsh-00069V-B3
	for mip6-web-archive@optimus.ietf.org; Sat, 06 Sep 2003 00:41: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 AAA08519
	for <mip6-web-archive@ietf.org>; Sat, 6 Sep 2003 00:40:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vUse-0001DU-00
	for mip6-web-archive@ietf.org; Sat, 06 Sep 2003 00:41:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vUse-0001DQ-00
	for mip6-web-archive@ietf.org; Sat, 06 Sep 2003 00:41:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vUse-00068h-Gq; Sat, 06 Sep 2003 00:41:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vUsW-00067e-P1
	for mip6@optimus.ietf.org; Sat, 06 Sep 2003 00:40:52 -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 AAA08506
	for <mip6@ietf.org>; Sat, 6 Sep 2003 00:40:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vUsT-0001C3-00
	for mip6@ietf.org; Sat, 06 Sep 2003 00:40:49 -0400
Received: from ns.sait.samsung.co.kr ([202.20.142.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vUsS-00018C-00
	for mip6@ietf.org; Sat, 06 Sep 2003 00:40:48 -0400
Received: from tyre (localhost [127.0.0.1])
	by ns.sait.samsung.co.kr (8.12.9/8.12.1) with SMTP id h864e5J5001758;
	Sat, 6 Sep 2003 13:40:10 +0900 (KST)
Message-ID: <008201c37431$d4ed5910$ea2f024b@tyre>
From: "JinHyeock Choi" <athene@sait.samsung.co.kr>
To: <Basavaraj.Patil@nokia.com>, <mip6@ietf.org>
References: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com>
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
Date: Sat, 6 Sep 2003 13:46:21 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: base64
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

PiBIb3dldmVyIHRoZXJlIGlzIG5vIGNvcnJlc3BvbmRpbmcgdGV4dCBkZXNjcmliaW5nIHdoYXQg
dGhpcyBtaWxlc3RvbmUNCj4gcmVhbGx5IG1lYW5zIGluIHRoZSBjaGFydGVyLiBNeSB2aWV3IG9m
IHRoZSBhYm92ZSBtaWxlc3RvbmUgaXMgYXMNCj4gZm9sbG93czoNCj4gICAgQ3VycmVudGx5IElQ
c2VjIHByb3ZpZGVzIHRoZSBtZWFucyBmb3IgYXV0aGVudGljYXRpbmcgYSBNTiB0byB0aGUNCj4g
ICAgSEEuIFRoaXMgbWFuZGF0ZXMgdGhlIGV4aXN0ZW5jZSBvZiBhbiBJUHNlYyBTQSBiZXR3ZWVu
IHRoZSBNTiBhbmQNCj4gICAgSEEuIEl0IGlzIHBvc3NpYmxlIHRoYXQgYW4gZXF1aXZhbGVudCBk
ZWdyZWUgb2Ygc2VjdXJpdHkgZm9yIHRoZQ0KPiAgICBCVS9CQWNrIGNhbiBiZSBhY2hpZXZlZCBi
eSBlbmNhcHN1bGF0aW5nIGFuIGF1dGhlbnRpY2F0b3IgaW4gYQ0KPiAgICBCaW5kaW5nIGRhdGEg
c3Vib3B0aW9uLiBUaGlzIGJhc2ljYWxseSBmYWxscyBiYWNrIHRvIHRoZSBNb2JpbGUNCj4gICAg
SVB2NCBtb2RlbCBvZiBhdXRoZW50aWNhdGlvbiBiZXR3ZWVuIE1OLUhBIHdoZXJlIHRoZSBNTi1I
QSBhdXRoDQo+ICAgIGV4dGVuc2lvbiBpcyBzdWZmaWNpZW50IHRvIGNyZWF0ZSB0aGUgYmluZGlu
ZyBpbiB0aGUgSEEuIFdpdGggdGhpcw0KPiAgICBhcHByb2FjaCB0aGVyZSBpcyBubyByZWFzb24g
dG8gaW1wbGVtZW50IElQc2VjL0lLRSh2MikgaW4gYSBNSVB2Ng0KPiAgICBNTiwgd2hpY2ggSSB0
aGluayBpcyBhbiBvdmVya2lsbCBmb3IgYmFzaWNhbGx5IGRvaW5nIGF1dGhlbnRpY2F0aW9uDQo+
ICAgIGJldHdlZW4gdHdvIGVudGl0aWVzIHRoYXQgYXJlIGF3YXJlIG9mIGVhY2ggb3RoZXIuIA0K
PiANCj4gU28gdGhlIHF1ZXN0aW9uIGlzOg0KPiAxLiBTaG91bGQgdGhlIE1vYmlsZSBJUHY2IHRh
a2Ugb24gdGhlIHdvcmsgaXRlbSBtZW50aW9uZWQgaW4gdGhlDQo+ICAgIG1pbGVzdG9uZSBhYm92
ZT8gDQo+IA0KPiBBOiANCj4gICAgWWVzICBbT10NCj4gICAgTm8gICBbIF0NCj4gDQo+IFJlYXNv
bjogDQo+IA0KPiBOb3RlIHRoYXQgaWYgdGhlcmUgaXMgY29uc2Vuc3VzIHRvIHdvcmsgb24gdGhp
cywgdGhlIGFib3ZlIHRleHQgb3INCj4gc29tZSBlcXVpdmFsZW50IHdvdWxkIGJlIGFkZGVkIHRv
IHRoZSBjaGFydGVyLg0KIA0KQmVzdCBSZWdhcmRzDQoNCkppbkh5ZW9jayBDaG9p


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sat Sep  6 01:53: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 BAA11636
	for <mip6-archive@odin.ietf.org>; Sat, 6 Sep 2003 01:53: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 19vW0N-0005Nq-2G
	for mip6-archive@odin.ietf.org; Sat, 06 Sep 2003 01:53:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h865r2ch020687
	for mip6-archive@odin.ietf.org; Sat, 6 Sep 2003 01:53:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19vW0M-0005Na-RL
	for mip6-web-archive@optimus.ietf.org; Sat, 06 Sep 2003 01: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 BAA11618
	for <mip6-web-archive@ietf.org>; Sat, 6 Sep 2003 01:52:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vW0J-0001QV-00
	for mip6-web-archive@ietf.org; Sat, 06 Sep 2003 01:52:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19vW0J-0001QS-00
	for mip6-web-archive@ietf.org; Sat, 06 Sep 2003 01: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 19vW0L-0005N6-4E; Sat, 06 Sep 2003 01: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 19vW0F-0005MM-DO
	for mip6@optimus.ietf.org; Sat, 06 Sep 2003 01:52: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 BAA11614
	for <mip6@ietf.org>; Sat, 6 Sep 2003 01:52:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vW0B-0001Pd-00
	for mip6@ietf.org; Sat, 06 Sep 2003 01:52:51 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19vW0B-0001Lx-00
	for mip6@ietf.org; Sat, 06 Sep 2003 01:52:51 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h865qCD27509;
	Sat, 6 Sep 2003 08:52:12 +0300
Date: Sat, 6 Sep 2003 08:52:11 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Basavaraj.Patil@nokia.com
cc: mip6@ietf.org
Subject: Re: [Mip6] Revised Charter
In-Reply-To: <697DAA22C5004B4596E033803A7CEF44013EFBB2@daebe007.americas.nokia.com>
Message-ID: <Pine.LNX.4.44.0309060841590.27355-100000@netcore.fi>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

a couple of quick comments..

it has been a while since I looked at MIPv6 spec, so I may have forgotten 
something, but I'm wondering what are the immediate problems at least in 
two work items that require getting addressed soon.

On Fri, 5 Sep 2003 Basavaraj.Patil@nokia.com wrote:
>      - Improving home agent reliability: in the event of a home agent
>        crashing, this would allow another home agent to continue
>        providing service to a given mobile node.

I'm not sure what this is going to mean?  Would this mean a 
HA state-sharing protocol between HA's, or something else?

I'm concerned how well this work item might fit in MIP6 WG, and whether 
doing such would create significant amount of new complexity.
 
>      - Support for a Mobile Node changing its home address, either
>        because of renumbering in its home network or because it
>        periodically changes addresses (perhaps via RFC3041)

Isn't this already supported?  Why else are we doing DHAAD as we speak?  
Couldn't one connect to another HA (or to the same one twice) to obtain 
two addresses, end of story?

Note: using RFC3041 on home addresses is probably very bad idea.  The 
prefix stays static, so in practice this will not give much additional 
privacy, unless there are thousands of MN's under the same HA prefix.

>   ------------------------------------------
> 
> 
>   Sep 03 Charter approval
> 
>   Nov 03 Problem statement documents (to IESG)
>            - Issues with firewall
>            - Mobile IPv6 transition between v4/v6 networks
> 
>   Jan 03 Bootstrapping problem statement to IESG
> 
>   Feb 04 Submit MIPv6 MIB to IESG
> 
>   Mar 04 Submit alternate security mechanisms for securing the
> 	 signaling message between Mobile Node (MN) and Home Agent
> 	 (HA) to IESG 
> 
>   Mar 04 Alternate Route Optimization scheme to IESG
> 
>   May 04 Home agent reliability to IESG
> 
>   Aug 04 Bootstrapping solution to IESG
> 
>   Nov 04 Separate specs for Home Agent (HA) Discovery, Route Optimization,
>          Renumbering to IESG

General note: the charter milestones are quite fast-tracked.  For this to 
succeed, I think we have to have a clear commitment from the WG and the 
document editors, and no major issues raised.

It's OK as is, but I would be a bit more pessimistic about the delivery 
dates.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sun Sep  7 13:29: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 NAA19847
	for <mip6-archive@odin.ietf.org>; Sun, 7 Sep 2003 13:29:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w3LZ-0002fR-8D
	for mip6-archive@odin.ietf.org; Sun, 07 Sep 2003 13:29:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h87HT97b010247
	for mip6-archive@odin.ietf.org; Sun, 7 Sep 2003 13:29:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w3LY-0002f1-Uq
	for mip6-web-archive@optimus.ietf.org; Sun, 07 Sep 2003 13: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 NAA19595
	for <mip6-web-archive@ietf.org>; Sun, 7 Sep 2003 13:29:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w3LV-0006g0-00
	for mip6-web-archive@ietf.org; Sun, 07 Sep 2003 13:29:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19w3LU-0006f7-00
	for mip6-web-archive@ietf.org; Sun, 07 Sep 2003 13:29:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w3LS-0002ba-4a; Sun, 07 Sep 2003 13:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w3Ka-0002VW-Rs
	for mip6@optimus.ietf.org; Sun, 07 Sep 2003 13:28: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 NAA19161
	for <mip6@ietf.org>; Sun, 7 Sep 2003 13:28:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w1tA-0001Am-00
	for mip6@ietf.org; Sun, 07 Sep 2003 11:55:44 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w1t9-00015n-00
	for mip6@ietf.org; Sun, 07 Sep 2003 11:55:43 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h87Ft2o07905;
	Sun, 7 Sep 2003 08:55:02 -0700
X-mProtect: <200309071555> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (10.241.54.41, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdX90PFh; Sun, 07 Sep 2003 08:55:01 PDT
Message-ID: <3F5B54D3.2060005@iprg.nokia.com>
Date: Sun, 07 Sep 2003 08:54:59 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
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: Pekka Savola <pekkas@netcore.fi>
CC: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: Re: [Mip6] Revised Charter
References: <Pine.LNX.4.44.0309060841590.27355-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0309060841590.27355-100000@netcore.fi>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Pekka Savola wrote:

>>     - Support for a Mobile Node changing its home address, either
>>       because of renumbering in its home network or because it
>>       periodically changes addresses (perhaps via RFC3041)
> 
> 
> Isn't this already supported?  

it is.

what is missing is how to authorize Binding Updates for the new HoA
configured from RFC 3041. the HA should be able to verify if the MN
owns the home address.

Vijay

Why else are we doing DHAAD as we speak?
> Couldn't one connect to another HA (or to the same one twice) to obtain 
> two addresses, end of story?
> 
> Note: using RFC3041 on home addresses is probably very bad idea.  The 
> prefix stays static, so in practice this will not give much additional 
> privacy, unless there are thousands of MN's under the same HA prefix.
> 
> 
>>  ------------------------------------------
>>
>>
>>  Sep 03 Charter approval
>>
>>  Nov 03 Problem statement documents (to IESG)
>>           - Issues with firewall
>>           - Mobile IPv6 transition between v4/v6 networks
>>
>>  Jan 03 Bootstrapping problem statement to IESG
>>
>>  Feb 04 Submit MIPv6 MIB to IESG
>>
>>  Mar 04 Submit alternate security mechanisms for securing the
>>	 signaling message between Mobile Node (MN) and Home Agent
>>	 (HA) to IESG 
>>
>>  Mar 04 Alternate Route Optimization scheme to IESG
>>
>>  May 04 Home agent reliability to IESG
>>
>>  Aug 04 Bootstrapping solution to IESG
>>
>>  Nov 04 Separate specs for Home Agent (HA) Discovery, Route Optimization,
>>         Renumbering to IESG
> 
> 
> General note: the charter milestones are quite fast-tracked.  For this to 
> succeed, I think we have to have a clear commitment from the WG and the 
> document editors, and no major issues raised.
> 
> It's OK as is, but I would be a bit more pessimistic about the delivery 
> dates.
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sun Sep  7 14:57:47 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 OAA28526
	for <mip6-archive@odin.ietf.org>; Sun, 7 Sep 2003 14:57: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 19w4ix-00071o-H8
	for mip6-archive@odin.ietf.org; Sun, 07 Sep 2003 14:57:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h87IvN4c027010
	for mip6-archive@odin.ietf.org; Sun, 7 Sep 2003 14:57:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w4ix-00071Z-Cp
	for mip6-web-archive@optimus.ietf.org; Sun, 07 Sep 2003 14:57:23 -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 OAA28492
	for <mip6-web-archive@ietf.org>; Sun, 7 Sep 2003 14:57:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w4iu-00007L-00
	for mip6-web-archive@ietf.org; Sun, 07 Sep 2003 14:57:20 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19w4iu-00007I-00
	for mip6-web-archive@ietf.org; Sun, 07 Sep 2003 14:57:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w4iv-00071G-GS; Sun, 07 Sep 2003 14:57:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19w4hN-0006zE-V1
	for mip6@optimus.ietf.org; Sun, 07 Sep 2003 14:55: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 OAA28399
	for <mip6@ietf.org>; Sun, 7 Sep 2003 14:55:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w4hL-0007bx-00
	for mip6@ietf.org; Sun, 07 Sep 2003 14:55:43 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19w4hK-0007bR-00
	for mip6@ietf.org; Sun, 07 Sep 2003 14:55:42 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id h87It5E21769;
	Sun, 7 Sep 2003 21:55:05 +0300
Date: Sun, 7 Sep 2003 21:55:04 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
cc: Basavaraj.Patil@nokia.com, <mip6@ietf.org>
Subject: Re: [Mip6] Revised Charter
In-Reply-To: <3F5B54D3.2060005@iprg.nokia.com>
Message-ID: <Pine.LNX.4.44.0309072152140.20520-100000@netcore.fi>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

On Sun, 7 Sep 2003, Vijay Devarapalli wrote:
> Pekka Savola wrote:
> >>     - Support for a Mobile Node changing its home address, either
> >>       because of renumbering in its home network or because it
> >>       periodically changes addresses (perhaps via RFC3041)
> > 
> > 
> > Isn't this already supported?  
> 
> it is.
> 
> what is missing is how to authorize Binding Updates for the new HoA
> configured from RFC 3041. the HA should be able to verify if the MN
> owns the home address.

Authorize to *whom*?

For CN?

Why can't one perform the return routability test for each one used?
Shouldn't that fix the problem?

For HA?

Why don't the current methods work?  Because the MN has created the 
RFC3041 address independently, without consulting Home Agent, and needs to 
sync up that with the HA?

> Why else are we doing DHAAD as we speak?
> > Couldn't one connect to another HA (or to the same one twice) to obtain 
> > two addresses, end of story?
> > 
> > Note: using RFC3041 on home addresses is probably very bad idea.  The 
> > prefix stays static, so in practice this will not give much additional 
> > privacy, unless there are thousands of MN's under the same HA prefix.
> > 
> > 
> >>  ------------------------------------------
> >>
> >>
> >>  Sep 03 Charter approval
> >>
> >>  Nov 03 Problem statement documents (to IESG)
> >>           - Issues with firewall
> >>           - Mobile IPv6 transition between v4/v6 networks
> >>
> >>  Jan 03 Bootstrapping problem statement to IESG
> >>
> >>  Feb 04 Submit MIPv6 MIB to IESG
> >>
> >>  Mar 04 Submit alternate security mechanisms for securing the
> >>	 signaling message between Mobile Node (MN) and Home Agent
> >>	 (HA) to IESG 
> >>
> >>  Mar 04 Alternate Route Optimization scheme to IESG
> >>
> >>  May 04 Home agent reliability to IESG
> >>
> >>  Aug 04 Bootstrapping solution to IESG
> >>
> >>  Nov 04 Separate specs for Home Agent (HA) Discovery, Route Optimization,
> >>         Renumbering to IESG
> > 
> > 
> > General note: the charter milestones are quite fast-tracked.  For this to 
> > succeed, I think we have to have a clear commitment from the WG and the 
> > document editors, and no major issues raised.
> > 
> > It's OK as is, but I would be a bit more pessimistic about the delivery 
> > dates.
> > 
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Mon Sep  8 00:07:39 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 AAA04972
	for <mip6-archive@odin.ietf.org>; Mon, 8 Sep 2003 00:07:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wDJ4-0006mb-6K
	for mip6-archive@odin.ietf.org; Mon, 08 Sep 2003 00:07:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8847DqX026055
	for mip6-archive@odin.ietf.org; Mon, 8 Sep 2003 00:07:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wDJ1-0006lI-EB
	for mip6-web-archive@optimus.ietf.org; Mon, 08 Sep 2003 00:07:11 -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 AAA04841
	for <mip6-web-archive@ietf.org>; Mon, 8 Sep 2003 00:07:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wDIR-0006Tz-91; Mon, 08 Sep 2003 00:06:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wCnb-0004Gu-P4
	for mip6@optimus.ietf.org; Sun, 07 Sep 2003 23:34: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 XAA02129
	for <mip6@ietf.org>; Sun, 7 Sep 2003 23:34:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wCnZ-0001Er-00
	for mip6@ietf.org; Sun, 07 Sep 2003 23:34:41 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wCnY-0001Dy-00
	for mip6@ietf.org; Sun, 07 Sep 2003 23:34:41 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h883Y2Y00503;
	Sun, 7 Sep 2003 20:34:02 -0700
X-mProtect: <200309080334> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (10.241.48.154, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdQeKurc; Sun, 07 Sep 2003 20:34:00 PDT
Message-ID: <3F5BF8A4.8050101@iprg.nokia.com>
Date: Sun, 07 Sep 2003 20:33:56 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
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: Pekka Savola <pekkas@netcore.fi>
CC: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: Re: [Mip6] Revised Charter
References: <Pine.LNX.4.44.0309072152140.20520-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0309072152140.20520-100000@netcore.fi>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

to the HA. the HA needs to prevent a misbehaving MN from claiming
another MN's home address. the HA doesnt know about the MN's new
RFC3041 home address.

this is not needed in all deployment scenarios though.

Vijay

Pekka Savola wrote:

> On Sun, 7 Sep 2003, Vijay Devarapalli wrote:
> 
>>Pekka Savola wrote:
>>
>>>>    - Support for a Mobile Node changing its home address, either
>>>>      because of renumbering in its home network or because it
>>>>      periodically changes addresses (perhaps via RFC3041)
>>>
>>>
>>>Isn't this already supported?  
>>
>>it is.
>>
>>what is missing is how to authorize Binding Updates for the new HoA
>>configured from RFC 3041. the HA should be able to verify if the MN
>>owns the home address.
> 
> 
> Authorize to *whom*?
> 
> For CN?
> 
> Why can't one perform the return routability test for each one used?
> Shouldn't that fix the problem?
> 
> For HA?
> 
> Why don't the current methods work?  Because the MN has created the 
> RFC3041 address independently, without consulting Home Agent, and needs to 
> sync up that with the HA?
> 
> 
>>Why else are we doing DHAAD as we speak?
>>
>>>Couldn't one connect to another HA (or to the same one twice) to obtain 
>>>two addresses, end of story?
>>>
>>>Note: using RFC3041 on home addresses is probably very bad idea.  The 
>>>prefix stays static, so in practice this will not give much additional 
>>>privacy, unless there are thousands of MN's under the same HA prefix.
>>>
>>>
>>>
>>>> ------------------------------------------
>>>>
>>>>
>>>> Sep 03 Charter approval
>>>>
>>>> Nov 03 Problem statement documents (to IESG)
>>>>          - Issues with firewall
>>>>          - Mobile IPv6 transition between v4/v6 networks
>>>>
>>>> Jan 03 Bootstrapping problem statement to IESG
>>>>
>>>> Feb 04 Submit MIPv6 MIB to IESG
>>>>
>>>> Mar 04 Submit alternate security mechanisms for securing the
>>>>	 signaling message between Mobile Node (MN) and Home Agent
>>>>	 (HA) to IESG 
>>>>
>>>> Mar 04 Alternate Route Optimization scheme to IESG
>>>>
>>>> May 04 Home agent reliability to IESG
>>>>
>>>> Aug 04 Bootstrapping solution to IESG
>>>>
>>>> Nov 04 Separate specs for Home Agent (HA) Discovery, Route Optimization,
>>>>        Renumbering to IESG
>>>
>>>
>>>General note: the charter milestones are quite fast-tracked.  For this to 
>>>succeed, I think we have to have a clear commitment from the WG and the 
>>>document editors, and no major issues raised.
>>>
>>>It's OK as is, but I would be a bit more pessimistic about the delivery 
>>>dates.
>>>
>>
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Mon Sep  8 13:36: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 NAA10084
	for <mip6-archive@odin.ietf.org>; Mon, 8 Sep 2003 13:36: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 19wPvp-000674-IR
	for mip6-archive@odin.ietf.org; Mon, 08 Sep 2003 13:36:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h88Ha5gB023492
	for mip6-archive@odin.ietf.org; Mon, 8 Sep 2003 13:36:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wPvp-00066p-E7
	for mip6-web-archive@optimus.ietf.org; Mon, 08 Sep 2003 13:36: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 NAA10057
	for <mip6-web-archive@ietf.org>; Mon, 8 Sep 2003 13:35:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wPvn-0004Ba-00
	for mip6-web-archive@ietf.org; Mon, 08 Sep 2003 13:36:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19wPvm-0004BW-00
	for mip6-web-archive@ietf.org; Mon, 08 Sep 2003 13: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 19wPvm-00065D-UK; Mon, 08 Sep 2003 13: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 19wPv8-00063V-99
	for mip6@optimus.ietf.org; Mon, 08 Sep 2003 13:35: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 NAA10021
	for <mip6@ietf.org>; Mon, 8 Sep 2003 13:35:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wPv6-0004AR-00
	for mip6@ietf.org; Mon, 08 Sep 2003 13:35:20 -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 19wPv5-0004AN-00
	for mip6@ietf.org; Mon, 08 Sep 2003 13:35:19 -0400
Message-ID: <019801c3762f$9c52abf0$956015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>, <Basavaraj.Patil@nokia.com>
Cc: <mip6@ietf.org>
References: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com> <3F58098E.1060102@kolumbus.fi>
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
Date: Mon, 8 Sep 2003 10:35:34 -0700
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I agree with Jari on this point, with the exception that I am not sure
whether the right solution is IKEv2 or an application specific mechanism.

I think we should be looking toward one mechanism for securing the HA-MN
link, and it should support bootstrapping and the MN changing address, with
the possibility of setting up a "security association" (which may or may not
be IKE-related) dynamically for dynamic home agent selection. Another
requirement I believe is important, not listed below, is ease of deployment
and maintenance. If the currently specified IKE mechanism turns out to be
too cumbersome or not adaptable to support these requirements, then we
should replace it, but it is not clear to me at this point whether that is
so. Having more than one mechanism leaves open the possibility for
interoperability problems on the host, especially if dynamic home agent
selection is to be supported.

            jak

----- Original Message ----- 
From: "Jari Arkko" <jari.arkko@kolumbus.fi>
To: <Basavaraj.Patil@nokia.com>
Cc: <mip6@ietf.org>
Sent: Thursday, September 04, 2003 8:57 PM
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item


> Basavaraj.Patil@nokia.com wrote:
> > Hello,
> >
> > The following is a milestone identified in the current charter for
> > Mobile IPv6:
> >
> >  o Mar 04 Submit alternate security mechanisms for HA-MN to IESG
> >
> > However there is no corresponding text describing what this milestone
> > really means in the charter. My view of the above milestone is as
> > follows:
> >    Currently IPsec provides the means for authenticating a MN to the
> >    HA. This mandates the existence of an IPsec SA between the MN and
> >    HA. It is possible that an equivalent degree of security for the
> >    BU/BAck can be achieved by encapsulating an authenticator in a
> >    Binding data suboption. This basically falls back to the Mobile
> >    IPv4 model of authentication between MN-HA where the MN-HA auth
> >    extension is sufficient to create the binding in the HA. With this
> >    approach there is no reason to implement IPsec/IKE(v2) in a MIPv6
> >    MN, which I think is an overkill for basically doing authentication
> >    between two entities that are aware of each other.
> >
> > So the question is:
> > 1. Should the Mobile IPv6 take on the work item mentioned in the
> >    milestone above?
> >
> > A:
> >    Yes  [ ]
> >    No   [ ]
>
> I believe we need the work item, but I am unsure about the text
> that was provided. Basically, at this time we lack two important
> functions from the HA-MN interface security. Here's what the old
> charter proposals said about them:
>
>     - A bootstrap mechanism for setting up security
>       associations between the MN and HA that would enable easier
>       deployment of Mobile IPv6.
>
>     - Support for the MN's changing addresses either because of
>       renumbering in its home network or because it periodically
>       changes addresses (perhaps via rfc3041)
>
> Its unclear to me whether your intent was to replace the work
> on these with the options work, or would both still be done?
> If its the latter, is that work independent of the alternative
> HA-MN security work or performed together?
>
> Basically, I believe the bootstrap and dynamic addressing
> features are more important than simply replacing current
> protocol mechanism with another. Note that, as discussed in
> IETF-57, taking in account these two features could well mean
> replacing IPsec with something else; the choices really are
> something IKEv2 based or something "application" layer based -
> and I prefer the latter. But I think the charter should be
> written so that we require a mechanism to be designed such
> that these two features are provided, and leave more room
> for the specific solution to be developed.
>
> --Jari
>
>
> _______________________________________________
> 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 Sep  8 14:21: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 OAA12213
	for <mip6-archive@odin.ietf.org>; Mon, 8 Sep 2003 14:21: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 19wQdL-0008UC-Qk
	for mip6-archive@odin.ietf.org; Mon, 08 Sep 2003 14:21:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h88IL3KB032614
	for mip6-archive@odin.ietf.org; Mon, 8 Sep 2003 14:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wQdL-0008Tx-MY
	for mip6-web-archive@optimus.ietf.org; Mon, 08 Sep 2003 14:21: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 OAA12174
	for <mip6-web-archive@ietf.org>; Mon, 8 Sep 2003 14:20:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wQdJ-00051Q-00
	for mip6-web-archive@ietf.org; Mon, 08 Sep 2003 14:21:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19wQdI-00051N-00
	for mip6-web-archive@ietf.org; Mon, 08 Sep 2003 14:21:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wQdK-0008Tc-G0; Mon, 08 Sep 2003 14:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19wQd7-0008T8-Vo
	for mip6@optimus.ietf.org; Mon, 08 Sep 2003 14:20: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 OAA12146
	for <mip6@ietf.org>; Mon, 8 Sep 2003 14:20:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19wQd5-00050v-00
	for mip6@ietf.org; Mon, 08 Sep 2003 14:20:47 -0400
Received: from fep06-0.kolumbus.fi ([193.229.0.57] helo=fep06-app.kolumbus.fi)
	by ietf-mx with esmtp (Exim 4.12)
	id 19wQd4-00050r-00
	for mip6@ietf.org; Mon, 08 Sep 2003 14:20:46 -0400
Received: from kolumbus.fi ([62.248.171.109]) by fep06-app.kolumbus.fi
          with ESMTP
          id <20030908181938.ZVA2570.fep06-app.kolumbus.fi@kolumbus.fi>;
          Mon, 8 Sep 2003 21:19:38 +0300
Message-ID: <3F5CC7C2.3070602@kolumbus.fi>
Date: Mon, 08 Sep 2003 21:17:38 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
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: James Kempf <kempf@docomolabs-usa.com>
CC: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: Re: [Mip6] Seeking consensus on a MIP6 charter item
References: <697DAA22C5004B4596E033803A7CEF44024DB66F@daebe007.americas.nokia.com> <3F58098E.1060102@kolumbus.fi> <019801c3762f$9c52abf0$956015ac@dclkempt40>
In-Reply-To: <019801c3762f$9c52abf0$956015ac@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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

James Kempf wrote:
> I agree with Jari on this point, with the exception that I am not sure
> whether the right solution is IKEv2 or an application specific mechanism.
> 
> I think we should be looking toward one mechanism for securing the HA-MN
> link, and it should support bootstrapping and the MN changing address, with
> the possibility of setting up a "security association" (which may or may not
> be IKE-related) dynamically for dynamic home agent selection. Another
> requirement I believe is important, not listed below, is ease of deployment
> and maintenance. If the currently specified IKE mechanism turns out to be
> too cumbersome or not adaptable to support these requirements, then we
> should replace it, but it is not clear to me at this point whether that is
> so. Having more than one mechanism leaves open the possibility for
> interoperability problems on the host, especially if dynamic home agent
> selection is to be supported.

I probably shouldn't claim I'm sure about what the right solution is
either. I agree with the issues you mention above. I guess it boils
down to the fact that concrete proposals are needed before we can
figure out what solution is the right one.

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 10 16:22: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 QAA17013
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 16:22: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 19xBTb-0000No-CO
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 16:22:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8AKM7UV001465
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 16:22:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xBTb-0000NY-4u
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 2003 16:22: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 QAA16989
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 16:22:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBTZ-0000YB-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 16:22:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBTZ-0000Y4-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 16:22:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xBTW-0000Mn-1X; Wed, 10 Sep 2003 16:22:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xBT8-0000KY-UH
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 16:21: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 QAA16956
	for <mip6@ietf.org>; Wed, 10 Sep 2003 16:21:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBT7-0000Vj-00
	for mip6@ietf.org; Wed, 10 Sep 2003 16:21:37 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBT6-0000T0-00
	for mip6@ietf.org; Wed, 10 Sep 2003 16:21:36 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h8AKL59F001667
	for <mip6@ietf.org>; Wed, 10 Sep 2003 13:21:05 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-163-62.cisco.com [128.107.163.62])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALK21188;
	Wed, 10 Sep 2003 13:10:01 -0700 (PDT)
Message-ID: <3F5F87B0.8090301@cisco.com>
Date: Wed, 10 Sep 2003 13:21:04 -0700
From: Alpesh <alpesh@cisco.com>
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] Issue with mipv6 charter
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

WG Folks:

Wondering if the charter should include an entity in the
visited domain/roaming network to aid in AAA/Diameter authentication,
access control etc? Currently, there is little, if any mechanism
to restrict a mobile node's activities in visited domain.

For practical deployment issues and network management/control
purposes, I think such an entity is needed.

Anyone else thinking on similar lines?

Alpesh


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 10 16:38: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 QAA17493
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 16: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 19xBj0-0002F3-Te
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 16:38:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8AKc2l5008604
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 16:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xBj0-0002Eg-Go
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 2003 16:38: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 QAA17479
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 16:37:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBiy-0001yX-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 16:38:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBiy-0001yS-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 16: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 19xBiz-0002Dc-GK; Wed, 10 Sep 2003 16: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 19xBi4-0001rw-8D
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 16:37: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 QAA17470
	for <mip6@ietf.org>; Wed, 10 Sep 2003 16:36:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBi2-0001tg-00
	for mip6@ietf.org; Wed, 10 Sep 2003 16:37:02 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xBi1-0001qg-00
	for mip6@ietf.org; Wed, 10 Sep 2003 16:37:01 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <ST25CBCL>; Wed, 10 Sep 2003 16:36:27 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D12@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Alpesh'" <alpesh@cisco.com>, mip6@ietf.org
Subject: RE: [Mip6] Issue with mipv6 charter
Date: Wed, 10 Sep 2003 16:36:23 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>



 > Wondering if the charter should include an entity in the
 > visited domain/roaming network to aid in AAA/Diameter authentication,
 > access control etc? 

=> a NAS ? ;) The description of this entity doesn't 
seem to be related to mobility in any way. I think
this work is generic for fixed and mobile nodes.

   Currently, there is little, if any mechanism
 > to restrict a mobile node's activities in visited domain.

=> Why do you say that? A NAS will do this job very well
provided that AAA mechanisms and roaming agreements 
are in place. 

 > For practical deployment issues and network management/control
 > purposes, I think such an entity is needed.

=> Absolutely, but MIP6 has nothing to do with it.

Hesham

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 10 18:32: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 SAA21500
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 18:32: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 19xDVK-0006Af-Ed
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 18:32:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8AMW2qw023721
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 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 19xDVK-0006AW-9C
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 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 SAA21485
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 18:31:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDVH-00042p-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 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 19xDVG-00042l-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 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 19xDVI-0006A1-Ej; Wed, 10 Sep 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 19xDV6-00065a-EN
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 18:31: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 SAA21481
	for <mip6@ietf.org>; Wed, 10 Sep 2003 18:31:39 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDV3-00041b-00
	for mip6@ietf.org; Wed, 10 Sep 2003 18:31:45 -0400
Received: from [63.78.179.216] (helo=mgw-dax1.ext.nokia.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDV2-00041K-00
	for mip6@ietf.org; Wed, 10 Sep 2003 18:31:44 -0400
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h8AMVg102299
	for <mip6@ietf.org>; Wed, 10 Sep 2003 17:31:42 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6498f7bd34ac12f254079@davir01nok.americas.nokia.com>;
 Wed, 10 Sep 2003 17:31:42 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 10 Sep 2003 15:30:23 -0700
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] Issue with mipv6 charter
Date: Wed, 10 Sep 2003 17:30:22 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com>
Thread-Topic: [Mip6] Issue with mipv6 charter
Thread-Index: AcN323GVvaI4kDPlTN2zSwI+bPoQVAAD1Row
To: <H.Soliman@flarion.com>, <alpesh@cisco.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 10 Sep 2003 22:30:23.0307 (UTC) FILETIME=[1FEBC1B0:01C377EB]
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>=20
>  > Wondering if the charter should include an entity in the
>  > visited domain/roaming network to aid in AAA/Diameter=20
> authentication,
>  > access control etc?=20
>=20
> =3D> a NAS ? ;) The description of this entity doesn't=20
> seem to be related to mobility in any way. I think
> this work is generic for fixed and mobile nodes.
>=20
>    Currently, there is little, if any mechanism
>  > to restrict a mobile node's activities in visited domain.
>=20
> =3D> Why do you say that? A NAS will do this job very well
> provided that AAA mechanisms and roaming agreements=20
> are in place.=20
>=20
>  > For practical deployment issues and network management/control
>  > purposes, I think such an entity is needed.
>=20
> =3D> Absolutely, but MIP6 has nothing to do with it.

I agree with Hesham's comments above.=20
Network Access authentication/authorization and roaming is in=20
the realm of NAS and AAA. I dont see what the MIP6 WG has to do
with this.=20

>=20
> Hesham
>=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  Wed Sep 10 18:54: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 SAA22074
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 18:54: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 19xDqc-0000KH-IS
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 18:54:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8AMs2Ti001247
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 18:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xDqc-0000K1-A4
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 2003 18:54: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 SAA22062
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 18:53:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDqY-00060N-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 18:53:58 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDqY-00060K-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 18:53:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xDqa-0000Iz-Un; Wed, 10 Sep 2003 18: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 19xDqB-0000GD-EM
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 18:53: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 SAA22038
	for <mip6@ietf.org>; Wed, 10 Sep 2003 18:53:26 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDq8-0005xd-00
	for mip6@ietf.org; Wed, 10 Sep 2003 18:53:32 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDq7-0005uv-00
	for mip6@ietf.org; Wed, 10 Sep 2003 18:53:32 -0400
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 h8AMr0bs027327;
	Wed, 10 Sep 2003 15:53:00 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-163-62.cisco.com [128.107.163.62])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALK43028;
	Wed, 10 Sep 2003 15:41:55 -0700 (PDT)
Message-ID: <3F5FAB4B.4060807@cisco.com>
Date: Wed, 10 Sep 2003 15:52:59 -0700
From: Alpesh <alpesh@cisco.com>
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: Basavaraj.Patil@nokia.com
CC: H.Soliman@flarion.com, mip6@ietf.org
Subject: Re: [Mip6] Issue with mipv6 charter
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com>
Content-Type: multipart/alternative;
 boundary="------------010409090401000304020004"
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


--------------010409090401000304020004
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Raj:

I am more or less looking at functionality in access router/first hop
router in the visited domain (home or foreign) to control the MN's
access to the network for authentication, billing, access control etc.

With route optimization, this is an issue from an operator perspective
since the mobile can bypass the HA.

I think this issue is added by the MIP protocol and should ideally be
addressed here.

-alpesh

Basavaraj.Patil@nokia.com wrote:

>> > Wondering if the charter should include an entity in the
>> > visited domain/roaming network to aid in AAA/Diameter 
>>authentication,
>> > access control etc? 
>>
>>=> a NAS ? ;) The description of this entity doesn't 
>>seem to be related to mobility in any way. I think
>>this work is generic for fixed and mobile nodes.
>>
>>   Currently, there is little, if any mechanism
>> > to restrict a mobile node's activities in visited domain.
>>
>>=> Why do you say that? A NAS will do this job very well
>>provided that AAA mechanisms and roaming agreements 
>>are in place. 
>>
>> > For practical deployment issues and network management/control
>> > purposes, I think such an entity is needed.
>>
>>=> Absolutely, but MIP6 has nothing to do with it.
>>    
>>
>
>I agree with Hesham's comments above. 
>Network Access authentication/authorization and roaming is in 
>the realm of NAS and AAA. I dont see what the MIP6 WG has to do
>with this. 
>
>  
>
>>Hesham
>>
>>_______________________________________________
>>Mip6 mailing list
>>Mip6@ietf.org
>>https://www.ietf.org/mailman/listinfo/mip6
>>    
>>
>
>  
>


--------------010409090401000304020004
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Raj:<br>
<br>
I am more or less looking at functionality in access router/first hop<br>
router in the visited domain (home or foreign) to control the MN's<br>
access to the network for authentication, billing, access control etc.<br>
<br>
With route optimization, this is an issue from an operator perspective<br>
since the mobile can bypass the HA. <br>
<br>
I think this issue is added by the MIP protocol and should ideally be<br>
addressed here.<br>
<br>
-alpesh<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Basavaraj.Patil@nokia.com">Basavaraj.Patil@nokia.com</a> wrote:<br>
<blockquote type="cite"
 cite="mid697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com">
  <blockquote type="cite">
    <pre wrap=""> &gt; Wondering if the charter should include an entity in the
 &gt; visited domain/roaming network to aid in AAA/Diameter 
authentication,
 &gt; access control etc? 

=&gt; a NAS ? ;) The description of this entity doesn't 
seem to be related to mobility in any way. I think
this work is generic for fixed and mobile nodes.

   Currently, there is little, if any mechanism
 &gt; to restrict a mobile node's activities in visited domain.

=&gt; Why do you say that? A NAS will do this job very well
provided that AAA mechanisms and roaming agreements 
are in place. 

 &gt; For practical deployment issues and network management/control
 &gt; purposes, I think such an entity is needed.

=&gt; Absolutely, but MIP6 has nothing to do with it.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I agree with Hesham's comments above. 
Network Access authentication/authorization and roaming is in 
the realm of NAS and AAA. I dont see what the MIP6 WG has to do
with this. 

  </pre>
  <blockquote type="cite">
    <pre wrap="">Hesham

_______________________________________________
Mip6 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Mip6@ietf.org">Mip6@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mip6">https://www.ietf.org/mailman/listinfo/mip6</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
</body>
</html>

--------------010409090401000304020004--


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 10 19:03: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 TAA22360
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 19:03: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 19xDzK-0001Kw-GP
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 19:03:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8AN32W0005132
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 19: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 19xDzK-0001Kh-B6
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 2003 19: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 TAA22339
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 19:02:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDzH-0006oy-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 19:02:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDzG-0006ov-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 19: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 19xDzJ-0001Jl-G7; Wed, 10 Sep 2003 19: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 19xDyW-0001Dl-M7
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 19:02:12 -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 TAA22310
	for <mip6@ietf.org>; Wed, 10 Sep 2003 19:02:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDyT-0006kH-00
	for mip6@ietf.org; Wed, 10 Sep 2003 19:02:09 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xDyS-0006h4-00
	for mip6@ietf.org; Wed, 10 Sep 2003 19:02:08 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h8AN1S719011;
	Wed, 10 Sep 2003 16:01:28 -0700
X-mProtect: <200309102301> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdIZsdzc; Wed, 10 Sep 2003 16:01:27 PDT
Message-ID: <3F5FAD47.66E30BFE@iprg.nokia.com>
Date: Wed, 10 Sep 2003 16:01:27 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alpesh <alpesh@cisco.com>
CC: mip6@ietf.org
Subject: Re: [Mip6] Issue with mipv6 charter
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com> <3F5FAB4B.4060807@cisco.com>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Alpesh wrote:
> 
> With route optimization, this is an issue from an operator perspective
> since the mobile can bypass the HA.
> 
> I think this issue is added by the MIP protocol and should ideally be
> addressed here.

the way I see it, it is one of the best features of MIPv6. :)

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 10 19:27: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 TAA22815
	for <mip6-archive@odin.ietf.org>; Wed, 10 Sep 2003 19:27: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 19xEMY-00044g-OT
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 19:27:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8ANR2aq015656
	for mip6-archive@odin.ietf.org; Wed, 10 Sep 2003 19:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xEMY-00044R-JX
	for mip6-web-archive@optimus.ietf.org; Wed, 10 Sep 2003 19:27: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 TAA22809
	for <mip6-web-archive@ietf.org>; Wed, 10 Sep 2003 19:26:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xEMX-00016o-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 19:27:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xEMW-00016l-00
	for mip6-web-archive@ietf.org; Wed, 10 Sep 2003 19:27:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xEMX-000442-KO; Wed, 10 Sep 2003 19:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xEMJ-00042R-1c
	for mip6@optimus.ietf.org; Wed, 10 Sep 2003 19:26: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 TAA22796
	for <mip6@ietf.org>; Wed, 10 Sep 2003 19:26:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xEMH-00015F-00
	for mip6@ietf.org; Wed, 10 Sep 2003 19:26:45 -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 19xEMG-000158-00
	for mip6@ietf.org; Wed, 10 Sep 2003 19:26:45 -0400
Message-ID: <02ed01c377f3$05269a00$956015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alpesh" <alpesh@cisco.com>, <Basavaraj.Patil@nokia.com>
Cc: <H.Soliman@flarion.com>, <mip6@ietf.org>
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com> <3F5FAB4B.4060807@cisco.com>
Subject: Re: [Mip6] Issue with mipv6 charter
Date: Wed, 10 Sep 2003 16:26:54 -0700
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alpesh,

> I am more or less looking at functionality in access router/first hop
> router in the visited domain (home or foreign) to control the MN's
> access to the network for authentication, billing, access control etc.
>
> With route optimization, this is an issue from an operator perspective
> since the mobile can bypass the HA.
>
> I think this issue is added by the MIP protocol and should ideally be
> addressed here.
>

Not sure I understand your point.

Since you've brought up route optimization, I presume your concern is with
movement beyond the first subnet of attachment, right? Because there,
clearly the first NAS can take care of the accounting/authentication.

The MN can bypass the HA but it can't bypass the first hop router. If the
first hop router is connected up to the NAS function somehow, like it does
in a standard dialup network, the accounting/authentication information gets
back to home network in any event.

So, it becomes an issue of co-ordination between the NASes, so that the
mobile's service profile is available at the new NAS when the mobile moves
to a new subnet. There's lots of work going on in various places on this
(IEEE 802.11 is the one I'm most familiar with), not IETF unfortunately. If
you'll permit me a small plug for a WG I co-chair:
<advertisement>
The Seamoby WG is finalizing a protocol for context transfer that might be
useful, but nobody's using it for that right now.
</advertisement>

But none of this is related to Mobile IP, so it really shouldn't be in the
MIPv6 WG charter. There might be some work for other WGs (AAA? PANA?)
however.

            jak


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 11 00: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 AAA29388
	for <mip6-archive@odin.ietf.org>; Thu, 11 Sep 2003 00: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 19xJQ6-00066A-Ua
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 00:51:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8B4p22o023438
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 00: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 19xJQ6-00065w-Mu
	for mip6-web-archive@optimus.ietf.org; Thu, 11 Sep 2003 00:51: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 AAA29385
	for <mip6-web-archive@ietf.org>; Thu, 11 Sep 2003 00:50:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xJQ4-0005tp-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 00:51:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xJQ3-0005tm-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 00:50:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xJQ4-00065V-Uw; Thu, 11 Sep 2003 00:51:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xJPH-000614-OC
	for mip6@optimus.ietf.org; Thu, 11 Sep 2003 00: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 AAA29382
	for <mip6@ietf.org>; Thu, 11 Sep 2003 00:50:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xJPF-0005pW-00
	for mip6@ietf.org; Thu, 11 Sep 2003 00:50:09 -0400
Received: from fep22-1.kolumbus.fi ([193.229.5.122] helo=fep22-app.kolumbus.fi)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xJPE-0005pI-00
	for mip6@ietf.org; Thu, 11 Sep 2003 00:50:08 -0400
Received: from kolumbus.fi ([62.248.171.109]) by fep22-app.kolumbus.fi
          with ESMTP
          id <20030911045007.IOQD19067.fep22-app.kolumbus.fi@kolumbus.fi>;
          Thu, 11 Sep 2003 07:50:07 +0300
Message-ID: <3F5FFE3E.4060607@kolumbus.fi>
Date: Thu, 11 Sep 2003 07:46:54 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
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: Alpesh <alpesh@cisco.com>
CC: James Kempf <kempf@docomolabs-usa.com>, H.Soliman@flarion.com,
        mip6@ietf.org
Subject: Re: [Mip6] Issue with mipv6 charter
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com> <3F5FAB4B.4060807@cisco.com> <02ed01c377f3$05269a00$956015ac@dclkempt40>
In-Reply-To: <02ed01c377f3$05269a00$956015ac@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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Alpesh,

I basically agree with Hesham, Vijay, and James. I'd like to
add that the functionality you seem to be requesting is
already being provided by existing dial-up NASes, wireless
LAN APs (802.1X, 802.11i stds), and so on. And this is
independent of Mobile IPv6, making it easier to deploy
without having to have a special access router where you
are.

However, there has been some discussion of future features
where there would be some linkage between the two. For
instance, it might be useful to be able to use the same
credentials for attaching to the network as well as talking
to your home agent.

--Jari



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 11 19:20: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 TAA18300
	for <mip6-archive@odin.ietf.org>; Thu, 11 Sep 2003 19:20: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 19xajM-0003a8-DZ
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:20:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8BNK451013762
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:20:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xajM-0003Zt-0M
	for mip6-web-archive@optimus.ietf.org; Thu, 11 Sep 2003 19:20: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 TAA18262
	for <mip6-web-archive@ietf.org>; Thu, 11 Sep 2003 19:19:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xajK-0007Ho-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19:20:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xajK-0007Hj-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19:20:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xajJ-0003Zb-P2; Thu, 11 Sep 2003 19:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xaij-0003Ye-To
	for mip6@optimus.ietf.org; Thu, 11 Sep 2003 19:19:26 -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 TAA18222
	for <mip6@ietf.org>; Thu, 11 Sep 2003 19:19:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xaii-0007HD-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:19:24 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xaih-0007GH-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:19:24 -0400
Received: from cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 11 Sep 2003 16:18:54 -0700
Received: from gdommety-w2k01.cisco.com (dhcp-128-107-163-214.cisco.com [128.107.163.214])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h8BNIqXr016033;
	Thu, 11 Sep 2003 16:18:52 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030911161456.02900418@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 11 Sep 2003 16:18:51 -0700
To: Soliman Hesham <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: RE: [Mip6] Issue with mipv6 charter
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922D12@ftmail.lab.flario
 n.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

Hesham,

I am assuming that Alpesh is trying to get some level of network 
authentication/authorization via MIP signalling.

I am assuming you mean NAS (network Access server), in which case what is 
the protocol that you
have in mind for L3 authentication/authorization? (assuming that L2 
authentication/authorization may or may not exist).

Thanks
Gopal


At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:


>  > Wondering if the charter should include an entity in the
>  > visited domain/roaming network to aid in AAA/Diameter authentication,
>  > access control etc?
>
>=> a NAS ? ;) The description of this entity doesn't
>seem to be related to mobility in any way. I think
>this work is generic for fixed and mobile nodes.
>
>    Currently, there is little, if any mechanism
>  > to restrict a mobile node's activities in visited domain.
>
>=> Why do you say that? A NAS will do this job very well
>provided that AAA mechanisms and roaming agreements
>are in place.
>
>  > For practical deployment issues and network management/control
>  > purposes, I think such an entity is needed.
>
>=> Absolutely, but MIP6 has nothing to do with it.
>
>Hesham
>
>_______________________________________________
>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 Sep 11 19: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 TAA18781
	for <mip6-archive@odin.ietf.org>; Thu, 11 Sep 2003 19:38: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 19xb0m-0004OP-De
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:38:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8BNc4nq016879
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xb0l-0004NK-Qv
	for mip6-web-archive@optimus.ietf.org; Thu, 11 Sep 2003 19: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 TAA18766
	for <mip6-web-archive@ietf.org>; Thu, 11 Sep 2003 19:37:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb0k-0007P6-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19:38:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb0j-0007P1-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19:38:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xb0k-0004Lq-Bw; Thu, 11 Sep 2003 19:38:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xb03-00049e-Jx
	for mip6@optimus.ietf.org; Thu, 11 Sep 2003 19:37: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 TAA18730
	for <mip6@ietf.org>; Thu, 11 Sep 2003 19:37:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb02-0007OS-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:37:18 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb01-0007O0-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:37:17 -0400
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h8BNakXq028808;
	Thu, 11 Sep 2003 16:36:46 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-163-66.cisco.com [128.107.163.66])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALL72349;
	Thu, 11 Sep 2003 16:25:31 -0700 (PDT)
Message-ID: <3F61070C.60107@cisco.com>
Date: Thu, 11 Sep 2003 16:36:44 -0700
From: Alpesh <alpesh@cisco.com>
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: Basavaraj.Patil@nokia.com
CC: H.Soliman@flarion.com, mip6@ietf.org
Subject: Re: [Mip6] Issue with mipv6 charter
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com>
Content-Type: multipart/alternative;
 boundary="------------040605050504040705040803"
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


--------------040605050504040705040803
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Raj:

My point is we already have layer 2 authentication and mobile
may be forced to do that in certain environments (but it may
as well not do be). What is the auth/authorization mechanism
available at layer 3? How can the access router control the
roaming node from attaching and using its services? This is
the functionality that I am looking at tying with MIP signalling
to be used by access router.


-a

Basavaraj.Patil@nokia.com wrote:

>> > Wondering if the charter should include an entity in the
>> > visited domain/roaming network to aid in AAA/Diameter 
>>authentication,
>> > access control etc? 
>>
>>=> a NAS ? ;) The description of this entity doesn't 
>>seem to be related to mobility in any way. I think
>>this work is generic for fixed and mobile nodes.
>>
>>   Currently, there is little, if any mechanism
>> > to restrict a mobile node's activities in visited domain.
>>
>>=> Why do you say that? A NAS will do this job very well
>>provided that AAA mechanisms and roaming agreements 
>>are in place. 
>>
>> > For practical deployment issues and network management/control
>> > purposes, I think such an entity is needed.
>>
>>=> Absolutely, but MIP6 has nothing to do with it.
>>    
>>
>
>I agree with Hesham's comments above. 
>Network Access authentication/authorization and roaming is in 
>the realm of NAS and AAA. I dont see what the MIP6 WG has to do
>with this. 
>
>  
>
>>Hesham
>>
>>_______________________________________________
>>Mip6 mailing list
>>Mip6@ietf.org
>>https://www.ietf.org/mailman/listinfo/mip6
>>
>>    
>>
>
>  
>


--------------040605050504040705040803
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Raj:<br>
<br>
My point is we already have layer 2 authentication and mobile<br>
may be forced to do that in certain environments (but it may <br>
as well not do be). What is the auth/authorization mechanism<br>
available at layer 3? How can the access router control the<br>
roaming node from attaching and using its services? This is<br>
the functionality that I am looking at tying with MIP signalling<br>
to be used by access router.<br>
<br>
<br>
-a<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Basavaraj.Patil@nokia.com">Basavaraj.Patil@nokia.com</a> wrote:<br>
<blockquote type="cite"
 cite="mid697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com">
  <blockquote type="cite">
    <pre wrap=""> &gt; Wondering if the charter should include an entity in the
 &gt; visited domain/roaming network to aid in AAA/Diameter 
authentication,
 &gt; access control etc? 

=&gt; a NAS ? ;) The description of this entity doesn't 
seem to be related to mobility in any way. I think
this work is generic for fixed and mobile nodes.

   Currently, there is little, if any mechanism
 &gt; to restrict a mobile node's activities in visited domain.

=&gt; Why do you say that? A NAS will do this job very well
provided that AAA mechanisms and roaming agreements 
are in place. 

 &gt; For practical deployment issues and network management/control
 &gt; purposes, I think such an entity is needed.

=&gt; Absolutely, but MIP6 has nothing to do with it.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I agree with Hesham's comments above. 
Network Access authentication/authorization and roaming is in 
the realm of NAS and AAA. I dont see what the MIP6 WG has to do
with this. 

  </pre>
  <blockquote type="cite">
    <pre wrap="">Hesham

_______________________________________________
Mip6 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Mip6@ietf.org">Mip6@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mip6">https://www.ietf.org/mailman/listinfo/mip6</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
</body>
</html>

--------------040605050504040705040803--


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 11 19:46: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 TAA19012
	for <mip6-archive@odin.ietf.org>; Thu, 11 Sep 2003 19:46: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 19xb8V-0004je-A5
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:46:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8BNk3JC018196
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 19:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xb8V-0004jP-57
	for mip6-web-archive@optimus.ietf.org; Thu, 11 Sep 2003 19:46: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 TAA19002
	for <mip6-web-archive@ietf.org>; Thu, 11 Sep 2003 19:45:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb8T-0007Tx-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19:46:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb8T-0007Tu-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 19: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 19xb8T-0004iY-W9; Thu, 11 Sep 2003 19: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 19xb7q-0004ht-Ht
	for mip6@optimus.ietf.org; Thu, 11 Sep 2003 19:45: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 TAA18994
	for <mip6@ietf.org>; Thu, 11 Sep 2003 19:45:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xb7o-0007Th-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:45:20 -0400
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 19xb7n-0007TO-00
	for mip6@ietf.org; Thu, 11 Sep 2003 19:45:20 -0400
Received: from cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 11 Sep 2003 16:58:15 -0700
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 h8BNiibs027810;
	Thu, 11 Sep 2003 16:44:45 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-163-66.cisco.com [128.107.163.66])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALL73351;
	Thu, 11 Sep 2003 16:33:30 -0700 (PDT)
Message-ID: <3F6108EB.4010603@cisco.com>
Date: Thu, 11 Sep 2003 16:44:43 -0700
From: Alpesh <alpesh@cisco.com>
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: Jari Arkko <jari.arkko@kolumbus.fi>
CC: James Kempf <kempf@docomolabs-usa.com>, H.Soliman@flarion.com,
        mip6@ietf.org
Subject: Re: [Mip6] Issue with mipv6 charter
References: <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com> <3F5FAB4B.4060807@cisco.com> <02ed01c377f3$05269a00$956015ac@dclkempt40> <3F5FFE3E.4060607@kolumbus.fi>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jari:

Jari Arkko wrote:

>
> Alpesh,
>
> I basically agree with Hesham, Vijay, and James. I'd like to
> add that the functionality you seem to be requesting is
> already being provided by existing dial-up NASes, wireless
> LAN APs (802.1X, 802.11i stds), and so on. And this is
> independent of Mobile IPv6, making it easier to deploy
> without having to have a special access router where you
> are. 

I understand that L2 authentication may or may not be present. I am
not talking about "special access router" , but just some additional
functionality in access router (which is present anyway).

My concern is with Layer3 authentication/authorization for the mobile 
node. If
there is a mechanism available to tie the L2 
authentication/authorization with L3
authentication/authorization, I am okay with that (can you point me to 
something
in that direction?).

With MIP and existing NAS infrastructure - when would you do NAS 
authen/authorization
 for L3 access - before/after MIP signalling?
-a

>
>
> However, there has been some discussion of future features
> where there would be some linkage between the two. For
> instance, it might be useful to be able to use the same
> credentials for attaching to the network as well as talking
> to your home agent.
>
> --Jari
>
>
>



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 11 23: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 XAA23357
	for <mip6-archive@odin.ietf.org>; Thu, 11 Sep 2003 23: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 19xeAK-0001Ce-9O
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 23:00:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8C308nd004624
	for mip6-archive@odin.ietf.org; Thu, 11 Sep 2003 23:00:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xeAI-0001CV-Rq
	for mip6-web-archive@optimus.ietf.org; Thu, 11 Sep 2003 23: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 WAA23321
	for <mip6-web-archive@ietf.org>; Thu, 11 Sep 2003 22:59:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xeAF-00014P-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 23:00:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xeAE-00014K-00
	for mip6-web-archive@ietf.org; Thu, 11 Sep 2003 23: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 19xeAG-0001CC-3y; Thu, 11 Sep 2003 23:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xe9F-0001BM-CA
	for mip6@optimus.ietf.org; Thu, 11 Sep 2003 22:59: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 WAA23313
	for <mip6@ietf.org>; Thu, 11 Sep 2003 22:58:53 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xe9B-00013x-00
	for mip6@ietf.org; Thu, 11 Sep 2003 22:58:57 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xe9A-00013u-00
	for mip6@ietf.org; Thu, 11 Sep 2003 22:58:57 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h8C2wt409233
	for <mip6@ietf.org>; Fri, 12 Sep 2003 05:58:56 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T64a0ca3260ac158f23077@esvir03nok.nokia.com>;
 Fri, 12 Sep 2003 05:58:55 +0300
Received: from daebh001.NOE.Nokia.com ([172.18.242.231]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 12 Sep 2003 05:58:54 +0300
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 11 Sep 2003 19:58:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C378D9.CB75874A"
Subject: RE: [Mip6] Issue with mipv6 charter
Date: Thu, 11 Sep 2003 21:58:51 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB6EF@daebe007.americas.nokia.com>
Thread-Topic: [Mip6] Issue with mipv6 charter
Thread-Index: AcN4vZVJihqcyCHUS06i6937Us8TVAAHAHaw
To: <alpesh@cisco.com>
Cc: <H.Soliman@flarion.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 12 Sep 2003 02:58:51.0787 (UTC) FILETIME=[CBBC7DB0:01C378D9]
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C378D9.CB75874A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

PANA is a possible solution for authentication at Layer 3 to the access =
router. So please
take a look at the PANA WG.
=20
-Basavaraj
=20
=20
 Raj:

My point is we already have layer 2 authentication and mobile
may be forced to do that in certain environments (but it may=20
as well not do be). What is the auth/authorization mechanism
available at layer 3? How can the access router control the
roaming node from attaching and using its services? This is
the functionality that I am looking at tying with MIP signalling
to be used by access router.


-a


------_=_NextPart_001_01C378D9.CB75874A
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE></TITLE>

<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D811235702-12092003><FONT face=3DArial color=3D#0000ff =
size=3D2>PANA=20
is a possible solution for authentication at Layer 3 to the access =
router. So=20
please</FONT></SPAN></DIV>
<DIV><SPAN class=3D811235702-12092003><FONT face=3DArial color=3D#0000ff =
size=3D2>take a=20
look at the PANA WG.</FONT></SPAN></DIV>
<DIV><SPAN class=3D811235702-12092003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D811235702-12092003><FONT face=3DArial color=3D#0000ff =

size=3D2>-Basavaraj</FONT></SPAN></DIV>
<DIV><SPAN class=3D811235702-12092003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D811235702-12092003>&nbsp;</SPAN></DIV>
<DIV><SPAN class=3D811235702-12092003>&nbsp;</SPAN>Raj:<BR><BR>My point =
is we=20
already have layer 2 authentication and mobile<BR>may be forced to do =
that in=20
certain environments (but it may <BR>as well not do be). What is the=20
auth/authorization mechanism<BR>available at layer 3? How can the access =
router=20
control the<BR>roaming node from attaching and using its services? This=20
is<BR>the functionality that I am looking at tying with MIP =
signalling<BR>to be=20
used by access router.<BR><BR><BR>-a<BR></DIV></BODY></HTML>

------_=_NextPart_001_01C378D9.CB75874A--

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Fri Sep 12 04:24:38 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 EAA12982
	for <mip6-archive@odin.ietf.org>; Fri, 12 Sep 2003 04:24:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xjDz-0003nf-0i
	for mip6-archive@odin.ietf.org; Fri, 12 Sep 2003 04:24:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8C8OEUM014608
	for mip6-archive@odin.ietf.org; Fri, 12 Sep 2003 04:24:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xjDx-0003nW-6a
	for mip6-web-archive@optimus.ietf.org; Fri, 12 Sep 2003 04:24: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 EAA12975
	for <mip6-web-archive@ietf.org>; Fri, 12 Sep 2003 04:24:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xjDt-0003aH-00
	for mip6-web-archive@ietf.org; Fri, 12 Sep 2003 04:24:09 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19xjDt-0003aE-00
	for mip6-web-archive@ietf.org; Fri, 12 Sep 2003 04:24:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xjDt-0003nE-5S; Fri, 12 Sep 2003 04:24:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19xjCq-0003lY-VU
	for mip6@optimus.ietf.org; Fri, 12 Sep 2003 04: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 EAA12961
	for <mip6@ietf.org>; Fri, 12 Sep 2003 04:22:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xjCn-0003Zx-00
	for mip6@ietf.org; Fri, 12 Sep 2003 04:23:02 -0400
Received: from alpha9.its.monash.edu.au ([130.194.1.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 19xjCn-0003Zu-00
	for mip6@ietf.org; Fri, 12 Sep 2003 04:23:01 -0400
Received: from localhost ([130.194.13.84]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01L0KVA9JG9K8ZGX0Y@vaxh.its.monash.edu.au> for mip6@ietf.org;
 Fri, 12 Sep 2003 13:49:55 +1000
Received: from blammo.its.monash.edu.au
 (localhost.its.monash.edu.au [127.0.0.1])	by localhost (Postfix)
 with ESMTP	id 3E8BD39C003; Fri, 12 Sep 2003 13:49:55 +1000 (EST)
Received: from eng.monash.edu.au (knuth.eng.monash.edu.au [130.194.252.110])
	by blammo.its.monash.edu.au (Postfix) with ESMTP	id 207F92DC006; Fri,
 12 Sep 2003 13:49:55 +1000 (EST)
Date: Fri, 12 Sep 2003 13:49:54 +1000
From: Greg Daley <greg.daley@eng.monash.edu.au>
Subject: Re: [Mip6] Issue with mipv6 charter
To: Alpesh <alpesh@cisco.com>
Cc: Basavaraj.Patil@nokia.com, H.Soliman@flarion.com, mip6@ietf.org
Reply-to: greg.daley@eng.monash.edu.au
Message-id: <3F614262.5040706@eng.monash.edu.au>
Organization: Monash University
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en, en-us
References: 
 <697DAA22C5004B4596E033803A7CEF44024DB6D1@daebe007.americas.nokia.com>
 <3F61070C.60107@cisco.com>
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi Alpesh,

There's really no need to tie this into mobileip.

A host may have no globally addresed unicast
sessions which require mobileip signalling,
but still need access link authentication to prevent
it from causing multicast routing changes within the
access network.

currently PANA WG is looking at providing authentication protocol
transport for when the access router is used as a choke point.
Other protocols back-ending to AAA services are appropriate
if link-layer devices are the chokes.

This is orthogonal to the requirement to provide consistent
unicast addressing for upper layer protocol sessions,
which is the purpose of Mobile IPv6.

Greg Daley


Alpesh wrote:
> Raj:
> 
> My point is we already have layer 2 authentication and mobile
> may be forced to do that in certain environments (but it may
> as well not do be). What is the auth/authorization mechanism
> available at layer 3? How can the access router control the
> roaming node from attaching and using its services? This is
> the functionality that I am looking at tying with MIP signalling
> to be used by access router.
> 
> 
> -a
> 
> Basavaraj.Patil@nokia.com wrote:
> 
>>> > Wondering if the charter should include an entity in the
>>> > visited domain/roaming network to aid in AAA/Diameter 
>>>authentication,
>>> > access control etc? 
>>>
>>>=> a NAS ? ;) The description of this entity doesn't 
>>>seem to be related to mobility in any way. I think
>>>this work is generic for fixed and mobile nodes.
>>>
>>>   Currently, there is little, if any mechanism
>>> > to restrict a mobile node's activities in visited domain.
>>>
>>>=> Why do you say that? A NAS will do this job very well
>>>provided that AAA mechanisms and roaming agreements 
>>>are in place. 
>>>
>>> > For practical deployment issues and network management/control
>>> > purposes, I think such an entity is needed.
>>>
>>>=> Absolutely, but MIP6 has nothing to do with it.
>>>    
>>>
>>
>>I agree with Hesham's comments above. 
>>Network Access authentication/authorization and roaming is in 
>>the realm of NAS and AAA. I dont see what the MIP6 WG has to do
>>with this. 
>>
>>  
>>
>>>Hesham
>>>
>>>_______________________________________________
>>>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 Sep 14 22:03: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 WAA23056
	for <mip6-archive@odin.ietf.org>; Sun, 14 Sep 2003 22:03: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 19yihj-0001Rj-Ep
	for mip6-archive@odin.ietf.org; Sun, 14 Sep 2003 22:03:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8F2336g005559
	for mip6-archive@odin.ietf.org; Sun, 14 Sep 2003 22:03:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yihj-0001Ra-8e
	for mip6-web-archive@optimus.ietf.org; Sun, 14 Sep 2003 22:03: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 WAA23039
	for <mip6-web-archive@ietf.org>; Sun, 14 Sep 2003 22:02:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19yihg-0006P8-00
	for mip6-web-archive@ietf.org; Sun, 14 Sep 2003 22:03:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19yihf-0006P4-00
	for mip6-web-archive@ietf.org; Sun, 14 Sep 2003 22:02:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19yihh-0001R7-Hv; Sun, 14 Sep 2003 22: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 19yihM-0001P4-C7
	for mip6@optimus.ietf.org; Sun, 14 Sep 2003 22:02:40 -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 WAA23027
	for <mip6@ietf.org>; Sun, 14 Sep 2003 22:02:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19yihJ-0006N0-00
	for mip6@ietf.org; Sun, 14 Sep 2003 22:02:37 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 19yihI-0006Jv-00
	for mip6@ietf.org; Sun, 14 Sep 2003 22:02:37 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <ST25CJ7A>; Sun, 14 Sep 2003 22:02:07 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D19@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Gopal Dommety'" <gdommety@cisco.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
Subject: RE: [Mip6] Issue with mipv6 charter
Date: Sun, 14 Sep 2003 22:02:04 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>



 > I am assuming that Alpesh is trying to get some level of network 
 > authentication/authorization via MIP signalling.
 > 
 > I am assuming you mean NAS (network Access server), in which 
 > case what is 
 > the protocol that you
 > have in mind for L3 authentication/authorization? (assuming that L2 
 > authentication/authorization may or may not exist).

=> I'm not quite sure what you mean because people
are running L3 authentication into L2 packets.
So, naturally, the authentication is L2-dependent
today (perhaps EAP is an exception). So to answer
your question, you can use: EAP, PPP, AKA, ...etc depending
on your link. If you don't want to depend on the 
link layer, use EAP over layer 4, i.e. use PANA
when it's done.

Hesham


 > 
 > Thanks
 > Gopal
 > 
 > 
 > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
 > 
 > 
 > >  > Wondering if the charter should include an entity in the
 > >  > visited domain/roaming network to aid in AAA/Diameter 
 > authentication,
 > >  > access control etc?
 > >
 > >=> a NAS ? ;) The description of this entity doesn't
 > >seem to be related to mobility in any way. I think
 > >this work is generic for fixed and mobile nodes.
 > >
 > >    Currently, there is little, if any mechanism
 > >  > to restrict a mobile node's activities in visited domain.
 > >
 > >=> Why do you say that? A NAS will do this job very well
 > >provided that AAA mechanisms and roaming agreements
 > >are in place.
 > >
 > >  > For practical deployment issues and network management/control
 > >  > purposes, I think such an entity is needed.
 > >
 > >=> Absolutely, but MIP6 has nothing to do with it.
 > >
 > >Hesham
 > >
 > >_______________________________________________
 > >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 Sep 18 05:56: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 FAA04942
	for <mip6-archive@odin.ietf.org>; Thu, 18 Sep 2003 05:56: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 19zvW9-0006lP-8a
	for mip6-archive@odin.ietf.org; Thu, 18 Sep 2003 05:56:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8I9u5tF025998
	for mip6-archive@odin.ietf.org; Thu, 18 Sep 2003 05:56:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zvW9-0006lF-4A
	for mip6-web-archive@optimus.ietf.org; Thu, 18 Sep 2003 05:56: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 FAA04921
	for <mip6-web-archive@ietf.org>; Thu, 18 Sep 2003 05:55:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zvW5-0003Xc-00
	for mip6-web-archive@ietf.org; Thu, 18 Sep 2003 05:56:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19zvW5-0003XY-00
	for mip6-web-archive@ietf.org; Thu, 18 Sep 2003 05:56:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zvW6-0006kP-CT; Thu, 18 Sep 2003 05:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 19zvVQ-0006j8-N2
	for mip6@optimus.ietf.org; Thu, 18 Sep 2003 05:55: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 FAA04878
	for <mip6@ietf.org>; Thu, 18 Sep 2003 05:55:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19zvVN-0003WB-00
	for mip6@ietf.org; Thu, 18 Sep 2003 05:55:17 -0400
Received: from node-c-04db.a2000.nl ([62.194.4.219] helo=helimore1960.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19zvVC-0003Vm-00
	for mip6@ietf.org; Thu, 18 Sep 2003 05:55:15 -0400
From: "DR.FRANK EFE" <frank.efe66@laposte.net>
Reply-To: frank.efe77@laposte.net
To: mip6@ietf.org
Date: Fri, 19 Sep 2003 11:54:03 -0700
X-Mailer: Microsoft Outlook Express 5.00.2919.6900 DM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <E19zvVC-0003Vm-00@ietf-mx>
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] PARTNER  NEEDED
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

                             CONFIDENTIAL


25 Adewabe Street=2C
Ikoyi Island=2C
Lagos=2E


                                                IFax=3A1775-522-8610

                                                   18=2F9=2F2003

ATTN=3ATHE PRESIDENT=2FCEO

FROM=3ADR=2EFRANK EFE=2E

Dear Sir=2C

I would like to firstly send to you the best wishes of good health and success in your pursuits particularly through my proposal as contained in this letter=2E

Before going into details of my proposal to you=2C I must first implore you to treat with the utmost confidentiality as this is required for its success and to have faith in this transaction=2Cfor opportunities like this only comes to one once in a life time=2E

My colleagues and I are senior officials of the Federal Government of my country's Contracts Review Panel =28CRP=29 who are interested in diverting some funds that are presently loating in the accounts of the Apex Bank of my country=2EIn order to commence this transaction=2C we solicit for your assistance to enable us transfer into your nominated account the said floating funds=2E We are determined to conclude the transfer before the end of this quarter of 2003=2E The source of the funds are as follows=3A During the last military regime in my country=2Cgovernment officials set up companies and awarded themselves contracts that were grossly over-invoiced in various ministries and parastatals=2EThe present civilian government set up the Contract Review Panel=2C which has the mandate to use the instruments of payments made available to it by the decree setting up the panel=2C to review these contracts and if necessary pay those who are being owed outstanding amounts=2E

My colleagues and I have identified quite a huge sum of
these funds which are presently floating in our =28Apex=29Central Bank ready for disbursement and would like to divert some of it for our own purposes=2E However=2C by virtue of our positions as civil servants and members of this panel=2C we cannot acquire these funds in our names or in the names of companies that are based in my country=2E I have therefore been mandated=2Cas a matter of trust by my colleagues in the panel=2C to look for a reliable overseas partner into whose account we can transfer the sum of U=2ES=2E$20=2C500=2C000=2E00 =28Twenty million=2C five hundred thousand U=2ES=2E dollars=29=2EThat is why I am seeking your assistance=2E We have agreed to share the money to be transferred into your account=2C if you agree with our proposition as follows=3B
=28i=2925% to the account owner=28you=29=2E
=28ii=2965% for us =28the panel officials=29=2E
=28iii=2910% to be used in settling all expenses =28by both you and us=29 incidental to the actualization of this project=2E

We wish to invest our share of the proceeds of this project in foreign stock markets and other viable business till we are ready and able to have access to them without raising any eyebrows here at home=2E Please note that this
transaction is 100% safe and risk-free=2E
We intend to effect the transfer within fourteen =2814=29banking days from the date of receipt of the following information through the ifax number stated above=3AYour company's
name=2Caddress=2Ctelephone and fax numbers we will use your company's name to apply for the payment and backdate the award of the contract in favour of your company=2E We are looking forward to doing this transaction with you and we solicit for your utmost confidentiality in this transaction=2E

I will bring you into a more detailed picture of this transaction when I hear from you=2EPlease get in touch through my IFAX # 177-552-286-10=2E

Best regards=2C

DR=2EFRANK EFE=2E




_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sat Sep 20 09:53:59 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 JAA04554
	for <mip6-archive@odin.ietf.org>; Sat, 20 Sep 2003 09:53:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0OPc-00006e-RN
	for mip6-archive@odin.ietf.org; Fri, 19 Sep 2003 12:47:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8JGlG1f000407
	for mip6-archive@odin.ietf.org; Fri, 19 Sep 2003 12:47:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0OPc-00006U-MG
	for mip6-web-archive@optimus.ietf.org; Fri, 19 Sep 2003 12:47: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 MAA13754
	for <mip6-web-archive@ietf.org>; Fri, 19 Sep 2003 12:47:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0OPb-0005zH-00
	for mip6-web-archive@ietf.org; Fri, 19 Sep 2003 12:47:15 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A0O7y-0005YE-00
	for mip6-web-archive@ietf.org; Fri, 19 Sep 2003 12:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Nrj-0003dl-4g; Fri, 19 Sep 2003 12:12:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A0Np5-0002me-5T
	for mip6@optimus.ietf.org; Fri, 19 Sep 2003 12:09: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 MAA08873
	for <mip6@ietf.org>; Fri, 19 Sep 2003 12:08:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A03Sh-0002Bg-00
	for mip6@ietf.org; Thu, 18 Sep 2003 14:25:03 -0400
Received: from asmtp2.prserv.net ([32.97.166.52] helo=prserv.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A03QD-0001yB-00
	for mip6@ietf.org; Thu, 18 Sep 2003 14:22:29 -0400
Received: from eremmell (194.muac.lsan.lsancass.dsl.att.net[12.99.240.194])
          by prserv.net (asmtp2) with SMTP
          id <2003091818215125201k66eue>
          (Authid: eremmell@attglobal.net);
          Thu, 18 Sep 2003 18:21:51 +0000
From: "Ed Remmell" <eremmell@elmic.com>
To: <mobile-ip@sunroof.eng.sun.com>, <mip6@ietf.org>
Date: Thu, 18 Sep 2003 11:21:51 -0700
Message-ID: <002101c37e11$bc820fd0$0500a8c0@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
In-Reply-To: <000801c3681e$00344900$0200a8c0@eremmell>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Mip6] RE: [mobile-ip] Win32 demo of Mobile IPv6 mobile node and correspondent node is available
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

FYI -

We recently updated our Win32 demo of dual stack + applications + MIPv6
MN+CN to v1.6; all known stability issues with the Win32 application are
now fixed (including the WinXP issue described below), also it has a
couple of MIPv6 bug fixes (including fixing Mobile Prefix Discovery,
which didn't work at all in v1.5). It is available here:

http://www.elmic.com/TreckDemo.zip

Thanks.
- Ed Remmell
Elmic Systems, USA

> -----Original Message-----
> From: owner-mobile-ip@sunroof.eng.sun.com 
> [mailto:owner-mobile-ip@sunroof.eng.sun.com] On Behalf Of Ed Remmell
> Sent: Thursday, August 21, 2003 12:54 PM
> To: mobile-ip@sunroof.eng.sun.com
> Subject: RE: [mobile-ip] Win32 demo of Mobile IPv6 mobile 
> node and correspondent node is available
> 
> 
> Note that we updated the PKZIP file on our web site 
> http://www.elmic.com/TreckDemo-1.5.zip this morning to fix a 
> couple of very minor MN/CN issues (which you would probably 
> never see), also to fix a stability issue (the main reason 
> for this email). So, if you are using this demo application, 
> please redownload it from the Elmic web site. Also, I've 
> noticed that with Windows XP Home Edition, sometimes (not all 
> the time - it appears to be dependent on what else is already 
> loaded into memory) it won't startup the very first time. 
> This never happens with Win 98 or Windows 2000, however. It 
> is perplexing (I have debugged it post-mortem, it gets an 
> access violation somewhere in MSVCRT.DLL), and it appears to 
> be due to some interaction with winpcap (since it always 
> occurs when we make the call to winpcap to get the Ethernet 
> adapter's MAC address). Anyways, if it happens, no biggie, 
> just attempt to restart the demo application and it has 
> always loaded and run successfully for me the 2nd (and 
> subsequent) times.
> 
> Thanks.
> - Ed
> 
> > -----Original Message-----
> > From: owner-mobile-ip@sunroof.eng.sun.com
> > [mailto:owner-mobile-ip@sunroof.eng.sun.com] On Behalf Of Ed Remmell
> > Sent: Thursday, August 14, 2003 2:36 PM
> > To: mobile-ip@sunroof.eng.sun.com
> > Subject: [mobile-ip] Win32 demo of Mobile IPv6 mobile node 
> > and correspondent node is available
> > 
> > 
> > ALL -
> > 
> > We've updated the Win32 port of our embedded systems' dual IP layer
> > (IPv4+IPv6) stack product to include support for Mobile IPv6
> > mobile node and correspondent node, using Eager Cell 
> > Switching for mobile node movement detection with a form of 
> > optimistic Duplicate Address Detection for fast handovers 
> > (protocol latency < 50 milliseconds). This Win32 binary demo 
> > is available for download at the following URL:
> > 
> > http://www.elmic.com/TreckDemo-1.5.zip
> > 
> > All you need to run it is a MS-Windows PC, and also winpcap
> > (we use winpcap to directly access the Ethernet card, we 
> > bypass the Windows stack). The readme.html file in 
> > TreckDemo-1.5.zip contains more information, here is the 
> > excerpt about our Mobile IPv6 support in this
> > demo:
> > 
> > Both mobile node and correspondent node functionality are
> > included in this demo. The correspondent node functionality 
> > is enabled by default: you can use the netstat tool to show 
> > active bindings by clicking the "binding" button. The mobile 
> > node functionality is enabled by specifying a home address in 
> > the "MN" field and then clicking the "Start" button to the 
> > right of that field. The mobile node will then attempt to 
> > discover a home agent for the specified home address, and if 
> > successful, then the "HA" field will be filled in with the 
> > address of the home agent. Next, the mobile node will try to 
> > register its home address with the home agent. In this demo, 
> > we have not included any of our IPsec/IKE functionality, 
> > although we have implemented full support for it in our 
> > Mobile IPv6 product. So, when you use this demo to test 
> > Mobile IPv6, you need to configure the home agent to allow 
> > the mobile node to register without using IPsec/IKE. If the 
> > mobile node successfully registers its home address, you will 
> > see the event "TM_6_MNBE_HA_REG_SUCCESS" logged. Then, the 
> > mobile node will by default use its registered home address 
> > as the source address of any communication it originates. 
> > This demo application has the mobile node use Eager Cell 
> > Switching for movement detection, which means that whenever 
> > the mobile node sees a Router Advertisement from a new 
> > router, it assumes that a L3 handover has occurred and will 
> > immediately switch to using that new router and update its 
> > mobility bindings in the home agent and correspondent nodes 
> > with a potentially new primary care-of address. Therefore, if 
> > you are testing this demo's mobile node functionality with 
> > multiple IPv6 routers on a link, this demo will execute 
> > frequent L3 handovers which will be sub-optimal. Note that 
> > our APIs are very flexible, and allow you to use other 
> > methods such as L2 triggers instead of Eager Cell Switching 
> > (by default, Eager Cell Switching is disabled in our 
> > implementation and has to be explicitly enabled by the user 
> > application, as it is in this demo application).
> > 
> > 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/in> dex.cvn?ID=10183
> >  
> > 
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.497 / Virus Database: 296 - Release Date: 7/4/2003
> >  
> > 
> > 
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.497 / Virus Database: 296 - Release Date: 7/4/2003
> >  
> > 
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
>  
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.512 / Virus Database: 309 - Release Date: 8/19/2003
 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 23 21:25: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 VAA16710
	for <mip6-archive@odin.ietf.org>; Tue, 23 Sep 2003 21:25: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 1A1yOw-0002h0-32
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 21:25:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O1P627010349
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 21:25:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yOv-0002gq-VM
	for mip6-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 21:25: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 VAA16674
	for <mip6-web-archive@ietf.org>; Tue, 23 Sep 2003 21:24:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1yOt-00022T-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 21:25:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1yOs-00022P-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 21:25:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yOs-0002g9-8n; Tue, 23 Sep 2003 21:25:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yOe-0002fA-Gy
	for mip6@optimus.ietf.org; Tue, 23 Sep 2003 21:24: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 VAA16649
	for <mip6@ietf.org>; Tue, 23 Sep 2003 21:24:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1yOb-00021m-00
	for mip6@ietf.org; Tue, 23 Sep 2003 21:24:45 -0400
Received: from [81.199.83.116] (helo=mrson695.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1A1yOW-00021F-00
	for mip6@ietf.org; Tue, 23 Sep 2003 21:24:43 -0400
From: "Dr Mrs Mariam Abacha" <mariam1abacha@gawab.com>
Reply-To: mariam2abacha@gawab.com
To: mip6@ietf.org
Date: Tue, 23 Sep 2003 18:24:40 -0700
X-Mailer: Microsoft Outlook Express 5.00.2919.6900 DM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1A1yOW-00021F-00@ietf-mx>
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Respond soonest
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Attn=3ASir=2FMa=2C

 I salute you in the name of Allah=2Cthe most
high God=2EI am Mrs=2E Mariam Abacha=2C the widow of the
late General Sani Abacha=2C former Nigerian Military
head of state who died mysteriously as a result of
Cardiac arrest=2ESince my husband died=2C my family has
been under restriction of movement and that not
withstanding=2C we have been molested and constantly
under watch by the seemingly Agent=2C above all our bank
accounts here and abroad have been frozen by the
Nigerian civilian Government=2E Furthermore=2C my eldest
son is in detention by the Nigerian Government for
more interrogation about my husband assets and some
vital documents=2E

Following the recent discovery of my husband's bank
account by the Nigerian Government with my son's bank
in which a huge some of US$700 million and Dutch Mark
450 million was lodged and f1=2E6 billion belonging to
my late husband was seized by the Government of
Nigeria=2EI therefore wish to personally appeal to you
seriously and religious for your urgent assistance to
transfer the sum of US$25=2E5 million into your account
in your country where I believe it will be safe=2C since
we can not leave the country=2C due to the restriction
of the movement imposed on the members of my family by
the Nigerian Government=2EYou can contact me through my
farmily lawyer's number 234 80333 13642=28barister Buba Mohhamed=29 And he shall arrange with you for
a face-to face meeting outside Nigeria inorder to lease with him toward effective completion ofthis transaction=2E

However=2C arrangement have been put
in place to move this money out of the country=2C in the
secret vault through a security Company to any of West
African States=2C Europe=2CAmerica as soon as you indicate
your interest=2C my Lawyer shall send to you the
Security Deposit Certificate and Airway Bill of the
luggage and other related documents so that you an
claim the luggage=2C which shall be tagged FAMILY
TREASUERS=2E

Conclusively=2C we have agreed to offer you 30% of the
total sum while 70% is to be held on trust by you
until we can decide on a suitable business investment
in your country subsequent to our free movement by the
Nigerian Government=2EPlease=2C reply urgently and treat
with absolute confidentiality and sincerity=2E


Yours sincerely=2C

Mariam Abacha=2E

N=2EB=2EYour reponse will determine the transaction and
please all information guarantee safety=2E


 



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 23 21:31:56 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 VAA17068
	for <mip6-archive@odin.ietf.org>; Tue, 23 Sep 2003 21:31:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yVB-00035Y-Gy
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 21:31:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O1VXPV011866
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 21:31:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yVB-00035J-CK
	for mip6-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 21:31:33 -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 VAA17019
	for <mip6-web-archive@ietf.org>; Tue, 23 Sep 2003 21:31: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 1A1yUg-0002xw-RX; Tue, 23 Sep 2003 21:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1yTs-0002w8-BY
	for mip6@optimus.ietf.org; Tue, 23 Sep 2003 21:30:12 -0400
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16927
	for <mip6@ietf.org>; Tue, 23 Sep 2003 21:30:03 -0400 (EDT)
Received: from cisco.com (171.68.223.137)
  by sj-iport-3.cisco.com with ESMTP; 23 Sep 2003 18:32:03 -0700
Received: from gdommety-w2k01.cisco.com (dhcp-128-107-163-214.cisco.com [128.107.163.214])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h8O1TbYc014949;
	Tue, 23 Sep 2003 18:29:38 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030923181806.029aeea8@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 23 Sep 2003 18:29:37 -0700
To: Soliman Hesham <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: RE: [Mip6] Issue with mipv6 charter
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922D19@ftmail.lab.flario
 n.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


Hesham,

Sorry for the delay.

I cam of the opinion that  802.1x authentication based authentication is L2 
authentication
It typically terminates on the AP and not on the access router. Typically 
AP is like a bridge. (PANA is another story).

Anyway, what I am trying to ask is whether there needs to be a L3 access 
control point
(if I can use that term) to help in authentication, access control, roaming 
etc. I think this is useful in service
provider environments (CDMA 2000 for example).


Thanks
Gopal


At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:


>  > I am assuming that Alpesh is trying to get some level of network
>  > authentication/authorization via MIP signalling.
>  >
>  > I am assuming you mean NAS (network Access server), in which
>  > case what is
>  > the protocol that you
>  > have in mind for L3 authentication/authorization? (assuming that L2
>  > authentication/authorization may or may not exist).
>
>=> I'm not quite sure what you mean because people
>are running L3 authentication into L2 packets.
>So, naturally, the authentication is L2-dependent
>today (perhaps EAP is an exception). So to answer
>your question, you can use: EAP, PPP, AKA, ...etc depending
>on your link. If you don't want to depend on the
>link layer, use EAP over layer 4, i.e. use PANA
>when it's done.
>
>Hesham
>
>
>  >
>  > Thanks
>  > Gopal
>  >
>  >
>  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
>  >
>  >
>  > >  > Wondering if the charter should include an entity in the
>  > >  > visited domain/roaming network to aid in AAA/Diameter
>  > authentication,
>  > >  > access control etc?
>  > >
>  > >=> a NAS ? ;) The description of this entity doesn't
>  > >seem to be related to mobility in any way. I think
>  > >this work is generic for fixed and mobile nodes.
>  > >
>  > >    Currently, there is little, if any mechanism
>  > >  > to restrict a mobile node's activities in visited domain.
>  > >
>  > >=> Why do you say that? A NAS will do this job very well
>  > >provided that AAA mechanisms and roaming agreements
>  > >are in place.
>  > >
>  > >  > For practical deployment issues and network management/control
>  > >  > purposes, I think such an entity is needed.
>  > >
>  > >=> Absolutely, but MIP6 has nothing to do with it.
>  > >
>  > >Hesham
>  > >
>  > >_______________________________________________
>  > >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  Tue Sep 23 22:06: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 WAA18575
	for <mip6-archive@odin.ietf.org>; Tue, 23 Sep 2003 22:06: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 1A1z2Z-0005db-Fu
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 22:06:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O263Q0021665
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 22:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1z2Z-0005dM-9y
	for mip6-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 22:06: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 WAA18538
	for <mip6-web-archive@ietf.org>; Tue, 23 Sep 2003 22:05:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1z2W-0002db-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 22:06:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1z2V-0002dY-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 22:05:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1z2X-0005cv-Fa; Tue, 23 Sep 2003 22:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1z2A-0005cZ-2Q
	for mip6@optimus.ietf.org; Tue, 23 Sep 2003 22:05: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 WAA18532
	for <mip6@ietf.org>; Tue, 23 Sep 2003 22:05:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1z26-0002dC-00
	for mip6@ietf.org; Tue, 23 Sep 2003 22:05:34 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1z26-0002d7-00
	for mip6@ietf.org; Tue, 23 Sep 2003 22:05:34 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <TG6DDPS1>; Tue, 23 Sep 2003 22:07:48 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D4F@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Gopal Dommety'" <gdommety@cisco.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
Subject: RE: [Mip6] Issue with mipv6 charter
Date: Tue, 23 Sep 2003 22:07:21 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


 > I cam of the opinion that  802.1x authentication based 
 > authentication is L2 
 > authentication
 > It typically terminates on the AP and not on the access 
 > router. Typically 
 > AP is like a bridge. (PANA is another story).

=> (I'll drift slightly off topic here but hopefully 
it helps). You call it L2 authentication because it 
is transported over L2. However, it is actually authenticating
a much higher layer identifier (NAI). So there is some layer
violation here but people don't seem to be keen on changing
that. That's why I thought PANA was a step in the right direction.

 > 
 > Anyway, what I am trying to ask is whether there needs to be 
 > a L3 access 
 > control point
 > (if I can use that term) to help in authentication, access 
 > control, roaming 
 > etc. I think this is useful in service
 > provider environments (CDMA 2000 for example).

=> I agree with the need for an L3 access control point
and that it would be useful for several systems. However, 
since such function is needed independently of mobility, 
it should not be included inside a mobility protocol. 
For instance, you refer to CDMA 2000 which offers a Simple
IP service where no mobility is needed in the terminal.
Also, other systems (e.g. GPRS) do not require MIP, yet
they still need this function. In fact, WLANs today are 
deployed in a way that doesn't require the use of MIP, 
yet they still need this function. So, including this function
in MIP does not seem useful. 

Hesham


 > 
 > 
 > Thanks
 > Gopal
 > 
 > 
 > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
 > 
 > 
 > >  > I am assuming that Alpesh is trying to get some level of network
 > >  > authentication/authorization via MIP signalling.
 > >  >
 > >  > I am assuming you mean NAS (network Access server), in which
 > >  > case what is
 > >  > the protocol that you
 > >  > have in mind for L3 authentication/authorization? 
 > (assuming that L2
 > >  > authentication/authorization may or may not exist).
 > >
 > >=> I'm not quite sure what you mean because people
 > >are running L3 authentication into L2 packets.
 > >So, naturally, the authentication is L2-dependent
 > >today (perhaps EAP is an exception). So to answer
 > >your question, you can use: EAP, PPP, AKA, ...etc depending
 > >on your link. If you don't want to depend on the
 > >link layer, use EAP over layer 4, i.e. use PANA
 > >when it's done.
 > >
 > >Hesham
 > >
 > >
 > >  >
 > >  > Thanks
 > >  > Gopal
 > >  >
 > >  >
 > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
 > >  >
 > >  >
 > >  > >  > Wondering if the charter should include an entity in the
 > >  > >  > visited domain/roaming network to aid in AAA/Diameter
 > >  > authentication,
 > >  > >  > access control etc?
 > >  > >
 > >  > >=> a NAS ? ;) The description of this entity doesn't
 > >  > >seem to be related to mobility in any way. I think
 > >  > >this work is generic for fixed and mobile nodes.
 > >  > >
 > >  > >    Currently, there is little, if any mechanism
 > >  > >  > to restrict a mobile node's activities in visited domain.
 > >  > >
 > >  > >=> Why do you say that? A NAS will do this job very well
 > >  > >provided that AAA mechanisms and roaming agreements
 > >  > >are in place.
 > >  > >
 > >  > >  > For practical deployment issues and network 
 > management/control
 > >  > >  > purposes, I think such an entity is needed.
 > >  > >
 > >  > >=> Absolutely, but MIP6 has nothing to do with it.
 > >  > >
 > >  > >Hesham
 > >  > >
 > >  > >_______________________________________________
 > >  > >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  Tue Sep 23 22:57: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 WAA20917
	for <mip6-archive@odin.ietf.org>; Tue, 23 Sep 2003 22:57: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 1A1zpv-0001ZI-UB
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 22:57:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O2v3ok006022
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 22:57:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1zpv-0001Z3-PX
	for mip6-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 22:57: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 WAA20910
	for <mip6-web-archive@ietf.org>; Tue, 23 Sep 2003 22:56:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1zps-0003Q8-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 22:57:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1zpr-0003Q5-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 22:56:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1zpt-0001Ye-Lj; Tue, 23 Sep 2003 22:57:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1zpO-0001Xj-Qy
	for mip6@optimus.ietf.org; Tue, 23 Sep 2003 22:56: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 WAA20858
	for <mip6@ietf.org>; Tue, 23 Sep 2003 22:56:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1zpL-0003P2-00
	for mip6@ietf.org; Tue, 23 Sep 2003 22:56:27 -0400
Received: from shonan.sfc.wide.ad.jp ([203.178.142.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1zpK-0003OH-00
	for mip6@ietf.org; Tue, 23 Sep 2003 22:56:26 -0400
Received: from galibier.nautilus6.org (unknown [203.178.138.3])
	by shonan.sfc.wide.ad.jp (Postfix) with SMTP id AF50A5D09A
	for <mip6@ietf.org>; Wed, 24 Sep 2003 11:55:55 +0900 (JST)
Date: Wed, 24 Sep 2003 11:50:40 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Message-Id: <20030924115040.2808c5fd.ernst@sfc.wide.ad.jp>
In-Reply-To: <4.3.2.7.2.20030923181806.029aeea8@mira-sjcm-3.cisco.com>
References: <748C6D0A58C0F94CA63C198B6674697A01922D19@ftmail.lab.flarion.com>
	<4.3.2.7.2.20030923181806.029aeea8@mira-sjcm-3.cisco.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
Subject: [Mip6] Are multihoming mechanisms part of the charter ?
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Dear all,

I'm sorry I didn't have the time to follow the discussion on the list
recently, so I may be mistaken.

I didn't see anything related to interface switiching mechanisms for
mobile hosts, is this something that could be considered in the
definition of the new charter ? I consider this mechanism as
tremendously important if we want to fully deploy mobility.

Thierry

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 23 23:09: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 XAA21457
	for <mip6-archive@odin.ietf.org>; Tue, 23 Sep 2003 23:09: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 1A201Z-0002DA-Kf
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 23:09:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O3954V008494
	for mip6-archive@odin.ietf.org; Tue, 23 Sep 2003 23:09:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A201Z-0002Cv-E5
	for mip6-web-archive@optimus.ietf.org; Tue, 23 Sep 2003 23: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 XAA21384
	for <mip6-web-archive@ietf.org>; Tue, 23 Sep 2003 23:08:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A201U-0003ZY-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 23:09:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A201T-0003ZV-00
	for mip6-web-archive@ietf.org; Tue, 23 Sep 2003 23:08:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A201V-00029b-CS; Tue, 23 Sep 2003 23: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 1A2011-00028Z-Tv
	for mip6@optimus.ietf.org; Tue, 23 Sep 2003 23:08: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 XAA21353
	for <mip6@ietf.org>; Tue, 23 Sep 2003 23:08:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A200y-0003Ya-00
	for mip6@ietf.org; Tue, 23 Sep 2003 23:08:28 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A200x-0003Xb-00
	for mip6@ietf.org; Tue, 23 Sep 2003 23:08:27 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <TG6DDPVF>; Tue, 23 Sep 2003 23:07:52 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D51@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Thierry Ernst'" <ernst@sfc.wide.ad.jp>, mip6@ietf.org
Subject: RE: [Mip6] Are multihoming mechanisms part of the charter ?
Date: Tue, 23 Sep 2003 23:07:49 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


 > I'm sorry I didn't have the time to follow the discussion on the list
 > recently, so I may be mistaken.
 > 
 > I didn't see anything related to interface switiching mechanisms for
 > mobile hosts, is this something that could be considered in the
 > definition of the new charter ? I consider this mechanism as
 > tremendously important if we want to fully deploy mobility.

=> Agreed. I hope we can include that, given the amount of 
discussion and interest generated before and during the 
Vienna meeting. 

Hesham

 > 
 > 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  Wed Sep 24 02:47: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 CAA26955
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 02:47: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 1A23QX-0006YK-Cq
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 02:47:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8O6l5RI025181
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 02:47:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A23QX-0006Y4-14
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 02:47: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 CAA26867
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 02:46:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A23QT-0006OV-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 02:47:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A23QS-0006OS-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 02:47:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A23QT-0006Wk-6E; Wed, 24 Sep 2003 02:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A23QF-0006Vg-N1
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 02:46: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 CAA26849;
	Wed, 24 Sep 2003 02:46:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A23QB-0006Nz-00; Wed, 24 Sep 2003 02:46:43 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A23QA-0006NO-00; Wed, 24 Sep 2003 02:46:43 -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 <0HLP00D01HGVZ8@mailout3.samsung.com>; Wed, 24 Sep 2003 15:46:07 +0900 (KST)
Received: from ep_ms7_bk (localhost [127.0.0.1])
 by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun
 23 2003)) with ESMTP id <0HLP0066JHGV8L@mailout3.samsung.com>; Wed,
 24 Sep 2003 15:46:07 +0900 (KST)
Received: from ep_was25 (ms7.samsung.com [203.254.225.101])
 by ms7.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTP id <0HLP00H5THGUFT@ms7.samsung.com>; Wed,
 24 Sep 2003 15:46:07 +0900 (KST)
Content-return: prohibited
Date: Wed, 24 Sep 2003 15:46:03 +0900
From: =?EUC-KR?B?vK2w5sHW?= <joo.suh@samsung.com>
To: Mipshop@ietf.org, mip6@ietf.org, mip4@ietf.org
Reply-to: joo.suh@samsung.com
Message-id: <0HLP00H5UHGVFT@ms7.samsung.com>
MIME-version: 1.0
Content-type: text/plain; charset=euc-kr
Content-transfer-encoding: 7BIT
X-Priority: 3
Msgkey: 20030924154603@joo.suh
X-MTR: 20030924154603@joo.suh
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
Content-Transfer-Encoding: 7BIT
Subject: [Mip6] question about fast handoff open source
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Hi, all,

If you know any open source for fast handoff implementation,
please let me know the web site.

In advance, thank you very much.

sincerely,
Kyungjoo Suh 

--------------------------------------------------------------------
' spamcontrol '  

									

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 10: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 KAA16190
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 10:10: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 1A2ALI-0005hd-0w
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 10:10:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OEA70l021917
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 10:10:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2ALG-0005fd-Ev
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 10: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 KAA16095
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 10:09:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ALC-0004VS-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 10:10:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ALC-0004VP-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 10:10:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2ALB-0005eD-Dn; Wed, 24 Sep 2003 10: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 1A2AKK-0005Zd-Hj
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 10:09:08 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15902;
	Wed, 24 Sep 2003 10:08:59 -0400 (EDT)
Message-Id: <200309241408.KAA15902@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: Wed, 24 Sep 2003 10:08:59 -0400
Subject: [Mip6] I-D ACTION:draft-haddad-mipv6-bub-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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: BUB: Binding Update Backhauling
	Author(s)	: W. Haddad et al.
	Filename	: draft-haddad-mipv6-bub-00.txt
	Pages		: 14
	Date		: 2003-9-24
	
Mobile IPv6 [1] defines two different modes to handle the 
mobility problem (i.e., mobile node moving accross different 
networks and changing its IP address). The two modes had been 
mainly designed for scenarios involving one mobile node and 
one static node (correspondent node). This document answers 
issues related to scenarios involving two mobile nodes (i.e., 
the correspodent node is also a mobile node). The document 
addresses also the double jumping problem where two mobile nodes 
move at the same time (i.e., switch to new subnets).
The document proposes a new mode called 'BUB' (Binding Update 
Backhauling) allowing a more secure, reliable and optimized 
exchange of Binding Updates (BUs) between two mobile endpoints.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-haddad-mipv6-bub-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-bub-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-bub-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-9-24092335.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-haddad-mipv6-bub-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-haddad-mipv6-bub-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-9-24092335.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 10:59: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 KAA20011
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 10: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 1A2B6e-0000VM-Ii
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 10:59:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OEx4ZF001934
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 10:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2B6e-0000V7-CT
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 10:59: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 KAA19956
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 10:58:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2B6b-0005V7-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 10:59:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2B6b-0005V4-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 10:59:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2B6b-0000Ui-2G; Wed, 24 Sep 2003 10: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 1A2B65-0000U5-B0
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 10:58: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 KAA19913
	for <mip6@ietf.org>; Wed, 24 Sep 2003 10:58:20 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2B62-0005Tz-00
	for mip6@ietf.org; Wed, 24 Sep 2003 10:58:26 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2B61-0005Tv-00
	for mip6@ietf.org; Wed, 24 Sep 2003 10:58:25 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h8OEw7625483
	for <mip6@ietf.org>; Wed, 24 Sep 2003 17:58:07 +0300 (EET DST)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T64e128ec0cac158f252b4@esvir05nok.ntc.nokia.com>;
 Wed, 24 Sep 2003 17:58:05 +0300
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 24 Sep 2003 07:57:51 -0700
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] Are multihoming mechanisms part of the charter ?
Date: Wed, 24 Sep 2003 09:57:51 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB7A5@daebe007.americas.nokia.com>
Thread-Topic: [Mip6] Are multihoming mechanisms part of the charter ?
Thread-Index: AcOCSjB7x33qZbNfQyO1dsAMx+XfLQAYVVSg
To: <H.Soliman@flarion.com>, <ernst@sfc.wide.ad.jp>, <mip6@ietf.org>
X-OriginalArrivalTime: 24 Sep 2003 14:57:51.0919 (UTC) FILETIME=[3A373BF0:01C382AC]
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>  > I'm sorry I didn't have the time to follow the discussion on the =
list
>  > recently, so I may be mistaken.
>  >=20
>  > I didn't see anything related to interface switiching mechanisms =
for
>  > mobile hosts, is this something that could be considered in the
>  > definition of the new charter ? I consider this mechanism as
>  > tremendously important if we want to fully deploy mobility.

"Fully deploy mobility"..... I think mobility can be deployed just
as well without having specific solutions for dealing with IF switching
mechanisms. But it is an interesting idea. There has been discussion in
progress since the last IETF with at least 3 I-Ds on this topic. It =
would
be good to identify what are the problems that IF switching solves and
subsequently what are the requirements. This can be taken up as a first=20
step before taking the leap.

-Basavaraj

>=20
> =3D> Agreed. I hope we can include that, given the amount of=20
> discussion and interest generated before and during the=20
> Vienna meeting.=20
>=20
> Hesham
>=20
>  >=20
>  > Thierry
>  >=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 11:29: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 LAA22145
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 11:29: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 1A2BZm-0002PY-MK
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 11:29:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OFTAcZ009249
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 11: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 1A2BZm-0002OW-Ev
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 11:29: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 LAA22130
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 11:29:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2BZi-0006F2-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 11:29:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2BZi-0006Ez-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 11: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 1A2BZc-0002Nu-KZ; Wed, 24 Sep 2003 11: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 1A2BZS-0002NU-DV
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 11:28: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 LAA22114
	for <mip6@ietf.org>; Wed, 24 Sep 2003 11:28:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2BZR-0006EQ-00
	for mip6@ietf.org; Wed, 24 Sep 2003 11:28:49 -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 1A2BZQ-0006EN-00
	for mip6@ietf.org; Wed, 24 Sep 2003 11:28:48 -0400
Message-ID: <008301c382b0$8ee2f780$956015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman Hesham" <H.Soliman@flarion.com>,
        "'Thierry Ernst'" <ernst@sfc.wide.ad.jp>, <mip6@ietf.org>
References: <748C6D0A58C0F94CA63C198B6674697A01922D51@ftmail.lab.flarion.com>
Subject: Re: [Mip6] Are multihoming mechanisms part of the charter ?
Date: Wed, 24 Sep 2003 08:28:51 -0700
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>  > I'm sorry I didn't have the time to follow the discussion on the list
>  > recently, so I may be mistaken.
>  >
>  > I didn't see anything related to interface switiching mechanisms for
>  > mobile hosts, is this something that could be considered in the
>  > definition of the new charter ? I consider this mechanism as
>  > tremendously important if we want to fully deploy mobility.
>
> => Agreed. I hope we can include that, given the amount of
> discussion and interest generated before and during the
> Vienna meeting.
>


So I'm wondering here whether this isn't a broader issue than MIP. There are
a couple of topics around multi-link hosts that seem related, namely
interface switching (or vertical handover, assuming that is what is meant by
interface switching) and multi-link transport. The specific part that
involves MIP would be changing the HA binding when the interface is switched
(for the first) or having multiple bindings for different interfaces (for
the second), but these seem like straightforward uses of MIP and not
something that really requires modifying MIP itself. Nevertheless, there are
other technical issues with these that might require some IETF attention,
but I'm not sure whether the MIP group is the right place.

Am I missing something?

            jak


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 11:54: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 LAA23456
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 11:54: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 1A2Bxs-0004Rg-9K
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 11:54:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OFs4r0017082
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 11:54:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2Bxs-0004RR-4o
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 11:54: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 LAA23355
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 11:53:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Bxq-0006aK-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 11:54:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Bxq-0006aG-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 11:54:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2Bxq-0004QJ-Rf; Wed, 24 Sep 2003 11:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2Bxm-0004PH-JE
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 11:53: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 LAA23334
	for <mip6@ietf.org>; Wed, 24 Sep 2003 11:53:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Bxk-0006Zh-00
	for mip6@ietf.org; Wed, 24 Sep 2003 11:53:56 -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 1A2Bxh-0006Zd-00
	for mip6@ietf.org; Wed, 24 Sep 2003 11:53:54 -0400
Message-ID: <016701c382b4$138e6890$956015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman Hesham" <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        <mip6@ietf.org>, "Gopal Dommety" <gdommety@cisco.com>
References: <4.3.2.7.2.20030923181806.029aeea8@mira-sjcm-3.cisco.com>
Subject: Re: [Mip6] Issue with mipv6 charter
Date: Wed, 24 Sep 2003 08:54:02 -0700
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Gopal,

I think there is probably some work to be done in authentication for MIPv6,
but I don't believe that it is at the MIP protocol level in the access
network. That should be handled by L2 authentication or PANA. The kind of
work I have in mind are Diameter extensions or possibly just Diameter/Radius
AVPs that allow interoperable authentication among roaming clients. To my
knowledge, the current Diameter MIP extension is IPv4 only, and I believe
3GPP2 uses some kind of Radius extension now though I don't know whether
that is IPv4 or version independent. There is also a question of how this
authentication interacts with the IKE setup back on the home agent.
Currently, if the mobile host authenticates via, say, an L2 protocol in the
access network to the NAS and Radius from the NAS to the foreign and home
network AAA servers, the only way the home agent would know that the client
is authenticated is via some kind of back end API between the home AAA
server and home agent. That is, there is no interaction at the protocol
level between, say, ESP Auth and the AAA auth that ties the IKE session
required for securing the MIP link to the AAA.

On another, more advanced level, the ability to dynamically obtain
bidirectionally authenticated MIPv6 service from a dynamically discovered
home agent in a foreign network might be of interest to carriers, and this
might require some work, possibly with IKEv2 and/or the above
Diameter/Radius extensions. I know there has been a good deal of interest
from 3GPP2 in this for MIPv4.

At any rate, I'm not sure whether it makes sense to put this in the charter
at this point. IMHO, the charter already has a lot of items and the schedule
for completing them is very aggressive (overly so, I think, given the number
of items). I do belive there is some interesting technical work here, that
could result in a very useful draft: examining requirements, how existing
mechanisms match them, and identifying where additional work is necessary,
and I think such a draft would necessarily require review by the MIP group.
If that review identifies some action items that require work on the MIPv6
protocol, that would be the time to think about adding them to the charter.

            jak

----- Original Message ----- 
From: "Gopal Dommety" <gdommety@cisco.com>
To: "Soliman Hesham" <H.Soliman@flarion.com>; "'Alpesh'" <alpesh@cisco.com>;
<mip6@ietf.org>
Sent: Tuesday, September 23, 2003 6:29 PM
Subject: RE: [Mip6] Issue with mipv6 charter


>
> Hesham,
>
> Sorry for the delay.
>
> I cam of the opinion that  802.1x authentication based authentication is
L2
> authentication
> It typically terminates on the AP and not on the access router. Typically
> AP is like a bridge. (PANA is another story).
>
> Anyway, what I am trying to ask is whether there needs to be a L3 access
> control point
> (if I can use that term) to help in authentication, access control,
roaming
> etc. I think this is useful in service
> provider environments (CDMA 2000 for example).
>
>
> Thanks
> Gopal
>
>
> At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
>
>
> >  > I am assuming that Alpesh is trying to get some level of network
> >  > authentication/authorization via MIP signalling.
> >  >
> >  > I am assuming you mean NAS (network Access server), in which
> >  > case what is
> >  > the protocol that you
> >  > have in mind for L3 authentication/authorization? (assuming that L2
> >  > authentication/authorization may or may not exist).
> >
> >=> I'm not quite sure what you mean because people
> >are running L3 authentication into L2 packets.
> >So, naturally, the authentication is L2-dependent
> >today (perhaps EAP is an exception). So to answer
> >your question, you can use: EAP, PPP, AKA, ...etc depending
> >on your link. If you don't want to depend on the
> >link layer, use EAP over layer 4, i.e. use PANA
> >when it's done.
> >
> >Hesham
> >
> >
> >  >
> >  > Thanks
> >  > Gopal
> >  >
> >  >
> >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
> >  >
> >  >
> >  > >  > Wondering if the charter should include an entity in the
> >  > >  > visited domain/roaming network to aid in AAA/Diameter
> >  > authentication,
> >  > >  > access control etc?
> >  > >
> >  > >=> a NAS ? ;) The description of this entity doesn't
> >  > >seem to be related to mobility in any way. I think
> >  > >this work is generic for fixed and mobile nodes.
> >  > >
> >  > >    Currently, there is little, if any mechanism
> >  > >  > to restrict a mobile node's activities in visited domain.
> >  > >
> >  > >=> Why do you say that? A NAS will do this job very well
> >  > >provided that AAA mechanisms and roaming agreements
> >  > >are in place.
> >  > >
> >  > >  > For practical deployment issues and network management/control
> >  > >  > purposes, I think such an entity is needed.
> >  > >
> >  > >=> Absolutely, but MIP6 has nothing to do with it.
> >  > >
> >  > >Hesham
> >  > >
> >  > >_______________________________________________
> >  > >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
>


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 12:27: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 MAA24926
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 12:27: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 1A2CTo-000727-Pb
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 12:27:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OGR4mL027031
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 12:27:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CTo-00071u-LO
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 12:27: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 MAA24908
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 12:26:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CTn-0006z2-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 12:27:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CTm-0006yz-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 12:27:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CTk-00070Q-O8; Wed, 24 Sep 2003 12:27:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CTf-0006zr-K1
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 12:26: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 MAA24892
	for <mip6@ietf.org>; Wed, 24 Sep 2003 12:26:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CTe-0006yS-00
	for mip6@ietf.org; Wed, 24 Sep 2003 12:26:54 -0400
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 1A2CTc-0006y9-00
	for mip6@ietf.org; Wed, 24 Sep 2003 12:26:52 -0400
Received: from cisco.com (171.68.223.138)
  by sj-iport-2.cisco.com with ESMTP; 24 Sep 2003 09:24:22 -0700
Received: from gdommety-w2k01.cisco.com (sjc-vpn3-807.cisco.com [10.21.67.39])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h8OGQCxX014809;
	Wed, 24 Sep 2003 09:26:16 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030924092509.029efb60@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 24 Sep 2003 09:26:09 -0700
To: "James Kempf" <kempf@docomolabs-usa.com>,
        "Soliman Hesham" <H.Soliman@flarion.com>,
        "'Alpesh'" <alpesh@cisco.com>, <mip6@ietf.org>
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [Mip6] Issue with mipv6 charter
In-Reply-To: <016701c382b4$138e6890$956015ac@dclkempt40>
References: <4.3.2.7.2.20030923181806.029aeea8@mira-sjcm-3.cisco.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


James,

I agree that we could leave it out  for now...

thanks
-Gopal

At 08:54 AM 9/24/2003 -0700, James Kempf wrote:
>Hi Gopal,
>
>I think there is probably some work to be done in authentication for MIPv6,
>but I don't believe that it is at the MIP protocol level in the access
>network. That should be handled by L2 authentication or PANA. The kind of
>work I have in mind are Diameter extensions or possibly just Diameter/Radius
>AVPs that allow interoperable authentication among roaming clients. To my
>knowledge, the current Diameter MIP extension is IPv4 only, and I believe
>3GPP2 uses some kind of Radius extension now though I don't know whether
>that is IPv4 or version independent. There is also a question of how this
>authentication interacts with the IKE setup back on the home agent.
>Currently, if the mobile host authenticates via, say, an L2 protocol in the
>access network to the NAS and Radius from the NAS to the foreign and home
>network AAA servers, the only way the home agent would know that the client
>is authenticated is via some kind of back end API between the home AAA
>server and home agent. That is, there is no interaction at the protocol
>level between, say, ESP Auth and the AAA auth that ties the IKE session
>required for securing the MIP link to the AAA.
>
>On another, more advanced level, the ability to dynamically obtain
>bidirectionally authenticated MIPv6 service from a dynamically discovered
>home agent in a foreign network might be of interest to carriers, and this
>might require some work, possibly with IKEv2 and/or the above
>Diameter/Radius extensions. I know there has been a good deal of interest
>from 3GPP2 in this for MIPv4.
>
>At any rate, I'm not sure whether it makes sense to put this in the charter
>at this point. IMHO, the charter already has a lot of items and the schedule
>for completing them is very aggressive (overly so, I think, given the number
>of items). I do belive there is some interesting technical work here, that
>could result in a very useful draft: examining requirements, how existing
>mechanisms match them, and identifying where additional work is necessary,
>and I think such a draft would necessarily require review by the MIP group.
>If that review identifies some action items that require work on the MIPv6
>protocol, that would be the time to think about adding them to the charter.
>
>             jak
>
>----- Original Message -----
>From: "Gopal Dommety" <gdommety@cisco.com>
>To: "Soliman Hesham" <H.Soliman@flarion.com>; "'Alpesh'" <alpesh@cisco.com>;
><mip6@ietf.org>
>Sent: Tuesday, September 23, 2003 6:29 PM
>Subject: RE: [Mip6] Issue with mipv6 charter
>
>
> >
> > Hesham,
> >
> > Sorry for the delay.
> >
> > I cam of the opinion that  802.1x authentication based authentication is
>L2
> > authentication
> > It typically terminates on the AP and not on the access router. Typically
> > AP is like a bridge. (PANA is another story).
> >
> > Anyway, what I am trying to ask is whether there needs to be a L3 access
> > control point
> > (if I can use that term) to help in authentication, access control,
>roaming
> > etc. I think this is useful in service
> > provider environments (CDMA 2000 for example).
> >
> >
> > Thanks
> > Gopal
> >
> >
> > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
> >
> >
> > >  > I am assuming that Alpesh is trying to get some level of network
> > >  > authentication/authorization via MIP signalling.
> > >  >
> > >  > I am assuming you mean NAS (network Access server), in which
> > >  > case what is
> > >  > the protocol that you
> > >  > have in mind for L3 authentication/authorization? (assuming that L2
> > >  > authentication/authorization may or may not exist).
> > >
> > >=> I'm not quite sure what you mean because people
> > >are running L3 authentication into L2 packets.
> > >So, naturally, the authentication is L2-dependent
> > >today (perhaps EAP is an exception). So to answer
> > >your question, you can use: EAP, PPP, AKA, ...etc depending
> > >on your link. If you don't want to depend on the
> > >link layer, use EAP over layer 4, i.e. use PANA
> > >when it's done.
> > >
> > >Hesham
> > >
> > >
> > >  >
> > >  > Thanks
> > >  > Gopal
> > >  >
> > >  >
> > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
> > >  >
> > >  >
> > >  > >  > Wondering if the charter should include an entity in the
> > >  > >  > visited domain/roaming network to aid in AAA/Diameter
> > >  > authentication,
> > >  > >  > access control etc?
> > >  > >
> > >  > >=> a NAS ? ;) The description of this entity doesn't
> > >  > >seem to be related to mobility in any way. I think
> > >  > >this work is generic for fixed and mobile nodes.
> > >  > >
> > >  > >    Currently, there is little, if any mechanism
> > >  > >  > to restrict a mobile node's activities in visited domain.
> > >  > >
> > >  > >=> Why do you say that? A NAS will do this job very well
> > >  > >provided that AAA mechanisms and roaming agreements
> > >  > >are in place.
> > >  > >
> > >  > >  > For practical deployment issues and network management/control
> > >  > >  > purposes, I think such an entity is needed.
> > >  > >
> > >  > >=> Absolutely, but MIP6 has nothing to do with it.
> > >  > >
> > >  > >Hesham
> > >  > >
> > >  > >_______________________________________________
> > >  > >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
> >
>
>
>_______________________________________________
>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  Wed Sep 24 12:31: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 MAA25082
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 12:31: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 1A2CXf-0007Ca-Pv
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 12:31:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OGV3gk027677
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 12:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CXf-0007BI-El
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 12:31: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 MAA25069
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 12:30:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CXd-00071k-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 12:31:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CXd-00071h-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 12:31:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CXd-0007AZ-RG; Wed, 24 Sep 2003 12:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2CWo-00079X-LG
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 12:30: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 MAA25029
	for <mip6@ietf.org>; Wed, 24 Sep 2003 12:30:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CWn-00070u-00
	for mip6@ietf.org; Wed, 24 Sep 2003 12:30:09 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2CWm-00070k-00
	for mip6@ietf.org; Wed, 24 Sep 2003 12:30:08 -0400
Received: from gdommety-w2k01.cisco.com (sjc-vpn3-807.cisco.com [10.21.67.39])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h8OGTIYc011647;
	Wed, 24 Sep 2003 09:29:27 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030924081728.02291360@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 24 Sep 2003 08:48:39 -0700
To: Soliman Hesham <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: RE: [Mip6] Issue with mipv6 charter
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922D4F@ftmail.lab.flario
 n.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

Hesham,


Two comments:

   AP is a bridge and performs L2 access authentication.
It need not have much of L3 knowledge.  It does not matter
what you are using for authentication (NAI/MAC address). It is still L2
  authentication, since it allows L2 access (There are systems such as
  Public Access where L3 access has an additional authentication,
That is when L3 access control happens).

I am not saying that access control cannot be done by some other protocol 
or independent of Mobility.
I think it is a good idea to keep them separate in some environments. 
However,  I think it adds to latency (that might not be acceptable) in 
other environments.
For example, one needs to perform L2 authentication (can be optional), then 
L3 access
control (today some systems do this with http for lack of a better protocol 
), then you need to perform MIP.
I feel that some environments benefit from MIP having access control (I am 
not saying that this is always desirable).

Look at the following 3 environments:

1. Take CDMA for example, what about clients with mobile IP service?. 
They  benefits from Access control in MIPv4 (Mobile IP
service deployed today).

2. Take Public access WLANs, they use http for access control.

3. One way to get VoIP over WLAN today is to use MIP
in WLAN envs  with no L2 authentication (only way to get decent roam times
(with out CCKM or TKIP). I think MIP having access control

I am fine with leaving this access control from MIP6 charter for now (for I 
think
that when the time is right, some deployments will  mandate it. I understand
  why you feel that Access control at MIP level is not important in GPRS 
like environment.


Thanks
Gopal



At 10:07 PM 9/23/2003 -0400, Soliman Hesham wrote:

>  > I cam of the opinion that  802.1x authentication based
>  > authentication is L2
>  > authentication
>  > It typically terminates on the AP and not on the access
>  > router. Typically
>  > AP is like a bridge. (PANA is another story).
>
>=> (I'll drift slightly off topic here but hopefully
>it helps). You call it L2 authentication because it
>is transported over L2. However, it is actually authenticating
>a much higher layer identifier (NAI). So there is some layer
>violation here but people don't seem to be keen on changing
>that. That's why I thought PANA was a step in the right direction.
>
>  >
>  > Anyway, what I am trying to ask is whether there needs to be
>  > a L3 access
>  > control point
>  > (if I can use that term) to help in authentication, access
>  > control, roaming
>  > etc. I think this is useful in service
>  > provider environments (CDMA 2000 for example).
>
>=> I agree with the need for an L3 access control point
>and that it would be useful for several systems. However,
>since such function is needed independently of mobility,
>it should not be included inside a mobility protocol.
>For instance, you refer to CDMA 2000 which offers a Simple
>IP service where no mobility is needed in the terminal.
>Also, other systems (e.g. GPRS) do not require MIP, yet
>they still need this function. In fact, WLANs today are
>deployed in a way that doesn't require the use of MIP,
>yet they still need this function. So, including this function
>in MIP does not seem useful.
>
>Hesham
>
>
>  >
>  >
>  > Thanks
>  > Gopal
>  >
>  >
>  > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
>  >
>  >
>  > >  > I am assuming that Alpesh is trying to get some level of network
>  > >  > authentication/authorization via MIP signalling.
>  > >  >
>  > >  > I am assuming you mean NAS (network Access server), in which
>  > >  > case what is
>  > >  > the protocol that you
>  > >  > have in mind for L3 authentication/authorization?
>  > (assuming that L2
>  > >  > authentication/authorization may or may not exist).
>  > >
>  > >=> I'm not quite sure what you mean because people
>  > >are running L3 authentication into L2 packets.
>  > >So, naturally, the authentication is L2-dependent
>  > >today (perhaps EAP is an exception). So to answer
>  > >your question, you can use: EAP, PPP, AKA, ...etc depending
>  > >on your link. If you don't want to depend on the
>  > >link layer, use EAP over layer 4, i.e. use PANA
>  > >when it's done.
>  > >
>  > >Hesham
>  > >
>  > >
>  > >  >
>  > >  > Thanks
>  > >  > Gopal
>  > >  >
>  > >  >
>  > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
>  > >  >
>  > >  >
>  > >  > >  > Wondering if the charter should include an entity in the
>  > >  > >  > visited domain/roaming network to aid in AAA/Diameter
>  > >  > authentication,
>  > >  > >  > access control etc?
>  > >  > >
>  > >  > >=> a NAS ? ;) The description of this entity doesn't
>  > >  > >seem to be related to mobility in any way. I think
>  > >  > >this work is generic for fixed and mobile nodes.
>  > >  > >
>  > >  > >    Currently, there is little, if any mechanism
>  > >  > >  > to restrict a mobile node's activities in visited domain.
>  > >  > >
>  > >  > >=> Why do you say that? A NAS will do this job very well
>  > >  > >provided that AAA mechanisms and roaming agreements
>  > >  > >are in place.
>  > >  > >
>  > >  > >  > For practical deployment issues and network
>  > management/control
>  > >  > >  > purposes, I think such an entity is needed.
>  > >  > >
>  > >  > >=> Absolutely, but MIP6 has nothing to do with it.
>  > >  > >
>  > >  > >Hesham
>  > >  > >
>  > >  > >_______________________________________________
>  > >  > >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  Wed Sep 24 16:19: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 QAA05978
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 16:19: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 1A2G6N-00072J-2S
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 16:19:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8OKJ7NB027047
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 16:19:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2G6M-00072A-Nl
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 16:19: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 QAA05937
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 16:18:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2G6K-00023b-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 16:19:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2G6K-00023Y-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 16:19:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2G6J-00071c-4l; Wed, 24 Sep 2003 16:19:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2G5e-00070s-Du
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 16:18: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 QAA05911
	for <mip6@ietf.org>; Wed, 24 Sep 2003 16:18:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2G5c-000236-00
	for mip6@ietf.org; Wed, 24 Sep 2003 16:18:20 -0400
Received: from smtp805.mail.sc5.yahoo.com ([66.163.168.184])
	by ietf-mx with smtp (Exim 4.12)
	id 1A2G5U-00022O-00
	for mip6@ietf.org; Wed, 24 Sep 2003 16:18:19 -0400
Received: from adsl-64-172-59-206.dsl.snfc21.pacbell.net (HELO adithya) (mohanp@sbcglobal.net@64.172.59.206 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 24 Sep 2003 19:19:51 -0000
Message-ID: <001501c382d0$d5b31e40$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Soliman Hesham" <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        <mip6@ietf.org>, "Gopal Dommety" <gdommety@cisco.com>
References: <4.3.2.7.2.20030924081728.02291360@mira-sjcm-3.cisco.com>
Subject: Re: [Mip6] Issue with mipv6 charter
Date: Wed, 24 Sep 2003 12:19:53 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
x-mimeole: Produced By Microsoft MimeOLE V6.00.2727.1300
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 Gopal,

Last time this issue was discussed, there were two cases.

1) MN booting up in a visited network.
2) MN moving in a visited network.

For (1) the latency is not a big issue. For (2), James replied earlier that
Seamoby is looking at
context transfer protocol which might be useful here.

So depending on how you classify your items below, we may not need anything
special.

-mohan



>
>    AP is a bridge and performs L2 access authentication.
> It need not have much of L3 knowledge.  It does not matter
> what you are using for authentication (NAI/MAC address). It is still L2
>   authentication, since it allows L2 access (There are systems such as
>   Public Access where L3 access has an additional authentication,
> That is when L3 access control happens).
>
> I am not saying that access control cannot be done by some other protocol
> or independent of Mobility.
> I think it is a good idea to keep them separate in some environments.
> However,  I think it adds to latency (that might not be acceptable) in
> other environments.
> For example, one needs to perform L2 authentication (can be optional),
then
> L3 access
> control (today some systems do this with http for lack of a better
protocol
> ), then you need to perform MIP.
> I feel that some environments benefit from MIP having access control (I am
> not saying that this is always desirable).
>
> Look at the following 3 environments:
>
> 1. Take CDMA for example, what about clients with mobile IP service?.
> They  benefits from Access control in MIPv4 (Mobile IP
> service deployed today).
>
 > 2. Take Public access WLANs, they use http for access control.
>
> 3. One way to get VoIP over WLAN today is to use MIP
> in WLAN envs  with no L2 authentication (only way to get decent roam times
> (with out CCKM or TKIP). I think MIP having access control
>
> I am fine with leaving this access control from MIP6 charter for now (for
I
> think
> that when the time is right, some deployments will  mandate it. I
understand
>   why you feel that Access control at MIP level is not important in GPRS
> like environment.
>
>
> Thanks
> Gopal
>
>
>
> At 10:07 PM 9/23/2003 -0400, Soliman Hesham wrote:
>
> >  > I cam of the opinion that  802.1x authentication based
> >  > authentication is L2
> >  > authentication
> >  > It typically terminates on the AP and not on the access
> >  > router. Typically
> >  > AP is like a bridge. (PANA is another story).
> >
> >=> (I'll drift slightly off topic here but hopefully
> >it helps). You call it L2 authentication because it
> >is transported over L2. However, it is actually authenticating
> >a much higher layer identifier (NAI). So there is some layer
> >violation here but people don't seem to be keen on changing
> >that. That's why I thought PANA was a step in the right direction.
> >
> >  >
> >  > Anyway, what I am trying to ask is whether there needs to be
> >  > a L3 access
> >  > control point
> >  > (if I can use that term) to help in authentication, access
> >  > control, roaming
> >  > etc. I think this is useful in service
> >  > provider environments (CDMA 2000 for example).
> >
> >=> I agree with the need for an L3 access control point
> >and that it would be useful for several systems. However,
> >since such function is needed independently of mobility,
> >it should not be included inside a mobility protocol.
> >For instance, you refer to CDMA 2000 which offers a Simple
> >IP service where no mobility is needed in the terminal.
> >Also, other systems (e.g. GPRS) do not require MIP, yet
> >they still need this function. In fact, WLANs today are
> >deployed in a way that doesn't require the use of MIP,
> >yet they still need this function. So, including this function
> >in MIP does not seem useful.
> >
> >Hesham
> >
> >
> >  >
> >  >
> >  > Thanks
> >  > Gopal
> >  >
> >  >
> >  > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
> >  >
> >  >
> >  > >  > I am assuming that Alpesh is trying to get some level of network
> >  > >  > authentication/authorization via MIP signalling.
> >  > >  >
> >  > >  > I am assuming you mean NAS (network Access server), in which
> >  > >  > case what is
> >  > >  > the protocol that you
> >  > >  > have in mind for L3 authentication/authorization?
> >  > (assuming that L2
> >  > >  > authentication/authorization may or may not exist).
> >  > >
> >  > >=> I'm not quite sure what you mean because people
> >  > >are running L3 authentication into L2 packets.
> >  > >So, naturally, the authentication is L2-dependent
> >  > >today (perhaps EAP is an exception). So to answer
> >  > >your question, you can use: EAP, PPP, AKA, ...etc depending
> >  > >on your link. If you don't want to depend on the
> >  > >link layer, use EAP over layer 4, i.e. use PANA
> >  > >when it's done.
> >  > >
> >  > >Hesham
> >  > >
> >  > >
> >  > >  >
> >  > >  > Thanks
> >  > >  > Gopal
> >  > >  >
> >  > >  >
> >  > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
> >  > >  >
> >  > >  >
> >  > >  > >  > Wondering if the charter should include an entity in the
> >  > >  > >  > visited domain/roaming network to aid in AAA/Diameter
> >  > >  > authentication,
> >  > >  > >  > access control etc?
> >  > >  > >
> >  > >  > >=> a NAS ? ;) The description of this entity doesn't
> >  > >  > >seem to be related to mobility in any way. I think
> >  > >  > >this work is generic for fixed and mobile nodes.
> >  > >  > >
> >  > >  > >    Currently, there is little, if any mechanism
> >  > >  > >  > to restrict a mobile node's activities in visited domain.
> >  > >  > >
> >  > >  > >=> Why do you say that? A NAS will do this job very well
> >  > >  > >provided that AAA mechanisms and roaming agreements
> >  > >  > >are in place.
> >  > >  > >
> >  > >  > >  > For practical deployment issues and network
> >  > management/control
> >  > >  > >  > purposes, I think such an entity is needed.
> >  > >  > >
> >  > >  > >=> Absolutely, but MIP6 has nothing to do with it.
> >  > >  > >
> >  > >  > >Hesham
> >  > >  > >
> >  > >  > >_______________________________________________
> >  > >  > >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


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 20:18: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 UAA16530
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 20:18: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 1A2Jpg-0004zF-Dn
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:18:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8P0I8ih019163
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:18:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2Jpg-0004z0-7I
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 20:18: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 UAA16467
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 20:18:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Jpe-00059b-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:18:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Jpd-00059Y-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:18:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2JpY-0004yb-Op; Wed, 24 Sep 2003 20:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2Joi-0004wD-UG
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 20:17: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 UAA16450
	for <mip6@ietf.org>; Wed, 24 Sep 2003 20:17:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Jog-000598-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:17:06 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2Jog-00058h-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:17:06 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <TG6DDT1D>; Wed, 24 Sep 2003 20:16:34 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D55@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'James Kempf'" <kempf@docomolabs-usa.com>,
        "'Thierry Ernst'"
	 <ernst@sfc.wide.ad.jp>, mip6@ietf.org
Subject: RE: [Mip6] Are multihoming mechanisms part of the charter ?
Date: Wed, 24 Sep 2003 20:16:30 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


 > So I'm wondering here whether this isn't a broader issue 
 > than MIP. There are
 > a couple of topics around multi-link hosts that seem related, namely
 > interface switching (or vertical handover, assuming that is 
 > what is meant by
 > interface switching) and multi-link transport. The specific part that
 > involves MIP would be changing the HA binding when the 
 > interface is switched
 > (for the first) or having multiple bindings for different 
 > interfaces (for
 > the second), but these seem like straightforward uses of MIP and not
 > something that really requires modifying MIP itself. 

=> In order to have multiple bindings for a single home 
address you need to modify MIP. That's the only part
I see affecting MIP itself. It's a very small change but very 
effective IMO.

 > Nevertheless, there are
 > other technical issues with these that might require some 
 > IETF attention,
 > but I'm not sure whether the MIP group is the right place.

=> It is the right place to address changes to MIP. 
There might be other issues related to vertical handovers
in general and we're not suggesting they get handled
in this WG.

Hesham

 > 
 > Am I missing something?
 > 
 >             jak
 > 

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 20:37: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 UAA17215
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 20:37: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 1A2K80-0005j2-Ki
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:37:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8P0b4w5021994
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:37:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2K7z-0005iP-NF
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 20:37: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 UAA17204
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 20:36:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2K7x-0005PV-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:37:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2K7x-0005PS-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:37:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2K7y-0005gl-3s; Wed, 24 Sep 2003 20:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2K7D-0005g5-Iy
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 20:36: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 UAA17185
	for <mip6@ietf.org>; Wed, 24 Sep 2003 20:36:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2K7B-0005P4-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:36:13 -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 1A2K7A-0005P1-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:36:12 -0400
Message-ID: <041601c382fd$0d7b3160$956015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman Hesham" <H.Soliman@flarion.com>,
        "'Thierry Ernst'" <ernst@sfc.wide.ad.jp>, <mip6@ietf.org>
References: <748C6D0A58C0F94CA63C198B6674697A01922D55@ftmail.lab.flarion.com>
Subject: Re: [Mip6] Are multihoming mechanisms part of the charter ?
Date: Wed, 24 Sep 2003 17:36:25 -0700
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>  > So I'm wondering here whether this isn't a broader issue
>  > than MIP. There are
>  > a couple of topics around multi-link hosts that seem related, namely
>  > interface switching (or vertical handover, assuming that is
>  > what is meant by
>  > interface switching) and multi-link transport. The specific part that
>  > involves MIP would be changing the HA binding when the
>  > interface is switched
>  > (for the first) or having multiple bindings for different
>  > interfaces (for
>  > the second), but these seem like straightforward uses of MIP and not
>  > something that really requires modifying MIP itself.
>
> => In order to have multiple bindings for a single home
> address you need to modify MIP. That's the only part
> I see affecting MIP itself. It's a very small change but very
> effective IMO.
>

OK, so this sounds like an item for the set of updates to the next revision
on the base MIPv6, right? Doesn't seem as if it would be a large enough item
for a separate RFC, or?

            jak


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 20:46: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 UAA17471
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 20:46: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 1A2KGg-0006Td-VN
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:46:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8P0k2Zw024893
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:46:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2KGg-0006TQ-Pr
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 20:46: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 UAA17456
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 20:45:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KGe-0005UW-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:46:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KGe-0005UT-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:46:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2KGf-0006T1-AI; Wed, 24 Sep 2003 20: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 1A2KG0-0006Lx-81
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 20:45: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 UAA17445
	for <mip6@ietf.org>; Wed, 24 Sep 2003 20:45:12 -0400 (EDT)
From: Vijay.Devarapalli@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KFx-0005UJ-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:45:17 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KFx-0005UG-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:45:17 -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.6) with ESMTP id h8P0jHt05173
	for <mip6@ietf.org>; Thu, 25 Sep 2003 03:45:17 +0300 (EET DST)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T64e34284b6ac158f23076@esvir03nok.nokia.com>;
 Thu, 25 Sep 2003 03:45:16 +0300
Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 24 Sep 2003 19:43:52 -0500
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] Are multihoming mechanisms part of the charter ?
Date: Wed, 24 Sep 2003 17:43:51 -0700
Message-ID: <F0B628F30F48064289D8CCC1EE21B7A80EB365@mvebe001.americas.nokia.com>
Thread-Topic: [Mip6] Are multihoming mechanisms part of the charter ?
Thread-Index: AcOC/ShvKts3EIjUS5eSjiX7qZ9ydAAAER7w
To: <kempf@docomolabs-usa.com>, <H.Soliman@flarion.com>,
        <ernst@sfc.wide.ad.jp>, <mip6@ietf.org>
X-OriginalArrivalTime: 25 Sep 2003 00:43:52.0872 (UTC) FILETIME=[17C6E280:01C382FE]
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Jim,

it is big enough to be a separate specification. for example here
is one proposal (that I consider complete)

http://www.ietf.org/internet-drafts/draft-wakikawa-mobileip-multiplecoa-0=
2.txt

Vijay

>=20
> OK, so this sounds like an item for the set of updates to the=20
> next revision
> on the base MIPv6, right? Doesn't seem as if it would be a=20
> large enough item
> for a separate RFC, or?
>=20
>             jak
>=20
>=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  Wed Sep 24 20:55: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 UAA17650
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 20: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 1A2KPP-0006rR-St
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:55:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8P0t379026367
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 20:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2KPP-0006qT-ME
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 20:55: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 UAA17635
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 20:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KPN-0005YY-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:55:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KPM-0005YV-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 20:55:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2KPO-0006q1-DR; Wed, 24 Sep 2003 20: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 1A2KOd-0006ok-RN
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 20: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 UAA17607
	for <mip6@ietf.org>; Wed, 24 Sep 2003 20:54:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KOb-0005Xn-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:54:13 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2KOa-0005XM-00
	for mip6@ietf.org; Wed, 24 Sep 2003 20:54:12 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <TG6DDTGC>; Wed, 24 Sep 2003 20:53:38 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A01922D57@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        Soliman Hesham
	 <H.Soliman@flarion.com>,
        "'Alpesh'" <alpesh@cisco.com>, mip6@ietf.org,
        Gopal Dommety <gdommety@cisco.com>
Subject: RE: [Mip6] Issue with mipv6 charter
Date: Wed, 24 Sep 2003 20:53:27 -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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

Gopal, 

Mohan's email below is a good summary. I don't 
see any latency issues in either of the cases listed 
below. At boot up it's a non issue and after that you
use CT, which is needed anyway. 

Also, whether authentication is carried on L2 or L3
it _is_ authenticating for network access and 
for charging. Some people chose to do it on L2 (actually
pretty much everyone chose that) but that doesn't mean
you need another L3 protocol on top. Of course, if we're 
starting fresh we could start with a L3 authentication 
mechanism that can bootstrap L2 security. This is where 
I think PANA will be useful. 

Hesham

 > -----Original Message-----
 > From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net]
 > Sent: Wednesday, September 24, 2003 3:20 PM
 > To: Soliman Hesham; 'Alpesh'; mip6@ietf.org; Gopal Dommety
 > Subject: Re: [Mip6] Issue with mipv6 charter
 > 
 > 
 >  Gopal,
 > 
 > Last time this issue was discussed, there were two cases.
 > 
 > 1) MN booting up in a visited network.
 > 2) MN moving in a visited network.
 > 
 > For (1) the latency is not a big issue. For (2), James 
 > replied earlier that
 > Seamoby is looking at
 > context transfer protocol which might be useful here.
 > 
 > So depending on how you classify your items below, we may 
 > not need anything
 > special.
 > 
 > -mohan
 > 
 > 
 > 
 > >
 > >    AP is a bridge and performs L2 access authentication.
 > > It need not have much of L3 knowledge.  It does not matter
 > > what you are using for authentication (NAI/MAC address). 
 > It is still L2
 > >   authentication, since it allows L2 access (There are 
 > systems such as
 > >   Public Access where L3 access has an additional authentication,
 > > That is when L3 access control happens).
 > >
 > > I am not saying that access control cannot be done by some 
 > other protocol
 > > or independent of Mobility.
 > > I think it is a good idea to keep them separate in some 
 > environments.
 > > However,  I think it adds to latency (that might not be 
 > acceptable) in
 > > other environments.
 > > For example, one needs to perform L2 authentication (can 
 > be optional),
 > then
 > > L3 access
 > > control (today some systems do this with http for lack of a better
 > protocol
 > > ), then you need to perform MIP.
 > > I feel that some environments benefit from MIP having 
 > access control (I am
 > > not saying that this is always desirable).
 > >
 > > Look at the following 3 environments:
 > >
 > > 1. Take CDMA for example, what about clients with mobile 
 > IP service?.
 > > They  benefits from Access control in MIPv4 (Mobile IP
 > > service deployed today).
 > >
 >  > 2. Take Public access WLANs, they use http for access control.
 > >
 > > 3. One way to get VoIP over WLAN today is to use MIP
 > > in WLAN envs  with no L2 authentication (only way to get 
 > decent roam times
 > > (with out CCKM or TKIP). I think MIP having access control
 > >
 > > I am fine with leaving this access control from MIP6 
 > charter for now (for
 > I
 > > think
 > > that when the time is right, some deployments will  mandate it. I
 > understand
 > >   why you feel that Access control at MIP level is not 
 > important in GPRS
 > > like environment.
 > >
 > >
 > > Thanks
 > > Gopal
 > >
 > >
 > >
 > > At 10:07 PM 9/23/2003 -0400, Soliman Hesham wrote:
 > >
 > > >  > I cam of the opinion that  802.1x authentication based
 > > >  > authentication is L2
 > > >  > authentication
 > > >  > It typically terminates on the AP and not on the access
 > > >  > router. Typically
 > > >  > AP is like a bridge. (PANA is another story).
 > > >
 > > >=> (I'll drift slightly off topic here but hopefully
 > > >it helps). You call it L2 authentication because it
 > > >is transported over L2. However, it is actually authenticating
 > > >a much higher layer identifier (NAI). So there is some layer
 > > >violation here but people don't seem to be keen on changing
 > > >that. That's why I thought PANA was a step in the right direction.
 > > >
 > > >  >
 > > >  > Anyway, what I am trying to ask is whether there needs to be
 > > >  > a L3 access
 > > >  > control point
 > > >  > (if I can use that term) to help in authentication, access
 > > >  > control, roaming
 > > >  > etc. I think this is useful in service
 > > >  > provider environments (CDMA 2000 for example).
 > > >
 > > >=> I agree with the need for an L3 access control point
 > > >and that it would be useful for several systems. However,
 > > >since such function is needed independently of mobility,
 > > >it should not be included inside a mobility protocol.
 > > >For instance, you refer to CDMA 2000 which offers a Simple
 > > >IP service where no mobility is needed in the terminal.
 > > >Also, other systems (e.g. GPRS) do not require MIP, yet
 > > >they still need this function. In fact, WLANs today are
 > > >deployed in a way that doesn't require the use of MIP,
 > > >yet they still need this function. So, including this function
 > > >in MIP does not seem useful.
 > > >
 > > >Hesham
 > > >
 > > >
 > > >  >
 > > >  >
 > > >  > Thanks
 > > >  > Gopal
 > > >  >
 > > >  >
 > > >  > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
 > > >  >
 > > >  >
 > > >  > >  > I am assuming that Alpesh is trying to get some 
 > level of network
 > > >  > >  > authentication/authorization via MIP signalling.
 > > >  > >  >
 > > >  > >  > I am assuming you mean NAS (network Access 
 > server), in which
 > > >  > >  > case what is
 > > >  > >  > the protocol that you
 > > >  > >  > have in mind for L3 authentication/authorization?
 > > >  > (assuming that L2
 > > >  > >  > authentication/authorization may or may not exist).
 > > >  > >
 > > >  > >=> I'm not quite sure what you mean because people
 > > >  > >are running L3 authentication into L2 packets.
 > > >  > >So, naturally, the authentication is L2-dependent
 > > >  > >today (perhaps EAP is an exception). So to answer
 > > >  > >your question, you can use: EAP, PPP, AKA, ...etc depending
 > > >  > >on your link. If you don't want to depend on the
 > > >  > >link layer, use EAP over layer 4, i.e. use PANA
 > > >  > >when it's done.
 > > >  > >
 > > >  > >Hesham
 > > >  > >
 > > >  > >
 > > >  > >  >
 > > >  > >  > Thanks
 > > >  > >  > Gopal
 > > >  > >  >
 > > >  > >  >
 > > >  > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
 > > >  > >  >
 > > >  > >  >
 > > >  > >  > >  > Wondering if the charter should include an 
 > entity in the
 > > >  > >  > >  > visited domain/roaming network to aid in 
 > AAA/Diameter
 > > >  > >  > authentication,
 > > >  > >  > >  > access control etc?
 > > >  > >  > >
 > > >  > >  > >=> a NAS ? ;) The description of this entity doesn't
 > > >  > >  > >seem to be related to mobility in any way. I think
 > > >  > >  > >this work is generic for fixed and mobile nodes.
 > > >  > >  > >
 > > >  > >  > >    Currently, there is little, if any mechanism
 > > >  > >  > >  > to restrict a mobile node's activities in 
 > visited domain.
 > > >  > >  > >
 > > >  > >  > >=> Why do you say that? A NAS will do this job very well
 > > >  > >  > >provided that AAA mechanisms and roaming agreements
 > > >  > >  > >are in place.
 > > >  > >  > >
 > > >  > >  > >  > For practical deployment issues and network
 > > >  > management/control
 > > >  > >  > >  > purposes, I think such an entity is needed.
 > > >  > >  > >
 > > >  > >  > >=> Absolutely, but MIP6 has nothing to do with it.
 > > >  > >  > >
 > > >  > >  > >Hesham
 > > >  > >  > >
 > > >  > >  > >_______________________________________________
 > > >  > >  > >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
 > 

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Wed Sep 24 23:03: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 XAA20812
	for <mip6-archive@odin.ietf.org>; Wed, 24 Sep 2003 23:03: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 1A2MPM-0004Da-KY
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 23:03:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8P338St016210
	for mip6-archive@odin.ietf.org; Wed, 24 Sep 2003 23:03:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2MPM-0004DL-GS
	for mip6-web-archive@optimus.ietf.org; Wed, 24 Sep 2003 23:03: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 XAA20791
	for <mip6-web-archive@ietf.org>; Wed, 24 Sep 2003 23:02:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2MPI-0006fT-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 23:03:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2MPI-0006fO-00
	for mip6-web-archive@ietf.org; Wed, 24 Sep 2003 23:03:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2MPF-0004Cj-8d; Wed, 24 Sep 2003 23: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 1A2MOj-0004B0-H7
	for mip6@optimus.ietf.org; Wed, 24 Sep 2003 23:02: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 XAA20758
	for <mip6@ietf.org>; Wed, 24 Sep 2003 23:02:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2MOf-0006er-00
	for mip6@ietf.org; Wed, 24 Sep 2003 23:02:25 -0400
Received: from shonan.sfc.wide.ad.jp ([203.178.142.130])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2MOf-0006eA-00
	for mip6@ietf.org; Wed, 24 Sep 2003 23:02:25 -0400
Received: from galibier.nautilus6.org (unknown [203.178.138.3])
	by shonan.sfc.wide.ad.jp (Postfix) with SMTP
	id DC5CE5D097; Thu, 25 Sep 2003 12:01:54 +0900 (JST)
Date: Thu, 25 Sep 2003 11:56:37 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: <Basavaraj.Patil@nokia.com>
Cc: H.Soliman@flarion.com, mip6@ietf.org
Subject: Re: [Mip6] Are multihoming mechanisms part of the charter ?
Message-Id: <20030925115637.6cc96d9a.ernst@sfc.wide.ad.jp>
In-Reply-To: <697DAA22C5004B4596E033803A7CEF44024DB7A5@daebe007.americas.nokia.com>
References: <697DAA22C5004B4596E033803A7CEF44024DB7A5@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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hi,

> >  > I'm sorry I didn't have the time to follow the discussion on the list
> >  > recently, so I may be mistaken.
> >  > 
> >  > I didn't see anything related to interface switiching mechanisms for
> >  > mobile hosts, is this something that could be considered in the
> >  > definition of the new charter ? I consider this mechanism as
> >  > tremendously important if we want to fully deploy mobility.
> 
> "Fully deploy mobility"..... I think mobility can be deployed just
> as well without having specific solutions for dealing with IF switching
> mechanisms. 

I used this wording on purpose, I was sure someone would raise a point
here ... Well, if we intend to deploy always connected devices, at
anytime, anywhere, probably the device cannot rely on only one
communication medium. So, I cannot see the deployment of mobility in its
full extend using only one interface.

> But it is an interesting idea. There has been discussion in
> progress since the last IETF with at least 3 I-Ds on this topic. It would
> be good to identify what are the problems that IF switching solves and
> subsequently what are the requirements. This can be taken up as a first 
> step before taking the leap.

OK, so it's time to inform this ML that authors of two of these drafts
have been gathering together to issue a problem statement draft. The
problem statement draft should be ready by end of next week and could be
used as an input to assess what need to be done and where.

But I suspect that MIP modifications is only a part of the work to be
done (but still a necessary part). Actually, I can see multihoming
supportive mechanisms affecting both MIP6, NEMO, and Multi6 WG
activities.

Thierry.


> > => Agreed. I hope we can include that, given the amount of 
> > discussion and interest generated before and during the 
> > Vienna meeting. 
> > 
> > Hesham

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 25 11:52: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 LAA01907
	for <mip6-archive@odin.ietf.org>; Thu, 25 Sep 2003 11:52: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 1A2YPU-0001ZN-4a
	for mip6-archive@odin.ietf.org; Thu, 25 Sep 2003 11:52:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PFq4EP006028
	for mip6-archive@odin.ietf.org; Thu, 25 Sep 2003 11: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 1A2YPT-0001Z9-WC
	for mip6-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 11: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 LAA01891
	for <mip6-web-archive@ietf.org>; Thu, 25 Sep 2003 11:51:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2YPS-0000R6-00
	for mip6-web-archive@ietf.org; Thu, 25 Sep 2003 11:52:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2YPS-0000R2-00
	for mip6-web-archive@ietf.org; Thu, 25 Sep 2003 11:52:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2YPR-0001YX-3b; Thu, 25 Sep 2003 11: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 1A2YOy-0001Xx-9b
	for mip6@optimus.ietf.org; Thu, 25 Sep 2003 11:51: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 LAA01868
	for <mip6@ietf.org>; Thu, 25 Sep 2003 11:51:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2YOw-0000QZ-00
	for mip6@ietf.org; Thu, 25 Sep 2003 11:51:30 -0400
Received: from shaku.sfc.wide.ad.jp ([203.178.143.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2YOw-0000Pw-00
	for mip6@ietf.org; Thu, 25 Sep 2003 11:51:30 -0400
Received: from monster.sfc.wide.ad.jp.sfc.wide.ad.jp ([193.190.227.114])
	(authenticated bits=0)
	by shaku.sfc.wide.ad.jp (8.12.10/8.12.0) with ESMTP id h8PFlfYv015798;
	Fri, 26 Sep 2003 00:47:43 +0900
Date: Fri, 26 Sep 2003 00:50:39 +0900
Message-ID: <s78vfrgdfzk.wl@monster.sfc.wide.ad.jp.sfc.wide.ad.jp>
From: Ryuji Wakikawa<ryuji@sfc.wide.ad.jp>
To: Vijay.Devarapalli@nokia.com
Cc: kempf@docomolabs-usa.com, H.Soliman@flarion.com, ernst@sfc.wide.ad.jp,
        mip6@ietf.org
Subject: Re: [Mip6] Are multihoming mechanisms part of the charter ?
In-Reply-To: <F0B628F30F48064289D8CCC1EE21B7A80EB365@mvebe001.americas.nokia.com>
References: <F0B628F30F48064289D8CCC1EE21B7A80EB365@mvebe001.americas.nokia.com>
User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd)
 MULE/4.1 (AOI)
Organization: Keio University
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>


Hi Vijay

We recently submitted draft-wakikawa-multiplecoa-02 version. 
We changed some terms and gave detailed example scenarios in Apendix.
Interface ID (IFID) is now called Binding Unique Identification number (BID).

We also explain detail operations when MN returns home. MN's returning
home is a bit tricky situation because HA defends MN's HoA by proxy
NA.

All extensions and issues are described in the draft. 
http://www.ietf.org/internet-drafts/draft-wakikawa-mobileip-multiplecoa-02.txt

I appreciate any comments on this draft (and this topic)

BTW, we also supports NEMO, too.

regards,
ryuji


At Wed, 24 Sep 2003 17:43:51 -0700,
Vijay.Devarapalli@nokia.com wrote:
> 
> Jim,
> 
> it is big enough to be a separate specification. for example here
> is one proposal (that I consider complete)
> 
> http://www.ietf.org/internet-drafts/draft-wakikawa-mobileip-multiplecoa-02.txt
> 
> Vijay
> 
> > 
> > OK, so this sounds like an item for the set of updates to the 
> > next revision
> > on the base MIPv6, right? Doesn't seem as if it would be a 
> > large enough item
> > for a separate RFC, or?
> > 
> >             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

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Thu Sep 25 12:46: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 MAA05008
	for <mip6-archive@odin.ietf.org>; Thu, 25 Sep 2003 12:46: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 1A2ZFl-0005Ih-Lu
	for mip6-archive@odin.ietf.org; Thu, 25 Sep 2003 12:46:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8PGk5R5020369
	for mip6-archive@odin.ietf.org; Thu, 25 Sep 2003 12:46:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2ZFl-0005IS-G3
	for mip6-web-archive@optimus.ietf.org; Thu, 25 Sep 2003 12:46: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 MAA04928
	for <mip6-web-archive@ietf.org>; Thu, 25 Sep 2003 12:45:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ZFj-0001Kt-00
	for mip6-web-archive@ietf.org; Thu, 25 Sep 2003 12:46:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ZFj-0001Kq-00
	for mip6-web-archive@ietf.org; Thu, 25 Sep 2003 12:46:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2ZFh-0005HH-0s; Thu, 25 Sep 2003 12: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 1A2ZEy-0005Cx-Jp
	for mip6@optimus.ietf.org; Thu, 25 Sep 2003 12:45: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 MAA04796
	for <mip6@ietf.org>; Thu, 25 Sep 2003 12:45:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ZEw-0001IP-00
	for mip6@ietf.org; Thu, 25 Sep 2003 12:45:14 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2ZEv-0001GH-00
	for mip6@ietf.org; Thu, 25 Sep 2003 12:45:13 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-3.cisco.com with ESMTP; 25 Sep 2003 09:47:42 -0700
Received: from gdommety-w2k01.cisco.com (sjc-vpn2-88.cisco.com [10.21.112.88])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h8PGiWYc016518;
	Thu, 25 Sep 2003 09:44:35 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030925094239.02878c50@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 25 Sep 2003 09:44:29 -0700
To: Soliman Hesham <H.Soliman@flarion.com>,
        "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        Soliman Hesham <H.Soliman@flarion.com>, "'Alpesh'" <alpesh@cisco.com>,
        mip6@ietf.org
From: Gopal Dommety <gdommety@cisco.com>
Subject: RE: [Mip6] Issue with mipv6 charter
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A01922D57@ftmail.lab.flario
 n.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

Hesham,

If there is CT enabled on the edges and there is another access
  control protocol, then it helps (big ifs in my opinion).
Anyway, let us drop this item for now.

Thanks for the comments
Gopal

At 08:53 PM 9/24/2003 -0400, Soliman Hesham wrote:
>Gopal,
>
>Mohan's email below is a good summary. I don't
>see any latency issues in either of the cases listed
>below. At boot up it's a non issue and after that you
>use CT, which is needed anyway.
>
>Also, whether authentication is carried on L2 or L3
>it _is_ authenticating for network access and
>for charging. Some people chose to do it on L2 (actually
>pretty much everyone chose that) but that doesn't mean
>you need another L3 protocol on top. Of course, if we're
>starting fresh we could start with a L3 authentication
>mechanism that can bootstrap L2 security. This is where
>I think PANA will be useful.
>
>Hesham
>
>  > -----Original Message-----
>  > From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net]
>  > Sent: Wednesday, September 24, 2003 3:20 PM
>  > To: Soliman Hesham; 'Alpesh'; mip6@ietf.org; Gopal Dommety
>  > Subject: Re: [Mip6] Issue with mipv6 charter
>  >
>  >
>  >  Gopal,
>  >
>  > Last time this issue was discussed, there were two cases.
>  >
>  > 1) MN booting up in a visited network.
>  > 2) MN moving in a visited network.
>  >
>  > For (1) the latency is not a big issue. For (2), James
>  > replied earlier that
>  > Seamoby is looking at
>  > context transfer protocol which might be useful here.
>  >
>  > So depending on how you classify your items below, we may
>  > not need anything
>  > special.
>  >
>  > -mohan
>  >
>  >
>  >
>  > >
>  > >    AP is a bridge and performs L2 access authentication.
>  > > It need not have much of L3 knowledge.  It does not matter
>  > > what you are using for authentication (NAI/MAC address).
>  > It is still L2
>  > >   authentication, since it allows L2 access (There are
>  > systems such as
>  > >   Public Access where L3 access has an additional authentication,
>  > > That is when L3 access control happens).
>  > >
>  > > I am not saying that access control cannot be done by some
>  > other protocol
>  > > or independent of Mobility.
>  > > I think it is a good idea to keep them separate in some
>  > environments.
>  > > However,  I think it adds to latency (that might not be
>  > acceptable) in
>  > > other environments.
>  > > For example, one needs to perform L2 authentication (can
>  > be optional),
>  > then
>  > > L3 access
>  > > control (today some systems do this with http for lack of a better
>  > protocol
>  > > ), then you need to perform MIP.
>  > > I feel that some environments benefit from MIP having
>  > access control (I am
>  > > not saying that this is always desirable).
>  > >
>  > > Look at the following 3 environments:
>  > >
>  > > 1. Take CDMA for example, what about clients with mobile
>  > IP service?.
>  > > They  benefits from Access control in MIPv4 (Mobile IP
>  > > service deployed today).
>  > >
>  >  > 2. Take Public access WLANs, they use http for access control.
>  > >
>  > > 3. One way to get VoIP over WLAN today is to use MIP
>  > > in WLAN envs  with no L2 authentication (only way to get
>  > decent roam times
>  > > (with out CCKM or TKIP). I think MIP having access control
>  > >
>  > > I am fine with leaving this access control from MIP6
>  > charter for now (for
>  > I
>  > > think
>  > > that when the time is right, some deployments will  mandate it. I
>  > understand
>  > >   why you feel that Access control at MIP level is not
>  > important in GPRS
>  > > like environment.
>  > >
>  > >
>  > > Thanks
>  > > Gopal
>  > >
>  > >
>  > >
>  > > At 10:07 PM 9/23/2003 -0400, Soliman Hesham wrote:
>  > >
>  > > >  > I cam of the opinion that  802.1x authentication based
>  > > >  > authentication is L2
>  > > >  > authentication
>  > > >  > It typically terminates on the AP and not on the access
>  > > >  > router. Typically
>  > > >  > AP is like a bridge. (PANA is another story).
>  > > >
>  > > >=> (I'll drift slightly off topic here but hopefully
>  > > >it helps). You call it L2 authentication because it
>  > > >is transported over L2. However, it is actually authenticating
>  > > >a much higher layer identifier (NAI). So there is some layer
>  > > >violation here but people don't seem to be keen on changing
>  > > >that. That's why I thought PANA was a step in the right direction.
>  > > >
>  > > >  >
>  > > >  > Anyway, what I am trying to ask is whether there needs to be
>  > > >  > a L3 access
>  > > >  > control point
>  > > >  > (if I can use that term) to help in authentication, access
>  > > >  > control, roaming
>  > > >  > etc. I think this is useful in service
>  > > >  > provider environments (CDMA 2000 for example).
>  > > >
>  > > >=> I agree with the need for an L3 access control point
>  > > >and that it would be useful for several systems. However,
>  > > >since such function is needed independently of mobility,
>  > > >it should not be included inside a mobility protocol.
>  > > >For instance, you refer to CDMA 2000 which offers a Simple
>  > > >IP service where no mobility is needed in the terminal.
>  > > >Also, other systems (e.g. GPRS) do not require MIP, yet
>  > > >they still need this function. In fact, WLANs today are
>  > > >deployed in a way that doesn't require the use of MIP,
>  > > >yet they still need this function. So, including this function
>  > > >in MIP does not seem useful.
>  > > >
>  > > >Hesham
>  > > >
>  > > >
>  > > >  >
>  > > >  >
>  > > >  > Thanks
>  > > >  > Gopal
>  > > >  >
>  > > >  >
>  > > >  > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
>  > > >  >
>  > > >  >
>  > > >  > >  > I am assuming that Alpesh is trying to get some
>  > level of network
>  > > >  > >  > authentication/authorization via MIP signalling.
>  > > >  > >  >
>  > > >  > >  > I am assuming you mean NAS (network Access
>  > server), in which
>  > > >  > >  > case what is
>  > > >  > >  > the protocol that you
>  > > >  > >  > have in mind for L3 authentication/authorization?
>  > > >  > (assuming that L2
>  > > >  > >  > authentication/authorization may or may not exist).
>  > > >  > >
>  > > >  > >=> I'm not quite sure what you mean because people
>  > > >  > >are running L3 authentication into L2 packets.
>  > > >  > >So, naturally, the authentication is L2-dependent
>  > > >  > >today (perhaps EAP is an exception). So to answer
>  > > >  > >your question, you can use: EAP, PPP, AKA, ...etc depending
>  > > >  > >on your link. If you don't want to depend on the
>  > > >  > >link layer, use EAP over layer 4, i.e. use PANA
>  > > >  > >when it's done.
>  > > >  > >
>  > > >  > >Hesham
>  > > >  > >
>  > > >  > >
>  > > >  > >  >
>  > > >  > >  > Thanks
>  > > >  > >  > Gopal
>  > > >  > >  >
>  > > >  > >  >
>  > > >  > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
>  > > >  > >  >
>  > > >  > >  >
>  > > >  > >  > >  > Wondering if the charter should include an
>  > entity in the
>  > > >  > >  > >  > visited domain/roaming network to aid in
>  > AAA/Diameter
>  > > >  > >  > authentication,
>  > > >  > >  > >  > access control etc?
>  > > >  > >  > >
>  > > >  > >  > >=> a NAS ? ;) The description of this entity doesn't
>  > > >  > >  > >seem to be related to mobility in any way. I think
>  > > >  > >  > >this work is generic for fixed and mobile nodes.
>  > > >  > >  > >
>  > > >  > >  > >    Currently, there is little, if any mechanism
>  > > >  > >  > >  > to restrict a mobile node's activities in
>  > visited domain.
>  > > >  > >  > >
>  > > >  > >  > >=> Why do you say that? A NAS will do this job very well
>  > > >  > >  > >provided that AAA mechanisms and roaming agreements
>  > > >  > >  > >are in place.
>  > > >  > >  > >
>  > > >  > >  > >  > For practical deployment issues and network
>  > > >  > management/control
>  > > >  > >  > >  > purposes, I think such an entity is needed.
>  > > >  > >  > >
>  > > >  > >  > >=> Absolutely, but MIP6 has nothing to do with it.
>  > > >  > >  > >
>  > > >  > >  > >Hesham
>  > > >  > >  > >
>  > > >  > >  > >_______________________________________________
>  > > >  > >  > >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
>  >
>
>_______________________________________________
>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 Sep 26 11:22: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 LAA10578
	for <mip6-archive@odin.ietf.org>; Fri, 26 Sep 2003 11:22: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 1A2uPz-0000Kf-Nd
	for mip6-archive@odin.ietf.org; Fri, 26 Sep 2003 11:22:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8QFM3Og001273
	for mip6-archive@odin.ietf.org; Fri, 26 Sep 2003 11:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2uPz-0000KS-Ho
	for mip6-web-archive@optimus.ietf.org; Fri, 26 Sep 2003 11:22: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 LAA10551
	for <mip6-web-archive@ietf.org>; Fri, 26 Sep 2003 11:21:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2uPy-0002Az-00
	for mip6-web-archive@ietf.org; Fri, 26 Sep 2003 11:22:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2uPy-0002Av-00
	for mip6-web-archive@ietf.org; Fri, 26 Sep 2003 11:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2uPx-0000Jy-5B; Fri, 26 Sep 2003 11:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A2uOy-0000Hv-Tn
	for mip6@optimus.ietf.org; Fri, 26 Sep 2003 11:21: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 LAA10513
	for <mip6@ietf.org>; Fri, 26 Sep 2003 11:20:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2uOx-0002AJ-00
	for mip6@ietf.org; Fri, 26 Sep 2003 11:21:00 -0400
Received: from twix.hotpop.com ([204.57.55.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A2uOx-00029t-00
	for mip6@ietf.org; Fri, 26 Sep 2003 11:20:59 -0400
Received: from hotpop.com (kubrick.hotpop.com [204.57.55.16])
	by twix.hotpop.com (Postfix) with SMTP id 2CA1B7DD1E6
	for <mip6@ietf.org>; Fri, 26 Sep 2003 15:20:04 +0000 (UTC)
Received: from tuanlinh (unknown [210.245.13.52])
	by smtp-1.hotpop.com (Postfix) with SMTP id C07B71A026B
	for <mip6@ietf.org>; Fri, 26 Sep 2003 08:42:53 +0000 (UTC)
Message-ID: <000801c3847e$858d94e0$340df5d2@tuanlinh>
Reply-To: "Tuan Linh" <bigbigbee@yahoo.com>
From: "Tuan Linh" <bigbigbee@hotpop.com>
To: <mip6@ietf.org>
Date: Fri, 26 Sep 2003 15:35:23 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C38443.CD2A90E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-HotPOP: -----------------------------------------------
                   Sent By HotPOP.com FREE Email
             Get your FREE POP email at www.HotPOP.com
          -----------------------------------------------
Subject: [Mip6] Can I have an any infomation about "overview of MIPv6 deployment in mobile network"?
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C38443.CD2A90E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



------=_NextPart_000_0005_01C38443.CD2A90E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0005_01C38443.CD2A90E0--



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sat Sep 27 23:46: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 XAA23261
	for <mip6-archive@odin.ietf.org>; Sat, 27 Sep 2003 23:46: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 1A3SVa-0000gK-OM
	for mip6-archive@odin.ietf.org; Sat, 27 Sep 2003 23:46:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8S3k6Rm002614
	for mip6-archive@odin.ietf.org; Sat, 27 Sep 2003 23:46:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A3SVa-0000g5-Ht
	for mip6-web-archive@optimus.ietf.org; Sat, 27 Sep 2003 23:46: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 XAA23251
	for <mip6-web-archive@ietf.org>; Sat, 27 Sep 2003 23:45:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A3SVY-0004gh-00
	for mip6-web-archive@ietf.org; Sat, 27 Sep 2003 23:46:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A3SVY-0004gd-00
	for mip6-web-archive@ietf.org; Sat, 27 Sep 2003 23:46:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A3SVV-0000fK-PS; Sat, 27 Sep 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 1A3SV5-0000ej-72
	for mip6@optimus.ietf.org; Sat, 27 Sep 2003 23:45:35 -0400
Received: from SERVER ([218.88.230.94])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA23214
	for <mip6@ietf.org>; Sat, 27 Sep 2003 23:45:20 -0400 (EDT)
Message-Id: <200309280345.XAA23214@ietf.org>
From: "marietta" <bjan2@email.com>
To: "mip6@ietf.org" <mip6@ietf.org>
Date: Sun, 28 Sep 2003 11:41:41 +0800
X-Priority: 3 (normal)
Importance: Normal
X-Mailer: AOL 7.0 for Windows US sub 118
MIME-Version: 1.0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64
Subject: [Mip6] Re: Read this and take control of your future.
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEgVHJhbnNpdGlvbmFs
Ly9FTiI+DQo8aHRtbD4NCjxoZWFkPg0KPHRpdGxlPlVudGl0bGVkIERvY3VtZW50PC90aXRsZT4N
CjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0idGV4dC9odG1sOyBjaGFy
c2V0PWlzby04ODU5LTEiPg0KPC9oZWFkPg0KDQo8Ym9keSBiZ2NvbG9yPSIjOTkwMDAwIiB0ZXh0
PSJ5ZWxsb3ciIGxpbms9IiNDQ0NDQ0MiIHZsaW5rPSIjQ0NDQ0NDIiBhbGluaz0iI0NDQ0NDQyIg
bGVmdG1hcmdpbj0iMCIgdG9wbWFyZ2luPSIwIiBtYXJnaW53aWR0aD0iMCIgbWFyZ2luaGVpZ2h0
PSIwIj4NCjx0YWJsZSB3aWR0aD0iMTAwJSIgYm9yZGVyPSIwIiBhbGlnbj0iY2VudGVyIiBjZWxs
cGFkZGluZz0iMCIgY2VsbHNwYWNpbmc9IjEiPg0KPHRyPg0KPHRkIGFsaWduPSJjZW50ZXIiPjxi
cj48YnI+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IndoaXRlIj48Yj5ET04nVCBMT1M8ZmQ4dTFhPkUg
QU5ZIE1PUkUgTU9ORVkgT04gWU88ZmQ4dTFhPlVSIEVYSVNUSU5HIEhPTUUgTE9BTiE8YnI+PGJy
PndlIGNvdWxkIGFsbCB1c2Ugc29tZSBleHRyYSBtb25leSBhdCB0aGUgZW5kIG9mIHRoZSB3ZWVr
ITxicj48QlI+RXZlPHFxcXBvZGQ+cnkgZGF5IHRoPG9xcXd3Pm91c2FuZHMgb2YgQW1lcmljYW5z
IGFyZSBzYTxra2tmb29mZD52aW5nIG1vbmV5LCBkb24ndCBiZSBvbmUgb2YgdGhlIGZldyB3aG8g
bWlzcyBvdXQhPEJSPjxicj5JIHBlcnNvbmFsbHkgY291bGRudCBoPHBwcGFhYXNzcmV3PmF2ZSBn
b3Qgb3V0IG9mIHRoZSBtZXNzIEkgd2FzIGluIHdpdGhvdXQgdGhpcyBzaXRlPGJyPjwvdGQ+DQo8
L3RyPg0KPHRyPjx0ZCBhbGlnbj0iY2VudGVyIj48YnI+PGEgaHJlZj0iaHR0cDovL3d3dy5hNHRh
NHRhd2UuY29tLzAvP29wZW4iPjxpbWcgc3JjPSJodHRwOi8vb3BlbkBhNHRhNHRhd2UuY29tL3Nw
YWNlci5naWYiPjxicj48ZmQ4dTFhPjxmb250IGNvbG9yPSJ5ZWxsb3ciIHNpemU9IjMiPjxiPjx1
PkNvbWUgYW5kIGJyb3dzZSBub3cuLjwvYT48YnI+PGJyPjwvdGQ+PC90cj4NCjwvdGFibGU+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Sun Sep 28 15:12: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 PAA27647
	for <mip6-archive@odin.ietf.org>; Sun, 28 Sep 2003 15:12: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 1A3gxf-0001Nz-Qe
	for mip6-archive@odin.ietf.org; Sun, 28 Sep 2003 15:12:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8SJC30B005323
	for mip6-archive@odin.ietf.org; Sun, 28 Sep 2003 15:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A3gxe-0001Nj-Vt
	for mip6-web-archive@optimus.ietf.org; Sun, 28 Sep 2003 15:12: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 PAA27594
	for <mip6-web-archive@ietf.org>; Sun, 28 Sep 2003 15:11:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A3gxd-0003xg-00
	for mip6-web-archive@ietf.org; Sun, 28 Sep 2003 15:12:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A3gxd-0003xd-00
	for mip6-web-archive@ietf.org; Sun, 28 Sep 2003 15:12:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A3gxd-0001N6-Oc; Sun, 28 Sep 2003 15:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A3gxd-0001Mt-8f
	for mip6@optimus.ietf.org; Sun, 28 Sep 2003 15:12:01 -0400
Received: from mail1.artmarket.com (mail1.artmarket.com [194.242.43.183])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27576
	for <mip6@ietf.org>; Sun, 28 Sep 2003 15:11:50 -0400 (EDT)
Date: Sun, 28 Sep 2003 15:11:50 -0400 (EDT)
Message-Id: <200309281911.PAA27576@ietf.org>
From: A  R  T <list@artaddiction.com>
To: <mip6@ietf.org>
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 PAA27581
Subject: [Mip6] [adv] 1700 - 2003  Story of the Art Market
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<TITLE>Artists search engine by Artprice TM - copyright Artprice.com</TIT=
LE>
<META http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-885=
9-1">
<META name=3D"UNSUB" content=3D"<!--26351250_1-->">
<META name=3D"ROBOTS" content=3D"NOINDEX">
</HEAD>
<BODY bgcolor=3D"#FFFFFF" text=3D"#000000">
<TABLE cellspacing=3D"0" cellpadding=3D"0" align=3D"center" border=3D"0">
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/fs.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><A href=3D"http://www.artistbiography.com/"><IMG src=3D"http://web.ar=
tprice.com/img/bio.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><A href=3D"http://web.artprice.com"><IMG src=3D"http://web.artprice.c=
om/img/Home.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/G.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><A href=3D"http://web.artprice.com"><IMG src=3D"http://web.artprice.c=
om/img/Home.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/fs.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>A</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>R</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/HelpBlack.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/AMI/AMInsight.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><A href=3D"http://web.artprice.com/corporate/EN/Visite/pages/nb.htm">=
<IMG src=3D"http://web.artprice.com/img/HelpBlack.gif" border=3D"0"></A><=
/TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>T</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/today.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/E.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>P</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/G.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/today.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/D.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/A.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/D.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/G.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/H.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>R</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>I</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/contact.gif"></TD>
<TD><A href=3D"http://web.artprice.com/corporate/EN/Visite/pages/3818.htm=
"><IMG src=3D"http://web.artprice.com/img/HelpBlack.gif" border=3D"0"></A=
></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/today.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>C</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/L.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/D.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>E</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>C</B></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>O</B></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B>M</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/G.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/fs.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/contact.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/contact.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/H.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/bio.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/today.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><A href=3D"http://www.artprice.net"><IMG src=3D"http://web.artprice.c=
om/img/map.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/L.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/bio.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD align=3D"center"><A href=3D"http://www.art-online.com">&nbsp;</A></TD=
>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/fs.gif"></TD>
<TD><A href=3D"http://www.americanartists.com/"><IMG src=3D"http://web.ar=
tprice.com/img/bio.gif" border=3D"0"></A></TD>
<TD align=3D"center" bgcolor=3D"#000000"><B><FONT color=3D"#FF0000">A</FO=
NT></B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><A href=3D"http://web.artprice.com/corporate/EN/Visite/pages/arch02.h=
tm"><IMG src=3D"http://web.artprice.com/img/HelpBlack.gif" border=3D"0"><=
/A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD align=3D"center"><B><FONT color=3D"#FF0000">R</FONT></B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD align=3D"center"><B><FONT color=3D"#FF0000">T</FONT></B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD><A href=3D"http://web.artprice.com/corporate/EN/Visite/pages/3834.htm=
"><IMG src=3D"http://web.artprice.com/img/HelpBlack.gif" border=3D"0"></A=
></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/H.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/search.gif"></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/bio.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD align=3D"center" bgcolor=3D"#FF0000"><B><FONT color=3D"#000000">M</FO=
NT></B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/C.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/fs.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD align=3D"center"><B>A</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD align=3D"center"><B>R</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/F.gif"></TD>
<TD align=3D"center"><B>K</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD><A href=3D"http://www.artprice.de"><IMG src=3D"http://web.artprice.co=
m/img/Home.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Shop.gif"></TD>
<TD align=3D"center"><B>E</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/B.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ps.gif"></TD>
<TD align=3D"center"><B>T</B></TD>
<TD><A href=3D"http://web.artprice.com/corporate/EN/Visite/pages/jb02.htm=
"><IMG src=3D"http://web.artprice.com/img/HelpBlack.gif" border=3D"0"></A=
></TD>
</TR>
<TR>=20
<TD><IMG src=3D"http://web.artprice.com/img/contact.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/G.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/contact.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/map.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD align=3D"center"><B>C</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/D.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/sig.gif"></TD>
<TD><A href=3D"http://www.13thcenturyart.com/"><IMG src=3D"http://web.art=
price.com/img/HelpBlack.gif" border=3D"0"></A></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Home.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/E.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/affil.gif"></TD>
<TD align=3D"center"><B>O</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Account.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/D.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/J.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/ind.gif"></TD>
<TD align=3D"center"><B>M</B></TD>
<TD><IMG src=3D"http://web.artprice.com/img/Mediums/I.gif"></TD>
<TD><IMG src=3D"http://web.artprice.com/img/bio.gif"></TD>
</TR>
</TABLE>
<BR><BR><BR>
<TABLE border=3D"0" bgcolor=3D"#FFFFFF" align=3D"center"><TR>
<FORM method=3Dget action=3D"http://web.artprice.com/en/artistsearch.aspx=
"><TD>
<A href=3D"http://web.artprice.com">
<IMG src=3D"http://web.artprice.com/Img/B/artprice_140.gif" align=3D"absm=
iddle" border=3D"0" alt=3D"artprice"></A>=20
<INPUT type=3Dtext name=3Dsearcharti size=3D39>
<INPUT type=3Dsubmit value=3D"OK" style=3D"CURSOR: hand">
<INPUT type=3Dhidden name=3Dl value=3Den>
</TD>
</FORM>
</TR></TABLE>
<CENTER>
<FONT size=3D"1" face=3D"Arial">
THE WORLD LEADER IN ART MARKET INFORMATION - WELT-LEADER IN KUNSTMARKT-IN=
FOS
<BR>LEADER MONDIAL DE L'INFORMATION SUR LE MARCHE=20
DE L'ART</FONT>
</CENTER>
<BR><BR><BR>
<BR><BR><BR>
<BR><BR><BR>
<BR><BR><BR>
<BR><BR><BR>
<BR><BR><BR>
<BR><BR><BR>

<TABLE cellspacing=3D"3" background=3D"http://web.artprice.com/Img/B/pixB=
l.gif">
<TR>=20
<TD> <FONT face=3D"Arial" size=3D"1">
<b>To remove</b> your email: mip6@ietf.org<br>
please click below:<br><a=20
href=3D'http://list.artaddiction.com/?m=3Dmip6%40ietf.org'>
http://list.artaddiction.com/?m=3Dmip6@ietf.org
</a><br>
In case the above link does not work you can go to<br>
http://list.artaddiction.com/<br>

or reply to this message as it is.<br>
Please allow us 72 H for your e-mail to be removed.<br>Thank you for your=
 co-operation. </FONT></TD>
<TD><FONT face=3D"Arial" size=3D"1">
<b>Pour d=E9sinscrire</b> votre email : mip6@ietf.org<br>
cliquez ci-dessous :<br><a=20
href=3D'http://list.artaddiction.com/?m=3Dmip6%40ietf.org'>http://list.ar=
taddiction.com/?m=3Dmip6@ietf.org</a><br>
Si le lien ci-dessus ne fonctionne pas, vous pouvez aller sur :<br>
http://list.artaddiction.com/
<br>ou r=E9pondez svp =E0 ce message sans en modifier le contenu.<br>

Votre d=E9sinscription sera effective dans les 72 H.<br>Merci de votre co=
op=E9ration. </FONT></TD>
</TR><TR><TD colspan=3D"2"><FONT size=3D"1" face=3D"Arial">En conformit&e=
acute; avec la loi=20
78-17 du 6/1/78 (CNIL), vous pouvez demander &agrave; ne plus figurer sur=
 notre=20
fichier de routage.<BR>
<IMG src=3D"http://web.artprice.com/img/LogoArtp_90.jpg" border=3D"0" ali=
gn=3D"absmiddle">IX=20
:28<BR>
</FONT><FONT face=3D"Arial, Helvetica, sans-serif" size=3D"1">Artprice.co=
m - Domaine=20
de la Source BP 69 - F-69270 St Romain au Mont D'or - RCS : 411 309 198</=
FONT></TD>
</TR></TABLE></BODY></HTML>



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Mon Sep 29 14:46: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 OAA03232
	for <mip6-archive@odin.ietf.org>; Mon, 29 Sep 2003 14:46: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 1A4324-0003ue-SL
	for mip6-archive@odin.ietf.org; Mon, 29 Sep 2003 14:46:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8TIk4g1015034
	for mip6-archive@odin.ietf.org; Mon, 29 Sep 2003 14: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 1A4324-0003uO-Nh
	for mip6-web-archive@optimus.ietf.org; Mon, 29 Sep 2003 14: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 OAA03220
	for <mip6-web-archive@ietf.org>; Mon, 29 Sep 2003 14:45:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4322-00034F-00
	for mip6-web-archive@ietf.org; Mon, 29 Sep 2003 14:46:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4322-00034B-00
	for mip6-web-archive@ietf.org; Mon, 29 Sep 2003 14:46:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4322-0003tz-50; Mon, 29 Sep 2003 14:46:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A431p-0003tf-N7
	for mip6@optimus.ietf.org; Mon, 29 Sep 2003 14:45: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 OAA03211
	for <mip6@ietf.org>; Mon, 29 Sep 2003 14:45:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A431n-000343-00
	for mip6@ietf.org; Mon, 29 Sep 2003 14:45:47 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A431m-00033z-00
	for mip6@ietf.org; Mon, 29 Sep 2003 14:45:46 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h8TIjiuI007981
	for <mip6@ietf.org>; Mon, 29 Sep 2003 11:45:44 -0700 (PDT)
Received: from san.rr.com (ramin.qualcomm.com [129.46.73.69])
	by sabrina.qualcomm.com (8.12.9/8.12.5/1.0) with ESMTP id h8TIjgBB023531
	for <mip6@ietf.org>; Mon, 29 Sep 2003 11:45:43 -0700 (PDT)
Message-ID: <3F787DCF.2060801@san.rr.com>
Date: Mon, 29 Sep 2003 11:45:35 -0700
From: Ramin <rrezaiif@san.rr.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Mip6] MIPv6 BindingUpdate security
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


In the context of IKE for MIP BindingUpdates, the MIPv6 based spec. 
(ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-mobileip-ipv6-24.txt) 
says:
"... the ID_IPV6_ADDR Identity Payload MUST NOT be used in IKEv1 phase 1."

Two questions:
- What is the rationale for this exclusion?
-  Is ID_IPV6_ADDR_SUBNET is legit type as identity payload in IKEv1 
phase 1?  That is, can we set the identity associated with the home 
address to the IPv6 subnet associated with the home address?  If yes, 
then wouldn't this type of ID violate the requirement that no MN should 
be able to send BindingUpdates for another MN?


Thank you,

-Ramin


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Mon Sep 29 16:19: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 QAA09533
	for <mip6-archive@odin.ietf.org>; Mon, 29 Sep 2003 16:19: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 1A44U7-0000vC-5T
	for mip6-archive@odin.ietf.org; Mon, 29 Sep 2003 16:19:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8TKJ7kn003538
	for mip6-archive@odin.ietf.org; Mon, 29 Sep 2003 16:19:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A44U5-0000u9-K5
	for mip6-web-archive@optimus.ietf.org; Mon, 29 Sep 2003 16:19: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 QAA09424
	for <mip6-web-archive@ietf.org>; Mon, 29 Sep 2003 16:18:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A44U3-0004PO-00
	for mip6-web-archive@ietf.org; Mon, 29 Sep 2003 16:19:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A44U3-0004PL-00
	for mip6-web-archive@ietf.org; Mon, 29 Sep 2003 16:19:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A44U1-0000tL-FY; Mon, 29 Sep 2003 16: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 1A44Tm-0000t4-Pd
	for mip6@optimus.ietf.org; Mon, 29 Sep 2003 16:18: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 QAA09412
	for <mip6@ietf.org>; Mon, 29 Sep 2003 16:18:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A44Tl-0004Op-00
	for mip6@ietf.org; Mon, 29 Sep 2003 16:18:45 -0400
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 1A44Ti-0004OD-00
	for mip6@ietf.org; Mon, 29 Sep 2003 16:18:43 -0400
Received: from cisco.com (171.68.223.137)
  by sj-iport-2.cisco.com with ESMTP; 29 Sep 2003 13:17:29 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h8TKI7Yb003483;
	Mon, 29 Sep 2003 13:18:07 -0700 (PDT)
Received: from cisco.com (dhcp-128-107-163-92.cisco.com [128.107.163.92])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AMA39305;
	Mon, 29 Sep 2003 13:04:19 -0700 (PDT)
Message-ID: <3F78937E.5030405@cisco.com>
Date: Mon, 29 Sep 2003 13:18:06 -0700
From: Alpesh <alpesh@cisco.com>
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: Soliman Hesham <H.Soliman@flarion.com>
CC: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, mip6@ietf.org,
        Gopal Dommety
 <gdommety@cisco.com>
Subject: Re: [Mip6] Issue with mipv6 charter
References: <748C6D0A58C0F94CA63C198B6674697A01922D57@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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hesham and others:

I still have my reservations to this - mostly arising out of latency,
cross layer authentication (and dependency there on - not a
strong opponent).

On the other hand, I am pretty much hearing the vote to leave
this issue outside the current charter and see how the work in
other WGs can solve/mitigate the issues for MiPv6 authentication.

We can leave it outside the charter.

-a

Soliman Hesham wrote:

>Gopal, 
>
>Mohan's email below is a good summary. I don't 
>see any latency issues in either of the cases listed 
>below. At boot up it's a non issue and after that you
>use CT, which is needed anyway. 
>
>Also, whether authentication is carried on L2 or L3
>it _is_ authenticating for network access and 
>for charging. Some people chose to do it on L2 (actually
>pretty much everyone chose that) but that doesn't mean
>you need another L3 protocol on top. Of course, if we're 
>starting fresh we could start with a L3 authentication 
>mechanism that can bootstrap L2 security. This is where 
>I think PANA will be useful. 
>
>Hesham
>
> > -----Original Message-----
> > From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net]
> > Sent: Wednesday, September 24, 2003 3:20 PM
> > To: Soliman Hesham; 'Alpesh'; mip6@ietf.org; Gopal Dommety
> > Subject: Re: [Mip6] Issue with mipv6 charter
> > 
> > 
> >  Gopal,
> > 
> > Last time this issue was discussed, there were two cases.
> > 
> > 1) MN booting up in a visited network.
> > 2) MN moving in a visited network.
> > 
> > For (1) the latency is not a big issue. For (2), James 
> > replied earlier that
> > Seamoby is looking at
> > context transfer protocol which might be useful here.
> > 
> > So depending on how you classify your items below, we may 
> > not need anything
> > special.
> > 
> > -mohan
> > 
> > 
> > 
> > >
> > >    AP is a bridge and performs L2 access authentication.
> > > It need not have much of L3 knowledge.  It does not matter
> > > what you are using for authentication (NAI/MAC address). 
> > It is still L2
> > >   authentication, since it allows L2 access (There are 
> > systems such as
> > >   Public Access where L3 access has an additional authentication,
> > > That is when L3 access control happens).
> > >
> > > I am not saying that access control cannot be done by some 
> > other protocol
> > > or independent of Mobility.
> > > I think it is a good idea to keep them separate in some 
> > environments.
> > > However,  I think it adds to latency (that might not be 
> > acceptable) in
> > > other environments.
> > > For example, one needs to perform L2 authentication (can 
> > be optional),
> > then
> > > L3 access
> > > control (today some systems do this with http for lack of a better
> > protocol
> > > ), then you need to perform MIP.
> > > I feel that some environments benefit from MIP having 
> > access control (I am
> > > not saying that this is always desirable).
> > >
> > > Look at the following 3 environments:
> > >
> > > 1. Take CDMA for example, what about clients with mobile 
> > IP service?.
> > > They  benefits from Access control in MIPv4 (Mobile IP
> > > service deployed today).
> > >
> >  > 2. Take Public access WLANs, they use http for access control.
> > >
> > > 3. One way to get VoIP over WLAN today is to use MIP
> > > in WLAN envs  with no L2 authentication (only way to get 
> > decent roam times
> > > (with out CCKM or TKIP). I think MIP having access control
> > >
> > > I am fine with leaving this access control from MIP6 
> > charter for now (for
> > I
> > > think
> > > that when the time is right, some deployments will  mandate it. I
> > understand
> > >   why you feel that Access control at MIP level is not 
> > important in GPRS
> > > like environment.
> > >
> > >
> > > Thanks
> > > Gopal
> > >
> > >
> > >
> > > At 10:07 PM 9/23/2003 -0400, Soliman Hesham wrote:
> > >
> > > >  > I cam of the opinion that  802.1x authentication based
> > > >  > authentication is L2
> > > >  > authentication
> > > >  > It typically terminates on the AP and not on the access
> > > >  > router. Typically
> > > >  > AP is like a bridge. (PANA is another story).
> > > >
> > > >=> (I'll drift slightly off topic here but hopefully
> > > >it helps). You call it L2 authentication because it
> > > >is transported over L2. However, it is actually authenticating
> > > >a much higher layer identifier (NAI). So there is some layer
> > > >violation here but people don't seem to be keen on changing
> > > >that. That's why I thought PANA was a step in the right direction.
> > > >
> > > >  >
> > > >  > Anyway, what I am trying to ask is whether there needs to be
> > > >  > a L3 access
> > > >  > control point
> > > >  > (if I can use that term) to help in authentication, access
> > > >  > control, roaming
> > > >  > etc. I think this is useful in service
> > > >  > provider environments (CDMA 2000 for example).
> > > >
> > > >=> I agree with the need for an L3 access control point
> > > >and that it would be useful for several systems. However,
> > > >since such function is needed independently of mobility,
> > > >it should not be included inside a mobility protocol.
> > > >For instance, you refer to CDMA 2000 which offers a Simple
> > > >IP service where no mobility is needed in the terminal.
> > > >Also, other systems (e.g. GPRS) do not require MIP, yet
> > > >they still need this function. In fact, WLANs today are
> > > >deployed in a way that doesn't require the use of MIP,
> > > >yet they still need this function. So, including this function
> > > >in MIP does not seem useful.
> > > >
> > > >Hesham
> > > >
> > > >
> > > >  >
> > > >  >
> > > >  > Thanks
> > > >  > Gopal
> > > >  >
> > > >  >
> > > >  > At 10:02 PM 9/14/2003 -0400, Soliman Hesham wrote:
> > > >  >
> > > >  >
> > > >  > >  > I am assuming that Alpesh is trying to get some 
> > level of network
> > > >  > >  > authentication/authorization via MIP signalling.
> > > >  > >  >
> > > >  > >  > I am assuming you mean NAS (network Access 
> > server), in which
> > > >  > >  > case what is
> > > >  > >  > the protocol that you
> > > >  > >  > have in mind for L3 authentication/authorization?
> > > >  > (assuming that L2
> > > >  > >  > authentication/authorization may or may not exist).
> > > >  > >
> > > >  > >=> I'm not quite sure what you mean because people
> > > >  > >are running L3 authentication into L2 packets.
> > > >  > >So, naturally, the authentication is L2-dependent
> > > >  > >today (perhaps EAP is an exception). So to answer
> > > >  > >your question, you can use: EAP, PPP, AKA, ...etc depending
> > > >  > >on your link. If you don't want to depend on the
> > > >  > >link layer, use EAP over layer 4, i.e. use PANA
> > > >  > >when it's done.
> > > >  > >
> > > >  > >Hesham
> > > >  > >
> > > >  > >
> > > >  > >  >
> > > >  > >  > Thanks
> > > >  > >  > Gopal
> > > >  > >  >
> > > >  > >  >
> > > >  > >  > At 04:36 PM 9/10/2003 -0400, Soliman Hesham wrote:
> > > >  > >  >
> > > >  > >  >
> > > >  > >  > >  > Wondering if the charter should include an 
> > entity in the
> > > >  > >  > >  > visited domain/roaming network to aid in 
> > AAA/Diameter
> > > >  > >  > authentication,
> > > >  > >  > >  > access control etc?
> > > >  > >  > >
> > > >  > >  > >=> a NAS ? ;) The description of this entity doesn't
> > > >  > >  > >seem to be related to mobility in any way. I think
> > > >  > >  > >this work is generic for fixed and mobile nodes.
> > > >  > >  > >
> > > >  > >  > >    Currently, there is little, if any mechanism
> > > >  > >  > >  > to restrict a mobile node's activities in 
> > visited domain.
> > > >  > >  > >
> > > >  > >  > >=> Why do you say that? A NAS will do this job very well
> > > >  > >  > >provided that AAA mechanisms and roaming agreements
> > > >  > >  > >are in place.
> > > >  > >  > >
> > > >  > >  > >  > For practical deployment issues and network
> > > >  > management/control
> > > >  > >  > >  > purposes, I think such an entity is needed.
> > > >  > >  > >
> > > >  > >  > >=> Absolutely, but MIP6 has nothing to do with it.
> > > >  > >  > >
> > > >  > >  > >Hesham
> > > >  > >  > >
> > > >  > >  > >_______________________________________________
> > > >  > >  > >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
> > 
>
>  
>



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 30 04:29: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 EAA12178
	for <mip6-archive@odin.ietf.org>; Tue, 30 Sep 2003 04:29: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 1A4FsZ-0000i2-JU
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 04:29:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8U8T7Dj002720
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 04:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4FsY-0000hn-2g
	for mip6-web-archive@optimus.ietf.org; Tue, 30 Sep 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 EAA12170
	for <mip6-web-archive@ietf.org>; Tue, 30 Sep 2003 04:28:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4FsV-0003lr-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 04:29:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4FsU-0003lo-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 04:29:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4FsU-0000hO-3e; Tue, 30 Sep 2003 04:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4FrV-0000eR-Pg
	for mip6@optimus.ietf.org; Tue, 30 Sep 2003 04:28: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 EAA12148
	for <mip6@ietf.org>; Tue, 30 Sep 2003 04:27:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4FrS-0003lc-00
	for mip6@ietf.org; Tue, 30 Sep 2003 04:27:58 -0400
Received: from web20408.mail.yahoo.com ([66.163.169.96] helo=web20420.mail.yahoo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1A4FrS-0003lZ-00
	for mip6@ietf.org; Tue, 30 Sep 2003 04:27:58 -0400
Message-ID: <20030930082759.80583.qmail@web20420.mail.yahoo.com>
Received: from [129.119.251.190] by web20408.mail.yahoo.com via HTTP; Tue, 30 Sep 2003 01:27:59 PDT
Date: Tue, 30 Sep 2003 01:27:59 -0700 (PDT)
From: Jahanzeb Faizan <jahanzeb_smu@yahoo.com>
To: mip6@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Mip6] ICMP Mobile Prefix Solicitation Message
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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

Hi,

Is there any timeout defined in Mobile IPv6 for the
ICMP Mobile Prefix Solicitation Message in case Home
agent does not respond to the Mobile Node's
solicitaiton.

I was reading the draft but didn't find any timeout
value for this. Is there any one who knows about this
issue.

Thanks
Jahanzeb

=====
Jahanzeb Faizan

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 30 04:37: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 EAA12435
	for <mip6-archive@odin.ietf.org>; Tue, 30 Sep 2003 04:37: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 1A4G0H-00010f-An
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 04:37:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8U8b4ME003835
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 04:37:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4G0E-0000yj-KP
	for mip6-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 04:37: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 EAA12421
	for <mip6-web-archive@ietf.org>; Tue, 30 Sep 2003 04:36:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4G0B-0003ow-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 04:36:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4G0B-0003oq-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 04:36:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4G0D-0000xn-4d; Tue, 30 Sep 2003 04:37:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4Fzb-0000xG-Qg
	for mip6@optimus.ietf.org; Tue, 30 Sep 2003 04:36: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 EAA12394
	for <mip6@ietf.org>; Tue, 30 Sep 2003 04:36:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4FzY-0003oM-00
	for mip6@ietf.org; Tue, 30 Sep 2003 04:36:20 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4FzX-0003oA-00
	for mip6@ietf.org; Tue, 30 Sep 2003 04:36:19 -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 h8U8Zl905490
	for <mip6@ietf.org>; Tue, 30 Sep 2003 10:35:47 +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 h8U8ZkHN066510;
	Tue, 30 Sep 2003 10:35:47 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200309300835.h8U8ZkHN066510@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Ramin <rrezaiif@san.rr.com>
cc: mip6@ietf.org
Subject: Re: [Mip6] MIPv6 BindingUpdate security 
In-reply-to: Your message of Mon, 29 Sep 2003 11:45:35 PDT.
             <3F787DCF.2060801@san.rr.com> 
Date: Tue, 30 Sep 2003 10:35:46 +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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>

 In your previous mail you wrote:

   In the context of IKE for MIP BindingUpdates, the MIPv6 based spec. 
   (ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-mobileip-ipv6-24.txt) 
   says:
   "... the ID_IPV6_ADDR Identity Payload MUST NOT be used in IKEv1 phase 1."
   
   Two questions:
   - What is the rationale for this exclusion?

=> because either you put the care-of address and you have no security
property on it (i.e., for instance it doesn't match an alternate subject
name in the certificate and IKE drops the session) or you put the home
address but the peer address is the care-of address (i.e., IKE can see
the peer address (the address IKE runs over) and the ID payload doesn't
match and drops the session).

   -  Is ID_IPV6_ADDR_SUBNET is legit type as identity payload in IKEv1 
   phase 1?

=> it should *not* be.

   That is, can we set the identity associated with the home 
   address to the IPv6 subnet associated with the home address?

=> we can't.

   If yes, 
   then wouldn't this type of ID violate the requirement that no MN should 
   be able to send BindingUpdates for another MN?
   
=> first there is no such requirement, second the IKE is between the MN
and its HA (which is by definition a fixed router).

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 Sep 30 13:12: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 NAA02664
	for <mip6-archive@odin.ietf.org>; Tue, 30 Sep 2003 13:12: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 1A4O2d-0004ML-5h
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 13:12:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8UHC3bB016751
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 13:12:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4O2c-0004M6-WE
	for mip6-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 13:12: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 NAA02621
	for <mip6-web-archive@ietf.org>; Tue, 30 Sep 2003 13:11:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4O2b-0001rT-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 13:12:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4O2a-0001rO-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 13:12:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4O2b-0004KP-6l; Tue, 30 Sep 2003 13:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4O2F-0004JW-61
	for mip6@optimus.ietf.org; Tue, 30 Sep 2003 13:11: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 NAA02570
	for <mip6@ietf.org>; Tue, 30 Sep 2003 13:11:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4O2D-0001qa-00
	for mip6@ietf.org; Tue, 30 Sep 2003 13:11:37 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4O2C-0001pO-00
	for mip6@ietf.org; Tue, 30 Sep 2003 13:11:36 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h8UHB1t23518;
	Tue, 30 Sep 2003 10:11:01 -0700
X-mProtect: <200309301711> Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (205.226.30.3, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpd2EqO6D; Tue, 30 Sep 2003 10:10:59 PDT
Message-ID: <3F79B946.308@iprg.nokia.com>
Date: Tue, 30 Sep 2003 10:11:34 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
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: Jahanzeb Faizan <jahanzeb_smu@yahoo.com>
CC: mip6@ietf.org
Subject: Re: [Mip6] ICMP Mobile Prefix Solicitation Message
References: <20030930082759.80583.qmail@web20420.mail.yahoo.com>
In-Reply-To: <20030930082759.80583.qmail@web20420.mail.yahoo.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Jahanzeb Faizan wrote:

>Hi,
>
>Is there any timeout defined in Mobile IPv6 for the
>ICMP Mobile Prefix Solicitation Message in case Home
>agent does not respond to the Mobile Node's
>solicitaiton.
>
it is defined.

>   o  If the mobile node is sending a Mobile Prefix Solicitation, it
>      SHOULD use an initial retransmission interval of
>      INITIAL_SOLICIT_TIMER (see Section 12).
>
Vijay


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



From exim@www1.ietf.org  Tue Sep 30 14: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 OAA06178
	for <mip6-archive@odin.ietf.org>; Tue, 30 Sep 2003 14:31: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 1A4PH6-0000xn-79
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 14:31:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8UIV43v003702
	for mip6-archive@odin.ietf.org; Tue, 30 Sep 2003 14:31:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4PH6-0000xd-1D
	for mip6-web-archive@optimus.ietf.org; Tue, 30 Sep 2003 14:31: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 OAA06131
	for <mip6-web-archive@ietf.org>; Tue, 30 Sep 2003 14:30:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4PH3-0002mW-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 14:31:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4PH3-0002mT-00
	for mip6-web-archive@ietf.org; Tue, 30 Sep 2003 14:31:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4PH3-0000wt-K3; Tue, 30 Sep 2003 14:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4PGX-0000vl-7G
	for mip6@optimus.ietf.org; Tue, 30 Sep 2003 14:30: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 OAA06122
	for <mip6@ietf.org>; Tue, 30 Sep 2003 14:30:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4PGU-0002mE-00
	for mip6@ietf.org; Tue, 30 Sep 2003 14:30:26 -0400
Received: from ua78d26hel.dial.kolumbus.fi ([62.248.153.78] helo=localhost.localdomain)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4PGT-0002mB-00
	for mip6@ietf.org; Tue, 30 Sep 2003 14:30:26 -0400
Received: from kolumbus.fi (argon [127.0.0.1])
	by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h8UIQftd022692;
	Tue, 30 Sep 2003 21:26:41 +0300
Message-ID: <3F79CAE1.7090108@kolumbus.fi>
Date: Tue, 30 Sep 2003 21:26:41 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
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: Jahanzeb Faizan <jahanzeb_smu@yahoo.com>
CC: Vijay Devarapalli <vijayd@iprg.nokia.com>, mip6@ietf.org
Subject: Re: [Mip6] ICMP Mobile Prefix Solicitation Message
References: <20030930082759.80583.qmail@web20420.mail.yahoo.com> <3F79B946.308@iprg.nokia.com>
In-Reply-To: <3F79B946.308@iprg.nokia.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: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Id: <mip6.ietf.org>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vijay Devarapalli wrote:
> 
> Jahanzeb Faizan wrote:
> 
>> Hi,
>>
>> Is there any timeout defined in Mobile IPv6 for the
>> ICMP Mobile Prefix Solicitation Message in case Home
>> agent does not respond to the Mobile Node's
>> solicitaiton.
>>
> it is defined.

Yes, see Sections 11.8 and 12.

--Jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www.ietf.org/mailman/listinfo/mip6



