Hi Sasha, I suggest further discussing the SRv6 sections in draft-burdet-bess-evpn-fast-reroute-07. There is another document on the loop prevention mechanism for SRv6.
Theirs is another way of achieving the same thing – using the behavior vs. using the flag. The draft link: https://datatracker.ietf.org/doc/draft-liu-bess-srv6-service-sid-nffrr-flag/00/ The differences between the draft [https://datatracker.ietf.org/doc/html/draft-burdet-bess-evpn-fast-reroute-07<https://urldefense.com/v3/__https:/ai.h3c.com/redirect?target=https*3A*2F*2Fdatatracker.ietf.org*2Fdoc*2Fhtml*2Fdraft-burdet-bess-evpn-fast-reroute-06__;JSUlJSUl!!NEt6yMaO-gk!BbBdHr7voVCInshbrsekYTjmCOpVIvSkGCSVsCSiEKNopTiVAeTTebr7ssc3v1UIbpiTOmFd7eGEZXH0CiWDHXbGYYQ$>] and the draft [https://datatracker.ietf.org/doc/draft-liu-bess-srv6-service-sid-nffrr-flag/00/] are as follows: 1. The focus of the "evpn fast reroute" draft is solely on FRR in the EVPN scenario, specifically for L2VPN scenarios. 2. In contrast, this draft [draft-liu-bess-srv6-service-sid-nffrr-flag-00] is applicable to both L3VPN and L2VPN networking. 3. This draft [draft-liu-bess-srv6-service-sid-nffrr-flag-00] does not require any additional definition of "Flavor". It only involves local behavior and does not require service SID flavor expansion. 1. The "evpn fast reroute" draft requires the use of arg to solve DF (Designated Forwarder) problems. However, if arg is used for other applications in the future, it may no longer be available for use in this context. 1. This draft [draft-liu-bess-srv6-service-sid-nffrr-flag-00] only provides a brief expansion on the definition of the "flag" and it is applicable to both L2VPN and L3VPN scenarios. Thanks, Changwang 发件人: Alexander Vainshtein <Alexander.Vainshtein=40rbbn....@dmarc.ietf.org> 发送时间: 2024年7月25日 6:16 收件人: Bocci, Matthew (Nokia - GB) <matthew.bo...@nokia.com>; zzh...@juniper.net; slitkows.i...@gmail.comi 抄送: draft-burdet-bess-evpn-fast-reroute.auth...@ietf.org; bess@ietf.org 主题: [bess] Adoption of the EVPN Fast Reroute draft 重要性: 高 Hi all, The EVPN Fast reroute draft<https://datatracker.ietf.org/doc/html/draft-burdet-bess-evpn-fast-reroute-07> has been mentioned as being in the middle of the queue for the BESS WG adoption call at the BESS WG session today. IMHO and FWIW this draft is: * Short, well-written and easy to understand * Addresses a real problem – prevention of transient forwarding loops while handing failure of one of the PE-CE links in a MH ES * Quite stable (the latest change was about SRv6 support). Therefore, I would like to suggest expediting the WG adoption call for this draft. 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. ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ BESS mailing list -- bess@ietf.org To unsubscribe send an email to bess-le...@ietf.org
