IETF Logo Mail Archive

Re: [rtcweb] Why are we asking the wrong questions?

Iñaki Baz Castillo <ibc@aliax.net> Thu, 20 October 2011 20:09 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 20BC71F0C61 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 13:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.635
X-Spam-Level:
X-Spam-Status: No, score=-2.635 tagged_above=-999 required=5 tests=[AWL=0.042, 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 SwJosVNdKy+Q for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 13:09:27 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B36731F0C34 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 13:09:27 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3388853vcb.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 13:09:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.25.75 with SMTP id a11mr11993290vdg.1.1319141365891; Thu, 20 Oct 2011 13:09:25 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Thu, 20 Oct 2011 13:09:25 -0700 (PDT)
In-Reply-To: <CAD5OKxtS8u5H0nq4vq6=OV7J157=SrHRVs6PyJOZyyL_AqeR1g@mail.gmail.com>
References: <CAD5OKxvBMt_EDzPprGeFGGTPS0z3DXAz9YJPDqCwF6HKuPrpFg@mail.gmail.com> <CA+9kkMB_t6g9oh0zxtYDgOkJ3+smjW7GCCS05M9werbGS_kLYg@mail.gmail.com> <CAD5OKxtS8u5H0nq4vq6=OV7J157=SrHRVs6PyJOZyyL_AqeR1g@mail.gmail.com>
Date: Thu, 20 Oct 2011 22:09:25 +0200
Message-ID: <CALiegf=oEm1v3SSDDG=gxX1WSZ0-h_HmQ9BK1Vmyt_xbzjNDkw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Why are we asking the wrong questions?
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: Thu, 20 Oct 2011 20:09:29 -0000

2011/10/20 Roman Shpount <roman@telurix.com>:
> Standard signaling protocol is a convenience feature for RTC. It is heavily
> dependent on the matching server component. It replicates functionality that
> is already available and requirements for it are unclear.

Hi Roman, could you please check this short document and specify which
"signaling protocol" (of the three appearing in the document) you
mean?:

  http://dev.sipdoc.net/projects/oversip/wiki/RTCweb_Signaling_Components

Thanks a lot.

PS: I suggest all the WG to avoid the term "TRCweb signaling protocol"
because it's confussing given the different fragments of RTCweb in
which something related to "signaling" exists.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email