Re: [rtcweb] Review request for RTCWeb standard signaling protocol

Iñaki Baz Castillo <ibc@aliax.net> Sat, 08 October 2011 16:34 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 6A79B21F8B53 for <rtcweb@ietfa.amsl.com>; Sat, 8 Oct 2011 09:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[AWL=0.045, 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 ukGfDVhuRF1s for <rtcweb@ietfa.amsl.com>; Sat, 8 Oct 2011 09:34:35 -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 D5F8D21F8906 for <rtcweb@ietf.org>; Sat, 8 Oct 2011 09:34:34 -0700 (PDT)
Received: by vws5 with SMTP id 5so4710639vws.31 for <rtcweb@ietf.org>; Sat, 08 Oct 2011 09:37:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.35.34 with SMTP id e2mr7130000vdj.52.1318091871171; Sat, 08 Oct 2011 09:37:51 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Sat, 8 Oct 2011 09:37:51 -0700 (PDT)
In-Reply-To: <CABRok6kd+QavT0ThBtHhygiscvs8OxtWwd2Zo_7+GcgYZW9eww@mail.gmail.com>
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com> <4E8AC222.4050308@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com> <CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com> <393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com> <CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com> <CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com> <CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com> <91986BEB-B85F-483D-A1DA-46236B2592D9@ag-projects.com> <CABRok6kd+QavT0ThBtHhygiscvs8OxtWwd2Zo_7+GcgYZW9eww@mail.gmail.com>
Date: Sat, 08 Oct 2011 18:37:51 +0200
Message-ID: <CALiegfnY98Rg3MPpgz0Dom7HZ1wVaDrhHKm+WFtrHcpGe+QbWw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Neil Stratford <neils@belltower.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Sat, 08 Oct 2011 16:34:35 -0000

2011/10/8 Neil Stratford <neils@belltower.co.uk>:
> The great thing about *not* defining a signalling protocol is that we are
> free to experiment with signalling in all kinds of ways.

Agreed. Defining a default/mandatory signaling protocol would limit
future scenarios. We don't know yet what RTCweb will be used for.
Signaling should depend on the needs of each service bringing media
capabilities, and that is achieved by providing the signaling within a
custom JavaScript code.

Anyhow I expect I will read again (probably in any other thread) the
same mail speaking about "the need for a default signaling protocol,
as H323 or MEGACO", by ignoring any rationale given in this and other
mails but most of the people in this maillist. I should make some SPAM
filtering rule.

Regards.

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