Re: [rtcweb] revisiting MTI

[David Singer <[e-mail]>]

> On Dec 16, 2014, at 12:10 , Adam Roach <[e-mail]> wrote:
> 
> On 12/16/14 13:33, David Singer wrote:
>> Except I can’t find the text “non-browser” in the referenced document.
> 
> Huh. I see the following (cf. <https://tools.ietf.org/html/draft-ietf-rtcweb-overview-13#section-2.2>):

Ah, the document linked to -12, which is different. I just followed the links/references.

> 
>>    o  A WebRTC non-browser is something that conforms to the protocol
>>       specification, but does not claim to implement the Javascript API.
>>       This can also be called a "WebRTC device" or "WebRTC native
>>       application".
>> 
> 
> 
> In terms of the text you cited about the relationship between terms, which is an outdated version of:
>>    All WebRTC browsers are WebRTC endpoints, so any requirement on a
>>    WebRTC endpoint also applies to a WebRTC browser.
>> 
> 
> If you think you see somewhere that we're imposing a requirement on an endpoint that doesn't *also* apply to a browser, please call it out explicitly.

no, quite the reverse.  If all browsers are also devices, then we only need to state the requirements for browsers if they differ from devices, and they don’t, do they?

> 
> If this is some oblique attempt to complain about the reference to the -12 version of the overview document [1]  by pretending to be daft [2]: you're not fooling anyone, so you can stop it. You may be misguided, but we all know that you're not stupid.

seriously, I just (quickly) reviewed the text and references as cited as being the ones people are asking for consensus on.

David Singer
Manager, Software Standards, Apple Inc.