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

: JSEP API changes - choosing a path forward

From: Li Li <Li.NJ.Li@huawei.com>
Date: Thu, 29 Mar 2012 06:13:42 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-id: <B60F8F444AAC9C49A9EF0D12D05E094221677E0C@szxeml535-mbs.china.huawei.com>
Hi,

Would it be fair to say that a key difference between these two proposals is who controls the signaling state machine: PeerConnection or the application?

Thanks.
Li

-----ʼԭ-----
: Harald Alvestrand [mailto:harald@alvestrand.no] 
ʱ: 2012321 0:15
ռ: public-webrtc@w3.org
: JSEP API changes - choosing a path forward

List,

we now have two member contributions suggesting changes to the 
PeerConnection API in order to align with the JSEP direction suggested 
in the IETF:

http://lists.w3.org/Archives/Public/public-webrtc/2012Mar/0049.html 
(from Adam)
http://lists.w3.org/Archives/Public/public-webrtc/2012Mar/0064.html 
(from Cullen)

In order to make quick progress, the chairs aim to call for the 
incorporation of one of these in the core document as soon as consensus 
is detected in the WG; if it's not obvious before what the
consensus is, the chairs aim to make a call one way or the other based 
on the list traffic up to ca March 30 (this is just after the IETF 
meeting, so people taking the opportunity for face-to-face discussion 
can report on those discussions here).

All list members who have reviewed both documents are encouraged to
state their opinion on the list.

                    Harald and Stefan

Received on Thursday, 29 March 2012 06:15:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 March 2012 06:15:42 GMT