IETF Logo Mail Archive

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

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Wed, 19 July 2017 07:14 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C3813178D; Wed, 19 Jul 2017 00:14:19 -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 sVWglFrZmfB0; Wed, 19 Jul 2017 00:14:18 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12EDA131BF4; Wed, 19 Jul 2017 00:14:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5666; q=dns/txt; s=iport; t=1500448458; x=1501658058; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=HL+TUHHxjtl1oNBgKTA9LIK8LtkcgomA69JpY9infX0=; b=e4+IFNodq6K4DNI+kl0rjIbg41oYEDc4ljNzqaZ8fTsDjsLE5u6tqeMf BzDU/gQgud8D8Uyyr7o2c1b5hZMeuI7RgSJg3UdazgGAQo3gRm/HhW1zw 3U+/SMGsgi4XUgb21us/k+UubKl+iBVhppg2F+E4holQv4QEMJqMgVYUI 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DnAABwBW9Z/5NdJa1cDgwBAQEBAgEBAQEIAQEBAYJva2SBFAeOBJFrkFiFLIIRLIUbAoNWPxgBAgEBAQEBAQFrKIUYAQEBAQOBCQIBCBEDAQIoBzIUCQgCBAESiUtkELFBiwUBAQEBAQEBAQEBAQEBAQEBAQEBGgWDKIUugySFCoVUBZEgjhYCh0mMTJIvlVcBHziBCnUVhSM5HIEoP3aHRoENAQEB
X-IronPort-AV: E=Sophos;i="5.40,380,1496102400"; d="scan'208,217";a="271803272"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2017 07:14:17 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v6J7EGmB014860 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Jul 2017 07:14:17 GMT
Received: from xch-rtp-005.cisco.com (64.101.220.145) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Jul 2017 03:14:16 -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 03:14:16 -0400
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Anoop Ghanwani <anoop@alumni.duke.edu>, "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: AQHTAFFgOlRBKe6TfkKeroOy95cn7KJbIToA
Date: Wed, 19 Jul 2017 07:14:16 +0000
Message-ID: <D594D20D.2138C0%sajassi@cisco.com>
References: <CA+-tSzwAfZZ8EyvVbXxxZgWesS_P0jSwjvcSKjT7N76iBnzhUQ@mail.gmail.com>
In-Reply-To: <CA+-tSzwAfZZ8EyvVbXxxZgWesS_P0jSwjvcSKjT7N76iBnzhUQ@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.104.24]
Content-Type: multipart/alternative; boundary="_000_D594D20D2138C0sajassiciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/XLLl6u20uJDZyfPwkYyHpZwoDCM>
Subject: Re: [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 07:14:20 -0000

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