Re: [rtcweb] Interest and need for Websocket subprotocol - JSEP over websockets

ranjit@ranjitvoip.com Wed, 03 December 2014 18:57 UTC

Return-Path: <ranjit@ranjitvoip.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD561A9091 for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.39
X-Spam-Level:
X-Spam-Status: No, score=-0.39 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2RwUA9A1NJG for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:57:37 -0800 (PST)
Received: from hs8.name.com (hs8.name.com [173.193.131.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FB481A90B9 for <rtcweb@ietf.org>; Wed, 3 Dec 2014 10:57:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ranjitvoip.com; s=default; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=NmFa/nXpoPiYLj2YhUNf67fZrCCGEolNiKs3sks+GAw=; b=KWGRlB7TXcZP/XRBpxCzt93PkHj95sTTrDN6+WLT3hhz3uUBs8bxgdIqCJ5YQtiCFu8zPkLxFAmAvR7Pjkf0stkTq0VXoy3NxcWfXOfxOOh/mhwdS2v6IUcLzNVIkxBveUCQVOSwSyUXlbcWjtOBw3KdXyaALN11bySxG9IGm0Y=;
Received: from localhost.localdomain ([127.0.0.1]:38691 helo=webmail.ranjitvoip.com) by hs8.name.com with esmtpa (Exim 4.84) (envelope-from <ranjit@ranjitvoip.com>) id 1XwF6x-0003Fo-Ex; Wed, 03 Dec 2014 12:57:15 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 03 Dec 2014 12:57:15 -0600
From: ranjit@ranjitvoip.com
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E64BCAB@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <6bef1cce67d1c9da7c29d8e0804f2551@ranjitvoip.com> <CAD5OKxs07wAu3V-x2gDnEmoAOEYL-X6njYmCTnfTBQB-YzD02w@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E64BCAB@US70UWXCHMBA02.zam.alcatel-lucent.com>
Message-ID: <554d17d3779404eed3868ae587510e2f@ranjitvoip.com>
X-Sender: ranjit@ranjitvoip.com
User-Agent: Roundcube Webmail/1.0.1
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - hs8.name.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ranjitvoip.com
X-Get-Message-Sender-Via: hs8.name.com: authenticated_id: ranjit@ranjitvoip.com
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/V3082tZZXwjaa9v6WuvfBUh3wy4
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Interest and need for Websocket subprotocol - JSEP over websockets
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 03 Dec 2014 18:57:38 -0000

Hello all

While I agree SIP over Websockets is default signaling protocol for 
WebRTC while working with IMS, there could be scenarios where WebRTC 
calls can get initiated from non SIP UAs like web browsers which do not 
support SIP. Then in such cases, the following things could happen
1) the WebRTC client on the browser can use JSEP to send its signaling 
information over WebSocket,
2) the JSEP message would then land on the WebRTC GW over WS.
3) This JSEP message would then be converted to a SIP message and then 
sent to IMS core.
4) within IMS core, its a regular SIP message
5) Again in the reverse direction, WebRTC GW would convert SIP to JSEP
6) JSEP message is sent over Websocket to UE.

now we see JSEP messages getting exchanged over Websockets. so if the 
websocket sub-protocol does not define the type as "jsep", then the 
WebRTC GW would not know the incoming message type and hence may discard 
it or its behavior may be uncertain.

Also the JSEP message needs to be enhanced to add more message types 
(along with current OFFER / ANSWER) to be able to map it with standard 
signaling protocol like SIP as defined in 
https://tools.ietf.org/html/draft-partha-rtcweb-jsep-sip-01

Regards
Ranjit

On 2014-12-03 12:40 pm, Makaraju, Maridi Raju (Raju) wrote:
> + 1 for using SIP over WebSocket.
> 
> FROM: rtcweb [mailto:rtcweb-bounces@ietf.org] ON BEHALF OF Roman
> Shpount
>  SENT: Wednesday, December 03, 2014 12:38 PM
>  TO: ranjit@ranjitvoip.com
>  CC: rtcweb@ietf.org
>  SUBJECT: Re: [rtcweb] Interest and need for Websocket subprotocol -
> JSEP over websockets
> 
> Is there any reason you cannot use SIP over WebSocket
> (https://tools.ietf.org/html/rfc7118 [1])?
> 
> Call signaling will require a lot more information then what is
> provided in JSEP. JSEP mostly deals with offer and answer processing.
> Signaling will also need to deal with things like who is calling, why
> they are calling, transfers, other application specific details. In
> other words, I think this is a very bad idea.
> 
> _____________
>  Roman Shpount
> 
> On Wed, Dec 3, 2014 at 1:31 PM, <ranjit@ranjitvoip.com> wrote:
> 
> Hi
>  With websockets as a de-facto transport protocol for WebRTC signaling
> and JSEP being the format of encoding information, there is a need for
> a defining a websocket sub-protocol : jsep. So I would like to know if
> there is any interest in the community and also the views from experts
> about the need for a websocket-sub protocol for JSEP.
> 
>  The main purpose of defining the sub protocol (jsep) is to make sure
> that the WebRTC client (WIC) and WebRTC server (E-CSCF) are receiving
> JSEP encoded messages.
> 
>  Thanks
>  Ranjit
> 
>  _______________________________________________
>  rtcweb mailing list
>  rtcweb@ietf.org
>  https://www.ietf.org/mailman/listinfo/rtcweb [2]
> 
> 
> 
> Links:
> ------
> [1] https://tools.ietf.org/html/rfc7118
> [2] https://www.ietf.org/mailman/listinfo/rtcweb