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

Krzysztof Szarkowicz <kszarkowicz@gmail.com> Tue, 04 September 2018 09:14 UTC

Return-Path: <kszarkowicz@gmail.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 7EBC9130E64 for <bess@ietfa.amsl.com>; Tue, 4 Sep 2018 02:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5KKIkcmBKO1m for <bess@ietfa.amsl.com>; Tue, 4 Sep 2018 02:13:58 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC67130E18 for <bess@ietf.org>; Tue, 4 Sep 2018 02:13:58 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id u24-v6so1371282pfn.13 for <bess@ietf.org>; Tue, 04 Sep 2018 02:13:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=hCBeo+Q1bP1caQQdWUUCM/7Itl4OxtS9Arr1+i9zUko=; b=WBhyiwkiUYJpL8q+i+Glk003+D6ZdBMA6hyo07cI167jhVzfT9llCiMTGwL7neCQ+Q KezBm2Eu241I3P19nWKwEvA2qf9yuxohOX4dXhBhZ4ZDy3pFK2r1NoS6VuW63AXab9fp SctaqsVhutfNhfH6ohDdi27CaxVZ5pDcHNXIJNfrVVGjmOGjmpENvcu8VOL55wi2zLq5 LCt5I6XnBm+4v+XZEicfyZ0HRkAIzfIJ8T0e3qJouk1mfWSwmbXlLktA+HomLz5s0Ytk uG2orrloZ3BZUzXY6xDTqcObVhTzFtppug79GZlwJmYRiWZEyfDGwqInPMrxGj2mIFTE Sbmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=hCBeo+Q1bP1caQQdWUUCM/7Itl4OxtS9Arr1+i9zUko=; b=W8gAiNWtyPyJCw0Ves5ZL/3KQW0hk10E+HUFUld4zWr6sC7XxMgpRa/RLL5r4Qvbud 5BwluNXP8GwqpcSUg6UqhD9eXHyUBRXOWfRCezj+xzjChOfHUEJJG5zIG6Qu2cK+8RN2 o1iwRIakerWDO73vWftI315KwYmAHtq1D6pzkYo9th/bf08umF9LBZsMIVYdVFnN6YI3 opzBpPXoI0v+AoRb76UAMFKlgOzV36VuI6FV8IRLtErlgKzEmMFcbfg5EcBYHY46zPy4 9NdasZjcgIXs+PiJmO20sCDoPZgAIkkMCvG1OAFkGSAimXWOuZfsrvsLXtusNgGMAuO/ NzXQ==
X-Gm-Message-State: APzg51CGZ9sMgPqzNtZ1cHLWiup28b9Nn9i9aOxTdI/O76oRJQAEYukU tEH6aAcyYqGSDKzoM1gleAU=
X-Google-Smtp-Source: ANB0VdYE5HkM7BTbBcmwV7/Hiw6/AdSMT5nFi/ufXEAAAd9EGS08oOwMIK2J8Yf39ainwGNd5n1+Hw==
X-Received: by 2002:a63:4b47:: with SMTP id k7-v6mr20092463pgl.351.1536052437531; Tue, 04 Sep 2018 02:13:57 -0700 (PDT)
Received: from [10.104.42.195] ([66.129.239.13]) by smtp.gmail.com with ESMTPSA id t21-v6sm34105569pfi.73.2018.09.04.02.13.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Sep 2018 02:13:56 -0700 (PDT)
From: Krzysztof Szarkowicz <kszarkowicz@gmail.com>
Message-Id: <8C36BC2A-377E-44AD-8D4F-9067126E7A62@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9A5E3BE6-A299-4DB4-8477-B0F1428F5045"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 04 Sep 2018 11:13:52 +0200
In-Reply-To: <DB5PR0301MB1909879542132AF7A6C01AF59D030@DB5PR0301MB1909.eurprd03.prod.outlook.com>
Cc: "Ali Sajassi (sajassi)" <sajassi@cisco.com>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, Rotem Cohen <Rotem.Cohen@ecitele.com>, Shell Nakash <Shell.Nakash@ecitele.com>, "bess@ietf.org" <bess@ietf.org>, Ron Sdayoor <Ron.Sdayoor@ecitele.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
References: <DB5PR0301MB1909252ACFD629C614D3C9F29D0D0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <E8C974A3-8D6A-4B21-91AA-766C8E7DE8EF@cisco.com> <DB5PR0301MB1909879542132AF7A6C01AF59D030@DB5PR0301MB1909.eurprd03.prod.outlook.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/u1PHmj7fRB6-B8rdWLgLjXWAOyY>
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 09:14:01 -0000

Hi Sasha,

To use LAG in A/S mode on per VLAN basis, you can use ‘hack’, where you use preference-based DF election (draft-ietf-bess-evpn-pref-df) to ensure with the configuration that *all* VLANs on given ESI use PE1 as DF, and *all* VLANs on that ESI use PE2 as non-DF. Then, you need to have a mechanism to signal from PE2 to the CE the link standby status (e.g. via LACP, as used in MC-LAG deployments; or, I could even imagine per link CFM/LFM/E-LMI), so that CE doesn’t use link to PE2.

Thanks,
Krzysztof


> On 2018-Sep-04, at 10:39, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> wrote:
> 
> 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 <mailto:Alexander.Vainshtein@ecitele.com>
>  
> From: Ali Sajassi (sajassi) [mailto:sajassi@cisco.com <mailto:sajassi@cisco.com>] 
> Sent: Tuesday, September 4, 2018 8:00 AM
> To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com <mailto:Alexander.Vainshtein@ecitele.com>>
> Cc: 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: 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:
> The default DF election procedure only involves the PEs attached to the specific ES
> 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.
> ___________________________________________________________________________
> _______________________________________________
> BESS mailing list
> BESS@ietf.org <mailto:BESS@ietf.org>
> https://www.ietf.org/mailman/listinfo/bess <https://www.ietf.org/mailman/listinfo/bess>