Hi Allen, Yisong, WG,
I agree with your viewpoint and confirm that Problem #2 has a significant impact on network performance. As a vendor, especially when the backbone network switch supports SRv6, deploying SRv6 L3VPN services on tail-end devices that have both the END SID and VPN SID can indeed greatly affect the switch's forwarding performance. I believe the problem scenarios described in the draft [draft-liu-idr-sr-segment-list-optimize] are common and need to be addressed. Best Regards, Changwang 发件人: allan michael <michaelalleni...@gmail.com> 发送时间: 2024年9月14日 9:26 收件人: Yisong Liu <liuyis...@chinamobile.com> 抄送: spring <spring@ietf.org>; Susan <sha...@ndzh.com>; idr <i...@ietf.org> 主题: [spring] Re: [Idr] Request SPRING WG review and comments for draft-liu-idr-sr-segment-list-optimize Hi Yisong , WG, I've reviewed your document, and the two issues mentioned are indeed very common. These problems are inevitable when transitioning from MPLS to SRv6 deployment. The document provides an excellent solution for addressing these challenges. During our actual deployment, we encountered this issue and could only work around it through manual configuration. Regarding Problem #2, this issue is indeed quite common. When deployed in the backbone network, switches experience significant performance impacts when handling both end nodes and VPN SIDs simultaneously. Typically, the chip needs to perform a loopback forwarding, which severely affects forwarding efficiency. Thanks, Allen On Wed, Sep 11, 2024 at 4:33 PM Yisong Liu <liuyis...@chinamobile.com<mailto:liuyis...@chinamobile.com>> wrote: Dear SPRING WG members, When presenting the draft-liu-idr-sr-segment-list-optimize at the IDR interim meeting, based on the suggestions from the IDR and SPRING chairs, we will distribute the described issues in SPRING mailing list. We hope to seek WG member's opinions to determine whether the problem scenarios described in the draft are common and need to be addressed. Here is the brief description of the problems of this draft. In the tunnel splicing scenarios or cross domain path splicing scenarios, the SRH extension header of VPN user's data packets forwarded based on this SRv6 Policy will simultaneously encapsulate the End SID and VPN SID of the egress node.In this way, the following problems will arise: Problem 1: PSP behavior may not be executable. Problem 2: The forwarding efficiency of egress node decreases. For detailed information , please see the draft in the link below : https://datatracker.ietf.org/doc/draft-liu-idr-sr-segment-list-optimize/ We request for review and comments in SPRING. Welcome any discussions, suggestions or comments. Best Regards Yisong on behalf of co-authors _______________________________________________ Idr mailing list -- i...@ietf.org<mailto:i...@ietf.org> To unsubscribe send an email to idr-le...@ietf.org<mailto:idr-le...@ietf.org> ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ 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!
_______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
