[Mip6] A question regarding draft-devarapalli-mip4-mobike-connectivity-00.txt

jouni.korhonen@teliasonera.com Wed, 31 August 2005 15:08 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAUCt-0000BI-IJ; Wed, 31 Aug 2005 11:08:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAUCr-0000BD-Jy for mip6@megatron.ietf.org; Wed, 31 Aug 2005 11:08:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25807 for <mip6@ietf.org>; Wed, 31 Aug 2005 11:08:50 -0400 (EDT)
From: jouni.korhonen@teliasonera.com
Received: from floor.dave.sonera.fi ([131.177.130.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAUEa-0008Mn-HF for mip6@ietf.org; Wed, 31 Aug 2005 11:10:43 -0400
Received: from floor.dave.sonera.fi (localhost [127.0.0.1]) by floor.dave.sonera.fi (Sendmail) with ESMTP id j7VF8Vb9001222 for <mip6@ietf.org>; Wed, 31 Aug 2005 18:08:31 +0300 (EEST)
Received: from FITMS201MB.tcad.telia.se (fitms201cb.tcad.telia.se [131.177.121.204]) by floor.dave.sonera.fi (Sendmail) with ESMTP id j7VF8TBm001206 for <mip6@ietf.org>; Wed, 31 Aug 2005 18:08:31 +0300 (EEST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6617.27
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Aug 2005 18:08:15 +0300
Message-ID: <07B14A720C46C344AC96AAA64F5D6A31014918AE@FITMS201MB.tcad.telia.se>
Thread-Topic: A question regarding draft-devarapalli-mip4-mobike-connectivity-00.txt
Thread-Index: AcWpanS/lBEfYJspT4qmhd0WCzPcSgEzVKmw
To: mip6@ietf.org, vijayd@iprg.nokia.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: [Mip6] A question regarding draft-devarapalli-mip4-mobike-connectivity-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

There was this MIP4 draft
(draft-devarapalli-mip4-mobike-connectivity-00)
proposing combining MOBIKE and MIP4 in a pretty nice way. Common
understanding is so far  seems to be that there shouldn't be anything
strictly MIP4 specific in this solution. Wouldn't it be worth thinking
of a MIP6 version of this proposed solution as well? Also, IMHO, it
could
be worth thinking how to make use of general IKEv2 capabilities that 
could come along with (possibly) tightly couple or colocated HA and
IKEv2
capable VPN GW.
 
>From a telco (3GPP-WLAN interworking.. and maybe 3GPP2-WLAN interworking
as well) perspective MOBIKE with MIP6 could actually provide one
solution
for migration in heterogeneous access network. I was thinking of the
case,
where the cellular using MIP6 would be considered as the trusted network
and the other accesses (e.g. WLANs) as untrusted. There MOBIKE could be
used to provide access also in untrusted IPv4 access networks.

Any comments?

Cheers,
	Jouni

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