Sasha, Thank you kindly for this.
Best Regards, Menachem From: Alexander Vainshtein <alexander.vainsht...@rbbn.com> Date: Thursday, 15 June 2023 at 12:12 To: Menachem Dodge <mdo...@drivenets.com> Cc: bess@ietf.org <bess@ietf.org> Subject: RE: Draft draft-ietf-bess-7432bis-07 Section 7.5, 7.11 and 14.1.1 Menachem, More inline below. Regards, Sasha From: Menachem Dodge <mdo...@drivenets.com> Sent: Thursday, June 15, 2023 11:56 AM To: Alexander Vainshtein <alexander.vainsht...@rbbn.com> Cc: bess@ietf.org Subject: [EXTERNAL] Re: Draft draft-ietf-bess-7432bis-07 Section 7.5, 7.11 and 14.1.1 Hello Sasha, Thank you kindly for your email. Based on what you have written the PE that is attached to this MH ES will send the RED=00 in the Type 1 Ethernet A-D ESI route and will send the L2-ATTR with the ‘P’ bit raised. [[Sasha]] There are two flavors of Ethernet A-D (EVPN Type 1) routes: per-ES (with all zeroes in the Label field and MAX-ET in the Ethernet Tag ID field) and per EVI (with the valid Ethernet Tag ID value identifying the BD for which it has been advertised, and with the valid “aliasing” label for this BD). In the case of an All-Active MH ES: * RED in the ESI Label Extended Community attached to (potentially, multiple copies of) the per-ES Ethernet A-D route (with different auto-generated RD in the NLRI of these copies) MUST be set to ‘00’ * P bit in the Layer 2 Attributes Extended Community attached to the per-EVI Ethernet A-D route SHOULD be set to ‘1’. If for whatever reason (example misconfiguration) another PE attached to the same MH ES sends RED=01 what should be the behavior of the first PE when it receives this information? [[Sasha]] I think that the only thing you can do is to report a misconfiguration problem. Thank you kindly. Best Regards, Menachem From: Alexander Vainshtein <alexander.vainsht...@rbbn.com<mailto:alexander.vainsht...@rbbn.com>> Date: Thursday, 15 June 2023 at 10:01 To: Menachem Dodge <mdo...@drivenets.com<mailto:mdo...@drivenets.com>> Cc: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>> Subject: RE: Draft draft-ietf-bess-7432bis-07 Section 7.5, 7.11 and 14.1.1 Menachem, Please see some tentative answers to your questions inline below. Hopefully this helps. Regards, Sasha From: BESS <bess-boun...@ietf.org<mailto:bess-boun...@ietf.org>> On Behalf Of Menachem Dodge Sent: Wednesday, June 14, 2023 11:29 AM To: bess@ietf.org<mailto:bess@ietf.org> Subject: [EXTERNAL] Re: [bess] Draft draft-ietf-bess-7432bis-07 Section 7.5, 7.11 and 14.1.1 Hello All, Please could someone kindly respond to my questions below. Thank you kindly. Best Regards, Menachem Dodge From: Menachem Dodge <mdo...@drivenets.com<mailto:mdo...@drivenets.com>> Date: Sunday, 11 June 2023 at 16:17 To: bess@ietf.org<mailto:bess@ietf.org> <bess@ietf.org<mailto:bess@ietf.org>> Subject: Draft draft-ietf-bess-7432bis-07 Section 7.5, 7.11 and 14.1.1 Hello All, I have a query regarding the behavior of a PE that is a member of an ES and has been configured to be in All-Active mode. According to section 7.5 the multihomed site redundancy mode is set to RED = 00: A value of 00 means that the multihomed site is operating in All-Active redundancy mode. What defines “operating”? Is this according to local configuration only? [[Sasha]] Please note that the highlighted text in the draft refers to operation of the customer site to which multiple EVPN PEs are attached via PE-CE links forming an All-Active MH ES. I.e., this site: · MUST be ready to receive and deliver to its proper destination an Ethernet frame received from any of these links · Expects that traffic it sends to remote sites via any of these links to be delivered to its proper destination. One example of such behavior is a site with a single CE that terminates all PE-CE links comprising the MH ES in question and locally treating them as a single Link Aggregation Group with all members being in the “Collecting and Distributing” state. In section 7.11 the ‘P’ bit of the L2-ATTR Extended Community MUST be set to 1 for multihoming All-Active scenarios by all active PE(s). What is an “active PE”? Is this according to local configuration only? [[Sasha]] From my POV an active PE in this context is a PE that can send and receive traffic via the PE-CE link that locally (in this PE) represents the All-Active MH ES in question. In section 14.1.1 it states that: For a given ES, if a remote PE has imported the set of Ethernet A-D per ES routes from at least one PE, where the "Single-Active" flag in the ESI Label extended community is set, then that remote PE MUST deduce that the ES is operating in Single-Active redundancy mode. My understanding is that the meaning of “remote PE” is a PE that is not a member of the ES. This statement indicates that the “remote PE” deduces that the ES is operating in Single-Active redundancy mode from the set of Ethernet A-D per ES routes it has received. What should be the behavior of the “local PE” that is a member of the ES ? I could not find this defined in the document. Does the “local PE” assume that the configuration of all attached PEs to the ES is consistent and therefore it sends RED = 00 and sets the ‘P’ bit in the L2-ATTR ? Or does the “local PE” change what it advertises according to what it receives from the other “local PEs” attached to the same ES? For example: If a PE is configured as all-active shall this PE Send RED=00 and set the ‘P’ bit in the L2-ATTR, even when it receives from another PE on the same Ethernet-Segment RED=01 ? Thank you kindly. Best Regards, Menachem Dodge System Architect [signature_3596491684] +972-526175734<tel:+972-526175734> mdo...@drivenets.com<mailto:mdo...@drivenets.com> follow us on Linkedin<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_15t5jYhehVPNVk4k3XQMC-3Fh-3DdRk-2Dsa5oEo1co-2DW-2DrsbekN-2DrQbV3uoqGT1Te6-5FdJh8A-3D-26u-3Dhttps-3A__urldefense.proofpoint.com_v2_url-3Fu-253Dhttps-2D3A-5F-5Fclicktime.symantec.com-5F15t5jYhKNhEMSZXNbRaKT-2D3Fh-2D3D4ICEtb7VW2zsmUntvmxpvqnWbmpd9lcYJ-2D5F-2D2Dmf6jTSIQ-2D3D-2D26u-2D3Dhttps-2D3A-5F-5Fwww.linkedin.com-5Fcompany-5Fdrivenets-2526d-253DDwMGaQ-2526c-253DeuGZstcaTDllvimEN8b7jXrwqOf-2Dv5A-5FCdpgnVfiiMM-2526r-253DcezglEhs6Oa-5FCKN9mhFbT8T8kmWwaNdtBDjE9bvBG-5FE-2526m-253D6xCepHKACzh0KVWAsSEkwpGGnnxJh9lzMjxdXygCvvM-2526s-253DNqmcevIbdYY0qJRrBYUjLW0o582Q62LcNNPm-5FHtL7Q0-2526e-253D&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=uTXV_JCOUR9Evsupl8dLG_5LGj6l27smQ5i5ZmQuU_0&s=0t8RDcCMgWtOeGB6Q7Ovs72eVK35HF1l-5UkdR8U0fo&e=> www.drivenets.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.drivenets.com&d=DwQGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=uTXV_JCOUR9Evsupl8dLG_5LGj6l27smQ5i5ZmQuU_0&s=yEI0S2cACfGUNXDp_1KQh-vx4l6Xnz8Rln36mQOR9yo&e=> [DriveNets Network Cloud]<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_15t5eiWNEshn5oEpVy1Ca-3Fh-3DJjeFaIexUOGbW1ZyvBWs-2D0eNRajdzPv7OTZAfLhEznU-3D-26u-3Dhttps-3A__urldefense.proofpoint.com_v2_url-3Fu-253Dhttps-2D3A-5F-5Fclicktime.symantec.com-5F15t5eiW2v5Ym2chT3sBAq-2D3Fh-2D3DPCZOTi5QP1jO4bPdWB2wjBkCg4eXF5tpvLQyxIuux3E-2D3D-2D26u-2D3Dhttps-2D3A-5F-5Fdrivenets.com-5Fproducts-5F-2526d-253DDwMGaQ-2526c-253DeuGZstcaTDllvimEN8b7jXrwqOf-2Dv5A-5FCdpgnVfiiMM-2526r-253DcezglEhs6Oa-5FCKN9mhFbT8T8kmWwaNdtBDjE9bvBG-5FE-2526m-253D6xCepHKACzh0KVWAsSEkwpGGnnxJh9lzMjxdXygCvvM-2526s-253DycxNvfEdD00X3JQayZlIUKWwvEMrYelm7zLBqdKf9f0-2526e-253D&d=DwMGaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=cezglEhs6Oa_CKN9mhFbT8T8kmWwaNdtBDjE9bvBG_E&m=uTXV_JCOUR9Evsupl8dLG_5LGj6l27smQ5i5ZmQuU_0&s=UKiVexmD3cbJOkxNo1k1itav_2qA43VriwnvKamEvXU&e=> Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website. Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
