Roman Shpount

I have also verified that this is what Chrome 73, Firefox 66 , IE 11, Edge 17, and Safari 12 are doing already. I have also noticed that Safari 12...

> It's ok because including a codec in an Offer on a recvonly or sendrecv m-line only requires the Offerer to be able to receive the codec; Including a receive-only...

@aboba RFC 9429 is not an error. An additional context might help, but it would not be normative. RFC 3264 will still be a normative document that controls how the...

@stefhak I am saying that the procedure for asymmetric codecs in sendrecv line is not defined in RFC 9429. Implementing asymmetric codecs on a sendrecv line using RFC 3264 is...

@stefhak > Thanks for elaborating @rshpount. One thing that is not clear to me is: your inputs indicate that the answer should only list one codec usually. I think current...

I think the general intent with the SDP offer/answer is to include codecs that you can only send in the sendonly m= line, codecs that can only receive on the...

@alvestrand The right thing would be to get rid of SDP and offer/answer and replace them with an API service that specifies which codecs should be sent and received from...

I agree with the note. I would expand it a little bit, saying that: "NOTE: Using SDP, it is not possible to indicate in a media section with the direction...