- From: Matthew Kaufman <matthew.kaufman@skype.net>
- Date: Fri, 02 Sep 2011 19:17:04 +0100
- To: Justin Uberti <juberti@google.com>
- CC: public-webrtc@w3.org
Received on Friday, 2 September 2011 18:17:45 UTC
On 9/2/11 7:12 PM, Justin Uberti wrote: > > > On Fri, Sep 2, 2011 at 1:57 PM, Matthew Kaufman > <matthew.kaufman@skype.net <mailto:matthew.kaufman@skype.net>> wrote: > > On 9/2/11 6:52 PM, Justin Uberti wrote: > > > I'm far from sold on RTP for this, but since I think we need a > sequence number (for congestion control) and a stream id (for > demux), it seems we're already halfway there. Will look at the > other methods - do you recall if these were mentioned in a > public draft or on the mailing list? > > > There were two IDs... Cary did a presentation at the last meeting > and is preparing a combined draft. > > I believe there was discussion on the list as well from some RTP > folks (or maybe it was just at the microphone back in Prague?) > about why putting data in RTP is the wrong thing. > > > Thanks, will look. Main concern is how SDES-SRTP works with something > non-RTP. Maybe that isn't supported. > It works fine... you just take the same SDES key you stuffed in (via Javascript, if we don't use SDP, perhaps) and encrypt with it. DTLS is even more obvious of course. Matthew Kaufman
Received on Friday, 2 September 2011 18:17:45 UTC