Re: [MEXT] LISP as a solution for some part of the DMM requirement

Marco Liebsch <marco.liebsch@neclab.eu> Mon, 08 August 2011 12:10 UTC

Return-Path: <Marco.Liebsch@neclab.eu>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8DB21F8AF4 for <mext@ietfa.amsl.com>; Mon, 8 Aug 2011 05:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level:
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOO1ts7GTmgL for <mext@ietfa.amsl.com>; Mon, 8 Aug 2011 05:10:50 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 85EE621F8AF3 for <mext@ietf.org>; Mon, 8 Aug 2011 05:10:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3C9C6280002FE; Mon, 8 Aug 2011 14:09:46 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-7SvbkQbk1c; Mon, 8 Aug 2011 14:09:46 +0200 (CEST)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 214E4280001AA; Mon, 8 Aug 2011 14:09:26 +0200 (CEST)
Received: from [10.1.6.32] (10.1.6.32) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.270.1; Mon, 8 Aug 2011 14:09:15 +0200
Message-ID: <4E3FD1EA.6040306@neclab.eu>
Date: Mon, 8 Aug 2011 14:09:14 +0200
From: Marco Liebsch <marco.liebsch@neclab.eu>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Charles E. Perkins" <charles.perkins@earthlink.net>
References: <CA5DD1FF.1C8BC%basavaraj.patil@nokia.com> <4E386F10.6080101@earthlink.net>
In-Reply-To: <4E386F10.6080101@earthlink.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.6.32]
Cc: mext@ietf.org, dino@cisco.com, Basavaraj.Patil@nokia.com
Subject: Re: [MEXT] LISP as a solution for some part of the DMM requirement
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: Mon, 08 Aug 2011 12:10:51 -0000

I agree on that point and a good solution for DMM may require a look
beyond Mobile IP protocols and their extensions. As discussed
with some of you at IETF81, I think a solution which supports DMM
above anchor level should be at least on the table for discussion.
LISP is one candidate that could support IP address continuity
after anchor re-location (handover between two anchors). The issue
to solve is at an appropriate mapping base and to push an update
of the MN's locator state at the ITR(s) to allow session continuity.

Maybe beyond MEXT scope, but reasonale enough for
being included to the discussion.

marco


Am 02.08.2011 23:41, schrieb Charles E. Perkins:
>
> Hello folks,
>
> I agree that LISP work should not be done in the [mext]
> working group.
>
> However, if the LISP design shows how to make a good
> solution for distributed anchoring, it is pertinent to
> our work insofar as it provides a model for the [mext]
> solution.  In that case, if we are fortunate, it would
> be easier to devise an appropriate solution by using
> the LISP distributed anchoring as a guide.
>
> Please note that I do not yet claim that LISP does
> what is needed -- only that we ought to take a look.
>
> Regards,
> Charlie P.
>
>
> On 8/2/2011 2:15 PM, Basavaraj.Patil@nokia.com wrote:
>>
>> I agree with Romain's comment.
>> The scope of DMM within the context of the MEXT WG is to reuse Mobile 
>> IPv6
>> protocols, extensions and elements to address the concerns of the base
>> Mobile IP model.
>>
>> Mobility using LISP may be a good solution in itself. I have no idea or
>> opinion about such a solution at the present time.
>>
>> I believe that we can address the DMM requirements with a few extensions
>> to MIP6 signaling and guidelines for deployment. Expanding the scope of
>> DMM beyond the base MIP6 protocol would be taking us down a path with no
>> visible end.
>>
>> -Basavaraj
>>
>> On 8/2/11 4:09 PM, "ext Romain KUNTZ"<rkuntz@us.toyota-itc.com>  wrote:
>>
>>> Hello,
>>>
>>> I fail to see how LISP would fall in the MEXT charter item, which
>>> concentrates on MIPv6-based DMM solution ('Operational 
>>> considerations for
>>> distributed use of Mobile IPv6'). If LISP is foreseen as a potential
>>> solution for distributed mobility management, that should probably be
>>> discussed in the Network WG, where LISP and LISP MN are discussed.
>>>
>>> Regards,
>>> Romain
>>>
>>> On Aug 1, 2011, at 16:50, Seok-Joo Koh wrote:
>>>
>>>> Dear Charles,
>>>>
>>>> I think the LISP can also be considered as a promising candidate
>>>> in the design of DMM solutions. Several works are being progressed
>>>> to use or extend the LISP for mobility support, which inlcude LISP-MN
>>>> draft
>>>> and many research papers. Actually, I am also considering how to 
>>>> extend
>>>> the LISP scheme in the DMM perspective.
>>>>
>>>> LISP is a network-based ID-LOC separation scheme and thus it may give
>>>> some
>>>> advantages for effective mobility support. On the other hand, it is
>>>> noted that
>>>> the current version of LISP and LISP-MN may need to be more enhanced
>>>> in terms of scalability in the mobile environment. For example, one
>>>> concern of LISP
>>>> is that the LISP EIDs may not be aggregated anymore in the mobile
>>>> networks, since
>>>> each mobile node will have its own distinctive EIDs that do not 
>>>> conform
>>>> the concerned mobile domain.
>>>> This may decrease the scaling benefits of original LISP.
>>>> We may need to design a new enhanced EID structure to be used for
>>>> mobile environment.
>>>> Nontheless, it is worthwhile to consider LISP as a promisng candidate
>>>> in the disign of DMM, I think.
>>>>
>>>> By the way, as I already said in this IETF DMM ad hoc meeting, the
>>>> urgent action item of DMM is
>>>> to make one or more introductory I-Ds with WG consensus, which may
>>>> include
>>>> the problem statements and requirements for DMM, use cases/scenarios,
>>>> and comparison matrix, etc.
>>>>
>>>> Regards,
>>>>
>>>> *************************
>>>> Seok-Joo Koh
>>>> http://protocol.knu.ac.kr/
>>>> *************************
>>>>
>>>> ----- Original Message ----- From: "Charles E. Perkins"
>>>> <charles.perkins@earthlink.net>
>>>> To: "mext"<mext@ietf.org>
>>>> Cc:<dino@cisco.com>
>>>> Sent: Tuesday, August 02, 2011 3:28 AM
>>>> Subject: [MEXT] LISP as a solution for some part of the DMM 
>>>> requirement
>>>>
>>>>
>>>>>
>>>>> Hello folks,
>>>>>
>>>>> At IETF 81, LISP for mobile devices was presented.
>>>>> While I am not yet convinced about the specific
>>>>> solution presented, I started to look at LISP as
>>>>> a possible component of an overall DMM solution.
>>>>>
>>>>> LISP has a website:
>>>>> http://www.lisp4.net
>>>>>
>>>>> For people who are unfamiliar, this issue of IPJ
>>>>> has a tutorial article about LISP:
>>>>> http://www.lisp4.net/docs/ipj_11-1.pdf
>>>>>
>>>>> The LISP draft for mobile nodes is accessible here:
>>>>> http://datatracker.ietf.org/doc/draft-meyer-lisp-mn/
>>>>>
>>>>> Comments?  I think that LISP should be added to the
>>>>> comparison matrix in my draft with Dapeng Liu.
>>>>> Would that be helpful?
>>>>>
>>>>> Regards,
>>>>> Charlie P.
>>>>>
>>>>> _______________________________________________
>>>>> MEXT mailing list
>>>>> MEXT@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mext
>>>>
>>>> _______________________________________________
>>>> MEXT mailing list
>>>> MEXT@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mext
>>>
>>> _______________________________________________
>>> MEXT mailing list
>>> MEXT@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mext
>>
>> _______________________________________________
>> MEXT mailing list
>> MEXT@ietf.org
>> https://www.ietf.org/mailman/listinfo/mext
>>
>
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext