Re: [rtcweb] Friday Agenda: Re: Friday Call details for signaling discussion

Iñaki Baz Castillo <ibc@aliax.net> Thu, 20 October 2011 10:45 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 3368E21F8A71 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 03:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.626
X-Spam-Level:
X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=0.051, 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 2+7cnvV0ITXs for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 03:45:33 -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 6CD2321F8A70 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 03:45:33 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so2778541vcb.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 03:45:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.25.75 with SMTP id a11mr10207288vdg.1.1319107531657; Thu, 20 Oct 2011 03:45:31 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Thu, 20 Oct 2011 03:45:31 -0700 (PDT)
In-Reply-To: <4E9FD139.2010406@ericsson.com>
References: <CA+9kkMBQDne_p7LmH_e38NQWqjjNh0jKjuLMZrtNh10db90hYg@mail.gmail.com> <4E9E9794.8000901@alvestrand.no> <4E9FD139.2010406@ericsson.com>
Date: Thu, 20 Oct 2011 12:45:31 +0200
Message-ID: <CALiegfkbdXLf2E38i8ELSCsD6JOUJnWMasQuYK13BhzBwji2_Q@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Friday Agenda: Re: Friday Call details for signaling discussion
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 10:45:34 -0000

2011/10/20 Magnus Westerlund <magnus.westerlund@ericsson.com>;:
> The proposed agenda for Firday is as follows:
>
> 10 min introduction from each signaling proposal:
> - draft-jennings-rtcweb-signaling-00 (ROAP) Cullen
> - draft-partha-rtcweb-signaling-00 (Standard signaling protocol) Partha
> - ? (No Protocol) ?
>
> In the above only clarifying questions may occur.
>
> 20 min discussion of each proposal
>
> 30 min concluding discussion
>
> From my perspective both draft-beck-rtcweb-alt-ic-00 and
> draft-ibc-rtcweb-sip-websocket-00 are relevant documents to the
> discussion as they provides useful proposals on how interconnect and SIP
> interop respectively can be done. But as they aren't proposals for how
> the actual signaling solution should work. Thus these are homework but
> don't get presentation time.

Hi Magnus. Honestly I don't consider that discussing about
draft-ibc-rtcweb-sip-websocket-00 should take place. It's just a
suggestion about a signaling protocol in RTCweb (in this case pure SIP
over WebSocket). It's not my aim that the WG considers such spec as a
standard signaling for RTCweb. Well, this is basically the same you
have said :)

In the other said, I'd really would like that, before the meeting, all
the folks could take some time to read:

  http://public.aliax.net/RTCweb_Signaling_Components.html
and
  http://www.ietf.org/mail-archive/web/rtcweb/current/msg02158.html

This means not wasting time if somebody proposes ROAP as a "default
signaling protocol" because ROAP is not that and cannot do that (more
info in the given links). Also, given the general confusion when the
term "signaling" appears in this WG, I've tryied to clarify its
meaning(s) in RTCweb context (first link).

For those who advocate for a "default signaling protocol", I hope
second link should make them to re-think about what such erroneous
decision would entail in current and *existing* WWW world.


Best regards.



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