Re: [netlmm] PMIP6-MIP6 Interactions - Take 2
Suresh Krishnan <suresh.krishnan@ericsson.com> Thu, 30 October 2008 14:02 UTC
Return-Path: <netlmm-bounces@ietf.org>
X-Original-To: netlmm-archive@optimus.ietf.org
Delivered-To: ietfarch-netlmm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E90428C137; Thu, 30 Oct 2008 07:02:09 -0700 (PDT)
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 154173A6A77 for <netlmm@core3.amsl.com>; Thu, 30 Oct 2008 07:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrHQxaqzmniq for <netlmm@core3.amsl.com>; Thu, 30 Oct 2008 07:02:05 -0700 (PDT)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 2006428C169 for <netlmm@ietf.org>; Thu, 30 Oct 2008 07:01:49 -0700 (PDT)
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id m9UE3OVZ003441; Thu, 30 Oct 2008 09:03:24 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Oct 2008 09:01:43 -0500
Received: from [142.133.10.113] ([142.133.10.113]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 30 Oct 2008 09:01:42 -0500
Message-ID: <4909BDCD.6050302@ericsson.com>
Date: Thu, 30 Oct 2008 09:59:41 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Christian Vogt <christian.vogt@nomadiclab.com>
References: <BE82361A0E26874DBC2ED1BA244866B929366661@NALASEXMB08.na.qualcomm.com><4D35478224365146822AE9E3AD4A266604C03826@exchtewks3.starentnetworks.com> <BE82361A0E26874DBC2ED1BA244866B929366745@NALASEXMB08.na.qualcomm.com> <5F09D220B62F79418461A978CA0921BD02F06861@pslexc01.psl.local> <24EA524C-A295-4C9A-A67E-627987BC13C2@nomadiclab.com>
In-Reply-To: <24EA524C-A295-4C9A-A67E-627987BC13C2@nomadiclab.com>
X-OriginalArrivalTime: 30 Oct 2008 14:01:43.0041 (UTC) FILETIME=[09C97F10:01C93A98]
Cc: NETLMM Mailing List <netlmm@ietf.org>, Mohana Jeyatharan <Mohana.Jeyatharan@sg.panasonic.com>
Subject: Re: [netlmm] PMIP6-MIP6 Interactions - Take 2
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: netlmm-bounces@ietf.org
Errors-To: netlmm-bounces@ietf.org
Hi Christian, I agree and this is described in section 5.3 of the draft George and I wrote http://tools.ietf.org/html/draft-tsirtsis-logically-separate-lmaha-00 Cheers Suresh Christian Vogt wrote: > On Oct 30, 2008, Mohana Jeyatharan wrote: > >> I agree with Rajeev. For multihoming case we need both BCEs(PMIP and >> MIP) to be present at LMA/HA and moreover both should be valid. > > > Mohana and Rajeev, > > a general comment: The simultaneous use of two mobility protocols > without coordination is bound to be problematic if you don't define a > clear precedence of one mobility protocol over the other. > > This directly applies to the specific case of MIP/P-MIP co-existence: > Both mobility protocols run simultaneously, yet there is no coordination > between the entities who initiate mobility signaling, i.e., mobile hosts > and MAGs. > > You don't need two BCEs to see why lack of precedences for the mobility > protocols could be a problem for multi-homing: As a simple example, > consider a host with 3G and WLAN interfaces, of which only the 3G > interface has a home address with mobility support. The host may create > a MIP binding to redirect traffic for its home address from 3G to WLAN. > In that case, the host certainly wouldn't want the network to remove > that binding due to subsequent movements of the 3G interface. > > Overall, I would recommend that, if two protocols for the same purpose > (such as mobility) operate simultaneously, it should be clear which > protocol takes precedence over the other. In the specific case of > MIP/P-MIP co-existence, that could mean that P-MIP pauses as long as a > MIP binding is active. Without such precedences, the two protocols will > end up fighting each other (namely, over BCEs), and you will likely end > up with undesired side effects. > > - Christian > > > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www.ietf.org/mailman/listinfo/netlmm _______________________________________________ netlmm mailing list netlmm@ietf.org https://www.ietf.org/mailman/listinfo/netlmm
- [netlmm] PMIP6-MIP6 Interactions - Take 2 Narayanan, Vidya
- [netlmm] Additional concern (Was Re: PMIP6-MIP6 I… Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Koodli, Rajeev
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Narayanan, Vidya
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Narayanan, Vidya
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Narayanan, Vidya
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Mohana Jeyatharan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Koodli, Rajeev
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Christian Vogt
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Christian Vogt
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Koodli, Rajeev
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Christian Vogt
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Mohana Jeyatharan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Soininen Jonne (NSN FI/Espoo)
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Christian Vogt
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Christian Vogt
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Hesham Soliman
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Hesham Soliman
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Premec, Domagoj
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Hesham Soliman
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Mohana Jeyatharan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Premec, Domagoj
- Re: [netlmm] Additional concern (Was Re: PMIP6-MI… Suresh Krishnan
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Basavaraj Patil
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Vijay Devarapalli
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Hesham Soliman
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Hesham Soliman
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Kilian Weniger
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 Giaretta, Gerardo
- Re: [netlmm] PMIP6-MIP6 Interactions - Take 2 BLUME, Oliver