Re: [dc] draft-khasnabish-vmmi-problems-00.txt

<david.black@emc.com> Wed, 01 February 2012 14:32 UTC

Return-Path: <david.black@emc.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A45111E815D for <dc@ietfa.amsl.com>; Wed, 1 Feb 2012 06:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.036
X-Spam-Level:
X-Spam-Status: No, score=-109.036 tagged_above=-999 required=5 tests=[AWL=0.962, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_HI=-8, 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 v+Yuju2yNWQJ for <dc@ietfa.amsl.com>; Wed, 1 Feb 2012 06:32:56 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id F2E7D11E811B for <dc@ietf.org>; Wed, 1 Feb 2012 06:32:55 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q11EWqOK022255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2012 09:32:53 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 1 Feb 2012 09:32:39 -0500
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q11EWbhL022431; Wed, 1 Feb 2012 09:32:38 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Wed, 1 Feb 2012 09:32:37 -0500
From: david.black@emc.com
To: liu.bin21@zte.com.cn, narten@us.ibm.com, vumip1@gmail.com
Date: Wed, 01 Feb 2012 09:32:35 -0500
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczgmucRAFiCZr/TQKayo9XONlILwAAUz8QQ
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD13B16A@MX14A.corp.emc.com>
References: <201202010434.q114YnPX010960@mse01.zte.com.cn>
In-Reply-To: <201202010434.q114YnPX010960@mse01.zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_7C4DFCE962635144B8FAE8CA11D0BF1E05AD13B16AMX14Acorpemcc_"
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2012 14:32:58 -0000

> About VM migration in the draft, we did not demand forcibly between the different vender(or SPs), so your concerns may not  exist.

In other words, there's no work for the IETF to do because interoperability is not a goal.  What have I missed?

Thanks,
--David

From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of liu.bin21@zte.com.cn
Sent: Tuesday, January 31, 2012 10:57 PM
To: narten@us.ibm.com; vumip1@gmail.com
Cc: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt


Thomas, thank you for your comments!

About VM migration in the draft, we did not demand forcibly between the different vender(or SPs), so your concerns may not
exist. As you say, "let's be realistic", our intention is to improve the flexibility of VM migration, as well as the breadth
of applications under the premise of market heavyweights are not opposed to it.In order to achieve these goals, analyse possible problems, discuss and resolve these problems, such as: VM migration is due to a non-public sector energy-efficient needs, rather than to public access without interruption, or business needs of the user's desktop migration, this demand may exist within a same service provider, or you say a same vender with mixed network, for example:

With the promotion of IPv6 technology, the existing IPv4 networks will be more and more IPv6 hosts, these applications driven
a series of tunnel technologies to provide solutions, such as: 6to4 tunnel technology, ISATAP tunnel technology, and so on.
Virtual machine migration technology will also be the basis of these network environments,in the transition network using tunneling transition technique, the connections between the subnets and the backbone network are achieved through the tunneling gateway. In the IPv4/IPv6 transition period, a variety of tunnels coexist. The establishment of the tunnel varies with different gateways. The traditional tunneling gateway only establishes tunnels for communication with the same type of gateway, the different types of traditional tunneling gateway cannot communicate with each other, which cannot meet the requirements of VPN communications in the transition period. A multi-tunnel VPN gateway is used to solve the problem of establishing the tunnel between the heterogeneous gateways.

Many thanks for guidance

Regards,

Bin Liu

liu.bin21@zte.com.cn
Richard.BoHan.liu@gmail.com



--------------------------------------------------------

ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.

This message has been scanned for viruses and Spam by ZTE Anti-Spam system.