Re: [dc] A purpose of the draft /// Re: draft-khasnabish-vmmi-problems-00.txt

<david.black@emc.com> Thu, 16 February 2012 23:15 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 2480221E806A for <dc@ietfa.amsl.com>; Thu, 16 Feb 2012 15:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.93
X-Spam-Level:
X-Spam-Status: No, score=-108.93 tagged_above=-999 required=5 tests=[AWL=0.469, BAYES_00=-2.599, J_CHICKENPOX_62=0.6, J_CHICKENPOX_73=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 1g8qlSGOpcCr for <dc@ietfa.amsl.com>; Thu, 16 Feb 2012 15:15:03 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 082EF21E8064 for <dc@ietf.org>; Thu, 16 Feb 2012 15:15:02 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1GNExHe004482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Feb 2012 18:14:59 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 16 Feb 2012 18:14:43 -0500
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1GNE7D5008677; Thu, 16 Feb 2012 18:14:43 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Thu, 16 Feb 2012 18:14:25 -0500
From: david.black@emc.com
To: richard.bohan.liu@gmail.com
Date: Thu, 16 Feb 2012 18:14:24 -0500
Thread-Topic: [dc] A purpose of the draft /// Re: draft-khasnabish-vmmi-problems-00.txt
Thread-Index: Aczs9v13n/CV2jDwQWSYp5vDsVzF1AACEAQg
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD33AEE3@MX14A.corp.emc.com>
References: <CABHc4M0Y54+bZ1ifXgvtPx+Rp=5wLiQiyaMheif-ASbCymqWXA@mail.gmail.com>
In-Reply-To: <CABHc4M0Y54+bZ1ifXgvtPx+Rp=5wLiQiyaMheif-ASbCymqWXA@mail.gmail.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: narten@us.ibm.com, david.black@emc.com, dc@ietf.org, vumip1@gmail.com
Subject: Re: [dc] A purpose of the draft /// Re: 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: Thu, 16 Feb 2012 23:15:09 -0000

Hi Richard,

I'll keep this brief:

> See here, some people may be in doubt: Is the existing program can not
> solve your problem?

The answer to that question is missing from the draft, and it should start
with a statement of what the actual problem is.  The actual problem is *not*
virtual machine migration in general (as stated in the draft's Introduction),
as that already works fine over IP based networks (both IPv4 and IPv6).

What work are you advocating that the IETF undertake, and how would that
work improve the current situation for vitual machine migration?

The draft does not contain any answer to that question either.

Thanks,
--David

> -----Original Message-----
> From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of Richard Bin liu
> Sent: Thursday, February 16, 2012 5:04 PM
> To: Black, David
> Cc: narten; dc; Bhumip Khasnabish
> Subject: [dc] A purpose of the draft /// Re: draft-khasnabish-vmmi-problems-00.txt
> 
> Greetings David,
> 
> Thank you for your comments and question, it is a good question.
> From your viewpoint, "the interoperability between the different
> vender (or SPs)" is the necessary condition of the "to work for the
> IETF", but I think it is only a sufficient condition of the "to work
> for the IETF", not a necessary condition, for example, do VM migration
> between private desktop system with IPV6 addresses systems is not one
> of the goals of the IETF? Of course yes. Whether or not to agree with
> my viewpoint, seamless VM migration between a variety of computing
> systems (servers, tablet PCs, mobile phone system) is an irreversible
> trend in the future. Do IETF going to miss it?
> 
> So, I am sorry, in my personal viewpoint, your query is debatable.
> 
> See here, some people may be in doubt: Is the existing program can not
> solve your problem?
> 
> Yes, the reasons for defect analysis of existing system can refer to
> my following opinion(you can seach "traditional tunneling gateway" to
> find it in this mail).
> 
> Many thanks for guidance
> 
> Regards,
> 
> Richard Bin Liu
> 
> liu.bin21@zte.com.cn
> Richard.BoHan.liu@gmail.com
> 
> -------------------------------------------------------
> > 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 at ietf.org [mailto:dc-bounces at ietf.org] On Behalf
> Of liu.bin21 at zte.com.cn
> Sent: Tuesday, January 31, 2012 10:57 PM
> To: narten at us.ibm.com; vumip1 at gmail.com
> Cc: dc at 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 at zte.com.cn
> Richard.BoHan.liu at gmail.com
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc