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

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sun, 02 September 2018 13:09 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 B1A3A1277C8 for <bess@ietfa.amsl.com>; Sun, 2 Sep 2018 06:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.09
X-Spam-Level:
X-Spam-Status: No, score=-4.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham 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 aX2bbckfuTTd for <bess@ietfa.amsl.com>; Sun, 2 Sep 2018 06:09:19 -0700 (PDT)
Received: from mail3.bemta25.messagelabs.com (mail3.bemta25.messagelabs.com [195.245.230.83]) (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 6880012008A for <bess@ietf.org>; Sun, 2 Sep 2018 06:09:19 -0700 (PDT)
Received: from [46.226.52.197] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-3.bemta.az-b.eu-west-1.aws.symcld.net id 76/B9-28243-DF0EB8B5; Sun, 02 Sep 2018 13:09:17 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WTbVBMYRTHe+69u3ul1bWVjuSlxZiRXW0jaox hBjNpRnzAIC/dravdmd1tZ+8u5YuoRkSaJka1o93sGEVSwyjMIhQNZfIS0oYW2VCTRIrc3buR L2d+55z/c57/c+dcEpe4hCEkk2ZkDDpaIxX6EovCVmyX/XidmxAxdE4YfbaxCI/+8jCTWIHFF g5XC2JttiFsPbZVoNYpU9MSBarWylKRPm9DmrNyP8pANXGHkS9JUGU4WO3dIncioQoxyBg4Tf DJWwS3LR+4ZAIppJZBzbkOoZsDqXCwHG/B3CKceozgfV+jRxRAJcDZnnacFyVCW92QgGc5DFc /8GgIag4MfrZ6WEzRUDBS6xmKqCnwvek85macCoaXzlIPA0WB7XoLznMQfOz6LeD1Suh8Z0V8 PQxOOswinqdDa2kucpsD6pYIDlTVewcpoLH8hnfQWrC11XEXkxzPhkvd23k995imzlFvfQFU1 cfycj2UX+v0ztdATnY1wfMMqDj6huDPXsHhp63UOz8Uui4/95ooEILdccFjQkIlwT3zV++JfB wqm4dQPgovHvdqnnVgz/xFFHu+0mS4X+Qk+PoCsFzrF/IcDmesPfgYP7jZhY2vW5CoAkUrDeo UlVFLqzUyRUSETKGIlClilsgioxRyeq9MKWdMsj0Ma5Rx6R5WzqZrkzTJch1jrEHcfiXr7w7X ovyylHo0lcSkQeL43YcSJJOUqcnpKppV7TSYNAxbj0JJUgriW525CZLJBiaFSdul1nBLOtYG0 k8aKH7m4NpiVk9rWXUK32pCq8mmzCMFOHnHUcjFR5546u5xLo70clFC6FJ1TEiwOILbcQnlPq wy6f6OHvsFWtH0kAAx8vHxkfjpGYNWbfy/70LBJJIGiF+4Hfqpdca/DlycOYwzRzzNcZsz0v9 aIRmozrlqww5/57Sg59jiBvvmqryWjloq3r+kIaO/e8AUxuovXtaufrXx26urliJXXkBfbU9+ /+yK5OiBmIqZR5KaG9Y4rthrSubeXr5PetAVuKgvdKnfti3tK2dFTeydlz6vfV3cTtOTwZGYL ceysrVWpmN0k/mq3XQiLquuZGFi+acss5RgVbRiPm5g6T898obq/QMAAA==
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-21.tower-285.messagelabs.com!1535893743!8040101!1
X-Originating-IP: [52.33.64.93]
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 20009 invoked from network); 2 Sep 2018 13:09:11 -0000
Received: from us-west-2b.mta.dlp.protect.symantec.com (HELO EUR02-VE1-obe.outbound.protection.outlook.com) (52.33.64.93) by server-21.tower-285.messagelabs.com with AES256-SHA256 encrypted SMTP; 2 Sep 2018 13:09:11 -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=IH1H14sMpxPe9Lg/JTTAFuka+Qh/+iPudtUDjClR5v8=; b=YeaGpfxv9/Iw8Oan6mcOH2YXl4Kbo+GykTCRM7XR21s8sICgW1vCi4U3fKuTug6qSEpR83bxfcbjOr3ppOV4gH7DMIodcFWpuswTemWOuLQL1Yx/730Sa3yl/CaK8IYq7hPRFPmgSgbOpFAo2S1IkcHluqc6p8Ucye6Ybx6WRFU=
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; Sun, 2 Sep 2018 13:09:01 +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; Sun, 2 Sep 2018 13:08:59 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "sajassi@cisco.com" <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+GTwSFScLNHhlNZw==
Date: Sun, 02 Sep 2018 13:08:59 +0000
Message-ID: <DB5PR0301MB1909252ACFD629C614D3C9F29D0D0@DB5PR0301MB1909.eurprd03.prod.outlook.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:FBFG5yRq6vpLFJGxZusNQV2a/WzAFdom1LmbMBjJQ6X/oTFLlqZdWv1AbfXKbG4qqcA9UOir1PvOnKpbuuqkEkcmFwYtnXCvswHZQuykoECHqyq3QqjHfcL0WKnWcTKWETQISMuELv6t9Q1aBukFDDVkD+G9/vpW4FHPlcobP56GIPO15Inb3pVBqPhoCAQcK8fDfzE00E0+6FX2M3EZxDXXOY3eXuJ2qTEXmjJNBP6V67wwK3+5I6CRiY/o265xuAK7DT91HH5u2Tav/zsOtZ0LFcycNRQ+oQTxkYv5qpKN1iuLumsOeb9AU4H7XWmVzlS2DloV+waZQ/2pteRjq9jryk8SiVQYxfIMiqHgxOYYFn2GERWw8X5wAQGh7cHsy5OVZI9pRf25CK8TkHopRZ3+GS3jmtDUzHgo+gx+SfRuXrCBfBvw3/pRTjLvZTzBmNlRGTuAZ0w5E0F5dD5BGw==; 5:GFk+KIk+JEXHrmDNXG7UNz32hgix1/DWi7G+Jf48ZNhPy7S8t6/L5CVoNhffdT4dZXhMtRjsbrvXvlZzJ3QSMLGX3oSwpYqW0L0mJafvpIXJSO1dbuPZhYlRqjnOp4kJg4KSLMSLT4WqVIzLRJHK53lGwnWgKrMcG362sxIySsA=; 7:DlySHh1tEDCeVyoXa7PyWPjeqzp7fzo2fbItQPISBxZm9o6wR6r+EqTItQ0/Va1UUL3cFyoW6gG2FrYfuPqQ/astLsV3+3XWLcJQ3p+bRtUzlo2KKpPp6flkrhUl1fdgC8DOyijYtaZuVxRUnrFSA97QlfRNsLRQU2zO+8z14Ro2CpafNybJsc87/TI7ezeCU434J4XbcPA6cc/HJ066svRVldk5JvRQ+wrrZ2gk7EzacHzeDFSJsRCUEbYECGXJ
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-ms-office365-filtering-correlation-id: 556d788a-b49e-47a7-9d64-08d610d53f87
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: <DB5PR0301MB2118F3897621911151AE41B69D0D0@DB5PR0301MB2118.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(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: 078310077C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39850400004)(366004)(376002)(346002)(136003)(252514010)(199004)(189003)(51874003)(6506007)(6436002)(26005)(99286004)(102836004)(186003)(86362001)(790700001)(6116002)(3846002)(4326008)(486006)(7696005)(5660300001)(53936002)(25786009)(5250100002)(316002)(2906002)(2501003)(606006)(476003)(33656002)(1730700003)(55016002)(8676002)(81156014)(54896002)(107886003)(66066001)(6306002)(81166006)(5640700003)(74316002)(6916009)(97736004)(9686003)(7736002)(54906003)(236005)(105586002)(5630700001)(8936002)(2900100001)(2351001)(106356001)(72206003)(68736007)(14454004)(478600001)(5024004)(256004); 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: KLS/HrexQgqY/OTJ0qv0qT2TOmkdi3kftWnBF/4ytvwWgy1lJkIl0BEp7uUDBZ8P+BaEWj1HZH8IAaJkpeRNT+R1I1mZRwrxdPp6L1wi0o7tlMSTIwUBdYdqEKeAXwgJ4jfxUnT+G1n5nFdVTF88BHJoYXCRz7I04SlPekrzvzA4Mshlat3yTJRJp6EgdFMYM9ZZ/PEA74z//iTteK56YCS5Emb2Dtpo5CANJ1Ik88Doe1XxfI6+0yl9QPyocWtmegi/+KJHUoIR2DN9MhH1Jx00OVOIQXbKWl3sMswDyO4QpeKyhWaSr2wz0H8U4bHKhWReGD3xygzutmR8f6NGzTHD8l4sjfhzC2y00rw3rl4=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB1909252ACFD629C614D3C9F29D0D0DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 556d788a-b49e-47a7-9d64-08d610d53f87
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Sep 2018 13:08:59.8184 (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/VQ988_KaH54yz0HXacxhVDszoHg>
Subject: [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: Sun, 02 Sep 2018 13:09:23 -0000

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.

a.       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?

b.       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?

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


___________________________________________________________________________

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