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

Melinda Shore <melinda.shore@gmail.com> Fri, 20 January 2012 02:15 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 8B68721F85DB for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 18:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.044
X-Spam-Level:
X-Spam-Status: No, score=-3.044 tagged_above=-999 required=5 tests=[AWL=0.555, 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 VPxzWyk7p9tN for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 18:15:49 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07A4121F85E3 for <dc@ietf.org>; Thu, 19 Jan 2012 18:15:48 -0800 (PST)
Received: by ghrr16 with SMTP id r16so48422ghr.31 for <dc@ietf.org>; Thu, 19 Jan 2012 18:15:48 -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=+BQvLAEgh2u7wtLtdJ/PatO8DGdvN6FFWxRWFRjcMew=; b=gwfTSrjX1xDKlu15SjyFMJ7lgG9TkKHgcFxClx6TeaQ642DfjUZVTrDBJ7pIlbyLKE duDAF7KxGiPoKQYvIsglX/Ep6qyzNEPBZNVNOsO/5PgiBzE/qXB/QALtAToGH3QWrikZ 4HzR/CQWz/piDAdjFONOo8oKV5J/8Iov+toXs=
Received: by 10.236.187.10 with SMTP id x10mr43188918yhm.4.1327025748663; Thu, 19 Jan 2012 18:15:48 -0800 (PST)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id q29sm3790830anh.1.2012.01.19.18.15.47 (version=SSLv3 cipher=OTHER); Thu, 19 Jan 2012 18:15:48 -0800 (PST)
Message-ID: <4F18CE61.6030002@gmail.com>
Date: Thu, 19 Jan 2012 17:16:01 -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: 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>
In-Reply-To: <406B8B5D-E1E5-4DF4-8DE2-D7D2A699430A@asgaard.org>
Content-Type: text/plain; charset="UTF-8"; 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 02:15:49 -0000

On 01/19/2012 05:11 PM, Christopher LILJENSTOLPE wrote:
> 	I agree with some subset of L2-in-L2, L2-in-L3, and L3-in-L3 encaps.
 > I'm not sure what we mean by network vs hypervisor based encaps.  Do
 > we really want to have a different encap depending on where it's
 > originated or terminated?  Anyone see problems with this if one end
 > of the connection is an appliance (and connected to, say a switch)
 > and one end that's a hypervisor guest?  When folks were asking for a
 > small subset (where small is 1<=n<=3 maybe) I didn't think that they
 > were saying that this was a set of two, one for hypervisors, and one
 > for "network elements" what ever that might mean (I would tend to
 > view a hypervisor switch as an element in the network)

I'm similarly unclear on what these distinctions actually are.  It
seems to me that in either case (network vs. "hypervisor") we're really
talking about tunnel endpoints.  Can someone state clearly what
the difference is in practice?

Thanks,

Melinda