Re: [netlmm] The term LMA

Ashutosh Dutta <adutta@research.telcordia.com> Thu, 10 May 2007 20:40 UTC

Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmFR4-0004NV-99; Thu, 10 May 2007 16:40:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmFR3-0004NQ-Lc for netlmm@ietf.org; Thu, 10 May 2007 16:40:25 -0400
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmFR2-0005Ui-B9 for netlmm@ietf.org; Thu, 10 May 2007 16:40:25 -0400
Received: from [192.4.8.161] (adutta-laptop.research.telcordia.com [192.4.8.161]) by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id l4AKeNcC012400; Thu, 10 May 2007 16:40:23 -0400 (EDT)
Message-ID: <46438339.4010803@research.telcordia.com>
Date: Thu, 10 May 2007 16:40:25 -0400
From: Ashutosh Dutta <adutta@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nsn.com>
Subject: Re: [netlmm] The term LMA
References: <C268A350.36787%basavaraj.patil@nsn.com>
In-Reply-To: <C268A350.36787%basavaraj.patil@nsn.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: netlmm@ietf.org
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

I also agree with Raj here. HA and PMA are probably the way to go to 
avoid confusion for PMIP. Functionality of HA will depend upon what kind 
of mobility function (e.g., CMIP, PMIP) one is using. I think we still 
need to figure out the extent of overlapping between CMIPv6 HA and 
PMIPV6 HA, or whether CMIPv6 HA is a subset of PMIPv6 HA or vice-versa.


Thanks
Ashutosh

Basavaraj Patil wrote:
> Hi Gerardo,
> 
> 
> On 5/10/07 10:11 AM, "ext Gerardo Giaretta" <gerardo.giaretta@gmail.com>
> wrote:
> 
>> Hi Raj,
>>
>> I disagree with this, mainly for two reasons.
>>
>> Based on the charter NETLMM is developing PMIP as a localized mobility
>> management protocol. Some other SDOs may use it as global mobility
>> management protocol, but we need to keep that in mind: therefore, I
>> would like to have this reflected in the anchor name.
> 
> Do you agree that the protocol as specified today can be used for global
> mobility as well?
> Why do we portray the work done as specifically being applicable only to
> local mobility? The protocol can be used to solve local mobility or global
> mobility and its better to acknowledge that than sticking our heads in the
> sand. 
> 
>> Secondly, I think a different name for the PMIP anchor (i.e. LMA) is
>> very useful when you start working on MIP6/PMIP6 mixed scenario where
>> LMA may or may not be co-located with the MIP6 HA.
> 
> Irrespective of co-location (which IMO is not an issue really since this is
> more of an implementation and deployment topic), I think what we have
> defined today as the LMA is an HA. So why not just refer to it as an HA. Do
> you believe the LMA is a specialized element being defined in Netlmm and the
> PMIP6 WG? 
> 
> I think it makes sense to get the scope and terminology right at this stage
> of the work in Netlmm.
> 
> -Raj
> 
>> Gerardo
>>
>> On 5/10/07, Basavaraj Patil <basavaraj.patil@nsn.com> wrote:
>>> Hello,
>>>
>>> The terminology that we have in the current PMIP6 I-D
>>> <draft-ietf-netlmm-proxymip6-00.txt> w.r.t LMA is not entirely
>>> accurate.
>>>
>>> LMA definition as per the I-D is:
>>> "
>>>       Local Mobility Anchor is the home agent for the mobile node in the
>>>       Proxy Mobile IPv6 domain.  It is the topological anchor point for
>>>       the mobile node's home prefix and is the entity that manages the
>>>       mobile node's reachability state.  It is important to understand
>>>       that the LMA has the functional capabilities of a home agent as
>>>       defined in Mobile IPv6 base specification [RFC-3775] and with the
>>>       additional required capabilities for supporting Proxy Mobile IPv6
>>>       as defined in this specification.
>>> "
>>>
>>> The protocol solution being discussed focuses on localized
>>> mobility. However this protocol also works equally well for the global
>>> mobility of the host. The term local mobility agent gives the
>>> perception that this entity is responsible only for local mobility and
>>> global mobility (if applicable) would be managed by a MIP6 HA. While
>>> this deployment model is feasible, it is equally feasible to manage
>>> global mobility of the host with the same protocol (as long as certain
>>> assumptions about Proxy MIP capability in the access router that a
>>> host attaches to exist).
>>>
>>> IMO, we should change the LMA term to what it really is, an HA. If the
>>> HA is used in the context of localized mobility, it MAY be refered to
>>> as an LMA. But if it is providing global mobility, then it is just an
>>> HA. And since there really is no difference in the functionality of
>>> these entities, it would be better to just refer to it as HA.
>>> A PMIP6 HA = MIP6 HA + DSMIP6 capabilities + PMIP6 enhancements
>>>
>>> -Raj
>>>
>>>
>>> _______________________________________________
>>> netlmm mailing list
>>> netlmm@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/netlmm
>>>
> 
> 
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm

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