Re: [MEXT] IETF-80 meeting minutes posted / clarifications on draft-liu-mext-distributed-mobile-ip
<pierrick.seite@orange-ftgroup.com> Thu, 21 April 2011 10:51 UTC
Return-Path: <pierrick.seite@orange-ftgroup.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 E5D41E06E1 for <mext@ietfc.amsl.com>;
Thu, 21 Apr 2011 03:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Level:
X-Spam-Status: No, score=-2.748 tagged_above=-999 required=5 tests=[AWL=-0.500,
BAYES_00=-2.599, HELO_EQ_FR=0.35, J_BACKHAIR_44=1, RCVD_IN_DNSWL_LOW=-1]
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 ylT7Qc3zgJdX for
<mext@ietfc.amsl.com>; Thu, 21 Apr 2011 03:51:54 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com
[195.101.245.16]) by ietfc.amsl.com (Postfix) with ESMTP id 33E05E06CD for
<mext@ietf.org>; Thu, 21 Apr 2011 03:51:54 -0700 (PDT)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain
[127.0.0.1]) by localhost (Postfix) with SMTP id AD627858002;
Thu, 21 Apr 2011 12:58:19 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by
p-mail2.rd.francetelecom.com (Postfix) with ESMTP id A6070858001;
Thu, 21 Apr 2011 12:58:19 +0200 (CEST)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by
ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);
Thu, 21 Apr 2011 12:51:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Apr 2011 12:51:51 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C46201A55F7D@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <15658A73-D07B-4011-809F-4375F213EA9A@us.toyota-itc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] IETF-80 meeting minutes posted / clarifications on
draft-liu-mext-distributed-mobile-ip
Thread-Index: Acv/mfkp9vsSR9QdQS6W77oLMHGwWAAYRU9A
References: <BANLkTimN4Czxq-g8ZGo+zUysNFxrBDGi6g@mail.gmail.com>
<843DA8228A1BA74CA31FB4E111A5C46201A55BA2@ftrdmel0.rd.francetelecom.fr>
<15658A73-D07B-4011-809F-4375F213EA9A@us.toyota-itc.com>
From: <pierrick.seite@orange-ftgroup.com>
To: <rkuntz@us.toyota-itc.com>
X-OriginalArrivalTime: 21 Apr 2011 10:51:53.0062 (UTC)
FILETIME=[1FD8E060:01CC0012]
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: Thu, 21 Apr 2011 10:51:55 -0000
Hi Romain, Thanks for the feedback. Please see inline. Regards, Pierrick > -----Message d'origine----- > De : Romain KUNTZ [mailto:rkuntz@us.toyota-itc.com] > Envoyé : mercredi 20 avril 2011 22:31 > À : SEITE Pierrick RD-RESA-REN > Cc : mext@ietf.org > Objet : Re: [MEXT] IETF-80 meeting minutes posted / clarifications on > draft-liu-mext-distributed-mobile-ip > > 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. > Right, reachability is an issue. Section 4.2 of http://tools.ietf.org/html/draft-yokota-dmm-scenario gives clues for solution. Relying temporally on a centralized mobility anchor point could be also a solution. Anyway, we have to think more about that. > 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? > Good point. But, IMHO, this issue is not specific to a distributed mobility architecture. For instance, http://tools.ietf.org/id/draft-ng-intarea-tunnel-loop-00.txt discusses the issue and proposes solution. > Regards, > Romain
- [MEXT] IETF-80 meeting minutes posted Julien Laganier
- Re: [MEXT] IETF-80 meeting minutes posted / clari… pierrick.seite
- Re: [MEXT] IETF-80 meeting minutes posted / clari… Romain KUNTZ
- Re: [MEXT] IETF-80 meeting minutes posted / clari… Jan Zorz @ go6.si
- Re: [MEXT] IETF-80 meeting minutes posted / clari… pierrick.seite
- Re: [MEXT] IETF-80 meeting minutes posted / clari… Romain KUNTZ
- Re: [MEXT] IETF-80 meeting minutes posted / clari… Behcet Sarikaya