Re: [bess] A question regarding Single-Active ES redundancy mode and DF election in RFC 7432

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 04 September 2018 08:39 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 F1D3B130E62 for <bess@ietfa.amsl.com>; Tue, 4 Sep 2018 01:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.779
X-Spam-Level:
X-Spam-Status: No, score=-1.779 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_FILL_THIS_FORM_SHORT=0.01, 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 iDYdGOKpJWrA for <bess@ietfa.amsl.com>; Tue, 4 Sep 2018 01:39:25 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.3]) (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 CA60C130E58 for <bess@ietf.org>; Tue, 4 Sep 2018 01:39:24 -0700 (PDT)
Received: from [85.158.142.103] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-3.bemta.az-a.eu-central-1.aws.symcld.net id E8/A5-02981-BB44E8B5; Tue, 04 Sep 2018 08:39:23 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTWUwTURSGuZ1pOxhGhwJyBJdYNVFDCxWNqGC MS0KiJhqjiRIDg4ztxDJgW2I1PpCgPpRFxWpEkYpWBVRQ4oK4I8oSQUANBkWCImpNtGoqQXG5 04vby8mX8//3nP/ezDCU5qMqghHsNsEi8WatagQ9M/KCXVe7uCAppqssKq6soYiKe9+SQy9QJ Dq/nVcmut2DihWKdUpRSs2wpyhNx7+/VmdWvkD2Xk8NlY3KepADjWBo7hgFX4vO0A4UyGg4pw KcrYmyoOFeICgvcKhlQcUlQPXpbpXMoVw07N3l9J+muIcI+r0N/tMhXDK0Dg4piCkFOq8MKgn PheOf+pDMNDcZDlZ5KJlZjofKr2dVZNs+BD15br8pEG/b5yWREDcaBprP+IdSXDh09bn8DBwH 7msPKMJh8PblDyXxp0LPq1JE+hPh4PNiNeFx0OHK9acG7rYaTuSfoolggIbym8ODlkPjkSZsY jBPggtv1hM/vmVzz08V6UdBVV0isWfCDt89FeHtcKWmfXjMeKjI76XJ2cv4fd2uYWEstOQ7h0 NUqOB+e4tyD9Id+udyhCXorSylD/lfKRiaivowM7g/Dapqo4llIjhze9WEp8LO4iPqf/tHkbo CzUm1iEaTLZ0XzTpDTIzOYIjVzcAUq+e36Xi9kKXbIEg2C49VPb/FqrduTd9gTtNLgq0a4Q8s bbPCWIN8OcY6NIZRaMPYckNBkmZkakbaVhNvNSVbssyCtQ6NZRgtsL5FWAu2CEbBvlE046/0t wxMkDaUbVyIZdaayadbRSORmtFSpjknr5Bi6p87cW3z15K7+3Ed+iDXZ7kHCikNLWVIQkQ4+0 XewMkjTFnSnwW//4QONC4ihEUBAQGaoEzBki7a/tc9KJxB2hDWIU8JEiXbnxweHFGBI7pv5ck RbfxfKSIbZXupEterwKyVF/e3P250tVnilPUTzrcab6yNXuP1zY8/d2PawOFHb5bcvrls1JOh jJPi59WdAyu9YXd/TukumZIwyx6s7r9aOyO+K6Etauad7k3ipJqky5G7qq5XXHoSvLtj6B27a nR8/Qo6+mK/r7OBdZx6OntysScvcl51bEFh2vyRWtpq4g3TKYuV/wV4lEnsBAQAAA==
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-28.tower-228.messagelabs.com!1536050358!6232223!1
X-Originating-IP: [52.27.180.120]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 29882 invoked from network); 4 Sep 2018 08:39:21 -0000
Received: from us-west-2c.mta.dlp.protect.symantec.com (HELO EUR01-HE1-obe.outbound.protection.outlook.com) (52.27.180.120) by server-28.tower-228.messagelabs.com with AES256-SHA256 encrypted SMTP; 4 Sep 2018 08:39:21 -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=0D+tcozrtpc3MNICi+qLzBhzqYbKz+8Me0w3+Y3B2H4=; b=m5GFdGnOP/CFvnKpIDVQ72JNKW7LP0ovBGwm3NrOwTEBQB3A8EO2DlO9Qhy4xdI/qSZUpLrlQPUeKV/5rLFiiuXznjvK4ki6EgFfa21FgAQ5eSq+u3+6Svj7YjEK2BFKiAnAnkxYCMZ1f5TsUt+PIJydbm3xtR9OUrQWzcIPFeY=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB2118.eurprd03.prod.outlook.com (10.167.228.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1101.14; Tue, 4 Sep 2018 08:39:16 +0000
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::95ea:6ef4:60c3:bc68]) by DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::95ea:6ef4:60c3:bc68%2]) with mapi id 15.20.1101.016; Tue, 4 Sep 2018 08:39:16 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
CC: "bess@ietf.org" <bess@ietf.org>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, Shell Nakash <Shell.Nakash@ecitele.com>, Ron Sdayoor <Ron.Sdayoor@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>
Thread-Topic: A question regarding Single-Active ES redundancy mode and DF election in RFC 7432
Thread-Index: AdRCuX4OWvLxpG+GTwSFScLNHhlNZwBOYp8AAA2H9jA=
Date: Tue, 04 Sep 2018 08:39:16 +0000
Message-ID: <DB5PR0301MB1909879542132AF7A6C01AF59D030@DB5PR0301MB1909.eurprd03.prod.outlook.com>
References: <DB5PR0301MB1909252ACFD629C614D3C9F29D0D0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <E8C974A3-8D6A-4B21-91AA-766C8E7DE8EF@cisco.com>
In-Reply-To: <E8C974A3-8D6A-4B21-91AA-766C8E7DE8EF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5PR0301MB2118; 6:L7HL0LxaKkEdZMECsqbOH1J/5CrAZSSoZOFb95F9wZCej8q4MmW8ozwLYP/1mJEzhiTKIGXOM0lHrPoO+Z60FiETVqDlvmmWS600nQgTCWHV46wNCUcM+EnZKCf8rIBNtqhoYuvSjmIku5bO6fncVXCARdheeJIML5BlVcn8ZoRfBuUoxveALUWHludC5SejxVp0C0Cr21PHgtU7uwCuP77n2+RAdf+qofTu08ZdduhnYWM33SOp6hwSnCEWLtG+A+bYEJY6TA3FTtY/fSawjQ7fkmGe5XHviXlQjG24tpGyCqjIuMaMtRzq2VJwKFio27sC8JPzO/q7pqnWYJ+yTREuYQhG3SYOmW6jjOoMdRfB15Il/V2qYHwkVUZ+gKlLjDGGUkEHQ6QftcP33eO1K42i+d3SEDa4u3lkrDUIDDm/KbIb/HcQGSzi+FxIGjg98QwxlrTX+lyIpYe4uqm/SA==; 5:ghzULZzGoOrYsQ+l7eSRZMjBPzjBHO9H5IkyG3/UKmFZUUVQp1l4IphaDigds7T4EisbXLRy9Wj5IdAVQ9/tk4Rn69lMx2fY8yw1M67TVA1HBATO/ZoGL+cOysyWWVSD2Gjhcv+qBUdKYpMDAgZbWuahPSY1E/m+ipmbzEZazLc=; 7:It/rgjOww2oDgmaMZm62PjeDHJSfD6zfWyojQ5tQw9wA2ayCsOZpr0CC5Bet4xuzhwu/yIlVvy2HTjP2B0v4CZFfxZVXo4fXO2FpIkSajmWKheE7RW3V/jAbhGE1hAlh8KkmPT2nHxy3D73ycgI0zL10Wwq2L7sKkn6X4u5ky3jxwmO97qrTyXJpEPVlYyY1TdJQ/cyPfHa+Nk70vTP4T9He92eoi1I8wvAhY+LKwbduV8DwhS4DtsSjGQ/LEXa+
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-ms-office365-filtering-correlation-id: 38c423fa-7040-4679-6cee-08d61241e663
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB2118;
x-ms-traffictypediagnostic: DB5PR0301MB2118:
x-microsoft-antispam-prvs: <DB5PR0301MB21187717609AFC48CB7E3E169D030@DB5PR0301MB2118.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(95692535739014)(21748063052155)(279101305709854)(21532816269658);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231311)(944501410)(52105095)(93006095)(93001095)(3002001)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699016); SRVR:DB5PR0301MB2118; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB2118;
x-forefront-prvs: 0785459C39
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(396003)(366004)(136003)(376002)(346002)(252514010)(199004)(189003)(54094003)(51874003)(229853002)(99286004)(26005)(53546011)(6506007)(6436002)(102836004)(186003)(86362001)(76176011)(790700001)(6116002)(3846002)(476003)(11346002)(446003)(606006)(7696005)(486006)(5660300001)(53936002)(25786009)(5250100002)(4326008)(316002)(2906002)(33656002)(6246003)(107886003)(6306002)(55016002)(8676002)(54896002)(81156014)(81166006)(66066001)(74316002)(6916009)(97736004)(9686003)(7736002)(236005)(54906003)(8936002)(2900100001)(478600001)(106356001)(72206003)(68736007)(14454004)(105586002)(5024004)(256004)(14444005); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB2118; H:DB5PR0301MB1909.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: 2t+VbFZrTtzYMjekbTgvXmSgy3gmGn5h+gEsZVExZ8uHbTTAjwqBbYvkBigeg4SfoFRgCQKns8oU//6UNo11kCoJjGo16WNXVNSc2uqkPfrsBVztzHgzy3gdRc3yius2RBU4ZVYaVVRYR4frlCj0oiNSzPC20Fq70FL4q0N3G/wrQcZnXhy/sVedwP73F9sCLFmygb5LDwXbCEsZA3MzwFvTEu4X5tbreS79wdnwArfkAIx7QNrRvO/QwKjgdGXUQiqni/KB3ExEII9Tn5N9aduCGujO/kUTykI7o8bvoAMpO09cdGLegKy9o+mEUEFPVAoKxl+W4Ztape572tdT2XqsMoe/yTn9zzKrI/6A2JA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB1909879542132AF7A6C01AF59D030DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 38c423fa-7040-4679-6cee-08d61241e663
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Sep 2018 08:39:16.5391 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB2118
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/FrLFTtyms6f3sgXqFrMQJhV7hVs>
Subject: Re: [bess] A question regarding Single-Active ES redundancy mode and DF election in RFC 7432
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 04 Sep 2018 08:39:27 -0000

Ali,
Lots of thanks for a prompt and detailed response.
It matches my understanding of the situation with Single-Active Redundancy Mode of Ethernet Segments in EVPN.
In particular, your confirmation that “You cannot use LAG to do active/standby on a per VLAN basis (aka EVPN single-active)” was quite important.

I have also noticed that Single-Active is not mentioned at all  in RFC 8388<https://tools.ietf.org/html/rfc8388>. I wonder what this means with regard to actual deployment of this mode.

Last but not least, I wonder if the expired draft<https://tools.ietf.org/html/draft-brissette-bess-evpn-mh-pa-01> on Port-Active multi-homing mode for EVPN will be refreshed and if, as part of such refresh, any details on the control plane of EVPN would be provided.

Regards, and, again, lots of thanks,
Sasha

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

From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com]
Sent: Tuesday, September 4, 2018 8:00 AM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: bess@ietf.org; Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>; Shell Nakash <Shell.Nakash@ecitele.com>; Ron Sdayoor <Ron.Sdayoor@ecitele.com>; Rotem Cohen <Rotem.Cohen@ecitele.com>
Subject: Re: A question regarding Single-Active ES redundancy mode and DF election in RFC 7432

Hi Sasha,

I don’t see any contradiction between the two statements from RFC 7432 that you mentioned below. For All-Active, DF election is for BUM traffic of a given VLAN (or group of VLANs in case of VLAN bundling) in the egress direction toward an ES. For Single-Active, DF election is for all traffic of a given VLAN (or group of VLANs …) in both directions of an ES. Now with respect to notification of active VLANs to a CE device: MVRP mechanism that is mentioned in the RFC is an IEEE standard way of doing such thing. However, if the CE support E-LMI, then that protocol can be used as well. Regarding LAG, it can be used to connect a CE in an active/standby mode where one link is active and another link in standby mode (assuming two-link bundle). You cannot use LAG to do active/standby on a per VLAN basis (aka EVPN single-active).

I will be travelling over next few days with limited email access, so please expect some delay for my responses.

Cheers,
Ali

From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>
Date: Sunday, September 2, 2018 at 6:09 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>>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com<mailto:Michael.Gorokhovsky@ecitele.com>>, Shell Nakash <Shell.Nakash@ecitele.com<mailto:Shell.Nakash@ecitele.com>>, Ron Sdayoor <Ron.Sdayoor@ecitele.com<mailto:Ron.Sdayoor@ecitele.com>>, Rotem Cohen <Rotem.Cohen@ecitele.com<mailto:Rotem.Cohen@ecitele.com>>
Subject: A question regarding Single-Active ES redundancy mode and DF election in RFC 7432

Ali and all,
I have a question regarding one of the aspects of RFC 7432, namely operation of the default Designated Forwarder (DF) election process on an Ethernet Segment (ES) that operates in the Single-Active Redundancy Mode.

RFC 7432 defines the Single-Active Redundancy Mode in Section 3 as following:
“Only a single PE, among all the PEs attached to an Ethernet segment, is allowed to forward traffic to/from that Ethernet segment for a given VLAN”.

The same RFC in Section 8.5 also specifies that the DF for a specific VLAN on a multi-homed Ethernet segment (ES) is the only PE attached to this segment that is responsible for sending BUM traffic for this VLAN to the CE. It also defined the default DF election procedure that elects a single “live” PE on the specific ES as the DF for each specific EVI that is represented on this ES.

These two definitions look contradictory to me, because:

  1.  The default DF election procedure only involves the PEs attached to the specific ES
  2.  In the Single-Active Redundancy mode the elected DF for a specific VLAN must also be the only PE that is allowed to forward traffic received with this VLAN from the CEs to the peer PEs. It is not clear to me, how this can be achieved.
     *   The RFC mentions MVRP as a possible method to notify the attached CEs that a specific PE is NOT a DF for a specific VLAN in the case of an ES that operates in the Single-Active Redundancy Mode. Does this mean that CEs that are attached to a multi-homed ES operating in Single-Active Redundancy Mode SHOULD support MVRP?
     *   Are there any alternatives to MVRP that can be used for this purpose. In particular, is it possible to use Ethernet Local Management Interface (E-LMI) as defined in MEF-16<http://www.mef.net/resources/technical-specifications/download?id=42&fileid=file1> for this purpose?
     *   The RFC mentions LAG as the method to connect the CE to a multi-homed ES operating in the All-Active Redundancy Mode. Is it possible to connect a CE that uses LAG to a multi-homed ES operating in the Single-Active Redundancy Mode?

Your feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto: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.
___________________________________________________________________________

___________________________________________________________________________

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.
___________________________________________________________________________