@techreport{ietf-idr-sr-epe-over-l2bundle-00, number = {draft-ietf-idr-sr-epe-over-l2bundle-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-sr-epe-over-l2bundle/00/}, author = {Changwang Lin and Zhenqiang Li and Ran Pang and Ketan Talaulikar and Mengxiao Chen}, title = {{Segment Routing BGP Egress Peer Engineering over Layer 2 Bundle Members}}, pagetotal = 11, year = 2024, month = sep, day = 2, 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 advertisement 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 members. This document updates {[}RFC9085{]} to allow the L2 Bundle Member Attributes TLV to be added to the BGP-LS Attribute associated with the Link NLRI of BGP peering link. 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.}, }