Re: [MEXT] LISP as a solution for some part of the DMM requirement
"Charles E. Perkins" <charles.perkins@earthlink.net> Tue, 02 August 2011 21:41 UTC
Return-Path: <charles.perkins@earthlink.net>
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 CB48F11E80C7 for <mext@ietfa.amsl.com>;
Tue, 2 Aug 2011 14:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
BAYES_00=-2.599]
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 N9bkA3+2VcDB for
<mext@ietfa.amsl.com>; Tue, 2 Aug 2011 14:41:34 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net
(elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com
(Postfix) with ESMTP id D470F11E808F for <mext@ietf.org>;
Tue, 2 Aug 2011 14:41:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net;
b=mji7vcEEgKEEyQ3995s3O9QQqio4E4+Qdyg0TfDO6O1h2Zlvt6fsfQit2sJGT6SZ;
h=Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [138.111.58.2] (helo=[172.17.96.56]) by
elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id
1QoMiZ-0003Jy-6v; Tue, 02 Aug 2011 17:41:39 -0400
Message-ID: <4E386F10.6080101@earthlink.net>
Date: Tue, 02 Aug 2011 14:41:36 -0700
From: "Charles E. Perkins" <charles.perkins@earthlink.net>
Organization: Wichorus Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
References: <CA5DD1FF.1C8BC%basavaraj.patil@nokia.com>
In-Reply-To: <CA5DD1FF.1C8BC%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad86e3fd2febb6acf1c9246c6b7a0f9f5b4d350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 138.111.58.2
Cc: dino@cisco.com, mext@ietf.org
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: Tue, 02 Aug 2011 21:41:35 -0000
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] 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