Re: [dispatch] X over websockets

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 14 February 2014 16:59 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380081A0300 for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 08:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 c-TnAV_-NGbr for <dispatch@ietfa.amsl.com>; Fri, 14 Feb 2014 08:59:36 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4FB1A012E for <dispatch@ietf.org>; Fri, 14 Feb 2014 08:59:35 -0800 (PST)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta13.westchester.pa.mail.comcast.net with comcast id SDGc1n0040Fqzac5DGzZ2n; Fri, 14 Feb 2014 16:59:33 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id SGzZ1n00Y3ZTu2S3UGzZHe; Fri, 14 Feb 2014 16:59:33 +0000
Message-ID: <52FE4B75.5040408@alum.mit.edu>
Date: Fri, 14 Feb 2014 11:59:33 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <20131213005747.777.34301.idtracker@ietfa.amsl.com> <CAHBDyN4tSRO_nYy7_-V4xfmDbF0ZeLJ24_fEOQ1p9Z2BvJyinQ@mail.gmail.com> <97B47463-42D2-4BA9-AC2F-DF8C67702DDC@cisco.com> <52FCE70C.1030608@gmail.com> <CAHBDyN7hySvbiJYnvRXDQ2ZS_FYFDMaODXBDRarE6DhRwC=fHQ@mail.gmail.com> <CA+ag07bPBHzODTWGKFrKE00nO_wiMgRv2GEwUpGCiH25-Xf2Cw@mail.gmail.com> <52FD112B.5040209@alum.mit.edu> <52FD2AE0.7060600@gmail.com> <CAHBDyN7nUrUDRCHT5HXfqroPD=5WPSE+yUvFhy4BLTdYTYm-Cg@mail.gmail.com>
In-Reply-To: <CAHBDyN7nUrUDRCHT5HXfqroPD=5WPSE+yUvFhy4BLTdYTYm-Cg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1392397173; bh=hwoM3naw/5v87yuOYwhw0DQpKNVHJlWtYYUG74grDos=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=gK4Kzv2qtsVs1CsV60lGO/xOTEow0WXVDnsieL1qJIwy8bi3p/mVk1M453MzQSlBP Ga3VZ/v+61TNA+Jnu8uufpkPTQk85aLVEUrBb7pgRLY8PUAVUD6NSna6KWlMRtBkBh 0SQ91OKfDv4traOWRFKXgB7B+bvFy0EqgvCaQLVmdrITcSUdxqHLtlJpc6jzc/aAUF zw/Qzcfhm11tvwQ0X9J1PClqL5ywz7UmzS4ybP1YxliyascNI1iW1CbEv9m4buTcVD QFewruIi1LyBV85fua7cIJeR5n5cDGTZVc2pTXeQlo/oHhPRzL30ql6GpiEPd4iX0o 6l4rZV7sZJ0RQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/qmtvRODu-AG4ltgGp3WoAItBq6s
Subject: Re: [dispatch] X over websockets
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 16:59:47 -0000

On 2/13/14 5:02 PM, Mary Barnes wrote:
> This topic has previously been raised (a year ago and periodically since
> then):
> http://www.ietf.org/mail-archive/web/dispatch/current/msg04693.html
>
> The suggestion was to have a "foo" over websocket discussion on the RAI
> list (which is really a lonely and largely ignored mailing list) but no
> one has taken that up:
> http://www.ietf.org/mail-archive/web/dispatch/current/msg04749.html
>
> Also, no one has put forth a concrete proposal to deal with it and we
> don't do work unless someones willing to put in the cycles.
>
> Thus, these work items have been trickling in (and out).  Since they are
> deemed useful in some contexts (and not harmful), they've been moving
> forward.  But, it certainly would be good for someone to put in some
> cycles to define a model and some guidelines for using websockets for
> any number of RAI protocols.

Mary,

I don't know how to distinguish what belongs on the RAI list vs. the 
dispatch list. But I have a perception that the dispatch list has a 
greater following.

	Thanks,
	Paul

> Mary.
>
>
> On Thu, Feb 13, 2014 at 2:28 PM, Sergio Garcia Murillo
> <sergio.garcia.murillo@gmail.com
> <mailto:sergio.garcia.murillo@gmail.com>> wrote:
>
>     El 13/02/2014 19:38, Paul Kyzivat escribió:
>
>         On 2/13/14 11:07 AM, Sergio Garcia Murillo wrote:
>
>             What I mean is that I expect quite a lot of "over
>             websocekts" drafts and
>             we should try to use the same solution for advertising it in
>             the SDP,
>             and not have each one have their own way of handling it.
>
>
>         Sigh. Yes, once we had the first of these, it was only a matter
>         of time before the flood began.
>
>         What concerns me is that for every "X over websockets" there is
>         probably also a good argument for "X over WebRTC Data Channel".
>
>         Are we going to let that happen?
>
>         Or for each X are we going to have a beauty contest between
>         websockets and data channel?
>
>         Or what?
>
>
>     Completely agree, we should try to "close" that discussion once and
>     for all and not have the same arguments and discussions in each
>     draft. I am not really aware of the IETF process, but could be
>     possible to create a draft to address it?
>
>     Best regards
>     Sergio
>
>
>     _________________________________________________
>     dispatch mailing list
>     dispatch@ietf.org <mailto:dispatch@ietf.org>
>     https://www.ietf.org/mailman/__listinfo/dispatch
>     <https://www.ietf.org/mailman/listinfo/dispatch>
>
>
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>