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

ranjit@ranjitvoip.com Wed, 03 December 2014 18:32 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 5AC011A8F40 for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.91
X-Spam-Status: No, score=0.91 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id pyAgnwoEwLp3 for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:32:39 -0800 (PST)
Received: from hs8.name.com (hs8.name.com []) (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 804851A8F4A for <rtcweb@ietf.org>; Wed, 3 Dec 2014 10:32:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ranjitvoip.com; s=default; h=Message-ID:Subject:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=yEZLcfVgQfCOXJmTK9UAxfbn3Vfkv9W7DonRjb0BIRw=; b=mMIFXPz6MTJFt2jypeDZ/+s47AnDYwTCB8uBeKXI4mk56m60t1XakglOaFQelfYmI7g11dmpF1tYeH+FkZF8XIjdhwpNjhp8IawnJRp6EFV5wT/5l1Js/Sy3jbXxvtii3wSYRdCKsM5cqOGZ12bhb496o054J0wkTtjBXejdSQM=;
Received: from localhost.localdomain ([]:35757 helo=webmail.ranjitvoip.com) by hs8.name.com with esmtpa (Exim 4.84) (envelope-from <ranjit@ranjitvoip.com>) id 1XwEiV-004KqV-QI for rtcweb@ietf.org; Wed, 03 Dec 2014 12:31:59 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 03 Dec 2014 12:31:59 -0600
From: ranjit@ranjitvoip.com
To: rtcweb@ietf.org
Message-ID: <6bef1cce67d1c9da7c29d8e0804f2551@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/lbI1SrIMokfIFDHRxYYlSVFvfQM
Subject: [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:32:40 -0000

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.