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

"Ashish Dalela (adalela)" <adalela@cisco.com> Fri, 20 January 2012 05:53 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 1C43721F857A for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 21:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level:
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 i0ThWZodki-n for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 21:52:59 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id C01BA21F8543 for <dc@ietf.org>; Thu, 19 Jan 2012 21:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=2969; q=dns/txt; s=iport; t=1327038779; x=1328248379; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=DVvprlpJ/uukeXOLeSoP9cjl7i1QyvWK3STOGSYZSrI=; b=QTVPZLvC/B9b8giSJ7tpIlrn2LzsU/Q/lxSW5E3Zum42yMQfAZez4gKt RMhbEtXoX5FCKVHsAs9KQHeJaRgKnHKXxaokbqyJJX36rT2N8dQ/kfNu4 q455QpX6fiHJVuiV977JtyqqTOvtKmCGWUHcdAdObaX60g39Pd5HkBWaF E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokTACEAGU9Io8UY/2dsb2JhbABDpyACh16BcgEBAQQBAQEPAR0KNAsMBAIBCBEEAQEBCgYXAQYBIAYfCQgBAQQLCAgah2KaNQGePwSLQ2MEiDqXX4dS
X-IronPort-AV: E=Sophos;i="4.71,540,1320624000"; d="scan'208";a="3809769"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 20 Jan 2012 05:52:57 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q0K5qvlQ008073; Fri, 20 Jan 2012 05:52:57 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Jan 2012 11:22:57 +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 11:22:55 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5102CB2380@XMB-BGL-416.cisco.com>
In-Reply-To: <4F18FB72.2090900@joelhalpern.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczXNFZ1NSiDPlw8TeSK9mx6Vbf2BAAAUVWg
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>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-OriginalArrivalTime: 20 Jan 2012 05:52:57.0542 (UTC) FILETIME=[C2A13660:01CCD737]
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 05:53:00 -0000

Joel,

Hypervisor control is in the hypervisor manager. Switch control is in
the network control plane. These are parallel silos, that don't
interact. 

Either the hypervisor manager defers control to the network control
plane, or the switches defer control to the manager. Or, some new third
entity emerges to control both, and both hypervisor and switch defer
control to that entity. 

We can't have separate control models and expect this to work in the
same way. 

Which of these (or other) models you think presents a reasonable
approach to reconcile hypervisor control and network control?

Thanks, Ashish

-----Original Message-----
From: Joel M. Halpern [mailto:jmh@joelhalpern.com] 
Sent: Friday, January 20, 2012 10:58 AM
To: Ashish Dalela (adalela)
Cc: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt

While one can construct strawman hypothesis in whcih there are reasons 
to have different tunnel control protocols depepnding upon end-point 
location, equally one can construct reasonably hypothesis in which the 
same protocol mechanisms work whether the end-point is at the VM, the 
Hypervisor, the ToR switch, or an aggregation switch.


Yours,
Joel

On 1/20/2012 12:07 AM, Ashish Dalela (adalela) wrote:
>
> I would not arrive at the conclusion that hypervisor work should or
> should not be done in IETF. That's a separate question. VXLAN and
NVGRE
> are hypervisor based approaches. But, they don't have control planes
> (yet). My point is that finding a common map-encap scheme isn't that
> hard. The harder part is how to make the hypervisor and network based
> map-encap *control planes* work the same way.
>
> If they don't work the same way, then L2-in-L2, L2-in-L3, L3-in-L3 has
a
> network flavor and a hypervisor flavor.
>
> Thanks, Ashish
>
>
> -----Original Message-----
> From: Melinda Shore [mailto:melinda.shore@gmail.com]
> Sent: Friday, January 20, 2012 10:06 AM
> To: Ashish Dalela (adalela)
> Cc: dc@ietf.org
> Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt
>
> On 1/19/12 7:26 PM, Ashish Dalela (adalela) wrote:
>> Bandwidth needs, but they have the
>> same tunnel. How do I distinguish between them based on the tunnel?
In
>> fact, if the tenant isolation is in the hypervisor, then the
> underlying
>> network has no clue which tenant needs what policy.
>
> Well, that's not true.  In the case of IPSec we've got SPIs, and
> there are similar demultiplexing mechanisms in other technologies.
>
> But frankly I think that if you're going to distinguish between
> tunnel endpoints in the hypervisor and tunnel endpoints in other
> sorts of network devices I think you're going to be somewhat
> hard-pressed to make the case for working on the former in
> the IETF.
>
> Melinda
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc
>