Artem Glazychev

@or-adar You are right, currently the timeout element only considers it's previous path segment. If the timeout calls Close - this call goes though all components. So, for example, if...

Yes, that's right

NSM does not explicitly limit pcap. I checked and it doesn't work for wireguard either. We need to look at the implementation of the pcap plugin in vpp. The reason...

I think it's worth starting with the vpp mailing list. Most likely there are guys there who can explain the details

In my opinion, our directory hierarchy looks a little confusing right now. For example, adding interdomain ipsec here will make the problem worse. In this issue, I propose to structure...

New multideath cases were added - https://github.com/networkservicemesh/deployments-k8s/tree/v1.12.0/examples/heal

This refers to the previous implementation of healing. I think this issue can be closed

Closed - https://github.com/networkservicemesh/sdk/pull/1408

**TODO:** Check the problem on the current main branch - run vl3-network with many clients Positive: create synthetic test before/after Negative: this is low priority issue

It looks like `grpc.WithBlock()` is anti-pattern - https://pkg.go.dev/google.golang.org/grpc#WithBlock We need to consider whether we can refuse it. As far as I remember, it is worth paying attention to DialTimeout.