Re: [rtcweb] New Version Notification for draft-guduru-rtcweb-codec-preferences-01.txt

[Kiran Kumar Guduru <[e-mail]>]

Samsung Enterprise Portal mySingle

Dear Raju,

Thanks for your comments.

Please see my comments inline.

 

------- Original Message -------

Sender : Makaraju, Maridi Raju (Raju)<[e-mail]>

Date : Jul 22, 2014 03:56 (GMT+09:00)

Title : RE: [rtcweb] New Version Notification for draft-guduru-rtcweb-codec-preferences-01.txt

 

>This seems like a pretty big hammer to solve a fairly small problem. This proposal adds 6 new API points for the purpose of >changing the order of codecs in createOffer, which seems like a high cost-benefit ratio. And while the use cases listed here are >helpful, they seem somewhat contrived to me, since it seems unlikely that the application can make better choices about >bandwidth >or power consumption than the browser.

[Raju] Per my understanding, the main object of this draft can be achieved with no additional APIs and with just the proposed introduction of preferredAudioCodecs and preferredVideoCodecs options to RTCOfferAnswerOptions constraint of createOffer()/createAnswer(). 

So, IMO I don’t think getCodecPreferences()/setCodecPreferences() add much value, so can be delayed or dropped.

The need for getSupportedAudioCodecs()/getSupportedVideoCodecs() in 1.0 can be questionable as the application can specify codecs order per known codecs (or get the list via a dummy createOffer() call). 

  [KIRAN] New API is added for this only because, it can be called on Peerconnection irrespective of its state and the order of parsing is also easy when compared to parsing of whole SDP returned through createOffer/Answer.

The draft talks about fulfilling A5 in [I-D.ietf-rtcweb-use-cases-and-requirements], but I do not see any explicit mention of how codecs can be removed? preferredAudio/VideoCodecs constraint only specifies the order of preference. Don’t you need another constraint to exclude specified codecs? It’s probably a bad design to have codecs not in the preferred list be removed automatically.

 
 [KIRAN] The removal of codecs is explained in section 6. 
  "The offer / answer
   SHOULD NOT contain audio codecs other than those specified by
   JavaScript application and the order of preference SHOULD be with
   high priority for the codecs first in the sequence."
 
Perhaps this is in indirect way. I will modify the statement to directly point this. I don't want to increase the constraints just for removal, which can be achieved with this constraint. So I followed this design.

BR

Raju