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

Re: New editor's draft (v20130603)

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Fri, 14 Jun 2013 08:31:31 +0200
Message-ID: <51BAB8C3.6030800@ericsson.com>
To: Randell Jesup <randell-ietf@jesup.org>
CC: public-webrtc@w3.org
On 2013-06-13 18:56, Randell Jesup wrote:
> On 6/5/2013 4:59 AM, Adam Bergkvist wrote:
>> On 2013-06-04 16:34, Randell Jesup wrote:
>>> One issue:   In RTCDataChannelInit:
>>>      boolean          negotiated
>>> <http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCDataChannelInit-negotiated>
>>> =true;
>>> The default should be false - it should be set to true on any
>>> externally-negotiated channel.
>> Oh, I interpreted preNegotiated (skipped the "pre" -> negotiated) as a
>> property on the channel that makes the user agent negotiate the
>> channel for you in-band. I.e., it's pre-negotiated (or just
>> negotiated) meaning that you (the developer) doesn't have to worry
>> about negotiation; the opposite of "externally-negotiated".
>> Should we use externallyNegotiated (default false) instead? That makes
>> sense on both sides.
> I pushed the naming change into FF 22 Beta 4 at the last second (write,
> review, land, approve to uplift, land in one day).  I can't
> realistically get any further non-major-failure fixes in for FF22, where
> we'll be exposing this by default.  Unless there's a driving reason, I'd
> like to avoid in-the-field changes where possible, though they are
> doable (but that would mean people trying to use this would need to do
> "negotiated: true, externally-negotiated: true" for as long as they
> wanted to support FF22).
> I'm ok with the name and description, so long as the default changes to
> 'false', which is what I implemented and landed.  We should just comment
> in the IDL file that this should be set to true if the application is
> using external negotiation.   I believe Peter Thatcher was also assuming
> the default would be false.

So I interpret what you're saying as that "negotiated" will be released 
in firefox, but with the opposite meaning from spec is saying currently 
(spec says "negotiated" != "externally negotiated"). I'm bit confused 
since you say that you're ok with the name and description.

Received on Friday, 14 June 2013 06:31:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:44 UTC