Re: [rtcweb] RTCweb signalling overview

"Olle E. Johansson" <oej@edvina.net> Fri, 09 September 2011 13:22 UTC

Return-Path: <oej@edvina.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 00E9021F8997 for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 06:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 lh1outllXta7 for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 06:22:30 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF4D21F8591 for <rtcweb@ietf.org>; Fri, 9 Sep 2011 06:22:30 -0700 (PDT)
Received: from [IPv6:2001:470:1f15:d79:1426:b5c4:b598:4131] (unknown [IPv6:2001:470:1f15:d79:1426:b5c4:b598:4131]) by smtp7.webway.se (Postfix) with ESMTPA id C59F0754BCE4; Fri, 9 Sep 2011 13:24:21 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=windows-1252
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE220BA3C91@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Fri, 9 Sep 2011 15:24:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <59F2188C-109B-4FDF-AAF0-6F90849F2F7F@edvina.net>
References: <E2827B1C-5706-41D0-8D96-D342C25901D1@edvina.net> <4E69BF72.5060908@alvestrand.no> <EDC0A1AE77C57744B664A310A0B23AE220BA3C91@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCweb signalling overview
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, 09 Sep 2011 13:22:31 -0000

9 sep 2011 kl. 15:08 skrev DRAGE, Keith (Keith):

> With respect to question 3 in this set.
>  
> As I said on the call, the requirements for what needs to be standardised between the two web servers depends on whether web server A needs to know anything about user B, and whether web server B needs to know anything about user A. I believe this goes beyond SDP, because it may need to be information beyond the media contents, e.g. it may need to include information about each user’s capabilities and preferences.
>  
> I actually have two slightly inconsistent views about this interface.
How good it feels to not be alone and confused :-)

>  
> Yes it does need to be standardised. I don’t like the idea of fragmentation being forced on the market because an appropriate standardised solution has not been identified.
Exactly.
>  
> No RTCWEB should not standardise it because it is out of scope of RTCWEB.
Yes, agree.

>  
> Surely this is also the interface by which support of interworking with legacy systems has to be attained?
Well, if the app developer wants to interface legacy systems. The important thing for rtcweb is to understand whether access to legacy systems affects the rtcweb architecture if the signalling is removed from scope.

>  
> Perhaps the easiest way out is to identify that full blow SIP is a solution for this specific interface, and RTCWEB identifies to SIPCORE as to whether there are any additional requirements that SIP cannot meet.
In addition, I see XMPP to be a solution for that specific interface too... 

/O
>  
> Regards
>  
> Keith
>  
>  
>  
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Harald Alvestrand
> Sent: 09 September 2011 08:26
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] RTCweb signalling overview
>  
> On 09/08/11 20:48, Olle E. Johansson wrote:
> For those of you that did not participate in today's meeting, there was an excellent overview presented by Martin Kaufman.
>  
> It gives you an overview over the issues with signalling - to sip or not to sip - and other issues. Do read it.
>  
> Use the file rtcweb-3.pptx in http://www.ietf.org/proceedings/82/slides/
> 
> Seconded.
> I liked the presentation even though I don't agree with the conclusions (I prefer Cullen's set).
> 
> 
>  
> /O
>  
>  
>  
>  
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>  
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

---
* Olle E Johansson - oej@edvina.net
* Cell phone +46 70 593 68 51, Office +46 8 96 40 20, Sweden