Re: [dispatch] X over websockets

Cullen Jennings <fluffy@iii.ca> Sat, 15 February 2014 23:29 UTC

Return-Path: <fluffy@iii.ca>
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 003241A016A for <dispatch@ietfa.amsl.com>; Sat, 15 Feb 2014 15:29:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level:
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, SPF_HELO_PASS=-0.001] 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 QpL05n1YY-dr for <dispatch@ietfa.amsl.com>; Sat, 15 Feb 2014 15:29:35 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 597691A01B4 for <dispatch@ietf.org>; Sat, 15 Feb 2014 15:29:35 -0800 (PST)
Received: from [10.66.246.94] (unknown [64.104.248.145]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F1E50509B5; Sat, 15 Feb 2014 18:29:30 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <52FD112B.5040209@alum.mit.edu>
Date: Sat, 15 Feb 2014 08:38:13 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F600D070-0BA7-418D-9F58-2E2FC9F29BBB@iii.ca>
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>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/N70-xPh6vyBC99p-OS6CKcmDvgA
Cc: DISPATCH <dispatch@ietf.org>
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: Sat, 15 Feb 2014 23:29:37 -0000

On Feb 14, 2014, at 5:38 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> Or for each X are we going to have a beauty contest between websockets and data channel?

Both is the reality of what IETF will probably end up doing 

> 
> Or what?

This really screams for a common framework that guides how to write a spec for X over web sockets or data channels.