From mobike-bounces@machshav.com Thu Nov 09 22:03:56 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiMgO-00037a-49
	for mobike-archive@lists.ietf.org; Thu, 09 Nov 2006 22:03:56 -0500
Received: from machshav.com ([147.28.0.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GiMgJ-0004wa-Oq
	for mobike-archive@lists.ietf.org; Thu, 09 Nov 2006 22:03:56 -0500
Received: by machshav.com (Postfix, from userid 512)
	id B1097FB2E0; Fri, 10 Nov 2006 03:03:35 +0000 (UTC)
Received: from machshav.com (localhost [127.0.0.1])
	by machshav.com (Postfix) with ESMTP id 998A1FB2D8;
	Fri, 10 Nov 2006 03:03:34 +0000 (UTC)
X-Original-To: mobike@machshav.com
Delivered-To: mobike@machshav.com
Received: by machshav.com (Postfix, from userid 512)
	id 7F45CFB2D8; Fri, 10 Nov 2006 03:03:33 +0000 (UTC)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170])
	by machshav.com (Postfix) with ESMTP id D9750FB2D1
	for <mobike@machshav.com>; Fri, 10 Nov 2006 03:03:32 +0000 (UTC)
Received: by ug-out-1314.google.com with SMTP id p31so404934ugc
	for <mobike@machshav.com>; Thu, 09 Nov 2006 19:03:31 -0800 (PST)
Received: by 10.78.204.7 with SMTP id b7mr2090076hug.1163127811021;
	Thu, 09 Nov 2006 19:03:31 -0800 (PST)
Received: by 10.78.106.16 with HTTP; Thu, 9 Nov 2006 19:03:30 -0800 (PST)
Message-ID: <e1a52ed30611091903g57c456dcya9445a9bc47deece@mail.gmail.com>
Date: Thu, 9 Nov 2006 22:03:31 -0500
From: "Shaili Desai" <shailients@gmail.com>
To: mobike@machshav.com
MIME-Version: 1.0
Subject: [Mobike] MOBIKE -IPv6
X-BeenThere: mobike@machshav.com
X-Mailman-Version: 2.1.9rc1
Precedence: list
List-Id: Mobile/Multihoming IKEv2 IETF list <mobike.machshav.com>
List-Unsubscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=unsubscribe>
List-Archive: <http://www.machshav.com/pipermail/mobike>
List-Post: <mailto:mobike@machshav.com>
List-Help: <mailto:mobike-request@machshav.com?subject=help>
List-Subscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1280550486=="
Sender: mobike-bounces@machshav.com
Errors-To: mobike-bounces@machshav.com
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

--===============1280550486==
Content-Type: multipart/alternative; 
	boundary="----=_Part_47061_24770985.1163127811001"

------=_Part_47061_24770985.1163127811001
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello all

I am new to this group.I am doing my project in Mobile VPN and was going
through the RFCs and drafts on MOBIKE but had a query,whether MOBIKE is
applicable to IPv6 as of now.

Thanks in advance.

-- 
Thanx
Shaili Desai
Master's Candidate
Telecommunications and Management
University of Maryland,College Park,USA

------=_Part_47061_24770985.1163127811001
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hello all</div>
<div>&nbsp;</div>
<div>I am new to this group.I am doing my project in Mobile VPN and was going through the RFCs and drafts on MOBIKE but had a query,whether MOBIKE is applicable to IPv6 as of now.</div>
<div>&nbsp;</div>
<div>Thanks in advance.<br clear="all"><br>-- <br>Thanx<br>Shaili Desai<br>Master's Candidate<br>Telecommunications and Management<br>University of Maryland,College Park,USA </div>

------=_Part_47061_24770985.1163127811001--

--===============1280550486==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mobike mailing list
Mobike@machshav.com
https://www.machshav.com/mailman/listinfo.cgi/mobike

--===============1280550486==--



From mobike-bounces@machshav.com Thu Nov 09 22:28:30 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GiN4A-0001P5-Ul
	for mobike-archive@lists.ietf.org; Thu, 09 Nov 2006 22:28:30 -0500
Received: from machshav.com ([147.28.0.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GiN46-0003Y7-Ic
	for mobike-archive@lists.ietf.org; Thu, 09 Nov 2006 22:28:30 -0500
Received: by machshav.com (Postfix, from userid 512)
	id 26F4BFB2E4; Fri, 10 Nov 2006 03:28:25 +0000 (UTC)
Received: from machshav.com (localhost [127.0.0.1])
	by machshav.com (Postfix) with ESMTP id 4598BFB2D8;
	Fri, 10 Nov 2006 03:28:23 +0000 (UTC)
X-Original-To: mobike@machshav.com
Delivered-To: mobike@machshav.com
Received: by machshav.com (Postfix, from userid 512)
	id 2BB30FB2D9; Fri, 10 Nov 2006 03:28:21 +0000 (UTC)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1])
	by machshav.com (Postfix) with ESMTP id 1A907FB2D2
	for <mobike@machshav.com>; Fri, 10 Nov 2006 03:28:19 +0000 (UTC)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1])
	by mail.kivinen.iki.fi (8.13.8/8.12.10) with ESMTP id kAA3SB39026075
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 10 Nov 2006 05:28:12 +0200 (EET)
Received: (from kivinen@localhost)
	by fireball.kivinen.iki.fi (8.13.8/8.12.11) id kAA3SBsV021771;
	Fri, 10 Nov 2006 05:28:11 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to
	kivinen@iki.fi using -f
MIME-Version: 1.0
Message-ID: <17747.61899.656127.167080@fireball.kivinen.iki.fi>
Date: Fri, 10 Nov 2006 05:28:11 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: "Shaili Desai" <shailients@gmail.com>
In-Reply-To: <e1a52ed30611091903g57c456dcya9445a9bc47deece@mail.gmail.com>
References: <e1a52ed30611091903g57c456dcya9445a9bc47deece@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 21.4.1
X-Edit-Time: 2 min
X-Total-Time: 2 min
Cc: mobike@machshav.com
Subject: [Mobike]  MOBIKE -IPv6
X-BeenThere: mobike@machshav.com
X-Mailman-Version: 2.1.9rc1
Precedence: list
List-Id: Mobile/Multihoming IKEv2 IETF list <mobike.machshav.com>
List-Unsubscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=unsubscribe>
List-Archive: <http://www.machshav.com/pipermail/mobike>
List-Post: <mailto:mobike@machshav.com>
List-Help: <mailto:mobike-request@machshav.com?subject=help>
List-Subscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mobike-bounces@machshav.com
Errors-To: mobike-bounces@machshav.com
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

Shaili Desai writes:
> I am new to this group.I am doing my project in Mobile VPN and was going
> through the RFCs and drafts on MOBIKE but had a query,whether MOBIKE is
> applicable to IPv6 as of now.

It should work with IPv4, IPv6 or mixed IPv4/IPv6 network, even when
moving from IPv4 address to IPv6 addres and back. 
-- 
kivinen@safenet-inc.com
_______________________________________________
Mobike mailing list
Mobike@machshav.com
https://www.machshav.com/mailman/listinfo.cgi/mobike



From mobike-bounces@machshav.com Mon Nov 13 00:46:37 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GjUeT-00079q-Sx
	for mobike-archive@lists.ietf.org; Mon, 13 Nov 2006 00:46:37 -0500
Received: from machshav.com ([147.28.0.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GjUeS-00012K-Dj
	for mobike-archive@lists.ietf.org; Mon, 13 Nov 2006 00:46:37 -0500
Received: by machshav.com (Postfix, from userid 512)
	id AAEE3FB2C2; Mon, 13 Nov 2006 05:46:31 +0000 (UTC)
Received: from machshav.com (localhost [127.0.0.1])
	by machshav.com (Postfix) with ESMTP id B949EFB2B0;
	Mon, 13 Nov 2006 05:46:28 +0000 (UTC)
X-Original-To: mobike@machshav.com
Delivered-To: mobike@machshav.com
Received: by machshav.com (Postfix, from userid 512)
	id AA755FB2B7; Mon, 13 Nov 2006 05:46:26 +0000 (UTC)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185])
	by machshav.com (Postfix) with ESMTP id C5BB9FB2AC
	for <mobike@machshav.com>; Mon, 13 Nov 2006 05:46:25 +0000 (UTC)
Received: by nf-out-0910.google.com with SMTP id x37so1802023nfc
	for <mobike@machshav.com>; Sun, 12 Nov 2006 21:46:22 -0800 (PST)
Received: by 10.78.171.13 with SMTP id t13mr5851453hue.1163396782035;
	Sun, 12 Nov 2006 21:46:22 -0800 (PST)
Received: by 10.78.106.16 with HTTP; Sun, 12 Nov 2006 21:46:21 -0800 (PST)
Message-ID: <e1a52ed30611122146w23c85187q85984d6c3a6a1a3c@mail.gmail.com>
Date: Mon, 13 Nov 2006 00:46:22 -0500
From: "Shaili Desai" <shailients@gmail.com>
To: mobike@machshav.com
MIME-Version: 1.0
Subject: [Mobike] MOBIKE -existing Mobile VPN
X-BeenThere: mobike@machshav.com
X-Mailman-Version: 2.1.9rc1
Precedence: list
List-Id: Mobile/Multihoming IKEv2 IETF list <mobike.machshav.com>
List-Unsubscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=unsubscribe>
List-Archive: <http://www.machshav.com/pipermail/mobike>
List-Post: <mailto:mobike@machshav.com>
List-Help: <mailto:mobike-request@machshav.com?subject=help>
List-Subscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1372484361=="
Sender: mobike-bounces@machshav.com
Errors-To: mobike-bounces@machshav.com
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8

--===============1372484361==
Content-Type: multipart/alternative; 
	boundary="----=_Part_77775_628606.1163396782020"

------=_Part_77775_628606.1163396782020
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello all

I was reading through RFC 4555 and could understand that MOBIKE adds
additional notification messages containing additional IP addresses and
sends these notifications when it detects mutlitple IP addresses.
I have couple of questions:

1)How does MOBIKE add more features than existing Mobile VPN solutions like
Cisco Mobile VPN and also Netmotion Wireless.Though Netmotion does it
through Virtual IP addresses.
I am not able to figure out,that Cisco Mobile VPN makes IPsec tunnel run
inside MIP tunnel and so to end user it  is still transparent and it
maintains the VPN connection with mobility.
2) So does MOBIKE , implement MIP tunnel inside the IPsec tunnel?As in the
RFC it says the outer header is the address which would change and not the
inner header of the tunnel. So, does MOBIKE apply the case 1, that is
section 2.1 of RFC 4093?
3) Also are there any figures and data available which says that MOBIKE does
improve the performance over existing Mobile VPN solutions.Were there any
performance tests which gave us the data, that clearly states the
requirement of MOBIKE over existing Mobile VPN solutions?
It would be great if someone can respond to my query. I am trying to work on
Mobile VPN for heterogenous networks, as my MS research study at University
of Maryland.

And if  someone can help me answer these questions, I would be more than
glad.

Thanks in advance and sorry if I am asking too naive questions.

-- 
Thanx
Shaili Desai
Master's Candidate
Telecommunications and Management
University of Maryland,College Park,USA

------=_Part_77775_628606.1163396782020
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hello all</div>
<div>&nbsp;</div>
<div>I was reading through RFC 4555 and could understand that MOBIKE adds additional notification messages containing additional IP addresses and sends these notifications when it detects mutlitple IP addresses.</div>
<div>I have couple of questions:</div>
<div>&nbsp;</div>
<div>1)How does MOBIKE add more features than existing Mobile VPN solutions like Cisco Mobile VPN and also Netmotion Wireless.Though Netmotion does it through Virtual IP addresses.</div>
<div>I am not able to figure out,that Cisco Mobile VPN makes IPsec tunnel run inside MIP tunnel and so to end user it&nbsp; is still transparent and it maintains the VPN connection with mobility.</div>
<div>2) So does MOBIKE , implement MIP tunnel inside the IPsec tunnel?As in the RFC it says the outer header is the address which would change and not the inner header of the tunnel. So, does MOBIKE apply the case 1, that is section 
2.1 of RFC 4093?</div>
<div>3) Also are there any figures and data available which says that MOBIKE does improve the performance over existing Mobile VPN solutions.Were there any performance tests which gave us the data, that clearly states the requirement of MOBIKE over existing Mobile VPN solutions?
</div>
<div>It would be great if someone can respond to my query. I am trying to work on Mobile VPN for heterogenous networks, as my MS research study at University of Maryland.</div>
<div>&nbsp;</div>
<div>And if&nbsp; someone can help me answer these questions, I would be more than glad.</div>
<div>&nbsp;</div>
<div>Thanks in advance and sorry if I am asking too naive questions.<br clear="all"><br>-- <br>Thanx<br>Shaili Desai<br>Master's Candidate<br>Telecommunications and Management<br>University of Maryland,College Park,USA </div>

------=_Part_77775_628606.1163396782020--

--===============1372484361==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mobike mailing list
Mobike@machshav.com
https://www.machshav.com/mailman/listinfo.cgi/mobike

--===============1372484361==--



From mobike-bounces@machshav.com Mon Nov 27 12:15:14 2006
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gok4Y-00033K-Us
	for mobike-archive@lists.ietf.org; Mon, 27 Nov 2006 12:15:14 -0500
Received: from machshav.com ([147.28.0.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gok4R-0002Yh-NU
	for mobike-archive@lists.ietf.org; Mon, 27 Nov 2006 12:15:14 -0500
Received: by machshav.com (Postfix, from userid 512)
	id CB2F8FB518; Mon, 27 Nov 2006 17:15:02 +0000 (UTC)
Received: from machshav.com (localhost [127.0.0.1])
	by machshav.com (Postfix) with ESMTP id 18946FB510;
	Mon, 27 Nov 2006 17:14:59 +0000 (UTC)
X-Original-To: mobike@machshav.com
Delivered-To: mobike@machshav.com
Received: by machshav.com (Postfix, from userid 512)
	id EC457FB513; Mon, 27 Nov 2006 17:14:57 +0000 (UTC)
Received: from michael.checkpoint.com (michael.checkpoint.com [194.29.32.68])
	by machshav.com (Postfix) with ESMTP id 3F813FB50E
	for <mobike@machshav.com>; Mon, 27 Nov 2006 17:14:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by michael.checkpoint.com (8.12.10+Sun/8.12.10) with SMTP id
	kARHEA6D027712; Mon, 27 Nov 2006 19:14:23 +0200 (IST)
Message-Id: <200611271714.kARHEA6D027712@michael.checkpoint.com>
Date: Mon, 27 Nov 2006 19:13:38 +0200
From: Yaron Sheffer <yaronf@checkpoint.com>
To: ipsec@ietf.org, mobike@machshav.com
MIME-Version: 1.0
X-Mailer: Sun Outlook Connector 7.1.228.0
X-imss-version: 2.043
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:6 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: Yoav Nir <ynir@checkpoint.com>
Subject: [Mobike] FW: I-D ACTION:draft-sheffer-ipsec-secure-beacon-01.txt
X-BeenThere: mobike@machshav.com
X-Mailman-Version: 2.1.9rc1
Precedence: list
List-Id: Mobile/Multihoming IKEv2 IETF list <mobike.machshav.com>
List-Unsubscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=unsubscribe>
List-Archive: <http://www.machshav.com/pipermail/mobike>
List-Post: <mailto:mobike@machshav.com>
List-Help: <mailto:mobike-request@machshav.com?subject=help>
List-Subscribe: <https://www.machshav.com/mailman/listinfo.cgi/mobike>,
	<mailto:mobike-request@machshav.com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mobike-bounces@machshav.com
Errors-To: mobike-bounces@machshav.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

Hi,

Sorry if you receive this mail twice.

Yoav and I would appreciate any comments you may have to this draft, either privately or to the IPsec mailing list.

Thanks,
	Yaron

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Monday, November 27, 2006 17:50
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-sheffer-ipsec-secure-beacon-01.txt 

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


	Title		: Secure Beacon: Securely Detecting a Trusted Network
	Author(s)	: Y. Nir, Y. Sheffer
	Filename	: draft-sheffer-ipsec-secure-beacon-01.txt
	Pages		: 12
	Date		: 2006-11-27
	
Remote access clients, in particular IPsec-based ones, are heavily
   deployed in enterprise environments.  In many enterprises the
   security policy allows remote-access clients to switch to unprotected
   operation when entering the trusted network.  This document specifies
   a method that lets a client detect this situation in a secure manner,
   with the help of a security gateway.  We propose a minor extension to
   IKEv2 to achieve this goal.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-sheffer-ipsec-secure-beacon-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-sheffer-ipsec-secure-beacon-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-sheffer-ipsec-secure-beacon-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


_______________________________________________
Mobike mailing list
Mobike@machshav.com
https://www.machshav.com/mailman/listinfo.cgi/mobike



