<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  
  
    <div class="moz-cite-prefix">Hi Nicolas,<br>
      <br>
      On 05/12/2012 11:03 AM, Nicolas Dufresne [via GStreamer-devel]
      wrote:<br>
    </div>
    <blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' cite="mid:1354723264.13266.11.camel@nicolas-tpx201"
      type="cite"> Good point, I forgot about SRTP. There is some effort
      that already
      <br>
      started [1].</blockquote>
    <br>
        I believe that effort has stalled. I exchanged emails with
    Olivier two days ago and he wrote: "You are correct that SRTP is a
    missing block, I'm not sure which thing to use to implement it. I'm
    not sure which SRTP variant will be adopted by the rtcweb workgroup,
    if it is DTLS-SRTP, then maybe we should go with something like
    openssl or gnutls, but I haven't investigated that fully. "<br>
    <br>
    <blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' cite="mid:1354723264.13266.11.camel@nicolas-tpx201"
      type="cite">For iSAC and iLBC I don't know exactly what it is.
      From
      <br>
      quick googling they seems to be speech base audio codecs, which in
      this
      <br>
      case shall be provided by the speex element. Payloader/Depayloader
      might
      <br>
      be missing, but writing those is fairly simple. Chrome negotiate
      codecs,
      <br>
      so I would not worry too much about that part.
      <br>
    </blockquote>
    <br>
        Hmm, I'm not sure this would work (who says WebRTC is supposed
    to support Speex?) but in any case I've got some excellent news. I
    just read at <a class="moz-txt-link-freetext" href="http://www.webrtc.org/faq-recent-topics" target="_top" rel="nofollow" link="external">http://www.webrtc.org/faq-recent-topics</a> that (at least
    on paper) Chrome 24 will introduce Opus support. So I think the only
    missing pieces here are:<br>
    <br>
    <ol>
      <li>SRTP support</li>
      <li>PeerConnection implementation.<br>
      </li>
    </ol>
        <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-05" target="_top" rel="nofollow" link="external">http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-05</a>
    indicates WebRTC uses the DTLS-SRTP variant.<br>
        I believe <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-uberti-rtcweb-jsep-02" target="_top" rel="nofollow" link="external">http://tools.ietf.org/html/draft-uberti-rtcweb-jsep-02</a>
    describes how to implement PeerConnection.<br>
    <br>
        Any idea how much would it would be to add these to GStreamer?<br>
    <br>
    Thanks,<br>
    Gili<br>
    <br>
    <blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' cite="mid:1354723264.13266.11.camel@nicolas-tpx201"
      type="cite"><br>
      best regards,
      <br>
      Nicolas
      <br>
      <br>
      [1] <a moz-do-not-send="true"
        href="https://bugzilla.gnome.org/show_bug.cgi?id=632206"
        target="_top" rel="nofollow" link="external">https://bugzilla.gnome.org/show_bug.cgi?id=632206</a><br>
      <br>
      _______________________________________________
      <br>
      gstreamer-devel mailing list
      <br>
      <a moz-do-not-send="true"
        href="/user/SendEmail.jtp?type=node&node=4657256&i=0"
        target="_top" rel="nofollow" link="external">[hidden email]</a>
      <br>
      <a moz-do-not-send="true"
        href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
        target="_top" rel="nofollow" link="external">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
      <br>
      <br>
      <hr noshade="noshade" size="1" color="#cccccc">
      <div style="color:#444; font: 12px
        tahoma,geneva,helvetica,arial,sans-serif;">
        <div style="font-weight:bold">If you reply to this email, your
          message will be added to the discussion below:</div>
        <a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/WebRTC-client-tp4657196p4657256.html" target="_top" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/WebRTC-client-tp4657196p4657256.html</a>
      </div>
      <div style="color:#666; font: 11px
tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em">
        To unsubscribe from WebRTC client, <a moz-do-not-send="true"
href="" target="_top" rel="nofollow" link="external">click
          here</a>.<br>
        <a moz-do-not-send="true"
href="http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" rel="nofollow" style="font:9px serif" target="_top" link="external">NAML</a> </div>
    </blockquote>
    <br>
  



        
        
        
<br/><hr align="left" width="300" />
View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/WebRTC-client-tp4657196p4657258.html">Re: WebRTC client</a><br/>
Sent from the <a href="http://gstreamer-devel.966125.n4.nabble.com/">GStreamer-devel mailing list archive</a> at Nabble.com.<br/>