[Mip4] RE: Comments on VPN Problem Statement Draft

"Jayshree Bharatia" <jayshree@nortelnetworks.com> Thu, 31 July 2003 20:45 UTC

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 QAA13262 for <mip4-archive@odin.ietf.org>; Thu, 31 Jul 2003 16:45:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iKII-0004pJ-Go for mip4-archive@odin.ietf.org; Thu, 31 Jul 2003 16:45:02 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6VKj2RJ018547 for mip4-archive@odin.ietf.org; Thu, 31 Jul 2003 16:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iKII-0004p4-B8 for mip4-web-archive@optimus.ietf.org; Thu, 31 Jul 2003 16:45: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 QAA13250 for <mip4-web-archive@ietf.org>; Thu, 31 Jul 2003 16:44:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iKIG-0007SH-00 for mip4-web-archive@ietf.org; Thu, 31 Jul 2003 16:45:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19iKIF-0007SE-00 for mip4-web-archive@ietf.org; Thu, 31 Jul 2003 16:44:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iKIH-0004oq-9M; Thu, 31 Jul 2003 16:45:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iKI2-0004ob-0q for mip4@optimus.ietf.org; Thu, 31 Jul 2003 16:44: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 QAA13241 for <mip4@ietf.org>; Thu, 31 Jul 2003 16:44:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iKI0-0007S8-00 for mip4@ietf.org; Thu, 31 Jul 2003 16:44:44 -0400
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx with esmtp (Exim 4.12) id 19iKHz-0007Rz-00 for mip4@ietf.org; Thu, 31 Jul 2003 16:44:43 -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 h6VKi3a22487; Thu, 31 Jul 2003 15:44:03 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id <301T8GX9>; Thu, 31 Jul 2003 15:44:03 -0500
Message-ID: <870397D7C140C84DB081B88396458DAF746AA2@zrc2c000.us.nortel.com>
From: Jayshree Bharatia <jayshree@nortelnetworks.com>
To: "'Adrangi, Farid'" <farid.adrangi@intel.com>
Cc: "'mip4@ietf.org'" <mip4@ietf.org>
Date: Thu, 31 Jul 2003 15:43:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C357A4.77DC6E36"
Subject: [Mip4] RE: Comments on VPN Problem Statement Draft
Sender: mip4-admin@ietf.org
Errors-To: mip4-admin@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>

Hello Farid,
 
As per our earlier discussion during IETF-57, my understanding is that you
will include the scenario of co-existed FA with the VPN gateway in the VPN
Problem Statement draft.
 
I agree that this particular scenario has problems and it won't work if the
MN is behind an FA in the foreign subnet. But again, this is a problem
statement draft. Hence, I believe that this is the appropriate document for
mentioning this scenario.
 
Thanks,
Jayshree
 
-----Original Message-----
From: Adrangi, Farid [mailto:farid.adrangi@intel.com] 
Sent: Monday, April 07, 2003 2:58 PM
To: Bharatia, Jayshree [RICH1:2H13:EXCH]
Cc: 'mobile-ip@sunroof.eng.sun.com'
Subject: RE: Comments on VPN Problem Statement Draft



Hello Jayshree

This is a good point - I knew someone was to bring this up!  At the time of
writing these scenarios, we (the design team) actually discussed this and
concluded this scenario would fall into a solution space.  Maybe we did not
make the right decision and we should rethink this.  But, before we take
this discussion further please allow me to ask you a few questions about the
details of the scenario (VPN+FA) that you have in mind .  Are you thinking
to broadcast FA advertisements through the IPsec tunnel to the MN?  If so,
how will this work if MN is already behind an FA in the foreign subnet?  Or,
If you had something different in mind, perhaps you can elaborate on that.

Best regards,

Farid

 

 

-----Original Message-----
From: Jayshree Bharatia [mailto:jayshree@nortelnetworks.com]
<mailto:%5bmailto:jayshree@nortelnetworks.com%5d> ,
Sent: Friday, April 04, 2003 3:14 PM
To: 'farid.adrangi@intel.com'
Cc: 'mobile-ip@sunroof.eng.sun.com'
Subject: Comments on VPN Problem Statement Draft

 

Hello Farid, 

This draft (draft-ietf-mobileip-vpn-problem-statement-req-01) currently
misses one scenario were the FA is co-existed with the VPN Gateway. I would
think that there are no technical issues supporting this scenario. It will
be good if you can add this scenario in the draft (perhaps as section 2.6?)
for completeness.

Thanks, 
Jayshree