IETF Logo Mail Archive

Re: [hybi] Proposed way forward for WebSockets

"Thomson, Martin" <Martin.Thomson@andrew.com> Tue, 27 July 2010 08:26 UTC

Return-Path: <Martin.Thomson@andrew.com>
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 BB8E53A6A1F for <hybi@core3.amsl.com>; Tue, 27 Jul 2010 01:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.214
X-Spam-Level:
X-Spam-Status: No, score=-3.214 tagged_above=-999 required=5 tests=[AWL=-0.615, 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 qnv8Ic-sryA6 for <hybi@core3.amsl.com>; Tue, 27 Jul 2010 01:26:40 -0700 (PDT)
Received: from csmailgw1.commscope.com (csmailgw1.commscope.com [198.135.207.244]) by core3.amsl.com (Postfix) with ESMTP id 65A543A67F5 for <hybi@ietf.org>; Tue, 27 Jul 2010 01:26:40 -0700 (PDT)
Received: from [10.86.20.102] ([10.86.20.102]:2195 "EHLO ACDCE7HC1.commscope.com") by csmailgw1.commscope.com with ESMTP id S28672489Ab0G0I1C (ORCPT <rfc822; hybi@ietf.org>); Tue, 27 Jul 2010 03:27:02 -0500
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC1.commscope.com (10.86.20.102) with Microsoft SMTP Server (TLS) id 8.1.436.0; Tue, 27 Jul 2010 03:27:01 -0500
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Tue, 27 Jul 2010 16:26:59 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: gabriel montenegro <g_e_montenegro@yahoo.com>, Anne van Kesteren <annevk@opera.com>, Ian Hickson <ian@hixie.ch>, Maciej Stachowiak <mjs@apple.com>
Date: Tue, 27 Jul 2010 16:29:05 +0800
Thread-Topic: [hybi] Proposed way forward for WebSockets
Thread-Index: AcstZFTsTb1cMXgDRv6F6FH134/8AwAAUwRw
Message-ID: <8B0A9FCBB9832F43971E38010638454F03EB77373F@SISPE7MB1.commscope.com>
References: <ECF0E97F-1DA2-4662-BA48-F68B65AA8179@apple.com> <4C4D66AF.9030905@opera.com> <Pine.LNX.4.64.1007270030120.24444@ps20323.dreamhostps.com> <1C4FD851-5145-4283-B13D-1AFAFF293DD2@apple.com> <op.vghmvj1x64w2qv@annevk-t60> <44396.86745.qm@web82608.mail.mud.yahoo.com>
In-Reply-To: <44396.86745.qm@web82608.mail.mud.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw1.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Proposed way forward for WebSockets
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: Tue, 27 Jul 2010 08:26:41 -0000

There is such a mechanism:

  Upgrade: someotherprotocol

We might want to avoid this, but it's nice to know that the option is there.

> -----Original Message-----
> From: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] On Behalf Of
> gabriel montenegro
> Sent: Tuesday, 27 July 2010 10:18 AM
> To: Anne van Kesteren; Ian Hickson; Maciej Stachowiak
> Cc: hybi@ietf.org
> Subject: Re: [hybi] Proposed way forward for WebSockets
> 
> Phasing out development is good, but I agree with Greg about
> building in, from
> day one, some way to extend or add other features as the charter is
> clear that
> this is not just for browsers. Even though it is possible to define
> future
> headers or using the subprotocol mechanism to define or change behavior
> to one's
> satisfaction, what is not clear is what would be the status of those
> specs, nor
> what document or delivery vehicle would be used. That is fine for some
> functionality, but what the charter calls for is for the WG to produce
> a general
> protocol (not just for browsers) as part of the official WG
> document. So it's
> not enough to say that one could define future behavior, we have to
> define a
> complete protocol which in my mind implies binary support at least.
> 
> BTW, I like to look at the charter, as that is what guides the
> WG. There used to
> be a time when charters were
> nice, decorative items in the IETF. That changed already several years
> ago. Now
> the IESG approves charter for a reason.
> The IESG will hold the WG accountable for it.
> 
> Gabriel
> 
> ----- Original Message ----
> > From: Anne van Kesteren <annevk@opera.com>
> > To: Ian Hickson <ian@hixie.ch>; Maciej Stachowiak <mjs@apple.com>
> > Cc: hybi@ietf.org
> > Sent: Tue, July 27, 2010 7:58:36 AM
> > Subject: Re: [hybi] Proposed way forward for WebSockets
> >
> > On Tue, 27 Jul 2010 03:00:08 +0200, Maciej Stachowiak <mjs@apple.com>
> wrote:
> > > Ian's suggested timeline below sounds like an excellent way to
> proceed, in my
> >opinion.
> >
> > +1
> >
> >
> > --Anne van Kesteren
> > http://annevankesteren.nl/
> > _______________________________________________
> > hybi mailing list
> > hybi@ietf.org
> > https://www.ietf.org/mailman/listinfo/hybi
> >
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

v2.23.0 | Report a Bug | By Email