Re: [rtcweb] draft-sipdoc-rtcweb-open-wire-protocol-00 (Open In-The-Wire Protocol for RTC-Web)

[Tim Panton <[e-mail]>]

On 27 Oct 2011, at 02:55, Iñaki Baz Castillo wrote:

> 2011/10/25 Iñaki Baz Castillo <[e-mail]>:
>> A new I-D draft-sipdoc-rtcweb-open-wire-protocol-00.txt has been
>> successfully submitted by Iñaki Baz Castillo,  Saúl Ibarra Corretgé
>> and José Luis Millán Villegas, and posted to the IETF repository.
>> 
>> Filename:        draft-sipdoc-rtcweb-open-wire-protocolRevision:
>>  00Title:           Open In-The-Wire Protocol for RTC-WebCreation
>> date:   2011-10-25WG ID:           Individual SubmissionNumber of
>> pages: 22
>> 
>> 
>> http://tools.ietf.org/html/draft-sipdoc-rtcweb-open-wire-protocol-00
>> http://www.ietf.org/id/draft-sipdoc-rtcweb-open-wire-protocol-00.txt
>> 
>> 
>> Abstract:  RTC-Web clients communicate with a server in order to
>> request or  manage realtime communications with other users.  This
>> document  exposes four hypothetical and different RTC-Web scenarios
>> and  analyzes the requirements of the in-the-wire protocol in each of
>> them.
>>   The aim of this document is to make RTC-Web properly fit in the
>> nature of the Web.
> 
> 
> Hi, just wondering if somebody has read this informational draft. I'd
> would really appreciate if folks agree with the conclusiones and
> requirements exposed in the document or want to discuss about them.
> The draft tries to clarify the scope of RTC-Web, and IMHO that's an
> important milestone before we can move on.
> 
> Thanks a lot.

Thank you for writing this up - before I had to ;-)
I agree with almost all of it, but I wonder if you could add a derived requirement:
"  4.  It MUST be possible for a website developer to make his RTC-Web
       scenario to interoperate with a pure SIP or XMPP/Jingle network
       without requiring a signaling protocol gateway (by using SIP over
       WebSocket [I-D.ibc-rtcweb-sip-websocket] or XMPP over WebSocket
       [I-D.moffitt-xmpp-over-websocket]).
  5. It must be possible for a website developer to make his RTC-Web
       scenario to interoperate without adding new infrastructure unless they wish to
       interop with the wider world - i.e. if the 
       mysite.com example wished to operate as an 'island' they
       would not need to add additional telephony or expertise 
       servers, as all the neccessary server side work could be done in php
       by his existing web programmers.  "

I think this is implied by your document, but I feel it is critically important 
so worth explicitly stating it. 

Tim.