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

Melinda Shore <melinda.shore@gmail.com> Fri, 20 January 2012 19:28 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 9375621F8685 for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 11:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.229
X-Spam-Level:
X-Spam-Status: No, score=-3.229 tagged_above=-999 required=5 tests=[AWL=0.370, 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 CiK7uqjcvrjD for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 11:28:24 -0800 (PST)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by ietfa.amsl.com (Postfix) with ESMTP id 55D9C21F8650 for <dc@ietf.org>; Fri, 20 Jan 2012 11:28:22 -0800 (PST)
Received: by ghy10 with SMTP id 10so568391ghy.27 for <dc@ietf.org>; Fri, 20 Jan 2012 11:28:21 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=7eS0BDfuHeTAF4tWE0ZRMiCB8MOsF7jqSI1Kue+5AoA=; b=HC8s3KNu0CHPUYZqO5rDeHa3zrK2S+SCjV3snICIJyL2bLj+Sj60Sz7AXX+3IkI23S PZVylX1NSHIbFMlLyb7ZxW34cq8IuC51K+8qc5vGGikCTUtFn6Zoh1OWSfsP9VkuYa3u Rk3E7aNUllO2HGwq32iHTUeM2KxNi/7GI5RrA=
Received: by 10.101.18.12 with SMTP id v12mr3617806ani.59.1327087701899; Fri, 20 Jan 2012 11:28:21 -0800 (PST)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id y14sm10617207anm.10.2012.01.20.11.28.20 (version=SSLv3 cipher=OTHER); Fri, 20 Jan 2012 11:28:21 -0800 (PST)
Message-ID: <4F19C061.4060609@gmail.com>
Date: Fri, 20 Jan 2012 10:28:33 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: "Ashish Dalela (adalela)" <adalela@cisco.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><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> <4F19034E.1070802@gmail.com> <618BE8B40039924EB9AED233D4A09C5102CB2524@XMB-BGL-416.cisco.com>
In-Reply-To: <618BE8B40039924EB9AED233D4A09C5102CB2524@XMB-BGL-416.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 20 Jan 2012 19:28:24 -0000

On 01/20/2012 07:32 AM, Ashish Dalela (adalela) wrote:
> Let's assume we are building protocols for hypervisors.

This may be the source of some of the confusion.  This is
a very vertical framing of the question, when more typically
we're dealing with horizontal communication.   Network
layering is not as clean as we'd necessarily like but what
we're usually dealing with is protocol peers talking
to each other.  That is to say, we're not building protocols
for *hypervisors*, we're building protocols for some functional
component of the network.  From what I've seen a bunch of us
are unclear on why you think that a hypervisor cannot be
where that component lives.

Melinda