Re: [Mipshop] MIPSHOP discussion on new items and milestones

Wassim Haddad <whaddad@tcs.hut.fi> Thu, 17 March 2005 01:19 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22374 for <mipshop-web-archive@ietf.org>; Wed, 16 Mar 2005 20:19:31 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBjjs-0000E5-EU for mipshop-web-archive@ietf.org; Wed, 16 Mar 2005 20:23:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBjeh-0005CD-U7; Wed, 16 Mar 2005 20:18:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBjeg-0005C8-3S for mipshop@megatron.ietf.org; Wed, 16 Mar 2005 20:18:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22262 for <mipshop@ietf.org>; Wed, 16 Mar 2005 20:18:26 -0500 (EST)
Received: from neon.tcs.hut.fi ([130.233.215.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBjio-0000C8-MI for mipshop@ietf.org; Wed, 16 Mar 2005 20:22:47 -0500
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147]) by neon.tcs.hut.fi (Postfix) with ESMTP id 462378000B4; Thu, 17 Mar 2005 03:18:20 +0200 (EET)
Date: Thu, 17 Mar 2005 03:18:20 +0200
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mipshop] MIPSHOP discussion on new items and milestones
In-Reply-To: <4238AAF3.8020002@iprg.nokia.com>
Message-ID: <Pine.LNX.4.58.0503170316360.27617@rhea.tcs.hut.fi>
References: <4238786E.9040202@sun.com> <4238AAF3.8020002@iprg.nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: gabriel montenegro <gab@sun.com>, mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Sender: mipshop-bounces@ietf.org
Errors-To: mipshop-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248

On Wed, 16 Mar 2005, Vijay Devarapalli wrote:

> hi all,
>
> gabriel montenegro wrote:
> >
> > Further work on FMIPv6
> > ----------------------
> >
> > - work on MN-AR security. For example:
> >
> >    - AAA-based keys for handovers - the need/desirability for such
> > 	an item was brought out in Jari's presentation in MOBOPTS.
> > 	even though this item does not yet exist in the form of
> > 	an I-D, it seems we should not have major difficulties
> > 	identifying interested parties to work on it.
> > 	This item is limited in terms of the deployment scenarios
> > 	it supports, but the carrier/service provider scenario it
> > 	caters to seems important enough to warrant work on it.
> > 	perhaps for PS?
> >
> >    - derive key from SeND for fmip (Rajeev/Kempf draft)
> > 	despite the IPR implications because of the use
> > 	of CGA (from SeND), this could target PS
> >
> > - work on FMIPv6 itself:
> >
> >    - The above items will go a long way towards solving the security
> > 	issues in FMIPv6. The current lack of such solutions is
> > 	perhaps the major issue why FMIP is currently experimental
> > 	and not PS. Given the above items, the WG could also take
> > 	on the effort to revise the base FMIP to PS. This effort
> > 	will clearly benefit from the fact that there are several
> > 	implementations of FMIPv6 (including publicly available
> > 	ones), so feedback from these effort will surely help in
> > 	cleaning it up towards PS.
> >
> >    - Apparently, the CDMA folks (in particular, those working
> > 	on "1x-EV evolution" have some interest in using FMIPv6.
> > 	Another potential WG item could be a document to describe
> > 	how FMIPv6 would work over such a link. This document
> > 	would be analogous to our current FMIPv6 over 802.11
> > 	document, and would similarly target informational.
>
> the FMIPv6 tasks look good. I like the last task very much. :)
>
> >
> > RR optimizations
> > ----------------
> > I must confess to me these seem less coherent and ready as a group than
> > the above group. E.g., it's not clear to me whether a standards-track
> > document would end up mixing different proposals, and how.
> >
> > - CGA type idea from OMIP
> > - CBA (credit-based) maybe no 'spot checks', just the basic stuff
> > 	as is being applied to HIP, for example. this could complement
> > 	other proposals like CGA or preconfigured MN-HA SA, for example.
> > - EBU - but have heard concern that this *increases* signaling cuz it adds
> > 	messages, what we want is less (not more) signaling.
>
> IMO, these work items should not be taken up by MIPSHOP.
> my understanding is that these proposals become mature in
> MOBOPTS and MOBOPTS will recommend to MIP6 WG when they are
> ready to be standardized as a proposed standard.
>
> I am *not* looking forward to multiple RR Optimization
> proposed standards in MIPSHOP.

=> I am looking exactly to the *opposite* especially when you have a
proposal which makes sense!


Wassim H.


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