Re: [Lsr] Temporary addition of links to flooding topology in dynamic flooding

2019-03-11 Thread Jeff Tantsura
+1 Les. In general - in ECMP cases LFA is meaningless (any ECMP member is loop-free per definition) so commonly used technology is fast-rehash, where in case of failure all the flows that would use the link in question are rehashed over other links in the bundle and that is done in HW.

Re: [Lsr] Temporary addition of links to flooding topology in dynamic flooding

2019-03-11 Thread Les Ginsberg (ginsberg)
Robert – I don’t think the word “random” is applicable. Section 6.7.11 states (emphasis added): “In the unlikely event of multiple failures on the flooding topology, it may become partitioned. The nodes that remain active on the edges of the flooding topology partitions will recognize

Re: [Lsr] Multiple failures in Dynamic Flooding

2019-03-11 Thread tony . li
Hi Huaimo, > In summary for multiple failures, two issues below in > draft-li-lsr-dynamyic-flooding are discussed: > 1) how to determine the current flooding topology is split; and > 2) how to repair/connect the flooding topology split. > For the first issue, the discussions are

Re: [Lsr] Multiple failures in Dynamic Flooding

2019-03-11 Thread Peter Psenak
Hi Huaimo, On 11/03/2019 18:08 , Huaimo Chen wrote: Hi Tony, In summary for multiple failures, two issues below in draft-li-lsr-dynamyic-flooding are discussed: 1) how to determine the current flooding topology is split; and there is no need to do that. The recovery mechanism

Re: [Lsr] draft-ketant-idr-bgp-ls-bgp-only-fabric

2019-03-11 Thread Ketan Talaulikar (ketant)
Hi Robert, Please check inline below. From: Robert Raszuk Sent: 10 March 2019 21:40 To: Ketan Talaulikar (ketant) Cc: idr@ietf. org ; lsr@ietf.org Subject: draft-ketant-idr-bgp-ls-bgp-only-fabric Hi Ketan, I have read your proposal of defining topology flooding in BGP with interest. It