Re: [sami] Bringing new work into the IETF

"So, Ning" <ning.so@verizon.com> Mon, 22 August 2011 13:51 UTC

Return-Path: <ning.so@verizon.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 0FD9921F863A for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 06:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level:
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599]
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 YHYdTORy-Iw2 for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 06:51:20 -0700 (PDT)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2181221F8A7D for <sami@ietf.org>; Mon, 22 Aug 2011 06:51:19 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe01.verizon.com with ESMTP; 22 Aug 2011 13:52:24 +0000
From: "So, Ning" <ning.so@verizon.com>
X-IronPort-AV: E=Sophos;i="4.68,263,1312156800"; d="scan'208";a="118853615"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi02.verizon.com with ESMTP; 22 Aug 2011 13:52:19 +0000
Received: from FHDP1LUMXC7V41.us.one.verizon.com ([169.254.1.38]) by FHDP1LUMXC7HB04.us.one.verizon.com ([166.68.59.191]) with mapi; Mon, 22 Aug 2011 09:52:19 -0400
To: Thomas Narten <narten@us.ibm.com>
Date: Mon, 22 Aug 2011 09:52:18 -0400
Thread-Topic: [sami] Bringing new work into the IETF
Thread-Index: AcxgxormVlgBbhKlQ4yaQ7iW18rKdQACX3wA
Message-ID: <6665BC1FEA04AB47B1F75FA641C43BC0814DBCB1@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> <201108221225.p7MCP8Ih021246@cichlid.raleigh.ibm.com>
In-Reply-To: <201108221225.p7MCP8Ih021246@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "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 13:51:21 -0000

Thomas,

Please see my reply inline.  

 
Best regards,
 
Ning So
Verizon Corporate Technology
(office) 972-729-7905
(Cell) 972-955-0914
 

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com] 
Sent: Monday, August 22, 2011 7:25 AM
To: So, Ning
Cc: David Harrington; 'Yingjie Gu(yingjie)'; sami@ietf.org
Subject: Re: [sami] Bringing new work into the IETF

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?

[Ning]:  Yes. 

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.

[Ning]:  It is important to have a common agreement on requirements.  I stated my opinion and use case.  I will reach out to the carriers I have been work with in other areas to see if they also have the similar requirements.  If it is true, then IETF has to play a key role in this.  Other SDO such as DMTF will also play a key role.  I hope the use cases and requirements can drive player agreement/participation, especially secondary players.          

Thomas