IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Fri, 21 October 2011 08:26 UTC

Return-Path: <ibc@aliax.net>
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 6DC3021F8B0D for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 01:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 aWbrGmdTIqez for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 01:26:49 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B448321F8B10 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 01:26:49 -0700 (PDT)
Received: by vws5 with SMTP id 5so3267737vws.31 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 01:26:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.166 with SMTP id m6mr13550544vdv.18.1319185605712; Fri, 21 Oct 2011 01:26:45 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Fri, 21 Oct 2011 01:26:45 -0700 (PDT)
In-Reply-To: <CALiegfmQBEEX+6FuA3tujePh3HUyfCU5Wy3N_=cn_K_GXZ267g@mail.gmail.com>
References: <CALiegfmQBEEX+6FuA3tujePh3HUyfCU5Wy3N_=cn_K_GXZ267g@mail.gmail.com>
Date: Fri, 21 Oct 2011 10:26:45 +0200
Message-ID: <CALiegf=2Kv1CpS+EONbKZ01R8vvX2g1ofQ+Wgj5EEETr0vQK_g@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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 08:26:50 -0000

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>

v2.23.0 | Report a Bug | By Email