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

Ted Hardie <ted.ietf@gmail.com> Wed, 03 December 2014 20:54 UTC

Return-Path: <ted.ietf@gmail.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 54FD61AC3D0 for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 12:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 MwtD385r288n for <rtcweb@ietfa.amsl.com>; Wed, 3 Dec 2014 12:54:32 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64A611A89EB for <rtcweb@ietf.org>; Wed, 3 Dec 2014 12:54:32 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so14605357ier.32 for <rtcweb@ietf.org>; Wed, 03 Dec 2014 12:54:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s770z3WqXAxwllRBf2CBJWVm7TL01QeBydvKE2Xtcbg=; b=HMGfxpqjOdN7u4CA6CDzD4rWZk5YkJv5PAMePOxovyXL1W2KrtNn8oyX4WADPUG8jg d4sSIir+5Xv6HtbCCM4j8MSOnt+E5JirIQLJ3UvGtWDw5iPhnkhTUeblgw3hcrk/6w6j cLrqmya0rQlzOKCDSdG0NSgElIhplq/SxI0U98PBFR1+um6ZGX6Zk0NOjS//0r9bzs3p GOPOQ0WBvGBxm5CtOYPQna+4rVeRuL/gT7rV3ggAsY3tP+esVZ6+NCxMvLKaOnhqFW96 PAHhYi+mjtKQ3KsANBkYXrqP1E2krN6Ini3L3bpdUxTGzWJVlzf1L2krE/qfD9+38asK SF4Q==
MIME-Version: 1.0
X-Received: by 10.42.194.17 with SMTP id dw17mr8807934icb.4.1417640071403; Wed, 03 Dec 2014 12:54:31 -0800 (PST)
Received: by 10.43.3.4 with HTTP; Wed, 3 Dec 2014 12:54:31 -0800 (PST)
In-Reply-To: <6bef1cce67d1c9da7c29d8e0804f2551@ranjitvoip.com>
References: <6bef1cce67d1c9da7c29d8e0804f2551@ranjitvoip.com>
Date: Wed, 3 Dec 2014 12:54:31 -0800
Message-ID: <CA+9kkMCzMHrTQwLn_WHfhTbF2Kx4V-6-pau-X5Q3N4O1WGk-_Q@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: ranjit@ranjitvoip.com
Content-Type: multipart/alternative; boundary=20cf30434a7ce01de90509560cf9
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/OSWpNkMeN72wAGh-ZoMz1sCJN5Y
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 20:54:38 -0000

Hi Ranjit,

On Wed, Dec 3, 2014 at 10:31 AM, <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
>
>
​If I understand your proposal correctly, I believe it is currently out of
scope for the working group.  If I understand
the minimally necessary item, it is to define a websocket sub-protocol
"jsep" so that gateways can use this token to indicate the appropriate
handling.   At least to my reading, this work is outside of our current
charter.

I'd suggest you start by approaching the area directors for pointers on
where the work might take place.

regards,

Ted




> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>