IETF Logo Mail Archive

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

"Ashish Dalela (adalela)" <adalela@cisco.com> Fri, 20 January 2012 01:07 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 9531C21F8594 for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 17:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.429
X-Spam-Level:
X-Spam-Status: No, score=-2.429 tagged_above=-999 required=5 tests=[AWL=0.170, 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 UnlCdaKDdOqo for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 17:07:39 -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 65FE221F858B for <dc@ietf.org>; Thu, 19 Jan 2012 17:07:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=2456; q=dns/txt; s=iport; t=1327021659; x=1328231259; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=bX5OJIbWHxLodZrcot+ytHsZpeLMkzkkzPnwOAw9wQ8=; b=kOiHJYVaV66Pxvy55smN2txUcjk6sllzxR1zt3M+ZV7EXa4Ihik8sbUk XuYvVapzwDS+NePbbG2ZFDgzIiG1J/bYusPY3Mda7N/8i4pDvbRlE/AsB 7cc8i5CBp4YTYU1e8AgZ8PWdQjdzoRB/qT4cRm+JoZGHO1jMEjl+es77X o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEANe9GE9Io8UY/2dsb2JhbABAA4UEp3cUgW+BcgEBAQMBEgEQDQRFBQcEAgEIDgMEAQEDAgYGFwECAgIBAUQJCAEBBAsICBMHh1qaWgGMYpFbgS+ICgEBMgEFUAEEBwELAQIBAQUDAQEBAQJJCkqBaDlCggszYwSIOZ8w
X-IronPort-AV: E=Sophos;i="4.71,539,1320624000"; d="scan'208";a="3789162"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 20 Jan 2012 01:07:37 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q0K17b01009948; Fri, 20 Jan 2012 01:07:37 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 06:37:37 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Fri, 20 Jan 2012 06:37:33 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5102CB22FF@XMB-BGL-416.cisco.com>
In-Reply-To: <1326992094.2513.10.camel@ecliptic.extremenetworks.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczWyxk1kFC7h3sUQF+SIAm9U/X+jwAQ85EA
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> <1326992094.2513.10.camel@ecliptic.extremenetworks.com>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: Steven Blake <sblake@extremenetworks.com>
X-OriginalArrivalTime: 20 Jan 2012 01:07:37.0707 (UTC) FILETIME=[E669B3B0:01CCD70F]
Cc: Thomas Narten <narten@us.ibm.com>, 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 01:07:40 -0000

> - Hypervisor based encapsulations
> - Network based encapsulations

> I don't see any reason why these need to differ.

The fact is that they do differ. A hypervisor based solution will not run a routing protocol (control plane), or we haven't seen that yet. That means many types of information will be pulled through configuration / mgmt control from a hypervisor controller rather than the network control plane. 

> - L2 in L2 encapsulation

> IEEE owns this space.

Then there is TRILL in IETF.

> - L2 in L3 encapsulation

> This is NVO3.  I would prefer to have to support the minimum number of
> NVO3 encapsulations in HW.

Minimum is not quantified :-) I thought you said you wanted only one.

> - L3 in L3 encapsulation

> There are already plenty to choose from.

We agree.

Thanks, Ashish

-----Original Message-----
From: Steven Blake [mailto:sblake@extremenetworks.com] 
Sent: Thursday, January 19, 2012 10:25 PM
To: Ashish Dalela (adalela)
Cc: Thomas Narten; dc@ietf.org
Subject: RE: [dc] draft-khasnabish-vmmi-problems-00.txt

On Thu, 2012-01-19 at 08:23 -0800, Ashish Dalela (adalela) wrote:

> >> "one encapsulation, please".  
> 
> How do you propose we reconcile the present scenario:
> 
> - Hypervisor based encapsulations
> - Network based encapsulations

I don't see any reason why these need to differ.

> - L2 in L2 encapsulation

IEEE owns this space.

> - L2 in L3 encapsulation

This is NVO3.  I would prefer to have to support the minimum number of
NVO3 encapsulations in HW.

> - L3 in L3 encapsulation

There are already plenty to choose from.


Regards,

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

v2.23.0 | Report a Bug | By Email