IETF Logo Mail Archive

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

Saúl Ibarra Corretgé <saul@ag-projects.com> Fri, 21 October 2011 09:12 UTC

Return-Path: <saul@ag-projects.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E423221F84DB for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 02:12:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ca1WDXFNP+Cn for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 02:12:06 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id EF52421F84DA for <rtcweb@ietf.org>; Fri, 21 Oct 2011 02:12:05 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id DB0AFB017D; Fri, 21 Oct 2011 11:11:59 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id E3B98B017D; Fri, 21 Oct 2011 11:11:58 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <CALiegf=2Kv1CpS+EONbKZ01R8vvX2g1ofQ+Wgj5EEETr0vQK_g@mail.gmail.com>
Date: Fri, 21 Oct 2011 11:11:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <837D51A3-BE0D-4BEA-98D4-D86BD460538C@ag-projects.com>
References: <CALiegfmQBEEX+6FuA3tujePh3HUyfCU5Wy3N_=cn_K_GXZ267g@mail.gmail.com> <CALiegf=2Kv1CpS+EONbKZ01R8vvX2g1ofQ+Wgj5EEETr0vQK_g@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of Signaling Components in RTCweb (clarifications)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2011 09:12:07 -0000

On Oct 21, 2011, at 10:26 AM, Iñaki Baz Castillo 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
> 

Sounds better now. Hopefully we can all now be on the same page when we discuss stuff about "signaling".

Thanks,

--
Saúl Ibarra Corretgé
AG Projects

v2.23.0 | Report a Bug | By Email