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

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 20 October 2011 14:58 UTC

Return-Path: <magnus.westerlund@ericsson.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 E54ED21F8BBE for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.402
X-Spam-Level:
X-Spam-Status: No, score=-106.402 tagged_above=-999 required=5 tests=[AWL=-0.103, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 3bANdJIKOhAC for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:58:37 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id E4CA521F8B5D for <rtcweb@ietf.org>; Thu, 20 Oct 2011 07:58:36 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-16-4ea0371b0039
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B6.96.13753.B1730AE4; Thu, 20 Oct 2011 16:58:36 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.137.0; Thu, 20 Oct 2011 16:58:35 +0200
Message-ID: <4EA03717.10406@ericsson.com>
Date: Thu, 20 Oct 2011 16:58:31 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <CA+9kkMBQDne_p7LmH_e38NQWqjjNh0jKjuLMZrtNh10db90hYg@mail.gmail.com> <4E9E9794.8000901@alvestrand.no> <4E9FD139.2010406@ericsson.com> <CALiegfkbdXLf2E38i8ELSCsD6JOUJnWMasQuYK13BhzBwji2_Q@mail.gmail.com>
In-Reply-To: <CALiegfkbdXLf2E38i8ELSCsD6JOUJnWMasQuYK13BhzBwji2_Q@mail.gmail.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "rtcweb@ietf.org" <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 14:58:38 -0000

On 2011-10-20 12:45, Iñaki Baz Castillo wrote:
> 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 :)

Sorry if I wasn't clear enough. I don't intended that we would have any
discussion either of your draft. Only that it is useful background
material for the discussion.

The below links seems useful to have read also before yesterdays conference.

Cheers

Magnus

> 
> 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.
> 
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------