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

Peter Saint-Andre - &yet <peter@andyet.net> Wed, 03 December 2014 18:40 UTC

Return-Path: <peter@andyet.net>
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 D0ACC1A6F9A for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 F1TI0ml6kKs5 for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 10:40:14 -0800 (PST)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com [209.85.213.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7244C1A1AC3 for <rtcweb@ietf.org>; Wed, 3 Dec 2014 10:40:14 -0800 (PST)
Received: by mail-ig0-f179.google.com with SMTP id r2so13269176igi.6 for <rtcweb@ietf.org>; Wed, 03 Dec 2014 10:40:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PrRSIIuzkhEn330UjgBPKpVX3b0OYonrNW3OvSaK/O8=; b=PAFKLH08saHe6ghIlkggVbWFsVCclcyn4IHqzZ1Cw3tPe4ZV0mSerGACqrd6q4Q4m2 q6ZW7RkxueZCMhT/hoPnYYs+c7Z2d2/EgL8StqRpQkXNxrw02HMs7LQlsUOw1Fa52Tx2 AnpmOI7z6lPJtqKG1u38VIzsSCJmIC6Oj+lsFO8+GANvwVBejDR0dY+UI9/j8x5tSBXq EYJADPjlTkZVjSzUh6ueShfo4PXmQXmXUbkcQmuW6nHEp6hnygH5CJlyaF2jcsznr+Tu 4CjRUYFuG5gA6yyKBD8tyDfdw3+uX94eJXoP8AaiJ4OrcDOjVSntj0fPFSw3GReTbS3j RUwQ==
X-Gm-Message-State: ALoCoQlgs0enRD05ZDyXIsLmPQF24dm3SNjYT9oNJ/Bw4XYQtcWkSBOgRm1h8iHghwQrItbOxYGK
X-Received: by 10.107.13.12 with SMTP id 12mr6155896ion.68.1417632013885; Wed, 03 Dec 2014 10:40:13 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id g70sm13105145ioe.18.2014.12.03.10.40.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Dec 2014 10:40:13 -0800 (PST)
Message-ID: <547F590C.7010608@andyet.net>
Date: Wed, 03 Dec 2014 11:40:12 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Roman Shpount <roman@telurix.com>, ranjit@ranjitvoip.com
References: <6bef1cce67d1c9da7c29d8e0804f2551@ranjitvoip.com> <CAD5OKxs07wAu3V-x2gDnEmoAOEYL-X6njYmCTnfTBQB-YzD02w@mail.gmail.com>
In-Reply-To: <CAD5OKxs07wAu3V-x2gDnEmoAOEYL-X6njYmCTnfTBQB-YzD02w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/aBGB4KqWixWSGb7Vs1linouOF7s
Cc: "rtcweb@ietf.org" <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:40:16 -0000

On 12/3/14, 11:37 AM, Roman Shpount wrote:
> Is there any reason you cannot use SIP over WebSocket
> (https://tools.ietf.org/html/rfc7118)?

Or XMPP over WebSocket for that matter:

https://tools.ietf.org/html/rfc7395

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

Indeed.

> In other words,
> I think this is a very bad idea.

At the least, limited and irrelevant. :-)

Peter

-- 
Peter Saint-Andre
https://andyet.com/