<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-sr-epe-over-l2bundle" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-epe-over-l2bundle-01">
   <front>
      <title>Segment Routing BGP Egress Peer Engineering over Layer 2 Bundle Members</title>
      <author initials="C." surname="Lin" fullname="Changwang Lin">
         <organization>New H3C Technologies</organization>
      </author>
      <author initials="Z." surname="Li" fullname="Zhenqiang Li">
         <organization>China Mobile</organization>
      </author>
      <author initials="R." surname="Pang" fullname="Ran Pang">
         <organization>China Unicom</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Chen" fullname="Mengxiao Chen">
         <organization>New H3C Technologies</organization>
      </author>
      <date month="March" day="2" year="2025" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-sr-epe-over-l2bundle-01" />
   
</reference>
