Re: [sami] Bringing new work into the IETF

Thomas Narten <narten@us.ibm.com> Mon, 22 August 2011 12:24 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: sami@ietfa.amsl.com
Delivered-To: sami@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7500721F8B48 for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 05:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9G8niWqyrLn for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 05:24:22 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id ABEAA21F8B46 for <sami@ietf.org>; Mon, 22 Aug 2011 05:24:19 -0700 (PDT)
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by e7.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p7MBwbDW027856 for <sami@ietf.org>; Mon, 22 Aug 2011 07:58:37 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7MCPBwY222600 for <sami@ietf.org>; Mon, 22 Aug 2011 08:25:11 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7MCPBBg030737 for <sami@ietf.org>; Mon, 22 Aug 2011 09:25:11 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-48-44-45.mts.ibm.com [9.48.44.45]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p7MCP9td030604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2011 09:25:10 -0300
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p7MCP8Ih021246; Mon, 22 Aug 2011 08:25:08 -0400
Message-Id: <201108221225.p7MCP8Ih021246@cichlid.raleigh.ibm.com>
To: "So, Ning" <ning.so@verizon.com>
In-reply-to: <6665BC1FEA04AB47B1F75FA641C43BC0814DB910@FHDP1LUMXC7V41.us.one.verizon.com>
References: <004c01cc57ec$7f602ed0$7e208c70$@com> <20110811074034.GA12533@elstar.local> <005701cc5806$03cd8370$0b688a50$@com> <4A95BA014132FF49AE685FAB4B9F17F605189C80@dfweml504-mbx.china.huawei.com> <006001cc5cbb$de6c48e0$9b44daa0$@com> <6665BC1FEA04AB47B1F75FA641C43BC08146326D@FHDP1LUMXC7V41.us.one.verizon.com> <004b01cc5d9e$c7015130$5503f390$@com> <CDDE62FF82604D09B92836C30BE7AD07@davidPC> <6665BC1FEA04AB47B1F75FA641C43BC0814DB910@FHDP1LUMXC7V41.us.one.verizon.com>
Comments: In-reply-to "So, Ning" <ning.so@verizon.com> message dated "Fri, 19 Aug 2011 12:54:37 -0400."
Date: Mon, 22 Aug 2011 08:25:08 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: "'Yingjie Gu(yingjie)'" <guyingjie@huawei.com>, David Harrington <ietfdbh@comcast.net>, "sami@ietf.org" <sami@ietf.org>
Subject: Re: [sami] Bringing new work into the IETF
X-BeenThere: sami@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: State Migration <sami.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sami>, <mailto:sami-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sami>
List-Post: <mailto:sami@ietf.org>
List-Help: <mailto:sami-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sami>, <mailto:sami-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 12:24:23 -0000

Just so I understand...

"So, Ning" <ning.so@verizon.com> writes:

> Telecom service provider such as Verizon have significant business
> with enterprises and government agencies.  One significant cloud
> service business for that market in the foreseeable future is to
> host overflow/expansion capacity for the enterprise/government data
> centers.  That means the provider data centers will have to be
> multi-tenant in nature with seamless inter-working with the customer
> data centers.  There are quite a few (I cannot number them)
> hypervisors out there in the market today, and the customers I know
> have all of them (although usually each customer has one or two
> hypervisors only).  Without standardization means the provider data
> center has to have all of the hypervisors in each and every data
> center in order to provide the services, and it also means the
> server/network capacity in the provider data centers are dedicated
> per Hypervisor without capacity sharing.

Are you saying you want interoperabilty between hypervisors? That is,
You want to be able to move a VM from hypervisor type A (i.e, from
vendor A) to a hypervisor of type B (i.e,. from Vendor B), and you'd
like the IETF to develop standards that allow this?

If so, that seems like trying to bite off a pretty big task, well
beyound what most others have been calling for.

It would be good to get clarity as to whether this is a goal and
whether there any of the key players (i.e., hypervisor vendors) agree.

Thomas