Re: [rtcweb] API draft: draft-kaplan-rtcweb-api-reqs-00

On Oct 21, 2011, at 7:40 AM, Harald Alvestrand wrote:

> On 10/21/2011 11:39 AM, Hadriel Kaplan wrote:
>> Howdy,
>> we've posted an initial strawman for "API requirements" for "no signaling" as our chairs have asked for for the con call.
>> I'm still not sure why we need to provide this in an I-D, but given only a few days notice and having other day jobs, we've tried our best in the short timeframe.
>> 
>> Note: given the announced conf call for Friday (today?), I've submitted this version without getting final proof-reading from the other authors.  So some new bits I wrote they may not agree with... in fact some bits I wrote *I* may not agree with, given how late it is at night for me (well I guess early in the morning technically).  Caveat emptor. :)
> Thank you, this document was most informative to me, and illustrated the position taken well (although I disagree with its conclusions).
> 
> It also served very nicely to illustrate the breadth of functionality that a "low level API" needs to expose.
> 
> One note (speaking as a W3C WG chair): While it's very nice to imagine that one can toss a task like "design an API" over to another organization and having it performed, in practice, the W3C functions much like the IETF; it's not a place where you throw work in order to get work done, it's a place where people who need the work done go to work on the problem.

And speaking as an editor in the W3C group to which you are referring, the point here is that protocol discussions are leading API discussions, and both are happening in the RTCWeb group, when the API discussions should all be happening in the W3C WebRTC group.  But, since JS API discussions are happening here, we now have a "no-signaling" draft in the IETF that lists requirements on the WebRTC API, *because the chairs asked for it*.

> 
> But we all knew that, I think....
> 
>> Link details below.
>> 
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> 
>> 	Title           : API Requirements for RTCWEB-enabled Browsers
>> 	Author(s)       : Hadriel Kaplan
>>                          Dan Burnett
>>                          Neil Stratford
>>                          Tim Panton
>> 	Filename        : draft-kaplan-rtcweb-api-reqs-00.txt
>> 	Pages           : 13
>> 	Date            : 2011-10-21
>> 
>>   This document discusses the advantages and disadvantages of several
>>   proposed approaches to what type of API and architectural model
>>   RTCWeb Browsers should expose and use.  The document then defines
>>   the requirements for an API that treats the Browser as a library and
>>   interface as opposed to a self-contained application agent.
>> 
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-kaplan-rtcweb-api-reqs-00.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-kaplan-rtcweb-api-reqs-00.txt
>> 
>> _______________________________________________
>> 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