[bess] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt

2024-11-04 Thread Luc André Burdet
Hi Sami, Yes, BUM is out of scope – Sasha already raised this question and it looks like I forgot to add the clarifying statement. I will in next rev. * IMHO and FWIW an explicit statement that “BUM is not in-scope of the draft, it is not redirected” would help the readers. It would also h

[bess] Last Call: (EVPN Virtual Ethernet Segment) to Proposed Standard

2024-11-04 Thread The IESG
The IESG has received a request from the BGP Enabled ServiceS WG (bess) to consider the following document: - 'EVPN Virtual Ethernet Segment' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive commen

[bess] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt

2024-11-04 Thread Shah, Himanshu
Hmm that is interesting.. I would have thought BUM would be in scope. If a node is DF elected and receives BUM and if his ES is down why can he not redirect to NDF? NDF, by virtue of getting traffic on ERL could then bypass the DF election status and forward it to that local ESI.. Thanks, Hima

[bess] Re: [Shepherding AD review] Pre-IETF Last-Call review of draft-ietf-bess-evpn-virtual-eth-segment-15

2024-11-04 Thread Gunter van de Velde (Nokia)
Hi Ali, Thanks for the update When none of the formal procedures changed and only clarifications have been made, then WGLC is not required. I started the request for a IETF LC for this draft. It will provide an opportunity to review the latest version of the document. Brgds, G/ From: Ali Saja

[bess] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt

2024-11-04 Thread Luc André Burdet
Hi Himanshu, If BUM is brought into scope, redirecting from Failed-NDF to DF would cause issues: DF will have duplicates. Only Failed-DF to NDF can be supported in a straightforward manner. However, BUM is (usually) ingress-replicated to both peering PEs. Consider ingress-replicated traffic t

[bess] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt

2024-11-04 Thread Shah, Himanshu
In line.. Thanks, Himanshu From: Luc André Burdet Date: Monday, November 4, 2024 at 6:16 PM To: Shah, Himanshu , Boutros, Sami , BESS Subject: [**EXTERNAL**] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt Hi Himanshu, If BUM is brought int

[bess] Re: Few questions about https://www.ietf.org/archive/id/draft-burdet-bess-evpn-fast-reroute-08.txt

2024-11-04 Thread Shah, Himanshu
Actually, not advertising ERL for conflicted ESI+EVI+VLAN is probably not a good idea since it will lose benefit for known unicasts.. ☹ Let me sync up with you, if you are attending the IETF or will sync up with Jorge or Patrice.. Thanks, Himanshu From: Shah, Himanshu Date: Monday, November 4

[bess] FW: New Version Notification for draft-ietf-bess-evpn-ip-aliasing-02.txt

2024-11-04 Thread Jorge Rabadan (Nokia)
FYI A new version of this draft has been posted. The refresh fixes some typos, updates references and adds some text as discussed in the mailing list. Thanks. Jorge (on behalf of the authors) From: internet-dra...@ietf.org Date: Monday, November 4, 2024 at 2:16 AM To: A. Sajassi , J. Drake , J

[bess] I-D Action: draft-ietf-bess-evpn-ip-aliasing-02.txt

2024-11-04 Thread internet-drafts
Internet-Draft draft-ietf-bess-evpn-ip-aliasing-02.txt is now available. It is a work item of the BGP Enabled ServiceS (BESS) WG of the IETF. Title: EVPN Support for L3 Fast Convergence and Aliasing/Backup Path Authors: A. Sajassi J. Rabadan S. Pasupula