Hi Neeraj, Exactly! And I mentioned this during my presentation at BESS. It Is also explicitly described in section 2.1.1 of the draft:
“ Since there is no L2 forwarding, there is no need for populating L2FIB; however, L2RIB needs to be populated for host mobility procedures because host mobility in EVPN is based on MAC mobility which is tracked in L2RIB.” Cheers, Ali From: Neeraj Malhotra <neeraj.i...@gmail.com> Date: Monday, November 6, 2023 at 4:13 PM To: Ali Sajassi (sajassi) <sajassi=40cisco....@dmarc.ietf.org> Cc: Alexander Vainshtein <alexander.vainsht...@rbbn.com>, draft-sajassi-bess-evpn-l3-optimized-...@ietf.org <draft-sajassi-bess-evpn-l3-optimized-...@ietf.org>, bess@ietf.org <bess@ietf.org>, Nitsan Dolev <nitsan.do...@rbbn.com> Subject: Re: [bess] A question about draft-sajassi-bess-evpn-l3-optimized-irb Hi Ali, Sasha, minor comment in case it wasn't already clear - each PE still learns all MACs in the control plane (for mobility procedures to work) but only locally connected MACs are installed in the forwarding plane. Hence the optimization. Ali, please confirm. Thanks, Neeraj On Mon, Nov 6, 2023 at 11:37 AM Ali Sajassi (sajassi) <sajassi=40cisco....@dmarc.ietf.org<mailto:40cisco....@dmarc.ietf.org>> wrote: Hi Sasha, Each PE only learns local MAC addresses and NOT remote ones. So, lets says you have a subnet that is stretched across 10 PEs and each PE has 100 locally connected hosts. So, the total number of MAC addresses for the subnet is 1000 (10X100) but each PE ONLY learns 100 MAC addresses. This is in contrast with the traditional EVPN-IRB where each PE learns all 1000 MAC addresses. Cheers, Ali From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> on behalf of Alexander Vainshtein <alexander.vainsht...@rbbn.com<mailto:alexander.vainsht...@rbbn.com>> Date: Monday, November 6, 2023 at 5:31 AM To: draft-sajassi-bess-evpn-l3-optimized-...@ietf.org<mailto:draft-sajassi-bess-evpn-l3-optimized-...@ietf.org> <draft-sajassi-bess-evpn-l3-optimized-...@ietf.org<mailto:draft-sajassi-bess-evpn-l3-optimized-...@ietf.org>> Cc: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>>, Nitsan Dolev <nitsan.do...@rbbn.com<mailto:nitsan.do...@rbbn.com>> Subject: [bess] A question about draft-sajassi-bess-evpn-l3-optimized-irb Hi, This the question I have tried to ask during the meeting. The Introduction to draft in question<https://datatracker.ietf.org/doc/html/draft-sajassi-bess-evpn-l3-optimized-irb-00#section-1> claims “improving MAC scalability of customer bridges and PE devices significantly”. The first of these claims is easy to understand: each specific CE switch has to learn just one MAC address (that of the optimized IRB) in addition to MAC addresses of its locally attached hosts. But I have doubts about the second of these claims: to the best of my understanding, each PE attached to the subnet in question will learn MAC addresses of all attached hosts in the subnet. What, if anything, did I miss? Regards, and lots of thanks in advance, Sasha Disclaimer This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. _______________________________________________ BESS mailing list BESS@ietf.org<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
