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

[Harald Alvestrand <[e-mail]>]

I've read the draft.

I note a lot of stuff that (if it has the consensus of the WG) should 
really be part of the -overview- draft, and the subsequent debate has 
indicated that it seems they are reasonably close to WG consensus. I'll 
try to incorporate these things in the -overview- revision.

There is some terminology I don't think I want to adopt, but we'll see 
once the revision gets out.
It's unlikely that such a revision occurs before Taipei (not that much 
time left this week, and discussions in Taipei may also influence 
-overview-), but it's my intent to do so.

Apologies for not (so far) sending a detailed review.

One query: Who is this -sipdoc- person? It seems to be the name of none 
of the authors, but since it got past the I-D submission machinery, it 
is presumably an author ID.

See http://www.ietf.org/id-info/guidelines.html#naming

                   Harald


On 10/27/2011 01:55 AM, 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.
>
>