Re: [rtcweb] Summary of Signaling Components in RTCweb (clarifications)

A nice summary. I found a minor typo though.

>From the text "This documents tries to summarize all the signaling
components of a RTCweb communication ir order to identify each
"signaling fragment" in all the path ",

ir order to => in order to

On Fri, Oct 21, 2011 at 17:26, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> 2011/10/19 Iñaki Baz Castillo <ibc@aliax.net>:
>> Hi all,
>> I've tryed to identify all the signaling components of a RTCweb
>> communication ir order to identify each "signaling fragment" in all
>> the path. There are various connotations for the "signaling" keyword
>> in RTCweb and IMHO they are generating confusion.
>>
>> I've exposed it into the following URL:
>>
>>  http://public.aliax.net/RTCweb_Signaling_Components.html
>
> Hi, I've made some changes to the document:
>
> - Renamed "JS-Browser Media Signaling" to "JS-Browser Media API" (it's
> an API and could also be a "protocol", but let's call it just "API"
> for better understanding).
>
> - Renamed "JS-Server Information Signaling" to "JS-Server Routing
> Signaling". IMHO this is the correct word.
>
> - Added a new section "3. JS Application API" (which is provided by
> the custom JS retrieved from the webserver, which should hide the
> internal complexity to the high-user => example: Phono API).
>
>
>  http://public.aliax.net/RTCweb_Signaling_Components.html
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>