[Idr] Re: [Idr]_WG_adoption_call_for___draft-lin-idr-sr-epe-over-l2bundle-07_(8/2_to_8/16)

[Yisong Liu <[e-mail]>]

Hi Sue,






I support the adoption of this draft and my considerations about the questions are :




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

Yes

2. Does this draft handle the BUM traffic in a way that Prevents looping?

Yes, I think the existing looping prevention mechanisms can apply to this draft.

3. Are there any problems in the technology described? 

I think there is no problem.







Best Regards

Yisong





 



发件人: Susan Hares

时间: 2024/08/02(星期五)22:11

收件人: idr;

主题: [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