W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2012

Enabling JSEP

From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
Date: Mon, 13 Feb 2012 15:30:39 +0100
Message-ID: <4F391E8F.7040302@ericsson.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hi, (as contributor)

I'm trying to wrap my head around JSEP. It was very clear during the 
IETF part of the interim meeting that the community wants the 
functionality that JSEP enables. But to me it was not so clearly spelled 
out what that is, so this is my attempt to list it:

1. Trickle candidates enabled to speed up session start (maybe exchanged 
in separate messages)

2. The possibility to modify (or even set) media session details beyond 
what an SDP o/a can do. Examples I've seen include PTs and SSRCs, but to 
me it is not clear what other things that app would like to set.

3. Separating to some extent the session description (or set up) for 
media flowing A -> B from the session description (set up) for media B -> A.

Is this what we should enable? What have I missed?

The background to the questions is of course that we need an API that 
enables what you want to do.

(I think 1. and 3. makes a lot of sense, and that we should have a 
closer look at 2. to understand more. If it is only PT and SSRC, then 
perhaps hints or a specific API could be used, but if there are a lot of 
other things that may not be a viable way.)

Received on Monday, 13 February 2012 14:31:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:27 UTC