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

"Ashish Dalela (adalela)" <adalela@cisco.com> Thu, 19 January 2012 16:23 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 793DD21F84DD for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 08:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=0.174, 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 l4WKHcW3cJIZ for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 08:23:20 -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 CBDF021F8619 for <dc@ietf.org>; Thu, 19 Jan 2012 08:23:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=2376; q=dns/txt; s=iport; t=1326990200; x=1328199800; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=Wt6FFeLRV+3oWo+iGWD9fE+83/UgYyIIaETvug436Xw=; b=LsrK6JEcp5PH55Tsr7us0sZfrfm7dqKDRdyZUEWfzLFfwpyYOgATfiFa n9bXblJKhZctl/gpQRYncVRhRFLvALxhj8BmqRdK6no6DfLhdiNgISqIo JJQ0pqp7NqUVn+fsoWfnQQnENsm5ikzmxLuomlWN84hSZvxflfWOW4CLC M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAERDGE9Io8UY/2dsb2JhbABBA6xfggWBcgEBAQMBAQEBDwEdCjQLDAQCAQgOAwQBAQsGFwEGASYfCQgBAQQBCggIFgSHWgiaNAGeWASJNzYBBVABBAcBCwECAQEIAQEBAQJJCkqBaFcWAQEBAgmCPmMEiDmfMA
X-IronPort-AV: E=Sophos;i="4.71,537,1320624000"; d="scan'208";a="3767207"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 19 Jan 2012 16:23:18 +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 q0JGNIXu003575; Thu, 19 Jan 2012 16:23:18 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); Thu, 19 Jan 2012 21:53:18 +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: Thu, 19 Jan 2012 21:53:16 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5102CB2291@XMB-BGL-416.cisco.com>
In-Reply-To: <1326989277.2513.4.camel@ecliptic.extremenetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczWxJOZ00cNuYvVSF6Xk7/uMykD9wAAL+Wg
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>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: Steven Blake <sblake@extremenetworks.com>, Thomas Narten <narten@us.ibm.com>
X-OriginalArrivalTime: 19 Jan 2012 16:23:18.0121 (UTC) FILETIME=[A709D590:01CCD6C6]
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: Thu, 19 Jan 2012 16:23:21 -0000

>> "one encapsulation, please".  

How do you propose we reconcile the present scenario:

- Hypervisor based encapsulations
- Network based encapsulations
- L2 in L2 encapsulation
- L2 in L3 encapsulation
- L3 in L3 encapsulation

Thanks, Ashish

-----Original Message-----
From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
Steven Blake
Sent: Thursday, January 19, 2012 9:38 PM
To: Thomas Narten
Cc: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt

On Thu, 2012-01-19 at 06:19 -0800, Thomas Narten wrote:

> > It may be very helpful to bring one or more of these
> > proprietary VM migration approaches to IETF for consideration
> > for standardization, if that is appropriate.
> 
> Well, let's start with this as a premise. Sure, in the utopia of open
> standards everwhere, having all this stuff standardized would be
> great.
> 
> But let's be realistic. Are any of the vendors/implementors of these
> systems coming to the IETF saying they want or need a standard? (If
> so, I must have missed this.)
> 
> If the market heavyweights are not indicating that they will
> participate and/or implement such a standard, would anything the IETF
> does in this space be relevant? (Based on experience, I fear the
> answer is a very clear "no".)
> 
> Finally, do we see operators who use the existing systems coming to
> the IETF saying they want open standards here? So far, the silence has
> been deafening so far...
> 
> > Sure, we'll update the draft to articulate these requirements.
> 
> Frankly, until and unless the questions above can be answered in a
> more positive manner, IMO there is little point in spending any cycles
> in this area, other than getting positive answers to the questions.
> 
> Or am I missing something?

Several system vendors (myself included) stood up in Taipei and said
"one encapsulation, please".  If IETF can facilitate industry
convergence on a small set of NVO3 encapsulations (preferably one), that
would be a big win for Ethernet switch vendors.


Regards,

/////////////////////////////////////////////
Steven Blake       sblake@extremenetworks.com
Extreme Networks              +1 919-884-3211

_______________________________________________
dc mailing list
dc@ietf.org
https://www.ietf.org/mailman/listinfo/dc