[bess] [BESS] Discussions about DF-election FSM.
<wang.yubao2@zte.com.cn> Fri, 12 April 2019 09:19 UTC
Return-Path: <wang.yubao2@zte.com.cn>
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 A4A6112017D for <bess@ietfa.amsl.com>; Fri, 12 Apr 2019 02:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 y1YKCWedK6Jn for <bess@ietfa.amsl.com>; Fri, 12 Apr 2019 02:19:31 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 2378F12013C for <bess@ietf.org>; Fri, 12 Apr 2019 02:19:30 -0700 (PDT)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Forcepoint Email with ESMTPS id 0801EAC054C91E8A77FD; Fri, 12 Apr 2019 17:19:29 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse02.zte.com.cn with SMTP id x3C9JDiO053571; Fri, 12 Apr 2019 17:19:13 +0800 (GMT-8) (envelope-from wang.yubao2@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid203; Fri, 12 Apr 2019 17:19:15 +0800 (CST)
Date: Fri, 12 Apr 2019 17:19:15 +0800
X-Zmail-TransId: 2afd5cb0581395030c4a
X-Mailer: Zmail v1.0
Message-ID: <201904121719158147013@zte.com.cn>
Mime-Version: 1.0
From: wang.yubao2@zte.com.cn
To: jorge.rabadan@nokia.com
Cc: bess@ietf.org, sajassi@cisco.com, jdrake@juniper.net
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse02.zte.com.cn x3C9JDiO053571
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/VMCvJW2iUbJl8l4cWTaAG3B5ALc>
Subject: [bess] [BESS] Discussions about DF-election FSM.
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: Fri, 12 Apr 2019 09:19:34 -0000
Hi Jorge, I read the draft-ietf-bess-evpn-df-election-framework-08 and find it seemed not clear in the DF election FSM . I didn't find clear explanation about when to advertise the ES route(RT-4) according to the FSM. I think it is the DF_TIMER (not ES_UP) event that triggers the advertising of ES route. Because if not the remote PEs will re-elect a new DF immediately after the advertisment, and the new DF may be the PE in DF_WAIT state itself. but I didn't find clear explanation in the relevant event transmissions. The description in draft-ietf-bess-evpn-df-election-framework-08 section 3.1 as follows: 2. INIT on ES_UP: transition to DF_WAIT. ... ... 6. DF_WAIT on DF_TIMER: transition to DF_CALC. 7. DF_CALC on entering or re-entering the state: (i) rebuild candidate list, hash and perform election (ii) Afterwards FSM generates CALCULATED event against itself. And I find in RFC7432 Section 8.5 that the advertising of ES route is not influenced by the DF_TIMER. 1. When a PE discovers the ESI of the attached Ethernet segment, it advertises an Ethernet Segment route with the associated ES-Import extended community attribute. 2. The PE then starts a timer (default value = 3 seconds) to allow the reception of Ethernet Segment routes from other PE nodes connected to the same Ethernet segment. This timer value should be the same across all PEs connected to the same Ethernet segment. So I think there is an update of RFC7432 and it needs to be clear described in the draft. or the DF timer in RFC7432 is not the same with the DF timer in that draft? Is my understanding right? Best Regards Bob
- [bess] [BESS] Discussions about DF-election FSM. wang.yubao2
- Re: [bess] [BESS] Discussions about DF-election F… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] [BESS] Discussions about DF-election F… wang.yubao2