[ortc] Same payload for different codecs in same RtpSender/RtpReceiver

ibc has just created a new issue for https://github.com/openpeer/ortc:

== Same payload for different codecs in same RtpSender/RtpReceiver ==
NOTE: Related email posted in  
https://lists.w3.org/Archives/Public/public-webrtc/2016Mar/0021.html.

[draft-ietf-mmusic-sdp-bundle-negotiation](https://tools.ietf.org/html/draft-ietf-mmusic-sdp-bundle-negotiation-27)
 in section 10.1.2:

```
   Multiple bundled "m=" lines might represent RTP based media.  As 
all
   RTP based media associated with a BUNDLE group belong to the same 
RTP
   session, in order for a given payload type value to be used inside
   more than one bundled "m=" line, all codecs associated with the
   payload type number MUST share an identical codec configuration.
   This means that the codecs MUST share the same media type, encoding
   name, clock rate and any parameter that can affect the codec
   configuration and packetization.
   [I-D.ietf-mmusic-sdp-mux-attributes] lists SDP attributes, whose
   attribute values must be identical for all codecs that use the same
   payload type value.
```

As I explain in the email this is a no sense. At the end it basically 
states that there cannot be two different codecs with same 
`payloadType` (or same codec with different codec parameters) within 
the same `RtpSender`/`RtpReceiver`.

This is a pain for a SFU developer as it forces me to override the 
payload types of different participants in the same conference 
(otherwise a receiver should create different transports for each 
media track...).

So, what about ORTC and this topic?

Please view or discuss this issue at 
https://github.com/openpeer/ortc/issues/407 using your GitHub account

Received on Monday, 7 March 2016 22:16:20 UTC