[Mipshop] MIPSHOP discussion on new items and milestones

gabriel montenegro <gab@sun.com> Wed, 16 March 2005 18:21 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 NAA18418 for <mipshop-web-archive@ietf.org>; Wed, 16 Mar 2005 13:21:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBdDM-0004O5-Ey for mipshop-web-archive@ietf.org; Wed, 16 Mar 2005 13:25:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBd6R-0008RL-0q; Wed, 16 Mar 2005 13:18:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DBd6P-0008Qj-FW for mipshop@megatron.ietf.org; Wed, 16 Mar 2005 13:18:41 -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 NAA18094 for <mipshop@ietf.org>; Wed, 16 Mar 2005 13:18:38 -0500 (EST)
Received: from dyn50.sunlabs.com ([204.153.12.50] helo=mail-mta.sunlabs.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DBdAU-0004Dy-Ed for mipshop@ietf.org; Wed, 16 Mar 2005 13:22:54 -0500
Received: from mail.sunlabs.com ([152.70.2.186]) by mail-mta.sfvic.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTP id <0IDG00L55IUT5600@mail-mta.sfvic.sunlabs.com> for mipshop@ietf.org; Wed, 16 Mar 2005 10:18:29 -0800 (PST)
Received: from [152.70.69.138] by mail.sunlabs.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 25 2004)) with ESMTPSA id <0IDG005IUIUQ1E10@mail.sunlabs.com> for mipshop@ietf.org; Wed, 16 Mar 2005 10:18:27 -0800 (PST)
Date: Wed, 16 Mar 2005 10:18:22 -0800
From: gabriel montenegro <gab@sun.com>
To: mipshop@ietf.org
Message-id: <4238786E.9040202@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-2022-JP"
Content-transfer-encoding: 7bit
X-Accept-Language: en-us, en
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit
Subject: [Mipshop] MIPSHOP discussion on new items and milestones
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: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit

Folks,

As you may be aware, the working group's current milestones are
all done.

I spoke with Margaret Wasserman (taking over from Thomas Narten
as our advising AD) during IETF week, about possible next steps
for MIPSHOP.

It seems like there is sufficient interest and plenty of potential
work items to keep the working group going. Possible items
Margaret and I talked about include the following areas:

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.

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.

----

These are the two areas I see most probable for continued work.
Nevertheless, there are other items people have mentioned. Feel
free to propose additional items if you consider they are ready for
standardization. This is diffucult to judge, but the following
are things to keep in mind (of course, they are *not absolute
requirements*):

- are the proposals mature (e.g., plenty of discussion, several
	revisions taking into account WG feedback, published
	results, existing implementations, etc)
- is there interest in the proposals (e.g., are folks interested
	in deploying, perhaps because the proposal enables certain
	scenarios, is there interest from *more than one party*, etc)
- is IPR resolved (at least RAND as per IETF rules, hopefully
	royalty free of course)

Items not ready *now* may of course be ready later on. In the meantime,
those items may continue being discussed in other working/research groups,
as individual submissions, etc.

I have spoken with some of you about the above (thanks for the feedback).
Even if you have privately expressed your opinions, please send your
comments on the above items to the list. Besides expressions of
support, negative opinions are equally important. I have purposely
listed perhaps more items than we'll be able to take on, so we
will probably have to cut the list a bit shorter. Hence, any
comments to help in that respect are also very useful.

So please consider the rechartering discussion for MIPSHOP open
(hopefully the directions mentioned above are close enough).

Comments?

-gabriel

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