IETF Logo Mail Archive

Re: [MEXT] IETF-80 meeting minutes posted / clarifications on draft-liu-mext-distributed-mobile-ip

Romain KUNTZ <rkuntz@us.toyota-itc.com> Wed, 20 April 2011 20:31 UTC

Return-Path: <rkuntz@us.toyota-itc.com>
X-Original-To: mext@ietfc.amsl.com
Delivered-To: mext@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id BFF84E0753 for <mext@ietfc.amsl.com>; Wed, 20 Apr 2011 13:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level:
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_BACKHAIR_44=1, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hm19yGlHLzNv for <mext@ietfc.amsl.com>; Wed, 20 Apr 2011 13:31:35 -0700 (PDT)
Received: from na3sys009aog103.obsmtp.com (na3sys009aog103.obsmtp.com [74.125.149.71]) by ietfc.amsl.com (Postfix) with SMTP id 55D00E0669 for <mext@ietf.org>; Wed, 20 Apr 2011 13:31:34 -0700 (PDT)
Received: from mail-pv0-f170.google.com ([74.125.83.170]) (using TLSv1) by na3sys009aob103.postini.com ([74.125.148.12]) with SMTP ID DSNKTa9CpsekAeqg2FeDLLaGpe15bEToNmsx@postini.com; Wed, 20 Apr 2011 13:31:35 PDT
Received: by mail-pv0-f170.google.com with SMTP id 16so826285pvg.15 for <mext@ietf.org>; Wed, 20 Apr 2011 13:31:34 -0700 (PDT)
Received: by 10.68.5.168 with SMTP id t8mr979322pbt.342.1303331494280; Wed, 20 Apr 2011 13:31:34 -0700 (PDT)
Received: from orii-lt2.paloalto.toyota-itc.com ([206.132.173.18]) by mx.google.com with ESMTPS id m10sm824568pbn.97.2011.04.20.13.31.29 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2011 13:31:30 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Romain KUNTZ <rkuntz@us.toyota-itc.com>
In-Reply-To: <843DA8228A1BA74CA31FB4E111A5C46201A55BA2@ftrdmel0.rd.francetelecom.fr>
Date: Wed, 20 Apr 2011 13:31:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <15658A73-D07B-4011-809F-4375F213EA9A@us.toyota-itc.com>
References: <BANLkTimN4Czxq-g8ZGo+zUysNFxrBDGi6g@mail.gmail.com> <843DA8228A1BA74CA31FB4E111A5C46201A55BA2@ftrdmel0.rd.francetelecom.fr>
To: "pierrick.seite@orange-ftgroup.com> <pierrick.seite@orange-ftgroup.com" <pierrick.seite@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1084)
Cc: mext@ietf.org
Subject: Re: [MEXT] IETF-80 meeting minutes posted / clarifications on draft-liu-mext-distributed-mobile-ip
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Apr 2011 20:31:37 -0000

Hello Pierrick,

Allow to jump into the discussion, I have a couple of questions regarding this draft.

On Apr 20, 2011, at 1:14, <pierrick.seite@orange-ftgroup.com> <pierrick.seite@orange-ftgroup.com> wrote:
> IMHO, the "multiple home addresses" feature was misunderstood during the meeting. It is not require that a MN attached to a HA uses severals HoAs. Actually, the MN can use several home addresses only when attached to several HAs. Considering the use-case above, it means:
> - Flow#1 served by HA1/AR1 and uses HoA1
> - flow#2 served by HA2/AR2 and uses HoA2

Still, how does a CN that wishes to contact a MN selects the correct Home Address? The MN would need to be always anchored to one HA in order to keep at least one stable HoA over time. 

Also, how would you prevent a malicious node to register 2 symmetric bindings at 2 different home agents (say HoA1<->HoA2 at HA1, and HoA2<->HoA1 at HA2), which could potentially lead to a routing loop between both HAs? 

Regards,
Romain

v2.8.7 | Report a Bug | By Email