Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis-logically-separate-lmaha-00.txt
"George Tsirtsis" <tsirtsis@googlemail.com> Fri, 28 March 2008 21:47 UTC
Return-Path: <netlmm-bounces@ietf.org>
X-Original-To: ietfarch-netlmm-archive@core3.amsl.com
Delivered-To: ietfarch-netlmm-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8C8C3A6D44; Fri, 28 Mar 2008 14:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.896
X-Spam-Level:
X-Spam-Status: No, score=-100.896 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 LcnCWOT1Juxq; Fri, 28 Mar 2008 14:47:52 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB23E3A68F7; Fri, 28 Mar 2008 14:47:52 -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 0C3843A68F7 for <netlmm@core3.amsl.com>; Fri, 28 Mar 2008 14:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 ZAYuoMyGX6wd for <netlmm@core3.amsl.com>; Fri, 28 Mar 2008 14:47:51 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by core3.amsl.com (Postfix) with ESMTP id 02E8B3A6831 for <netlmm@ietf.org>; Fri, 28 Mar 2008 14:47:50 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 25so400858wfa.31 for <netlmm@ietf.org>; Fri, 28 Mar 2008 14:47:50 -0700 (PDT)
Received: by 10.141.129.14 with SMTP id g14mr1812932rvn.274.1206740870217; Fri, 28 Mar 2008 14:47:50 -0700 (PDT)
Received: by 10.140.135.15 with HTTP; Fri, 28 Mar 2008 14:47:50 -0700 (PDT)
Message-ID: <d3886a520803281447w6e7902d4x4030813e532117c3@mail.gmail.com>
Date: Fri, 28 Mar 2008 21:47:50 +0000
From: George Tsirtsis <tsirtsis@googlemail.com>
To: Genadi Velev <Genadi.Velev@eu.panasonic.com>
In-Reply-To: <1FEB9B9F2EC38343955D02B2AE86AACB7FDAA9@lan-ex-02.panasonic.de>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080325104501.8FC4428C302@core3.amsl.com> <d3886a520803250349j3380584cj8ff0d9aa8134068@mail.gmail.com> <1FEB9B9F2EC38343955D02B2AE86AACB7FDAA9@lan-ex-02.panasonic.de>
Cc: Netlmm <netlmm@ietf.org>
Subject: Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis-logically-separate-lmaha-00.txt
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: netlmm-bounces@ietf.org
Errors-To: netlmm-bounces@ietf.org
Hi Genadi, I am glad you now understand the issue with the multiple links. What you suggest, however, is entirely unrealistic. Below you say: "> Therefore, IMHO we shall differentiate between cases where overwriting > the MIPv6 BCE by PMIPv6 PBU is technically desired and another cases > (simultaneous multiple IP links are up) where maintenance of separate > PMIPv6/MIPv6 BCEs is desired." Could you please explain how would the HA/LMA know whether a given MN can maintain multiple links in parallel or not? And before we start talking about AAA servers, god-boxes, capabilities negotiation, telepathy, and other, at best non-universal and at worst non-existent, system level bells and whistles, please remember that here we are in the IETF talking about PMIP-MIP interactions. Let me also repeat my earlier comment about how unthinkable what you suggest would seem to a casual observer if we were talking about GTP-MIP interactions. I repeat, would you find acceptable that a GTP registration overwrites a MIP BCE? under any circumstances? Finally, I am really perplexed about this. What is so "hot" about overwriting BCEs? Why so much insistence in the face of overwhelming evidence that it is a bad idea and when there is a perfectly valid, bug-free alternative? Regards and have a nice weekend George On Fri, Mar 28, 2008 at 4:10 PM, Genadi Velev <Genadi.Velev@eu.panasonic.com> wrote: > Hi George, > > I appreciate your effort in capturing the problem of HA-LMA collocated > implementation. You indeed observe an aspect of the MIPv6-PMIPv6 > interactions problem that was not considered at the time when the > MIP-PMIP interactions I-D was written. You say in your document: > > "This logic [GV: PMIPv6 PBUs to overwrite state created by PMIPv6 BUs > and vice versa] breaks down if one considers MNs that are capable of > maintaining more than one link at the same time. Such capability is > common and can be utilised in many different way, while specifically > MIPv6 allows for the following behavior:" > > It is obvious that a collocated HA/LMA must have multiple simultaneously > active BCEs (MIPv6 and/or PMIPv6) whenever the MN maintains multiple IP > links. However, I don't see why generally "BCE Overwriting is Wrong". > There are at least 2 cases coming to my mind in which overwriting is OK: > case 1) if the MN has a single interface and moves from non-PMIPv6 > domain to PMIPv6 domain and case 2) if the MN performs a hard-handover > (vertical handover) between interfaces. For example, PMIPv6 > specification describes that the Handoff Indicator (HI) field in the PBU > can explicitly tell the HA/LMA that interface handover is performed (HI > value of 2). In that case the PMIPv6 PBUs can overwrite the MIPv6 BCE. > > Therefore, IMHO we shall differentiate between cases where overwriting > the MIPv6 BCE by PMIPv6 PBU is technically desired and another cases > (simultaneous multiple IP links are up) where maintenance of separate > PMIPv6/MIPv6 BCEs is desired. > > Genadi > > > > > -----Original Message----- > > From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On > > Behalf Of George Tsirtsis > > > Sent: Tuesday, March 25, 2008 11:49 AM > > To: Netlmm > > Cc: mext@ietf.org > > Subject: [MEXT] Fwd: > > > > I-DAction:draft-tsirtsis-logically-separate-lmaha-00.txt > > > > Hi all, > > > > Krishnan and I put together a draft describing what the expected > > behavior of a combined LMA/HA implementation should be. This should > > help the discussions around the so called scenario C of the PMIP-MIPv6 > > interactions draft (draft-giaretta-netlmm-mip-interactions). > > > > I hope you find the discussion in this draft useful. > > Please let us know if you have any comments/questions. > > > > Regards > > George > > > > > > ---------- Forwarded message ---------- > > From: <Internet-Drafts@ietf.org> > > Date: 2008/3/25 > > Subject: I-D Action:draft-tsirtsis-logically-separate-lmaha-00.txt > > To: i-d-announce@ietf.org > > > > > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. > > > > Title : Behavior of Collocated HA/LMA > > Author(s) : G. Tsirtsis, S. Krishnan > > Filename : > > draft-tsirtsis-logically-separate-lmaha-00.txt > > Pages : 9 > > Date : 2008-03-25 > > > > In discussions about PMIPv6-MIPv6 interactions in NETLMM WG, scenario > > C describes the case of collocation of LMA and HA function. In this > > case a PMIP network emulates the "home link" for MNs using MIPv6. > > This document argues that even when LMA and HA functions are > > Collocated they MUST be treated as logically separate entities. In > > particular this draft argues that PMIP BCEs MUST NOT overwrite MIPv6 > > BCEs and vice versa. > > > > A URL for this Internet-Draft is: > > > > http://www.ietf.org/internet-drafts/draft-tsirtsis-logically-s > > eparate-lmaha-00.txt > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > > > > _______________________________________________ > > I-D-Announce mailing list > > I-D-Announce@ietf.org > > https://www.ietf.org/mailman/listinfo/i-d-announce > > Internet-Draft directories: http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > > MEXT mailing list > > MEXT@ietf.org > > https://www.ietf.org/mailman/listinfo/mext > > > > > > > > > Panasonic R&D Center Germany GmbH > 63225 Langen, Hessen, Germany > Reg: AG Offenbach (Hessen) HRB 33974 > Managing Director: Thomas Micke > > > _______________________________________________ netlmm mailing list netlmm@ietf.org https://www.ietf.org/mailman/listinfo/netlmm
- [netlmm] Fwd: I-D Action:draft-tsirtsis-logically… George Tsirtsis
- [netlmm] One vs. Two BCEs per MN for PMIPv6-MIPv6… Kilian Weniger
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… Kilian Weniger
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… George Tsirtsis
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… George Tsirtsis
- Re: [netlmm] [MEXT] One vs. Two BCEs per MN for P… Hesham Soliman
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… Kilian Weniger
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… George Tsirtsis
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… George Tsirtsis
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… Genadi Velev
- Re: [netlmm] [MEXT] Fwd: I-DAction:draft-tsirtsis… George Tsirtsis
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Genadi Velev
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Hesham Soliman
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… George Tsirtsis
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Genadi Velev
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Genadi Velev
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Hesham Soliman
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Genadi Velev
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Hesham Soliman
- Re: [netlmm] [MEXT] Fwd:I-DAction:draft-tsirtsis-… Genadi Velev