Hi Alvaro, Thank you for the review and comments.
1.Regarding 3.1: RFC9086 defines the BGP EPE advertisement for BGP-LS, including the PeerAdj SID (Type-1102) for L3 link. RFC9085 in section 2.2 defines the Adjacency SID TLV (Type-1099), LAN Adjacency SID TLV, and the L2 Bundle Member Attributes TLV, explicitly stating that these TLVs are intended for IGP link. According to section 2.2.3, the L2 Bundle Member Attributes TLV can include the IGP Adjacency SID TLV (Type-1099), but not BGP PeerAdj SID (Type-1102) . This document describes how to support BGP EPE SIDs on the L2 bundle member interfaces. We reuse the BGP PeerAdj SID TLV (Type-1102), not the IGP Adjacency SID TLV (Type-1099), to carry EPE SIDs for L2 bundle member. Hence, we declare the PeerAdj SID TLV (Type-1102) defined in RFC9086 as a sub-TLV of the L2 Bundle Member Attributes TLV defined in RFC9085. Therefore, the update proposed in section 3.1 is needed. 2.Regarding 3.2: This section primarily aims to illustrate how BGP EPE allocates END.X SIDs on the L2 Bundle member interfaces and how it is advertised through the L2 Bundle Member Attributes TLV. No update is needed, because [RFC9514] already specified that END.X SID TLV can be carried in the L2 Bundle Member Attributes TLV. Thanks, Changwang 发件人: Alvaro Retana <aretana.i...@gmail.com> 发送时间: 2024年5月14日 16:08 收件人: li_zhenqi...@hotmail.com 抄送: draft-lin-idr-sr-epe-over-l2bundle <draft-lin-idr-sr-epe-over-l2bun...@ietf.org>; idr-chairs <idr-cha...@ietf.org>; i...@ietf.org; spring@ietf.org 主题: Re: [spring] request for review and comments [spring-chair hat off + idr] Hi! I took a quick look at the draft -- it uses existing TLVs to convey the information, which is good. Given that (IIRC) BGP-LS does not limit TLVs' use as sub-TLVs, rfc9085 already contemplates using the Adjacency SID TLV (as a sub-TLV), and rfc9086 already says that additional TLVs can be included to describe a link's characteristics, I find the contents quite obvious. The update proposed in §3.1 is not needed: This document updates [RFC9085] and [RFC9086] to allow the PeerAdj SID TLV to be included as a sub-TLV of the L2 Bundle Member Attributes TLV. [I expected something similar in §3.2 about using the SRv6 End.X SID TLV as a sub-TLV, but that text is not present. It is not needed anyway.] My 2c. Alvaro. On May 10, 2024 at 5:17:09 AM, li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com> (li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com>) wrote: Dear SPRING experts, IDR is considering to start the WG adoption call for Segment Routing BGP Egress Peer Engineering over Layer 2 Bundle. As suggested by IDR WG chair, we request for review and comments in SPRING. Any discussion, suggestion or comment is appreciated. Some information about the draft: Abstract There are deployments where the Layer 3 interface on which a BGP peer session is established is a Layer 2 interface bundle. In order to allow BGP-EPE to control traffic flows on individual member links of the underlying Layer 2 bundle, BGP Peering SIDs need to be allocated to individual bundle member links, and dvertisement of such BGP Peering SIDs in BGP-LS is required. This document describes how to support Segment Routing BGP Egress Peer Engineering over Layer 2 bundle. link https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/ ________________________________ Best Regards, Zhenqiang Li China Mobile li_zhenqi...@hotmail.com<mailto:li_zhenqi...@hotmail.com> _______________________________________________ spring mailing list -- spring@ietf.org<mailto:spring@ietf.org> To unsubscribe send an email to spring-le...@ietf.org<mailto:spring-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
