W3C home > Mailing lists > Public > public-webrtc@w3.org > September 2013

Re: Transport control API

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Tue, 17 Sep 2013 15:33:16 -0400
Message-ID: <5238AE7C.5000802@bbs.darktech.org>
To: public-webrtc@w3.org
On 12/09/2013 4:41 AM, Harald Alvestrand wrote:
> On 09/11/2013 07:43 AM, cowwoc wrote:
>>
>>     One thing I would like to discuss (unfortunately we ran out of 
>> time during the call) is whether there is consensus that the current 
>> WebRTC implementations should ramp up faster.
>
> Gili, I repeat what I have said to you on the call, in previous email 
> conversations, and in previous calls.
>
> TAKE THIS ISSUE TO RMCAT.
>
> If you can get a documented IETF consensus that a particular ramp-up 
> speed is safe, the W3C API will adopt by reference that consensus.
>
> The W3C *WILL NOT, CAN NOT AND SHOULD NOT* try to override IETF 
> consensus on what's safe for the Internet.
>
> (the fact that the current Chrome implementation is overly 
> conservative even by IETF standards is a bug in the Chrome 
> implementation. That issue belongs on discuss-webrtc@googlegroups.com. 
> It is not a specification matter.)
>
> If this is not clear enough:
>
> The ramp-up speed is OUT OF SCOPE FOR THE WORLD WIDE WEB CONSORTIUM.
>
>           Harald
>

     Done. Stefan helped me understand how to approach the topic at 
RMCAT, and I posted to Chrome-specific list about the second issue. 
Thank you for help.

Gili
Received on Tuesday, 17 September 2013 19:33:52 UTC

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