[Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)

["[e-mail]" <[e-mail]>]

Hello Sue and all,

As a coauthor I support the adoption of this draft and I don't know any IPR that may relate to it.

Does this BGP-LS addition help SR Egress Peering points in operational networks?  
Yes.

Does this draft handle the BUM traffic in a way that Prevents looping?(Broadcast, Unknown Unicast, and Multicast (BUM))
No. This dfaft defines no new method for loop preventing  because  existing mechanisms work for L2bundle.

Are there any problems in the technology described?
No.



Best Regards,
Zhenqiang Li
China Mobile
[e-mail]
 
From: Susan Hares
Date: 2024-08-02 22:11
To: [e-mail]
Subject: [Idr] WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
IDR WG: 
 
This begins a 2 week WG adoption call for  
draft-lin-idr-sr-epe-over-l2bundle-07.txt
https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/
 
 
The authors should reply to this email with an 
IPR statement indicating whether they know of an intellectual property. 
 
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.
 
 
In your comments regarding adoption,  please consider 
 
Does this BGP-LS addition help SR Egress Peering points
in operational networks?  
Does this draft handle the BUM traffic in a way that 
Prevents looping?
(Broadcast, Unknown Unicast, and Multicast (BUM))
Are there any problems in the technology described? 
 
Cheerily, Sue Hares