Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-23 Thread Wanghaibo (Rainsword)
Hi Greg, Thanks for your suggestion. I think your suggestion is good, we will modify it in the next version. Regards, Haibo |-Original Message- |From: Greg Mirsky [mailto:gregimir...@gmail.com] |Sent: Sunday, March 20, 2022 4:29 AM |To: Wanghaibo (Rainsword) |Cc: draft-wang-bess-sbfd-di

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-19 Thread Greg Mirsky
Hi Haibo, thank you for the clarification. I may suggest a text for Section 3: In some EVPN deployments, for example, when it spans over multiple domains, only one of a pair of interconnected PEs benefits from monitoring the status of the connection. In such a case, using S-BFD [RFC7880] is advant

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-15 Thread Wanghaibo (Rainsword)
Hi Greg, Thanks for you comments. Yes, the resources will save at PE1 and PE2 as figure 1. This is a typical 3PE scenario. The service is like this: +-++-++-+ | UCE1|| APE1||SPE1 |, +-++-+` /+-+ `. `, .'

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-15 Thread Greg Mirsky
Hi Haibo, thank you for your expedient response. If I understand the scenario you're addressing, it is where a single PE with moderate resources is connected to a PE that acts as the edge device for the access network. To improve the quality of user experience, customer's PE is connected to a secon

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-15 Thread Wanghaibo (Rainsword)
Hi Reshad, Thanks for your comments first. |Authors, in section 3.1 3rd paragraph, last sentence, I'm not sure I fully understand. Instead of |having 2 S-BFD sessions on PE3 (as initiator) to PE1 and PE2 (the responders), how are you merging |this into 1 single session? [Haibo]: There ma

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-15 Thread Wanghaibo (Rainsword)
Hi Greg, Thanks for your comments. The scenario you pointed out is a 4PE scenario, but in our solution, a large number of scenarios are based on 3PE. In a 3PE scenario, deploying BFD wastes resources. A large number of single-homed PEs may be connected to the dual-homed PEs. The dua

Re: [bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-14 Thread Greg Mirsky
Hi Reshad, I agree with you that if in all the deployment scenarios there's always only one node in a pair of nodes that needs to be aware of the path continuity to the remote system, then S-BFD has an advantage compared to "classic" RFC 5880-style BFD. I think that the use case presented in the do

[bess] A question about the draft-wang-bess-sbfd-discriminator

2022-03-14 Thread Greg Mirsky
Hi Haibo and the Authors, thank you for updating the draft. I've read the new version and have a question about the use case presented in the document. There are three PEs with two of them providing redundant access to a CE. It appears that a more general case would be if both CEs use redundant con