Re: [MEXT] LISP as a solution for some part of the DMM requirement
Julien Laganier <julien.ietf@gmail.com> Thu, 04 August 2011 16:03 UTC
Return-Path: <julien.ietf@gmail.com>
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 E3B3B21F8BAB for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASHcnGscgtuf for <mext@ietfa.amsl.com>; Thu, 4 Aug 2011 09:03:19 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7281221F856C for <mext@ietf.org>; Thu, 4 Aug 2011 09:03:19 -0700 (PDT)
Received: by wwe5 with SMTP id 5so1391913wwe.13 for <mext@ietf.org>; Thu, 04 Aug 2011 09:03:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Rpvd3i3f/sZtb4CpbxR52oQttTN9CyZcfzC0QJNTAB4=; b=ZFgXDj//ArQdPJW1Simo1Td+0nrbA28OjSSASBmXNtrPHQumv8sUhL0tSXjfRQ+VDb W+RJZBUYfY8sjpDOlNe3OM3kirPo6XrlIpnzuJagcxIupQs1lD8cMnCsBdz8U0TSzNtO 4WiMtMYykA7mRou26H7SgN3/toldPAAJnvfrg=
MIME-Version: 1.0
Received: by 10.227.177.133 with SMTP id bi5mr895502wbb.39.1312473813629; Thu, 04 Aug 2011 09:03:33 -0700 (PDT)
Received: by 10.227.152.13 with HTTP; Thu, 4 Aug 2011 09:03:33 -0700 (PDT)
In-Reply-To: <A276F714BCCD434DA6A3A7DB39CD72E8@knucpl>
References: <CA5DDBC3.1C939%basavaraj.patil@nokia.com> <A276F714BCCD434DA6A3A7DB39CD72E8@knucpl>
Date: Thu, 04 Aug 2011 09:03:33 -0700
Message-ID: <CAE_dhjssZHxvZwkqO1R9bYypX2n0Ui0nZL=qFTNg7XkhP=EyBQ@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Seok-Joo Koh <sjkoh@knu.ac.kr>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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: Thu, 04 Aug 2011 16:03:21 -0000
Seok-Joo, At this point it is not clear that new mechanisms are needed thus the question on where should solution work be undertaken seems a bit premature. For now I' d advise people interested in the DMM work to focus on what are their requirements and then see how the MIPv6 protocol suite can be applied to fulfill those. --julien On Tue, Aug 2, 2011 at 4:29 PM, Seok-Joo Koh <sjkoh@knu.ac.kr> wrote: > Hello there, > > To my understanding, this thread of discussion was intended to review LISP > so as to collect a lot of useful information in the perspective of DMM > requirements, > NOT to make specific schemes, such as MIP-based, PMIP-based, or LISP-based > DMM solutions. > > It seems that the issues on DMM requirements are under the scope of MEXT WG, > as described in the WG charter. > However, it is still unclear to me which WG is appropriate to develop > specific solutions for DMM: > MIP-based DMM -> MEXT WG ? > PMIP-based DMM -> NETEXT WG ? > LISP-based DMM -> LISP WG ? > or > all the issues shall fall into the MOPOPT RG ?? > > ************************* > Seok-Joo Koh > http://protocol.knu.ac.kr/ > ************************* > > ----- Original Message ----- From: <Basavaraj.Patil@nokia.com> > To: <charles.perkins@earthlink.net> > Cc: <dino@cisco.com>; <mext@ietf.org> > Sent: Wednesday, August 03, 2011 6:58 AM > Subject: Re: [MEXT] LISP as a solution for some part of the DMM requirement > > >> >> Hi Charlie, >> >> On 8/2/11 4:41 PM, "ext Charles E. Perkins" >> <charles.perkins@earthlink.net> wrote: >> >>> >>> 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. >> >> If the LISP design helps in alleviating the concerns that we have >> identified as some of the key issues in I-D >> draft-patil-mext-dmm-approaches-01.txt (Sec 3), then maybe yes. If we have >> to incorporate LISP based mobility as a solution for DMM, then we have an >> issue, because at the present time it can be perceived that the problems >> could be solved within the framework of MIP6 signaling and network >> elements. >> >> -Basavaraj >> >> >>> >>> 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 > > _______________________________________________ > MEXT mailing list > MEXT@ietf.org > https://www.ietf.org/mailman/listinfo/mext >
- [MEXT] LISP as a solution for some part of the DM… Charles E. Perkins
- Re: [MEXT] LISP as a solution for some part of th… Seok-Joo Koh
- Re: [MEXT] LISP as a solution for some part of th… Sri Gundavelli
- Re: [MEXT] LISP as a solution for some part of th… Sri Gundavelli
- Re: [MEXT] LISP as a solution for some part of th… Alexandru Petrescu
- Re: [MEXT] LISP as a solution for some part of th… Alexandru Petrescu
- Re: [MEXT] LISP as a solution for some part of th… Alexandru Petrescu
- Re: [MEXT] LISP as a solution for some part of th… Romain KUNTZ
- Re: [MEXT] LISP as a solution for some part of th… Basavaraj.Patil
- Re: [MEXT] LISP as a solution for some part of th… Charles E. Perkins
- Re: [MEXT] LISP as a solution for some part of th… Templin, Fred L
- Re: [MEXT] LISP as a solution for some part of th… Basavaraj.Patil
- Re: [MEXT] LISP as a solution for some part of th… Seok-Joo Koh
- Re: [MEXT] LISP as a solution for some part of th… Sri Gundavelli
- Re: [MEXT] LISP as a solution for some part of th… Julien Laganier
- Re: [MEXT] LISP as a solution for some part of th… Seok-Joo Koh
- Re: [MEXT] LISP as a solution for some part of th… Marco Liebsch
- Re: [MEXT] LISP as a solution for some part of th… Marco Liebsch
- [MEXT] Requirements of DMM h chan
- Re: [MEXT] Requirements of DMM Seok-Joo Koh
- Re: [MEXT] Requirements of DMM h chan
- Re: [MEXT] Requirements of DMM h chan
- Re: [MEXT] Requirements of DMM h chan