IETF Logo Mail Archive

Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC

"LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com> Tue, 03 June 2014 08:08 UTC

Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872EB1A0167; Tue, 3 Jun 2014 01:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFR1PSOnsK7V; Tue, 3 Jun 2014 01:08:07 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A241A0162; Tue, 3 Jun 2014 01:08:06 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s5387qIc006285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 3 Jun 2014 03:07:54 -0500 (CDT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s5387HJv014086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Jun 2014 10:07:50 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 3 Jun 2014 10:07:27 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "Larry Kreeger (kreeger)" <kreeger@cisco.com>, "Ken Gray (kegray)" <kegray@cisco.com>
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: AQHPdQIKiFgojcPjTkKOT8QRrMyEo5tMzYgAgAAXToCAAAXwAIABD1GAgABBcQCAAZtmgIAGlzUAgAAUtACAAl8ssIAAQpoAgAX2RmA=
Date: Tue, 03 Jun 2014 08:07:27 +0000
Message-ID: <B30152B129674240ADF67727A967301408CBAF@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <CFA3BF05.2C990%kegray@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D23D42@dfweml701-chm.china.huawei.com> <74FD38F4-0824-45A0-8B56-40A02B903430@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D254E4@dfweml701-chm.china.huawei.com> <CFA4FAC6.2D25F%kegray@cisco.com> <CFABA416.FE778%kreeger@cisco.com> <4A95BA014132FF49AE685FAB4B9F17F645D27721@dfweml701-chm.china.huawei.com> <B30152B129674240ADF67727A967301408C6F7@FR711WXCHMBA03.zeu.alcatel-lucent.com> <4A95BA014132FF49AE685FAB4B9F17F645D2975D@dfweml701-chm.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645D2975D@dfweml701-chm.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408CBAFFR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/LnCQsKwFLVhtlP-nEiQkhKAgeBI
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 08:08:09 -0000

Linda,

It is a local decision to assign whatever VNI value is best suited. As I have mentioned before, it is a locally significant value that is used as a demultiplexer.
An NVE can use a VLAN ID as a locally significant value if it wants to.

Marc

________________________________
From: Linda Dunbar [mailto:linda.dunbar@huawei.com]
Sent: Friday, May 30, 2014 5:02 PM
To: LASSERRE, MARC (MARC); Larry Kreeger (kreeger); Ken Gray (kegray)
Cc: nvo3@ietf.org; ietf@ietf.org; IETF-Announce
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC

Marc,

Questions inserted below:

From: LASSERRE, MARC (MARC) [mailto:marc.lasserre@alcatel-lucent.com]


-       Page 13 Second bullet: the text says that each VNI is automatically generated by the egress NVE. Isn't each VNI supposed to match a local virtual network (e.g. represented by VLAN)? When the same NVE acts as Ingress NVE for the attached VMs, aren't the VNI for ingress direction statically provisioned? Why need automatic egress VNI generation?

The value of the VN context identifier is a value locally significant to an NVE and does not have to match a local virtual network. It is simply used as a demultiplexer. This value can be automaticaly computed or provisioned.

[Linda]If the NVE's VAPS (VNI) are connected to VMs via Ethernet where VLAN is used, it is much easier to use locally significant VLAN. Why require egress to automatically generate local VNI value?  It would be better to change the text to:

"Each VNI value on egress NVE is either mapped to locally significant Virtual Network identifier (e.g. VLAN for Ethernet), or generated by NVA or Control Plane".

Linda

nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3

v2.23.0 | Report a Bug | By Email