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

Sri Gundavelli <sgundave@cisco.com> Tue, 02 August 2011 03:13 UTC

Return-Path: <sgundave@cisco.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 88C2821F8C79 for <mext@ietfa.amsl.com>; Mon, 1 Aug 2011 20:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.164
X-Spam-Level:
X-Spam-Status: No, score=-3.164 tagged_above=-999 required=5 tests=[AWL=-0.565, 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 gEO3hhUMVE0X for <mext@ietfa.amsl.com>; Mon, 1 Aug 2011 20:13:06 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1BF21F8B3C for <mext@ietf.org>; Mon, 1 Aug 2011 20:13:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=sgundave@cisco.com; l=3860; q=dns/txt; s=iport; t=1312254793; x=1313464393; h=date:subject:from:to:cc:message-id:in-reply-to: mime-version:content-transfer-encoding; bh=gifAlodua7bTjGngFHmjItd8MVPEcD61uZxhiePKpCY=; b=L0/YYfbyxYliwPyJz9/ozMdEYCXRDX0927B5BoV9DbYbFSpeCbo/kqBR MkWHue8VQAZF29E0+J3mhMizt9g8VZB2GfG5M/hJJcriDyvsdbewMYYqh ZSVFuw2+cH4c0OQOa1/WzCF4npgfQfcZgPhUpzS9krEp1x5+Aj5hkOtBK c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAHVqN06rRDoI/2dsb2JhbABCDqdSd4FAAQEBAQIBEgEnAgE8BQ0BCIEdAQEEAQ0FGweHSqFuAZ8WhkIEh1qLIYUQix1X
X-IronPort-AV: E=Sophos;i="4.67,304,1309737600"; d="scan'208";a="8648204"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by rcdn-iport-3.cisco.com with ESMTP; 02 Aug 2011 03:13:09 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p723D9GH032752; Tue, 2 Aug 2011 03:13:09 GMT
Received: from xmb-sjc-214.amer.cisco.com ([171.70.151.145]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 1 Aug 2011 20:13:09 -0700
Received: from 10.32.246.212 ([10.32.246.212]) by xmb-sjc-214.amer.cisco.com ([171.70.151.145]) with Microsoft Exchange Server HTTP-DAV ; Tue, 2 Aug 2011 03:13:08 +0000
User-Agent: Microsoft-Entourage/12.30.0.110427
Date: Mon, 01 Aug 2011 20:13:04 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: Seok-Joo Koh <sjkoh@knu.ac.kr>, "Charles E. Perkins" <charles.perkins@earthlink.net>, mext <mext@ietf.org>
Message-ID: <CA5CB950.23275%sgundave@cisco.com>
Thread-Topic: [MEXT] LISP as a solution for some part of the DMM requirement
Thread-Index: AcxQwhfLnuKfCPPY3k6t02z05yDwwQ==
In-Reply-To: <77C2DE20B9834174B0856B541F903036@knucpl>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 02 Aug 2011 03:13:09.0216 (UTC) FILETIME=[1AE78600:01CC50C2]
Cc: dino@cisco.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: Tue, 02 Aug 2011 03:13:11 -0000

Hi Charlie,

I agree, we have to look at other approaches and bring any value added
features to MIPv6/PMIPv6 protocols that its missing today. But, I've to say,
I'm still trying to understand the DMM problem statement and what DMM should
translate to:

- Is it about optimized routing path ? This is very subjective and the
requirement may vary based on the use-case. Very much depends on the
placement of the anchor point. No solution on the table can ever solve this,
unless we assume the target site where the CN is located, or the ISP above
is providing some new location functions. This new location function, sure,
can be a proxy home agent at the global internet level too, for the argument
sake, providing direct path to the access network where the MN is currently
attached. We also have talked some time back on the Global HAHA, as an
approach of session re-anchoring.

- Is it about moving from a centralized one box model to more distributed
zillion box model ? This sounds very promising on the paper. But, as we
discussed during the DMM BOF, rolling out a zillion pizza box type box
anchors sounds very cool. Sure, but we bring back ten-fold complexity in the
form of building distributed charging, Legal Intercept, DPI, Inline
services, hotlining, high-availability ...etc etc, which are now part of
that one central anchor box. It is to be noted, we have not seen a true
distributed service deployed in the internet today, other than DNS.  But, I
agree, if this about building a true internet, who the heck cares about all
of these functions, in the true spirit.

Either way, I assumed any of the new solution will be bound by the following
parameters:

- The signaling protocol will continue to be based on MIPv6/PMIPv6 signaling
semantics. 

- We will not introduce a new client, what is now MIP client struggling to
make it to every variants of operating systems.

- Any client-based solution will be an extension on top of DSMIP. Any
network-based solution will be an extension to PMIPv6



I hope we can discuss the solution approaches in the next meeting and bring
new extension to MIPv6/PMIPv6 protocols.




Regards
Sri


























On 8/1/11 4:50 PM, "Seok-Joo Koh" <sjkoh@knu.ac.kr> 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/
> *************************
>