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

Melinda Shore <melinda.shore@gmail.com> Fri, 20 January 2012 06:01 UTC

Return-Path: <melinda.shore@gmail.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 8416521F84FD for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 22:01:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 YdiOmGuT2ge0 for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 22:01:54 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C744E21F84F6 for <dc@ietf.org>; Thu, 19 Jan 2012 22:01:53 -0800 (PST)
Received: by ggnr5 with SMTP id r5so112067ggn.31 for <dc@ietf.org>; Thu, 19 Jan 2012 22:01:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jvJ4Yw+OmP/l/tsd4WAwtT8oN8otUGG5E/QuZOmL7pk=; b=HdqljFbbwv5cE8vn8i1cag/+fvNI6OWcomYORu2+8YNuHF9eK46kTf3ZMlIodTEos7 eAPTIL7jyMMYJL2ZerIKIbGEWW+FnGXApcRbX7ecug1wQKkYpx4v4juUzMae4Snp555+ S4rp5NK3RgBVOHrsvIXWpa8mm/iTpFJrfxwbU=
Received: by 10.236.189.105 with SMTP id b69mr10957118yhn.90.1327039313427; Thu, 19 Jan 2012 22:01:53 -0800 (PST)
Received: from polypro.local (66-230-87-211-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.211]) by mx.google.com with ESMTPS id j11sm5378644anl.8.2012.01.19.22.01.52 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Jan 2012 22:01:52 -0800 (PST)
Message-ID: <4F19034E.1070802@gmail.com>
Date: Thu, 19 Jan 2012 21:01:50 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.25) Gecko/20111213 Lightning/1.0b2 Thunderbird/3.1.17
MIME-Version: 1.0
To: dc@ietf.org
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><201201191419.q0JEJTLF010649@cichlid.raleigh.ibm.com> <1326989277.2513.4.camel@ecliptic.extremenetworks.com> <618BE8B40039924EB9AED233D4A09C5102CB2291@XMB-BGL-416.cisco.com><406B8B5D-E1E5-4DF4-8DE2-D7D2A699430A@asgaard.org> <4F18CE61.6030002@gmail.com> <618BE8B40039924EB9AED233D4A09C5102CB2330@XMB-BGL-416.cisco.com> <4F18EF4A.3060308@gmail.com> <618BE8B40039924EB9AED233D4A09C5102CB234C@XMB-BGL-416.cisco.com> <4F18FB72.2090900@joelhalpern.com> <618BE8B40039924EB9AED233D4A09C5102CB2380@XMB-BGL-416.cisco.com>
In-Reply-To: <618BE8B40039924EB9AED233D4A09C5102CB2380@XMB-BGL-416.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 20 Jan 2012 06:01:54 -0000

On 1/19/12 8:52 PM, Ashish Dalela (adalela) wrote:
> Hypervisor control is in the hypervisor manager. Switch control is in
> the network control plane. These are parallel silos, that don't
> interact.

It seems to me that you're implying that we can't put protocols on
the hypervisor - is that correct?

I'm still having a hard time understanding your argument.  Can you
talk about specific information elements that you'd need for a
hypervisor but not a VPN concentrator (or vice versa), or protocol
elements ditto?  I'd find it helpful if you could illustrate what
the issue is.

Melinda