[Mip6] Re: Using IPsec between mobile and correspondent IPv6 node

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Tue, 09 August 2005 11:18 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2S8J-000565-MQ; Tue, 09 Aug 2005 07:18:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2S8I-000560-Di for mip6@megatron.ietf.org; Tue, 09 Aug 2005 07:18:58 -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 HAA29010 for <mip6@ietf.org>; Tue, 9 Aug 2005 07:18:55 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2SgA-0003jw-Sz for mip6@ietf.org; Tue, 09 Aug 2005 07:54:00 -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 j79BIXn23844; Tue, 9 Aug 2005 13:18:33 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id j79BIUes041291; Tue, 9 Aug 2005 13:18:34 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200508091118.j79BIUes041291@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Warodom Werapun <ple@graduate.kmitl.ac.th>
In-reply-to: Your message of Tue, 09 Aug 2005 14:09:55 +0700. <42F856C3.7030504@graduate.kmitl.ac.th>
Date: Tue, 09 Aug 2005 13:18:30 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org
Subject: [Mip6] Re: 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

 In your previous mail you wrote:

       I have read draft-dupont-mipv6-cn-ipsec-00.txt, they sugguests to 

=> it is draft-ietf-mip6-cn-ipsec-01.txt now.

   use IPsec to protect Return routability (RR) method before process 

=> no, IPsec is used to verify HoA option and to protect RO signaling
in this draft.

   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.

=> I believe you make some confusion between RFC 377[56] which uses
IPsec to protect some RR messages and the draft which protects directly
the BU/BA,

       But Instead of using IPSec to protect RR method, why we don't use 
   IPSec to protect BU?

=> this is the idea of the draft.

    Does it make handoff process faster? :-)

=> of course it is faster because there is no RR phase (.5 RTT in place
of >1.5 RTT).
   
Can you read the last version and if you find it is not clear enough
propose improvements? I know the wording is not so good and as it will
be last called soon...

Thanks

Francis.Dupont@enst-bretagne.fr

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