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

Thomas Narten <narten@us.ibm.com> Thu, 19 January 2012 14:19 UTC

Return-Path: <narten@us.ibm.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 1E55E21F862A for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 06:19:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.999
X-Spam-Level:
X-Spam-Status: No, score=-108.999 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, 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 pRMwRaN6C66u for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 06:19:56 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 8F06721F8629 for <dc@ietf.org>; Thu, 19 Jan 2012 06:19:56 -0800 (PST)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <dc@ietf.org> from <narten@us.ibm.com>; Thu, 19 Jan 2012 07:19:54 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 19 Jan 2012 07:19:53 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 313C23E4005A for <dc@ietf.org>; Thu, 19 Jan 2012 07:19:52 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q0JEJj5V151738 for <dc@ietf.org>; Thu, 19 Jan 2012 07:19:47 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q0JEJec0021179 for <dc@ietf.org>; Thu, 19 Jan 2012 07:19:40 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-76-45-53.mts.ibm.com [9.76.45.53]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q0JEJbJK020524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Jan 2012 07:19:39 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q0JEJTLF010649; Thu, 19 Jan 2012 09:19:31 -0500
Message-Id: <201201191419.q0JEJTLF010649@cichlid.raleigh.ibm.com>
To: Bhumip Khasnabish <vumip1@gmail.com>
In-reply-to: <CANtnpwjexDPazOXLYHHjn3+JDi-o49Bv5ptDExAZHAA8Ra2m-A@mail.gmail.com>
References: <CAH==cJxfmae0u0bSF4cn_haLgY1T-vnw2102PApzYtj5Aty=GQ@mail.gmail.com> <CANtnpwhFJ746ooi9GUCxfBqsOXu14hDka0D9inhh5pPq3U_ZTA@mail.gmail.com> <201201171540.q0HFeNan008591@cichlid.raleigh.ibm.com> <CANtnpwjexDPazOXLYHHjn3+JDi-o49Bv5ptDExAZHAA8Ra2m-A@mail.gmail.com>
Comments: In-reply-to Bhumip Khasnabish <vumip1@gmail.com> message dated "Wed, 18 Jan 2012 01:33:50 -0500."
Date: Thu, 19 Jan 2012 09:19:28 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12011914-4242-0000-0000-0000008D5F51
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: Thu, 19 Jan 2012 14:19:57 -0000

> It may be very helpful to bring one or more of these
> proprietary VM migration approaches to IETF for consideration
> for standardization, if that is appropriate.

Well, let's start with this as a premise. Sure, in the utopia of open
standards everwhere, having all this stuff standardized would be
great.

But let's be realistic. Are any of the vendors/implementors of these
systems coming to the IETF saying they want or need a standard? (If
so, I must have missed this.)

If the market heavyweights are not indicating that they will
participate and/or implement such a standard, would anything the IETF
does in this space be relevant? (Based on experience, I fear the
answer is a very clear "no".)

Finally, do we see operators who use the existing systems coming to
the IETF saying they want open standards here? So far, the silence has
been deafening so far...

> Sure, we'll update the draft to articulate these requirements.

Frankly, until and unless the questions above can be answered in a
more positive manner, IMO there is little point in spending any cycles
in this area, other than getting positive answers to the questions.

Or am I missing something?

Thomas