José Luis Millán

> What about if we allow packets with higher layers be forwarded only if their PID value is between S_PID - 10 and S_PID being S_PID the PID of the...

Yes @jcague, that's true. Indeed I misinterpreted that when reading this exactly from @ggarber [article](http://www.rtcbits.com/2017/04/howto-implement-temporal-scalability.html). I'll do some local tests to verify a second concern I have, and comment here...

Before going forward with this draft I want to make sure what's causing the problem for #989. There, we can see that some Consumers are continuously receiving the T1 layer...

> Idea: let old packets with temporal layer greater than current temporal layer pass to the consuming endpoint UNTIL a keyframe (for the target spatial layer) is sent to it....

Self note: Retest locally and prepare for merge.

> So I just suggest you make minInterval and minCount configurable. Of course, it's up to you to change them or not Minimum interval could be set to 100 or...

Indeed this and https://github.com/versatica/mediasoup/pull/1088 add the same functionality, right?

I like the approach. Something that worries me is the synchronous nature of the implementation. Plugins processing impacts directly on worker performance (not in this specific 'ping' example but potentially...

Something that worries me about the approach in your example is that there are no boundaries about what a plugin can do as it receives the core instances. It could,...

> the thing here is that worker plugins should just run on C++ without interacting with the Node/Rust layer. Of course, this communication is about worker and plugins only. I...