IETF Logo Mail Archive

Re: [nvo3] [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Thu, 20 July 2017 00:17 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F692129B2A; Wed, 19 Jul 2017 17:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 QuN-1k11K5eH; Wed, 19 Jul 2017 17:17:57 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DC35126BFD; Wed, 19 Jul 2017 17:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10220; q=dns/txt; s=iport; t=1500509877; x=1501719477; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vzAjZyROFbJKkxyVBz84yQnEGzhfr35ZlPEk3jO84sM=; b=km964qry1dXRBABeJO+Py2sAl/Gz2LNythFXu4OvnGSndqjAVt9T6hN7 lUfg179dyYo3kpnHRJzbrM/DVHuEHpS2kLFfn0lVmVPTipUPUuOMYJV71 Rr59xB+eSgf4YI1m2l5al/lSl3muB/xSJJ6ES/yT9hWbLd4Zsd5xWaQ5X M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DpAACc9W9Z/4wNJK1cDgwBAQEBAgEBAQEIAQEBAYJva2SBFAeOBJFniC6IKoUsghEshRsCg2M/GAECAQEBAQEBAWsohRgBAQEBA3kQAgEIEQMBAigHIREUCQgCBA4FiUtMAxUQsxWHNQ2DXwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgyiFLoMkgleCM4VUBZEghiSHOjsCh0mHXoRwkjCMDIlPAR84gQp1FYUjORyBKD92iBOBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.40,381,1496102400"; d="scan'208,217";a="275772862"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jul 2017 00:17:56 +0000
Received: from XCH-RTP-003.cisco.com (xch-rtp-003.cisco.com [64.101.220.143]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v6K0Ht4O001248 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jul 2017 00:17:56 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-003.cisco.com (64.101.220.143) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Jul 2017 20:17:55 -0400
Received: from xch-rtp-005.cisco.com ([64.101.220.145]) by XCH-RTP-005.cisco.com ([64.101.220.145]) with mapi id 15.00.1210.000; Wed, 19 Jul 2017 20:17:55 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>
CC: "bess@ietf.org" <bess@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08
Thread-Index: AQHTAFFgOlRBKe6TfkKeroOy95cn7KJbIToAgAB0hYCAAKl/AA==
Date: Thu, 20 Jul 2017 00:17:55 +0000
Message-ID: <D595C2B0.213DB5%sajassi@cisco.com>
References: <CA+-tSzwAfZZ8EyvVbXxxZgWesS_P0jSwjvcSKjT7N76iBnzhUQ@mail.gmail.com> <D594D20D.2138C0%sajassi@cisco.com> <CA+-tSzywX3t_pMj7b4k2xq=iYbAtMxYCoR4Spj63O=_perZivw@mail.gmail.com>
In-Reply-To: <CA+-tSzywX3t_pMj7b4k2xq=iYbAtMxYCoR4Spj63O=_perZivw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.60.138]
Content-Type: multipart/alternative; boundary="_000_D595C2B0213DB5sajassiciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/EsE6FfWRvjeYEtU9xYIXjqTG2O4>
Subject: Re: [nvo3] [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 20 Jul 2017 00:17:59 -0000

Hi Anoop,

The provided text is fine. Given that it is just a minor clarification text, I think it should be OK to incorporate it; however, I need to check with the chairs and the AD given that this draft has already gone through the WG LC.

Cheers,
Ali

From: <ghanwani@gmail.com<mailto:ghanwani@gmail.com>> on behalf of Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>>
Date: Wednesday, July 19, 2017 at 9:11 AM
To: Cisco Employee <sajassi@cisco.com<mailto:sajassi@cisco.com>>
Cc: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>, "nvo3@ietf.org<mailto:nvo3@ietf.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>>
Subject: Re: [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08

Thanks Ali.

May be worth modifying the sentence below to say:
>>>

8) When a 802.1Q interface is used between a CE and a PE, each of the
   VLAN ID (VID) on that interface can be mapped onto a bridge table
   (for upto 4094 such bridge tables). More than one bridge table may be
   mapped onto a single MAC-VRF (in case of VLAN-aware bundle service).

>>>

Anoop

On Wed, Jul 19, 2017 at 12:14 AM, Ali Sajassi (sajassi) <sajassi@cisco.com<mailto:sajassi@cisco.com>> wrote:

From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of Anoop Ghanwani <anoop@alumni.duke.edu<mailto:anoop@alumni.duke.edu>>
Date: Tuesday, July 18, 2017 at 10:39 PM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject: [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08


This is what the draft says about bundled service:
https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-08#section-4
>>>

8) When a 802.1Q interface is used between a CE and a PE, each of the
   VLAN ID (VID) on that interface can be mapped onto a bridge table
   (for upto 4094 such bridge tables). All these bridge tables may be
   mapped onto a single MAC-VRF (in case of VLAN-aware bundle service).

>>>

So it sounds like 1:1 is supported (that's the straightforward case where the inner VLAD ID is stripped from the encap'ed packet) and All:1 is supported (i.e. the service is blind to the incoming tag and just preserves it as is, potentially with normalization if translation is required).

What about the case for n:1 where I want some subset of VLAN IDs coming in on a port to map to VNID1, and another subset map to VNID2?  Is that explicitly disallowed?  If so, why?

That's is also supported. Refer to section 6 of RFC 7432 for different service interfaces that are supported.

Cheers,
Ali

Thanks,
Anoop

v2.23.0 | Report a Bug | By Email