Re: [hybi] New mailing list: hybi (HTTP "long poll" and related protocols)

Mark Nottingham <mnot@mnot.net> Mon, 30 March 2009 20:00 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D967828C0E7 for <hybi@core3.amsl.com>; Mon, 30 Mar 2009 13:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.843
X-Spam-Level:
X-Spam-Status: No, score=-4.843 tagged_above=-999 required=5 tests=[AWL=-2.244, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M+40HCnacVZE for <hybi@core3.amsl.com>; Mon, 30 Mar 2009 13:00:43 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 98C5D3A6846 for <hybi@ietf.org>; Mon, 30 Mar 2009 13:00:43 -0700 (PDT)
Received: from [192.168.1.1] (unknown [209.131.62.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CA4D1D051E; Mon, 30 Mar 2009 16:01:39 -0400 (EDT)
Message-Id: <36F0A3E3-5476-4C58-854D-1AB40190D497@mnot.net>
From: Mark Nottingham <mnot@mnot.net>
To: Ian Hickson <ian@hixie.ch>
In-Reply-To: <Pine.LNX.4.62.0903301933210.25058@hixie.dreamhostps.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 31 Mar 2009 07:01:36 +1100
References: <67830A60-4ACD-4646-9C46-9B168E7D305A@mnot.net> <Pine.LNX.4.62.0903301933210.25058@hixie.dreamhostps.com>
X-Mailer: Apple Mail (2.930.3)
Cc: hybi@ietf.org
Subject: Re: [hybi] New mailing list: hybi (HTTP "long poll" and related protocols)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2009 20:00:44 -0000

On 31/03/2009, at 6:41 AM, Ian Hickson wrote:

> On Tue, 31 Mar 2009, Mark Nottingham wrote:
>>
>> As discussed in the APPS area meeting last week, a new mailing list  
>> has
>> been created to discuss the standards implications and actions  
>> related
>> to HTTP "long poll" techniques (e.g., COMET, BOSH) as well as new
>> protocols that serve similar use cases (e.g., WebSockets, rHTTP).
>
> Thanks!
>
> I notice the description of the list is "Server-Initiated HTTP",  
> while at
> least some of the techniques proposed, in particular Web Socket, are  
> only
> tangentially related to HTTP (WebSocket is a client-initiated Web- 
> aware
> bidirectional socket, it's not server-initiated and the HTTP aspect is
> just an optional bootstrapping mechanism). Is the scope intended to
> include or exclude long-term discussion of such solutions?

Ah, the original name of the list was si-http; that's a bit of a  
leftover from that discussion. The scope is definitely to include such  
discussions, at least until we figure out otherwise.


> Also, what is the process by which discussion on this list can  
> result in a
> standards-track document? Browser vendors have started asking me about
> implementing WebSocket or whatever replaces it, so a clear picture  
> of how
> we get to something stable sooner rather than later would be very  
> helpful.
> (It is an unfortunate reality that once we have multiple  
> implementations
> of a feature, the spec becomes stable by necessity, regardless of  
> whether
> we have had the proper time to review it or not.)


Either something being an individual submission, or by a Working Group  
forming.

AIUI the bar is relatively high for individual submission standards- 
track documents these days; i.e., if there are contentious issues,  
it's likely that it'll need a WG.


--
Mark Nottingham     http://www.mnot.net/