RE: [Suspected Junk Mail] New functionality in PR - priority

Exactly.  RtpEncodingParameters isn’t just about simulcast/SVC, and all settings need to be part of RtpParameters so changes can be applied all at once.

Peter Thatcher said:

​As far as I understand, 1.0 will only have one​ RtpEncodingParameters
value ​(no simulcast), in which case being at the encoding level is equivalent to being at the RtpSender level.  In other words, for 1.0, there really isn't a distinction except to allow it in the future to be at the encoding level rather than the RtpSender level.

But even if at the RtpSender level and not the encoding level, it should be part of RtpParameters and set via RtpSender.setParameters, not by a separate attribute, so that all parameters, including priority, can be made in one atomic change (or not, if rejected).