Re: [rtcweb] Working Group Last Call: JSEP

Agreed. The sole purpose it serves at this point is to enable serial
forking.

I would be happy to remove it.

On Wed, Nov 9, 2016 at 5:36 PM, Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> +1.
>
> One of the reasons we added setDirection() was to be able to handle the
> "warm up" case with no recourse to pranswer (as demonstrated in Example 12
> in Section 11.2 as you cite).
>
> Given that, it is hard to motivate an implementation to support pranswer
> (e.g. in the Edge WebRTC 1.0 feature now in Windows Insider Preview, we
> left out support for pranswer).
>
>
>
> On Tue, Nov 8, 2016 at 10:43 AM, Philipp Hancke <fippo@goodadvice.pages.de
> > wrote:
>
>> Am 21.10.2016 um 21:25 schrieb Ted Hardie:
>>
>>> The chairs would like to start a working group last call on
>>> draft-ietf-rtcweb-jset-17 to end on November 9th, 2016, 17:00 KST.
>>>
>>> Please review thoroughly, as working through the last comments will be
>>> the
>>> major effort of our working group meeting in Seoul.
>>>
>>
>> One question: why is pranswer still in there? The major use-case for this
>> seems to be transport warm-up (4.1.7.1) for which I think transceivers are
>> the new way as shown in http://w3c.github.io/webrtc-pc
>> /#simple-peer-to-peer-example-with-warm-up
>>
>> pranswer has not seen much traffic on this list. Together with BUNDLE it
>> seems to have been broken in Chrome since 2014 if I understand
>> https://bugs.chromium.org/p/webrtc/issues/detail?id=3349 correctly. And
>> I recall it being broken in 2013 when using DTLS.
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>