Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Jorge, Lots of thanks for an encouraging response. I can imagine an implementation which would derive Type 1 RDs of all per-ES Ethernet A-D routes from one loopback address and all the rest of Type 1 RDs – from another loopback address. Explicitly recommending to derive all Type 1 RDs of all EVP

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Hi Sasha, About your suggestion on 7432bis, it’s kind of implicit, but I see no harm in adding a sentence. Thanks. Jorge From: Alexander Vainshtein Date: Sunday, May 28, 2023 at 1:26 AM To: Jorge Rabadan (Nokia) Cc: bess@ietf.org , draft-rabadan-bess-evpn-inter-domain-op...@ietf.org , rfc74

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Jorge, Lots of thanks for your response. Please see inline below. Regards, Sasha From: Jorge Rabadan (Nokia) Sent: Tuesday, May 16, 2023 11:42 PM To: Alexander Vainshtein ; wang.yub...@zte.com.cn Cc: bess@ietf.org; draft-rabadan-bess-evpn-inter-domain-op...@ietf.org; rfc7432...@ietf.org Subjec

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Hi Sasha, However, neither 7432bis nor any other RFC or standard I am aware of says that the same IP address PE address of the PE MUST (or, at least, SHOULD) be used as the Administrator field of Type 1 RDs in per-ES A-D routes and Type 1 RDs assigned to MAC-VRFs. And this is obviously a pre

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Hi Sasha, Thanks for your helpful notes. There is only one method to determine the RD of A-D per ES routes in the original years of RFC7432, but now there are at least two methods to determine the RD of A-D per ES routes. If it is the only reason why RFC7432 restrict the RD of A-D per

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Yubao, Please note that an EVPN PE that s attached to a MH ES, generally speaking, has to generate multiple per-ES A-D routes with the ESI of this MH ES in their NLRI. This happens because: * The set of these routes, in its entirety, must carry the Route Targets of all the EVI that are local

Re: [bess] [EXTERNAL] Re: Discussion on rfc7432bis and draft-rabadan-bess-evpn-inter-domain-opt-b

Jorge, Yubao and all, A couple of comments. The current version of 7432bis says that: * Per-ES EVPN A-D routes MUST use Type 1 RDs with the Administrator field comprising “an IP address of the PE (typically, the loopback