Re: [sami] Bringing new work into the IETF

"So, Ning" <ning.so@verizon.com> Mon, 22 August 2011 18:48 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 7663321F8C09 for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 11:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level:
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 XkOMZeFOq56l for <sami@ietfa.amsl.com>; Mon, 22 Aug 2011 11:48:43 -0700 (PDT)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7BCB721F8BE8 for <sami@ietf.org>; Mon, 22 Aug 2011 11:48:43 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe02.verizon.com with ESMTP; 22 Aug 2011 18:49:47 +0000
From: "So, Ning" <ning.so@verizon.com>
X-IronPort-AV: E=Sophos;i="4.68,264,1312156800"; d="scan'208";a="119086523"
Received: from fhdp1lumxc7hb04.verizon.com (HELO FHDP1LUMXC7HB04.us.one.verizon.com) ([166.68.59.191]) by fldsmtpi02.verizon.com with ESMTP; 22 Aug 2011 18:49:47 +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 14:49:47 -0400
To: "sami@ietf.org" <sami@ietf.org>
Date: Mon, 22 Aug 2011 14:49:46 -0400
Thread-Topic: [sami] Bringing new work into the IETF
Thread-Index: AcxgxormVlgBbhKlQ4yaQ7iW18rKdQACX3wAAARHw8YABpV4IA==
Message-ID: <6665BC1FEA04AB47B1F75FA641C43BC0814DBF10@FHDP1LUMXC7V41.us.one.verizon.com>
References: <6665BC1FEA04AB47B1F75FA641C43BC0814DBCB1@FHDP1LUMXC7V41.us.one.verizon.com> <CA77E180.13DD5%bschlies@cisco.com>
In-Reply-To: <CA77E180.13DD5%bschlies@cisco.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
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 18:48:44 -0000

Benson,

Thank you for bringing ODCA to my attention.  I have had very limited exposure to DMTF, and no exposure to ODCA at all.  After reading a bit more on their work, those SDOs appear to be better places for the type of work I have in mind.  I cannot cover those SDOs, so I will alert internally to have other people involved.  

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


-----Original Message-----
From: Benson Schliesser [mailto:bschlies@cisco.com] 
Sent: Monday, August 22, 2011 10:36 AM
To: So, Ning; Thomas Narten
Cc: sami@ietf.org
Subject: Re: [sami] Bringing new work into the IETF

Hi, Ning.

On 8/22/11 8:52 AM, "So, Ning" <ning.so@verizon.com> wrote:
>> Thomas Narten said:
> 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. 
> ...
> [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.

It's good that you mention the DMTF.  You should also investigate other groups such as ODCA (http://www.opendatacenteralliance.org/), which has a working group on this topic.

Assuming that hypervisor compatibility, control APIs, etc, are worked out in a different forum - what role do you think the IETF has in this space?  I have my own thoughts on this topic, but I don't want to put words in your mouth. Can you be specific?

Thanks,
-Benson