[bess] A question about RFC 8317

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 20 December 2018 11:30 UTC

Return-Path: <Alexander.Vainshtein@ecitele.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 3725B131056 for <bess@ietfa.amsl.com>; Thu, 20 Dec 2018 03:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 EwuGIml7A4Cz for <bess@ietfa.amsl.com>; Thu, 20 Dec 2018 03:30:00 -0800 (PST)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBBCF131054 for <bess@ietf.org>; Thu, 20 Dec 2018 03:29:59 -0800 (PST)
Received: from [85.158.142.193] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-b.eu-central-1.aws.symcld.net id F9/1C-08788-53D7B1C5; Thu, 20 Dec 2018 11:29:57 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA2WTf0xTVxTHue+9vj4rXZ4F7aHoGNVp0q1dO4W VmSUuLkvNRmJiYiLDaVsebZNSWFuywmZiwBAKmcoGG9QyEAiWbmNCcHPxD1nBYGFLtkYmmnTI LKvFUI3DH8Bge32vZZr9c/O55/s95557kkPhkmlKRjEuJ2O36a1yUkTsyh5yKfOOZRerB45qf WNtuNYb3qsNP1khtVHPsEAb/7mW0J6JdSNt5Ms+4R6hLnbKi3TNywMCXU/PIqa7XjMp1IVvhj BdvGOe3E8WCSw2Q7nrqMA8u5RTcS4qci2OnxYeR/NBUQMSUQTdhUPtxAhKXCT0KQxqQk8E/GU awYWGWaIBraNI+g0Y/CpMJjiTLoTZmToyYcLpJgw+80U5IYOWw92BAOJNO2DcdwbjWQWxySE8 wQT9IvR9W8+xmD4M5+vcHCN6Ezwe/5rz47QUbkY6OAY6E2Z+nSB53gix26sC3m+A6dmziI/nQ uvvXiHPWyDU0ch9B+jrJEROrCYFJdxvacF5LoSRpvNsIYrlrTB05zDvjyB41N6X9Cug/+ovSb ZCbO5Ekp8H/yczBJ8Qx+F+KEDwhTZD+418Pv6bAGruLXJdS2gjXPX+lUyIYNDe/BjnxyWD8DU 3Oo0Unqd+7eHG6kbga2vGPdyYNkCwLULwJht8P9+Y5Jeh89IDkueXoPfsXTzFPw3fxp6NUyzv Bl+Lmg/nQt3oLZx/qwfB5+6RtZoLUzfwlKm5cUaYirf9MEWk4mNXJrG15N7lT1HKtDQfRv9Pf h1Go4FkQy9A6zdXEJ/cjWDF35X8QRbci14TPp3ciaR+pDXYLSazs0xvsSo1arVSo9mpzFfmva bSVysNKqZSaWRsTrueFVX6Dx0qR1WZ0VqisjHOQcSuU8kHZMFF1HnOFEBZFCbfKFbszS6WPGc oL6ky6x3mI/ZKK+MIoM0UJQfxnWpW22BnTIyr1GJldzIlA5UuzxSv/5iVxY4KfZnDYuKlcfQO NTX8zxc45W+tb8WpP7gzzp31/b1enBpzP/TiEsJWbmNkUvGDxAt0ooS50rb2QGrvQ2iLLEOM0 tLSJOkVjL3M4nxWn0NSCskzxPGP2CrpFptzrY85tkWMbdE6hCVadOr/k2TH0aBHki0KhqR/52 nejhlLty/ccu8/WBT885VHddXN+cX9B7apt31HBfbFDZd3HenuzKP2FLy6+73JTTnrpTuKmKa Ll4LuH5c8q35Z+bsFh0xSLT1x4aGoag7a00qNK28tm7LcA7k5bxa8v+7gobaTtccKfdsVCy1q 2+WTsdGdXV5dVE44zHqNArc79P8CwofL8vIEAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-35.tower-238.messagelabs.com!1545305392!3326808!1
X-Originating-IP: [52.27.180.120]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.14.24; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 27098 invoked from network); 20 Dec 2018 11:29:55 -0000
Received: from us-west-2c.mta.dlp.protect.symantec.com (HELO EUR04-DB3-obe.outbound.protection.outlook.com) (52.27.180.120) by server-35.tower-238.messagelabs.com with AES256-SHA256 encrypted SMTP; 20 Dec 2018 11:29:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3ojYa8k7H7kykxWuXzGttm29TYQIBwku8iVw14etgqY=; b=SF/R/1vaLTz5HCpknDjeJYxbbTKx/ozSq0eFCM/SIQqIa9PwIxfGJCwMtTG5g3Py4QEnxrydvseGgyyKf32CZ4BbQHP/RUgnvUbUNcaaWy/WYBiE49Ja4ATiXaznZ9Zgsu/3UFVO1EtRrJMnSdC+NliEkgRWb8OZ4t20t1qpGkc=
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com (52.135.146.29) by AM0PR03MB4609.eurprd03.prod.outlook.com (20.177.40.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1446.19; Thu, 20 Dec 2018 11:29:50 +0000
Received: from AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::dd0e:6be2:6377:6f6d]) by AM0PR03MB3828.eurprd03.prod.outlook.com ([fe80::dd0e:6be2:6377:6f6d%4]) with mapi id 15.20.1446.020; Thu, 20 Dec 2018 11:29:50 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Ali Sajassi <sajassi@cisco.com> (sajassi@cisco.com)" <sajassi@cisco.com>
CC: "Samer Salam (ssalam)" <ssalam@cisco.com>, "John E Drake (jdrake@juniper.net)" <jdrake@juniper.net>, "ju1738@att.com" <ju1738@att.com>, "sboutros@vmware.com" <sboutros@vmware.com>, "jorge.rabadan@nokia.com" <jorge.rabadan@nokia.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: A question about RFC 8317
Thread-Index: AdSYUr9cSCgYcdt7R1u6vcshLnORdA==
Date: Thu, 20 Dec 2018 11:29:50 +0000
Message-ID: <AM0PR03MB38289E905EE9421BA529727B9DBF0@AM0PR03MB3828.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM0PR03MB4609; 6:42vle673m1mo4cNCI5uvGSo1qthCeIWMlTMCOmwN0+yx78AhpWVqjhrYYnIqYL8HELqZ+yhYUwa4/wFLgTCwY07rQHal8bZ0DmQ5smlj3BULgvK0ID6UH0DdkXatQJwV0/vRn2FvpLbpXCxXG2KxMKRzw1EnitfwDYlHlcj7m6xVI/WsV/fOkn/qgFDUSxv6e/F2hnt4O+AJUpOM3S4ZIuICd7X98UZJSV/6hyQzxKD2VcBOx+VYIzu36uFanozdkfFe/hudw4u2xeFIhULyh1LQPztQlX1LA8/BIeZ14BvhXryiQ83NFoa5Hvjhj0vOw53VUC8R8cVMqJ9M9gL/SPWnJ8YB8FqcHHp6MWKaLZcgG2OxHVtSFH8Ichm2RsHPNdRIoWIqU1ddjgN34jWOt7PiFKlxuyk3pCW+WwbieoMWHraJCpaz4TI5VTQjGt11JrFO3UjhscVZ3kkf25ZRXA==; 5:zBmOUYhzoa/mLo4Tnow+56X6+yy93mys1fz3rMUpYhZFDUEqGOx4jOGJ3CdGYaQKVKoZLlDb5ksj4syn0Aiem4jTDRF+vFLmbWwhUxmRkwzw2fmQxJiJDVaRjbO972kDYr4pwZcYhZtSVbGaBHa3XYDPd+iFfMhNtKJubGN77ow=; 7:H5qSus0R+QhxtvrwwDd+MfWUmDqGqQ+LBTd1r0mfzTeiAF1dKl9bFtcfBq8Kb5jbkwyA9XMbRufE7lNffQPh+6VzZZmFnKWQJlW0aCbkd2rJt9Jig/abtif15Ic33VSJ93qAGAeBaXBzSS3tK0ETtw==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 608efbeb-ea2f-40cf-5fa8-08d6666e7455
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(49563074)(7193020); SRVR:AM0PR03MB4609;
x-ms-traffictypediagnostic: AM0PR03MB4609:
x-microsoft-antispam-prvs: <AM0PR03MB4609385079BD7C412BDCC8F19DBF0@AM0PR03MB4609.eurprd03.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(3230021)(999002)(5005026)(102415395)(6040522)(2401047)(8121501046)(3231475)(944501520)(4983020)(52105112)(93006095)(93001095)(10201501046)(3002001)(6055026)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:AM0PR03MB4609; BCL:0; PCL:0; RULEID:; SRVR:AM0PR03MB4609;
x-forefront-prvs: 0892FA9A88
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(396003)(346002)(39860400002)(376002)(51874003)(199004)(189003)(2906002)(5660300001)(14454004)(8676002)(81156014)(81166006)(186003)(53936002)(72206003)(99286004)(478600001)(861006)(25786009)(68736007)(316002)(4326008)(26005)(8936002)(86362001)(74316002)(7696005)(7736002)(6506007)(54906003)(102836004)(71200400001)(71190400001)(99936001)(476003)(33656002)(256004)(606006)(486006)(106356001)(6306002)(9686003)(54556002)(236005)(54896002)(105586002)(790700001)(3846002)(6116002)(66066001)(6436002)(733005)(97736004)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR03MB4609; H:AM0PR03MB3828.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: nGsWWYN4Ue53lqS7T6lGR2JG8AJwv0p6HHTvevEQ/Ch4AAR8NuI535CqTY86CYWQ62KHjn2QsXdXxCfIW/xZZZP+JHrkG3sCs2d10ipZ8B1fCEmMJLpzjeW2UsXb+gQEW6u0KsF3pr3/wM/7ReHX/f8iexpIMZLRO9SfjM0TeFT02xXN36LE/9MbD663KQLsxwA8OjK+8I9fznEDEcE4tsj9EQaS6l9uI1u/BH/8P3LhyFrzYiPKSwDIP2bieMrPB9W24m+/WaufElfc38pXIWMvzzE2kyaoLyDcoYnBw4D+0FqlLgyDq32O8xfXcWWv
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/related; boundary="_006_AM0PR03MB38289E905EE9421BA529727B9DBF0AM0PR03MB3828eurp_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 608efbeb-ea2f-40cf-5fa8-08d6666e7455
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Dec 2018 11:29:50.2781 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR03MB4609
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/XIukgNU3mVjrIpYetf7_1z2mhmY>
Subject: [bess] A question about RFC 8317
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 20 Dec 2018 11:30:04 -0000

Ali and all,
I have read RFC 8317<https://tools.ietf.org/html/rfc8317>17>, and I would like to clarify a question dealing with Leaf ACs of an EVPN-based E-Tree service on All-Active Multi-Homed Ethernet Segments (MH ES).

The reference model for my question is shown in the Embedded diagram below.


[cid:image002.png@01D49865.895588B0]

It shows an EVPN E-tree service with one Root customer site and two leaf customer sites, where each Leaf CE is dual-homed to the same pair of PEs using two different All-Active multi-homed Ethernet Segments.

Suppose that the scheme with two RTs (one identifying the Root site and the other identifying the Leaf sites) is used as described in 4.3.1.

Suppose also that each MAC-VRF uses per MAC-VRF label assignment as defined in section 9.2.1 of RFC 7432, i.e., advertises exactly one EVPN application label that identifies it as the Egress MAC-VRF, while the disposition of the received Ethernet frame within this MAC-VRF is based on the destination MAC address. In this case the per MAC-VRF label can be also used as the "aliasing" label in the per EVI EAD route.

PE-1 will receive and accept per EVI EAD routes for both MH ES for PE-2 and PE-3 with the corresponding "aliasing" labels.

Suppose that MAC-VRF in PE-2 learns some {MAC, IP} pair  {X, Y}  locally from the Leaf CE-1 and advertises this pair in the EVPN MAC/IP Advertisement route. With the "two RTs" scheme this route will be accepted by the MAC-VRF in PE-1 but it will not be accepted by the MAC-VRF in PE3. As a consequence:

-          MAC-VRF in PE-1 will know that this pair has been learned from the "blue" all-active MH ES, and therefore can decide to send locally received unicast frames with destination MAC address X to PE-3 using the corresponding "aliasing label". No other labels will be included in the EVN encapsulation of such  frames because they are received from the Root AC.

-          MAC-VRF in PE-3 will not know anything about MAC address X, therefore, when it receives an EVPN-encapsulated frame with this destination, it will treat it as an "unknown unicast" and flood it to both Leaf CE-1 (where it should be sent) and to Leaf CE-2 (where it should not be sent).

Is this what is really supposed to happen in this scenario? If not, what did I miss in the E-tree EVPN solution?

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________