[Mip6] Using IPsec between mobile and correspondent IPv6 node
Warodom Werapun <ple@graduate.kmitl.ac.th> Tue, 09 August 2005 07:11 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2OGQ-0004iZ-1j; Tue, 09 Aug 2005 03:11:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2OGO-0004i1-1a for mip6@megatron.ietf.org; Tue, 09 Aug 2005 03:11:04 -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 DAA16293 for <mip6@ietf.org>; Tue, 9 Aug 2005 03:10:59 -0400 (EDT)
Received: from bundit.graduate.kmitl.ac.th ([161.246.39.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2Oo5-0004tZ-Np for mip6@ietf.org; Tue, 09 Aug 2005 03:46:01 -0400
Received: from graduate.kmitl.ac.th ([161.246.39.95]) by bundit.graduate.kmitl.ac.th (8.12.8/8.12.5) with ESMTP id j7978uwD009241; Tue, 9 Aug 2005 14:09:01 +0700
Message-ID: <42F856C3.7030504@graduate.kmitl.ac.th>
Date: Tue, 09 Aug 2005 14:09:55 +0700
From: Warodom Werapun <ple@graduate.kmitl.ac.th>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language: th, en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
X-Enigmail-Version: 0.75.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="TIS-620"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Graduate-MailScanner-Information: Please contact the ISP for more information
X-Graduate-MailScanner: Found to be clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: Francis.Dupont@enst-bretagne.fr
Subject: [Mip6] Using IPsec between mobile and correspondent IPv6 node
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
I have read draft-dupont-mipv6-cn-ipsec-00.txt, they sugguests to
use IPsec to protect Return routability (RR) method before process
binding update. It solves man in the middle attack problems in HA-CN
and MN-CN path,right? So, The Kbm using in BU and BA are safed now.
But Instead of using IPSec to protect RR method, why we don't use
IPSec to protect BU? Does it make handoff process faster? :-)
Thank you for your reply,
--
Warodom Werapun
PGP: http://plex.coe.psu.ac.th/myPGP.txt
_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6
- [Mip6] Using IPsec between mobile and corresponde… Warodom Werapun
- [Mip6] Re: Using IPsec between mobile and corresp… Francis Dupont