Hi WG, I am still waiting for the issue about “SRv6 VPN SID in Multicast” in WGLC draft [*] draft-ietf-spring-sr-replication-segment to be resolved.
To be collaborative, I had already mentioned repeatedly to use “Source Address” for considering as an possible option to solve the issue. Considering that there may be interests in the WG to learn more about how “Source address” could possibly solve the “SRv6 VPN SID in multicast” issue, I think it may be useful to read the draft [*] draft-xl-msr6-source-segment-02. The draft is exactly about using SRv6 VPN SID in Multicast, and has considered SRv6-TreeSID already, but hasn’t got reviewed by Spring WG because of some reasons, among which is the argument that there is no need for multicast to be SRv6-copatible. Now since there are interests of making SRv6-compatible multicast solution, I think it may be a proper time to review this draft. We request comments on the draft from Spring WG, and remind to pay close attention if it has the issue of “breaking SRv6 architecture” that had on the WGLC draft. [*]The draft https://www.ietf.org/archive/id/draft-xl-msr6-source-segment-02.html [*]WGLC draft https://datatracker.ietf.org/doc/draft-ietf-spring-sr-replication-segment/ Thanks, Jingrong 本邮件及其附件可能含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments may contain confidential information from HUAWEI, 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 https://www.ietf.org/mailman/listinfo/spring
