IETF Logo Mail Archive

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

"Ashish Dalela (adalela)" <adalela@cisco.com> Fri, 20 January 2012 16:32 UTC

Return-Path: <adalela@cisco.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 8344E21F85C0 for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 08:32:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.451
X-Spam-Level:
X-Spam-Status: No, score=-2.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599]
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 K03U6gKv9NWm for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 08:32:23 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 024C521F85B8 for <dc@ietf.org>; Fri, 20 Jan 2012 08:32:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=1251; q=dns/txt; s=iport; t=1327077143; x=1328286743; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=rzumigU1Er+YkVV7TwW7grM4ZIzow2UwrhRTdssgyFk=; b=Rmlp2U5SpCyFh/VNfLzrH8ExC7rpfokgcWK22UH8E4dglcC+QPdK1ky4 1gaxTrXjB2PnZTLqPxV0O+YC075qnQC3j7iyDNPbXi2FIL7nyp1s6RcJT DT5qEH+YHc9v3idSu1EAofKtu88gNdlxsHa3+VjbEC8rI95N4CyKUddO6 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8EAOWVGU9Io8UY/2dsb2JhbABDrw2BcgEBAQQBAQEPAR0KNBcEAgEIEQQBAQEKBhcBBgEmHwkIAQEEAQoICBMHh2KaDQGePQSLQ2MEiDqfMg
X-IronPort-AV: E=Sophos;i="4.71,543,1320624000"; d="scan'208";a="3846353"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 20 Jan 2012 16:32:21 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q0KGWLpl022824; Fri, 20 Jan 2012 16:32:21 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Jan 2012 22:02:20 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Jan 2012 22:02:19 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5102CB2524@XMB-BGL-416.cisco.com>
In-Reply-To: <4F19034E.1070802@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczXOQwOm5R89m7gR8qEThF3S4Z0DgAVjY1Q
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>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>, dc@ietf.org
X-OriginalArrivalTime: 20 Jan 2012 16:32:20.0838 (UTC) FILETIME=[14EFA060:01CCD791]
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 16:32:24 -0000

Let's assume we are building protocols for hypervisors. Can you suggest
what type of protocols will allow a hypervisor based solution interact
with a non-hypervisor based server? I.e. encap-decap done in the
hypervisor is not understood by the non-virtualized server.

Thanks, Ashish


-----Original Message-----
From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
Melinda Shore
Sent: Friday, January 20, 2012 11:32 AM
To: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt

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
_______________________________________________
dc mailing list
dc@ietf.org
https://www.ietf.org/mailman/listinfo/dc

v2.23.0 | Report a Bug | By Email