Sergio Garcia Murillo

I am doing media server cascading, and I can have easily more than 100 ssrcs in the same bundle. This would be a great boost for my use case.

how about splitting the PR in two: - one for extracting the current ssrc lookup code into a different .c file with clean function definitions called by strp.c (should not...

that's why I think splitting the PR in two, one for creating an interface for ssrc lookup and another for adding the sse2 logic would be helpful.

As discussed in this thread, we have extracted the current stream list implementation and create an internal api + default implementation in https://github.com/cisco/libsrtp/pull/612

Yes, I recently discovered that defines starting with an underscore are reserved, would you be willing to provide a CR?

Would you mind issuing a PR?

How do you think it can be optimized? i am against early-optimizations without clear metrics from real live scenarios.

Also, what do you see wrong in your graphics?

do you have a sendonly stream? in this case I use rtx/nacks to get the rtt periodically. If not, there should be nacks according to the packet losses.

nack policy is a bit aggressive, I send one nack packet each time a packet is lost and on subsequent packets until rtx is received or timeout happens. This nacks...